Questions about the impacts, implications if we enable Modern Authentication.

Frequent Contributor

Hi Experts,


One of our customer raised the below query:


The customer would like to update their tenant to enable modern authentication so that conditional access applies properly. They’ve searched various websites and have conflicting information on the side effects of running the command:


Set-OrganizationConfig -OAuth2ClientProfileEnabled $true


However the below link indicates that there may be some issues:


They’d like to understand the repercussions of making this change, and can draft an appropriate change request for their customer.


Any inputs would be of great help. Many thanks!!

1 Reply

Main impacts are Password prompts (Users will be prompted for creds once tokens expire). And that's about it TBH. Unless they are running old legacy office clients etc. there may be some issues around that, but it's one of those things where you aren't forcing modern auth, you're just allowing it, so impact is minimal.

It was only an issue with my org cause people forget their passwords cause they rely on Windows Hello for Business PIN's.


I want to say there was also an issue with the passwords not taking but I don't think it was related to this. If so, we had to basically try logging in, password wouldn't take, and then click on try logging in with a different account, manually type in e-mail and password and it would then take. This from what I remember happened on users that had synced domain accounts that had Azure AD Joined computers. Anyone with domain joined machines was fine.