Hey Caspar,
It looks like the OAuth configuration didn’t get set up properly during the Hybrid Configuration Wizard process, and that's likely causing the issues with Teams integration. Don't worry—this can be fixed manually!
- First, check if OAuth is even enabled on your on-prem Exchange. You can do that with this command:
Get-AuthConfig
If OAuth isn't enabled, you can turn it on by running:
Set-AuthConfig -OAuth2ClientProfileEnabled $true
-Add the Office 365 Authentication Server: Once OAuth is enabled, you need to add Office 365 as an authentication server. Run this:
New-AuthServer -Name "Office 365" -AuthMetadataUrl "https://login.microsoftonline.com/<tenant GUID>/v2.0" -AuthType OAuth
Just replace <tenant GUID> with your actual tenant GUID. This will make sure your Exchange server trusts Office 365 for OAuth.
-After that, run the Teams integration test again from Microsoft’s site. It should now recognize the mailbox and the Exchange API endpoint without errors.
-If all goes well, it might help to run the Hybrid Configuration Wizard again just to make sure everything is aligned properly.
-Lastly, make sure your Exchange server is fully patched. Sometimes, missing updates can cause these kinds of issues.