When you create a Teams meeting in Outlook for another user, you get the error:…
We have a hybrid deployment between the Exchange on-premises organization and Exchange Online organization. The delegate permissions are set for the user to create Teams meetings. When we run Outlook and create a Teams meeting for other Exchange on-premises users, a Microsoft Teams error shows up with the message: Sorry, but we can’t connect to the server right now. Please try again later. Why is this happening, and what is the solution for unable to create Teams meeting for another user?
Table of contents
Teams error: Sorry, but we can’t connect to the server right now. Please try again later.
Start Outlook and click on the Calendar icon. In this example, we did sign in with Amanda’s mailbox.
She wants to create a Microsoft Teams meeting on behalf of the user Grace. Click in the user’s calendar and click New Teams Meeting.
A Microsoft Teams error message window shows up.
Sorry, but we can’t connect to the server right now. Please try again later.
The only option you have is to click on the OK button.
The delegate cannot schedule Teams meeting. Why is this happening, and why do we get the error that Microsoft Teams can’t connect to the server right now?
Solution for delegate unable to schedule Teams meeting
After running the hybrid configuration wizard, you need to apply one more change to have Teams delegate working for the on-premises users.
Make sure to keep your Exchange Servers up to date. The below steps will work for:
- Exchange Server 2013 CU19 and later
- Exchange Server 2016
- Exchange Server 2019
All the cmdlets need to be run in Exchange Management Shell on-premises.
Let’s go through the below steps to enable calendar delegation for the on-premises Exchange mailbox users and fix the Teams delegate scheduling not working.
1. Create mail user for partner application
Create a new mail user and assign it the appropriate management role rights. We will use that account in the next steps.
- -Name: Teams-ApplicationAccount
- -ExternalEmailAddress: Teams-ApplicationAccount@yourdomain.com
- -DomainController: DomainControllerFQDN
[PS] C:\>New-MailUser -Name "Teams-ApplicationAccount" -ExternalEmailAddress "Teams-ApplicationAccount@exoip.com" -DomainController "dc01-2016.exoip.local" Name RecipientType ---- ------------- Teams-ApplicationAccount MailUser
2. Hide new mail user from address lists
This command will hide the new mail user from address lists.
[PS] C:\>Set-MailUser -Identity "Teams-ApplicationAccount" -HiddenFromAddressListsEnabled $True -DomainController "dc01-2016.exoip.local"
3. Assign user application management role
Assign the UserApplication management role to this new account.
[PS] C:\>New-ManagementRoleAssignment -Role "UserApplication" -User "Teams-ApplicationAccount" -DomainController "dc01-2016.exoip.local" Name Role RoleAssigneeName RoleAssigneeType AssignmentMethod EffectiveUserName ---- ---- ---------------- ---------------- ---------------- ----------------- UserApplication-Teams-Appli... UserApplication Teams-ApplicationAccount User Direct
4. Assign archive application management role
Assign the ArchiveApplication management role to this new account (not required for delegation, but we recommend running it).
[PS] C:\>New-ManagementRoleAssignment -Role "ArchiveApplication" -User "Teams-ApplicationAccount" -DomainController "dc01-2016.exoip.local" Name Role RoleAssigneeName RoleAssigneeType AssignmentMethod EffectiveUserName ---- ---- ---------------- ---------------- ---------------- ----------------- ArchiveApplication-Teams-Ap... ArchiveApplication Teams-ApplicationAccount User Direct
5. Create and enable partner application
Create a new partner application and use the account that you did create in the previous step. The application ID is Skype for Business Online (00000004-0000-0ff1-ce00-000000000000).
[PS] C:\>New-PartnerApplication -Name "Teams" -ApplicationIdentifier "00000004-0000-0ff1-ce00-000000000000" -Enabled $True -LinkedAccount "Teams-ApplicationAccount" Name ApplicationIdentifier Realm UseAuthServer Enabled ---- --------------------- ----- ------------- ------- Teams 00000004-0000-0ff1-ce00-000000000000 True True
6. Restart Information Internet Services (IIS)
Restart IIS to have the changes take immediately into effect.
[PS] C:\>iisreset Attempting stop... Internet services successfully stopped Attempting start... Internet services successfully restarted
Create Teams meeting on behalf of another user
Start the Outlook application and go to the Calendar. Create a New Teams Meeting on behalf of another user.
Microsoft Teams will create a join the meeting link in the meeting invitation. Fill in the To/Subject field and send the invitation.
If you still get the error, restart Microsoft Teams and Microsoft Outlook. Another option is to restart the machine.
The Teams meeting looks excellent in the calendar.
Microsoft Teams meeting permission error
You may see another Microsoft Teams error after you implement the above change.
Looks like you don’t have permission to schedule meetings for this account. Talk to the owner to get permission and try again.
Read the article: Manage Teams meeting delegate permission »
In this article, you learned why you get the Teams error: Sorry, but we can’t connect to the server right now. Please try again later. It happens when you want to create a Teams meeting in Outlook for on-premises mailboxes. The solution is that after you run the Office 365 Hybrid Configuration Wizard, you need to create a new partner application for Teams.
Did you enjoy this article? You may also like the course Exchange hybrid. Don’t forget to follow us and share this article.