Hi Kevin,

Thanks for your post. I fully understand your situation when you tried to publish a calendar in OWA. It was coming from OWA interface can't get a properly response from Exchange Online service or Office365 AD back-end service. (could be related to service maintenance or user's profile corruption). However, as a walk-around solution to publish a calendar in Powershell, you can do the following steps:.

1, connect Exchange online via Powershell (what you have done)
2,Set-MailboxCalendarFolder -Identity mailbox-alias:\calendar -PublishEnabled $true  (replace mailbox-alias as your user's alias)
3,Get-MailboxCalendarFolder -Identity mailbox-alias:\calendar (use the information from PublishedCalendarUrl as the publish URL address)

Thanks, Neo Zhu

Neo -

I was able to do that however I may have a subsequent issue.  The links that the GetMailboxCalendarFoler provided are as follows however both take me to a login page.  The rule I created was a public free/busy calendar so there should not be a need to see a login prompt (especially an Office 365 login).  

mail02.bluecloudhosts.com/.../calendar.html

mail02.bluecloudhosts.com/.../calendar.ics

I am wondering if I have my DNS setup improperly?  We are aliasing mail02.bluecloudhosts.com to ch1prd0610.outlook.com in DNS (we have DNS hosted elsewhere).  Is that correct?

Hi Kevin,

Thanks for your reply. DNS will not cause this issue. As for this case, could be related to the sharing policy. Could you export all your sharing policy out?

"get-shareingpolicy"  detail information "Get-SharingPolicy -Identity "Default Sharing Policy" |fl"

On the other hand, you can publish other user's calendar with OWA UI and see what's going on.

Thanks, Neo Zhu

Here is the output from the sharing policy:

ModuleType Name                      ExportedCommands

---------- ----                      ----------------

Script     tmp_1e33feae-f16a-4e7c... {Start-ProvisioningRequest, Set-MailboxAutoReplyConfiguration, Set-PopSu...

PS C:\Users\kevin.justice.BCH-MD1> Get-SharingPolicy -Identity "Default Sharing Policy" |fl

RunspaceId        : e9ef4270-52d4-475e-af73-b3cdc17b9773

Domains           : {Anonymous:CalendarSharingFreeBusyReviewer, *:CalendarSharingFreeBusySimple}

Enabled           : True

Default           : True

AdminDisplayName  :

ExchangeVersion   : 0.10 (14.0.100.0)

Name              : Default Sharing Policy

DistinguishedName : CN=Default Sharing Policy,CN=Federation,CN=Configuration,CN=matice.onmicrosoft.com,CN=Configuration

                   Units,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=namprd06,DC=prod,DC=outlook,DC=com

Identity          : Default Sharing Policy

Guid              : 0844526d-2711-44f7-9c1a-fc67d4781c6b

ObjectCategory    : namprd06.prod.outlook.com/Configuration/Schema/ms-Exch-Sharing-Policy

ObjectClass       : {top, msExchSharingPolicy}

WhenChanged       : 3/14/2012 2:27:41 PM

WhenCreated       : 3/14/2012 2:27:41 PM

WhenChangedUTC    : 3/14/2012 6:27:41 PM

WhenCreatedUTC    : 3/14/2012 6:27:41 PM

OrganizationId    : namprd06.prod.outlook.com/Microsoft Exchange Hosted Organizations/matice.onmicrosoft.com - namprd06

                   .prod.outlook.com/Configuration/Services/Microsoft Exchange/ConfigurationUnits/matice.onmicrosoft.c

                   om/Configuration

OriginatingServer : BL2PRD0610DC002.namprd06.prod.outlook.com

IsValid           : True

I posted what was requested.  Please advise.

Hi Kevin,

I have checked the detailed information of your sharing policy, and haven't found any incorrect settings about it. My suggestion is to re-publish the calendar in OWA. Please see Calendar Publishing.

Thanks,
Reken Liu

I reshared the calendar and in the email, there is a link to the calendar.html page and it takes me to a login screen.  I've I've given rights to allow anyone to see my free/busy info, why would the person need to login (which they can't anyway).

The link it provided is:

mail02.bluecloudhosts.com/.../calendar.html

Hi Kevin,

I have just published my calendar to the internet, and compared my link with the link you provided. I noticed that there are something differences in the format. I list the two links here for your reference:

Your calendar publish url:

http://mail02.bluecloudhosts.com/owa/calendar/80f5f1a356474c80a3a0ac326fbf7404@maticeinteractive.com/8ccf1f7fdeaa48a2a99e06a42164324a17383724564818773825/calendar.html

My calendar publish url:

http://myservername/owa/calendar/myalias@maticeinteractive.com/mypublishedcalendarname/calendar.html

Based on the situation, would you please edit the url by replacing the complex strings in the url with your alias, and the calendar name you are publishing? After that, please try to access it to see if it can be accessed without login.

Thanks,
Reken Liu

I was able to get this working but there is still an underlying problem.  To get it working I went into OWA and clicked calendar/share/changepublishingsettings.  When I did this I got the following error:

The input object cannot be bound to any parameters for the command either because the command does not take pipeline input or the input and its properties do not match any of the parameters that take pipeline input.

I noticed the url of that page is this:

bl2prd0610.outlook.com/.../calendarpublishing.slab

So I changed the url to this:

bl2prd0610.outlook.com/.../calendarpublishing.slab\calendar&pspid=_1332854304838_17353588

and the page came up correctly.   Once there I noticed that the access level was "restricted" so I changed it to public and hit save.  When it refreshed, it changed the urls from this:

mail02.bluecloudhosts.com/.../calendar.html

to this:

ch1prd0610.outlook.com/.../calendar.html

And unbelievably that works.  

HOWEVER, the deeper problem is that the links in OWA for some functions still don't work (like Calendar/Share/Change Sharing Permission and Calendar/Share/ChangePublishingSettings).  What is wrong with my system that is causing it to not properly create URL's in the OWA?

Hello Kevin,

If you are publishing the calendar to the Internet, if you choose "restricted" it should not affect the person trying to view it.  If they have the URL it generates, they will be able to access the calendar and will not be prompted.  You can use DNS CNAMEs to redirect users to the link, but they should not be prompted, regardless of DNS setting or whether CNAME records are used. 

If you are sharing the calendar internally, then users should be prompted for credentials, but this is a different issue entirely and should have a new case opened for it, if there are any problems.