Create Authorization server objects in Exchange on-premises This only works for Exchange 2013 and higher, I have been working on this in a mixed Exchange 2016 and Exchange 2019 environment.Ĭonfiguring OAuth between Office 365 and Exchange Online involve a number of steps. So, time to test, guided by the Microsoft article and write down my experiences. The HCW can configure Azure Active Directory for OAuth authentication, it can create the IntraOrganizationConnectors, but it cannot export and import the (self-signed) certificate on the Exchange server, nor can it (or does it) create the authorization server objects in Active Directory. So, if you are logged on to some Microsoft service, this service can use OAuth to access services in Exchange on-premises and vice versa.Įxample of these cross-premises services are: OAuth is used cross-premises to logon to other services, on behalf of the user. I used that article for the PowerShell commands in this blogpost. The Learn more option redirects to the Microsoft page Configure OAuth authentication between Exchange and Exchange Online organizations. If you need features that rely on OAuth, you can try running the HCW again or manually configure OAuth using these manual steps. HCW8064 – The HCW has completed, but was not able to perform the OAuth portion of your Hybrid configuration.
As long as I can remember the Hybrid Configuration Wizard finishes successfully, and itgenerates the error about the OAuth portion of the hybrid configuration.
0 kommentar(er)
