Sending Invites to Public Folder calendars does not show up
We recently did a O365 migration and fighting with an issue with PF Calendars. The data is there and the permissions carried over.
When a user pulls up a series on the Public Folder calendar, it will tell them that the calendar address doesn't exist anymore after opening the series event but you can still see the event and all the attendees. Calendar wasn't showing in the GAL either, but I fixed that by turning mail enabled back on and I verified it is turned on in the parent and the child items. It showed in the GAL then.
Error when viewing the series still exists. If you create a test event and pick it from the GAL, and it doesn't matter if select the calendar as the TO or a resource the test event will never show on the shared one, but of course it shows on the personal one.
Shouldn't Turning Mail enabled back on fixed the issues for this?
I know moving to a room resource the preferred option, but not ideal here, just trying to function after a migration.
Dashrender last edited by
calendar as the TO or a resource the test event will never show on the shared one, but of course it shows on the personal one
Do you have auto accept calendar items enabled?
I am trying to open the PF folder mailbox as another mailbox to open in outlook and it cant find it. Tried from OWA and it say there is no mailbox for the user. Mail Enabled is on, and I see it listed in the Public Folders Mailboxes tab in Exchange Online. So it has a mailbox.....Perplexed.....
When Looking at the PF, I see the test messages in the PF, so the tests are making it to the PF, but it is not auto accepting the meeting. But I cant turn auto accept on, if it wont let me into the mailbox.
Turns out that these functions cant be used in Exchange Online. PF is very rudimentary in Exchange Online.Only option is to move them to Resources. This is per a Microsoft rep and his supervisor.
Mike Davis last edited by
Creating them as a resource seems like it will be the better move going forward. Public Folder support in o365 has been sketchy at best. Even with resources, you may have to drill in using powershell to change some of the options, but it works.