Hello

We have a group of people that need a common calendar so that sounds simple enough, right?  I created a shared mailbox and set the permissions on the calendar for everyone that requires access to Owner.  I thought that would be it but nobody can add anything to it.  They can see the calendar but if they try to do anything in it they get the error "Cannot open the free/busy information.  You do not have sufficient permission to perform this operation."

You can't log into OWA with a shared mailbox account even after you enable it, so I can't share the calendar that way.

I know I can fix this by giving the users Full access to the mailbox in EAC but that would add the shared mailbox to everyone's Outlook which we don't want.  I also know I could fix that problem by going into ADUC and removing the delegate attribute in the mailbox account but do I really need to go through these hacks just to set up a shared calendar?

We are using Exchange 2013 with Outloo

Hi Hutch,

You need to give Folder Visible permission on the Top-Level folder(including any parent folder if exists) of the mailbox and on the calendar too if not given.

Once done, it will allow user to see the calendar and only items below which they have permission to.

This will not show all the items inside the parent folder.

FolderVisible   The user can view the specified folder, but can't read or edit items within the specified public folder.

Set-MailboxFolderPermission -Identity SharedMailbox@contoso.com:\Calendar -User Tomgroup@contoso.com -AccessRights FolderVisible

https://technet.microsoft.com/en-us/library/ff522363(v=exchg.150).aspx

Add-MailboxFolderPermission -Identity ayla@contoso.com:\Marketing -User Ed@contoso.com -AccessRights FolderVisible

https://technet.microsoft.com/en-us/library/dd298062(v=exchg.150).aspx

I'm sorry Satyajit, but you are mistaken.  On a shared mailbox, not a shared calendar of a user's mailbox, you are not able to add, edit or delete anything.  You can only view, at least with Outlook 2007.  we are getting around this right now by doing the edits in OWA.

Hi Hutch,

Okay, you mean its Outlook 2007 causing the issue and on the permissions side its all set & working.

You may try with a trial version of Outlook2013 to test if it works.