Now when the user signs in it is prompted to type in the 6 digit code instead. I have now added a secondary MFA authenticator to each user, now using a third-party authenticator app. When they sign in it prompts them to open Microsoft Authenticator and approve the sign-in, as expected. The Conditional Access policy enforces MFA for all cloud apps. Enforcing of MFA is controlled via a Conditional Access. They’ll call on the 3rd.I have a group of AzureAD users that have requires MFA when signing in. The only change notworth is no more basic auth for exchange, which I only have 3 people who haven’t responded in the past 2 months. ![]() Who confirmed that as far as he could tell, the enforcing of MFA is not like how the MSP said, and it’s the registering part that is changing. To cover my butt, I opened a ticket for azure AD, and live chatted with a tech. Was the fact of having a in case anything hits the fan, you have a global admin without MFA to make any adjustments to your tenant. ![]() We don’t use SSRP, we use MFA for most users, a few application service accounts strictly use Microsoft Graph, etc. They know article they provided when asked was for the combining MFA and SSRP into one registration now. They sent out an email last week stating on October 1st Microsoft will be enforcing MFA for all users. So we’re stuck using them for licensing for now. ![]() We only use them for licensing, as after they migrated mailboxes support was Questionable for the entire year, charges for keeping things ‘updated’ when I know I did the updating.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |