![]() It’s a sad situation from Microsoft, but we’re here to help. While we don’t know why Microsoft Active Directory (that’s built into every 365 hosting account) would have MFA turned on and still let it show as “Disabled” anywhere else in 365, we can walk you through steps for taking a deeper look. Some mysteries may take longer to clear up (or may require a system re-vamp by Microsoft.) We can’t tell you why Microsoft lets MFA show as “Disabled” Recently Microsoft 365 hosting has implemented a new set of default standards, “ Security Defaults”, that are automatically turned on for a new 365 “tenant” from in the Azure Active Directory that’s built into 365. With a little digging our SaneBox support team quickly uncovered the answer to what’s going on here. In this case of getting reports from users, the 1st thing the admin would do is login to their Microsoft 365 Admin center and look under MFA (multi factor authentication), and then they’d see - it actually still shows as “Disabled” for each and every user! We’ve heard from the administrators of Microsoft 365 hosting accounts that say their users report being asked to set up Microsoft Authenticator app even though that admin person themselves didn’t know that would happen and hadn’t turned the MFA (also known as 2FA) on yet. If you’re one of the “ Admins” for your 365 hosting, follow along with these steps we’ve put together below to show you what’s going on. If you’ve had a Microsoft 365 hosting account setup recently for email at your company and your users are being prompted to set up authentication codes - but you looked and the MFA in your 365 admin shows as “Disabled” - then follow along here and we’ll show you why. Microsoft 365: Why are we being asked to use authentication codes if 365 admin shows MFA "Disabled"
0 Comments
Leave a Reply. |