Shared Exchange Calendars on iOS devices

Just a quick post on how to view an Exchange 2010 shared calendar/mailbox on your iPhone or iPad…

Once you’ve (or your admin has) configured Exchange to allow iCal publishing, you can then send links via email from the shared calendar mailbox itself:


On the iOS device, you can then click the webcal: link in the email, which will allow you to subscribe to the Calendar:



29 thoughts on “Shared Exchange Calendars on iOS devices

  1. Maybe I’m missing something, but this method isn’t an option on the Mac (Outlook for Mac 15.6). If I right-click on a calendar, there isn’t an option to publish a calendar (only Properties & Sharing Permissions). I also don’t see that option in OWA (Firefox 36.0.1).

    Frankly, dealing with shared/delegate calendars is a low-grade nightmare on the Mac.

    I’ll have to see if I can publish it from Outlook 2013.

  2. Pingback: Mailbox App Exchange Ios | Free Documents App

  3. Can you share a calendar on the Exchange 2007 and access it via iDevices

    I mean, same as you have mentioned on your blog, but on 2007 eXchange server. Do they have that facility. Or is there another way?

    Many thanks in advance

  4. Steve… I was able to publish calendar on Internet (but I have to replace HTTP:// as https://) but When I try to subscribe to calendar on iPhone or iPad its not working. Any thoughts?

    To me it looks like that because we are redirecting http to https

  5. i to am having issues with ipads not showing the full details for the appointments. it only shows busy for the free busy info. this is a external user to my domain with appropriate permissions. any ideas what to check on?

  6. This may be off topic, but I think it relates. Do you know the secret to getting my own secondary calendars to show up on my iOS device? If I create a new calendar in Outlook, under ‘My Calendars’, I haven’t been able to get that calendar to appear on my iPad. However, check out this scenario:

    – I am on my iPad and visit an online calendar with ‘Export as iCalendar’ option, which I click.
    – At that point the details of that event pop up with an option button at bottom to “Add to Calendar”, which I click.
    -Now I’m presented with the option to add to an existing Calendar on my iPad, or I can select “New Calendar”, even under Exchange.
    -If I create a new Calendar, I can name it, add the event to it, and that new Calendar immediately appears not only on my mobile device, but also in my Windows Outlook 2010 client under ‘My Calendars’.

    Now, my question is, how do I flip this process? How do I get my additional calendars (created on my Windows device in Outlook 2010) to appear on my iPad? Furthermore, is there a way to get the Room Mailbox calendars to appear on the iOS device, without going through the ‘Subscribe’ process. Any way to get this to happen natively through Exchange? The bigger question though, is how to get these additional Calendars (created in the Outlook client) to display on the iOS device like they will in the reverse process I described above.

    Thanks so much, Steve. I learn a tremendous amount from you and the UCArchitects! Thank you all!

  7. Is it possible to set up a shared mailbox on iPad? I don’t need the calendar, just my mailbox and a shared.


  8. My calendar shows just busy for everything. Ive enabled anonymous to view, but I the calendar still shows no information… Does anybody have any suggestions?

    • Thanks Michah for advertising your app on my website 😉

      Personally, publishing in OWA is pretty simple but your app sounds great for those environments where it is not enabled and of course Exchange 2007

      One often overlooked area with EWS-based Calendar Sharing apps is how they handle appointments the owner has set to Private. As it’s not a real permission, some application developers don’t check for this property and show private appointments that they shouldn’t do. More information here:

      Does your application honour these properties?


      • Well, sorry for the cheap opportunism, but I wrote the app after getting frustrated with the limitation and then read people all over the web having the same frustration, so I’m really trying to help — I am not getting rich from this. 😉

        EWS (GetUserAvailabilityRequest) handles the private appointment for me, so they come in as private to the query. I couldn’t display the real information if I wanted to. Also, if someone just has free/busy permission, but not meeting titles, they all come back as private.

      • This is perhaps a bit of a rhetorical question but why is it up to the client to suppress private information? If a user sets an appointment to private, then Exchange should suppress it; otherwise the information is “out there”.

          • Thanks for responding. The reason is: if I give you permission to look at my calendar but I set some of my info to private, then as things stand, there’s nothing to keep you from seeing my private info if you deliberately use a client that doesn’t respect the private flag. Even if I can’t find a client, I’ll bet it wouldn’t be particularly hard to write a quick & dirty script to extract private info if Exchange isn’t protecting it.

            Basically Exchange is exposing info (telling the owner that’s it’s private) while doing no more than politely requesting potential readers to avert their gaze.

            Maybe I’m misunderstanding but if not…that’s a bug by design.

            In any case, thanks very much for the info on Exchange config & iOS access. I’ll add something nifty I found in my environment: when an Outlook 2010 user clicks the link for a published calendar that’s been sent to them, it gets added to “Other Calendars” and then it also appears in their mobile device over ActiveSync. This works for both iOS and Android.

            More specifics: Exchange 2010; the shared calendar and the account that’s mounting it are on the same server.

  9. Well, it’s not always working. If your Outlook Web App is only available at https it’s not going to work because this calendar publishing asumes http is available too.

      • Yes, it seems to me that the calendar links in OWA is hardcoded to http which is not usable on our network. Our Outlook Web App is only available on port 443. I hoped this could be configurable, but haven’t found anything and probably have to wait and see if MS is fixing it someday. Currently this calendar sharing is only available to the users in our company smart enough to manually change http to https 🙂 Other than that, it’s a great feature.

Comments are closed.