![]() Since they have removed their account from the application they can not authenticate to the portal. The problem lies in that even though they are visiting the portal from devices that are excluded from MFA via conditional access (Compliant/Hybrid AD Joined) the portal is still enforcing MFA to log in. The end users try to fix the issue themselves and will remove their accounts from the app and try to reenroll by going to and restarting the setup process. I have had multiple scenarios this week where the Microsoft Authenticator app has stopped displaying the approve/deny message. This is causing issues when users need to re set up the account in the Authenticator app. We turned off the ability to receive texts/calls and are forcing the Authenticator app. We have recently implemented MFA with a conditional access policy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |