Forum Discussion
Solved
Can't create Teams meeting for other user
Hello.
I have one user that is unable to create Teams meetings for another user in Outlook. They have full access to the other mailbox (they are both hosted on-premise with Exchange 2016) and can schedule regular meetings, just not Teams. It shows the following message:
Sorry, but we cannot connect to the server right now. Please try again later.
The error message is useless as it doesn't say which server it is trying to connect to. I have checked our OWA and ECP, everything functions perfectly. Has anyone else seen this before and fixed it?
Thanks.
Dai_Webb Hi! Then I would walk through this step-by-step https://docs.microsoft.com/en-us/microsoftteams/exchange-teams-interact#requirements-to-create-and-view-meetings-for-mailboxes-hosted-on-premises
Note the "To enable calendar delegation for these users" section as well.
This is the solution:
Teams meeting in Shared Mailboxes does not work with Automaping Shared Mailboxes.
Shared mailbox has to be added to Outlook manually as an additional account for it to work.Remove the shared mailbox access in EAC, via Powershell assign full access permissions with automaping off
Add-MailboxPermission -Identity "SharedMailbox" -User "Username" -AccessRights FullAccess -InheritanceType all -AutoMapping $false
Add the shared mailbox to Outlook manually.
Best regards,
Marco Francisco
Was able to repro this issue in our environment.
Seems like assigning -AccessRights FullAccess causes the issue
When this was removed and we left only delegate rights for calendar it works.
For our environment we tested in the following scenario:
- both user A and B (delegate and delegator) were o365 users
- both were on Office Pro Plus using Outlook 2016
Users didn't complain about this previously because we've only recently introduced Teams into our environment (we still have Skype but it is being phased out) And as another person in this forum mentioned, Skype meeting and regular meetings are not impacted.
To get this working:
- User A must give User B calendar delegate permissions in Outlook
- ensure that -AccessRights FullAccess has NOT been applied
- When User B adds the calendar in Outlook it needs to be done through: File > Open & Export > Other User’s Folder
Note: some of our users - we have EA's that not only manage calendars for their executives - also need access to their Inbox and want it to appear in Outlook beneath their own mailbox. So for these users we ensured that 'Inbox' permissions were also delegated. Then User B went into Outlook to add the mailbox through: File > Account Settings > Account Settings > New ....when prompted select 'Office 365'
This is the solution:
Teams meeting in Shared Mailboxes does not work with Automaping Shared Mailboxes.
Shared mailbox has to be added to Outlook manually as an additional account for it to work.Remove the shared mailbox access in EAC, via Powershell assign full access permissions with automaping off
Add-MailboxPermission -Identity "SharedMailbox" -User "Username" -AccessRights FullAccess -InheritanceType all -AutoMapping $false
Add the shared mailbox to Outlook manually.
Best regards,
Marco Francisco
Dai_Webb Hi, have you verified all prerequisites?
ChristianBergstrom thanks for the reply.
Yes, as far as I can tell everything required is setup. We have been using Teams happily for some time but I think this is the first time we have experienced this issue with
For info, we have Exchange 2016 CU17 hosted on-prem and no mailboxes in the cloud, they are all on-prem. The hybrid setup has been in place for some time.
Dai_Webb So only for one user? In that case I would focus on the client (new .ost / new profile etc.) Perhaps another member has seen this before and will reply.
