Set-OrganizationConfig –OAuth2ClientProfileEnabled $trueįigure 2: Setting OAuth2ClientProfileEnabled to “True” So we need to enable it using the following command: We can do so with the following command:įigure 1: Verifying the configuration state of the OAuth2ClientProfileEnabled parameterĪs you can see in my case it is set to false. Let’s first verify whether it is enabled or disabled for our Exchange Online tenant. This parameter lives under the “ OrganizationConfig” noun. In order to enable this, we need to connect to Exchange Online using PowerShell and set the parameter “ Oauth2ClientProfileEnabled” to “ true”. The first thing is to ensure modern authentication support is enabled in the Exchange Online tenant. However, in order to utilize modern authentication for ADAL based clients like the Outlook desktop client, one or two things (depending on the version of the respective Outlook client) must be performed. So as discussed previously in this article series, most of the Office 365 clients have already been automatically moved to the modern authentication model in an automatic fashion. Enabling ADAL Client Support at the Tenant Level We took a closer look at what modern authentication consists of and how the authentication flow looks like for ADAL enabled Outlook clients. In part 5 of this article series revolving around the available identity models and the authentication story for Exchange Online, our focus was on the Exchange Online authentication story as it was up until now. Exchange Online Identity Models and Authentication Demystified (Part 7).Exchange Online Identity Models and Authentication Demystified (Part 5).Exchange Online Identity Models and Authentication Demystified (Part 4).Exchange Online Identity Models and Authentication Demystified (Part 3).
Exchange Online Identity Models and Authentication Demystified (Part 2).Exchange Online Identity Models and Authentication Demystified (Part 1).If you would like to read the other parts in this article series please go to:
0 kommentar(er)
