One way to set up multi-factor authentication for Office 365 is to turn on the security defaults in Azure Active Directory. Using Security Defaults to Enforce Multi-factor Authentication It is strongly discouraged to use your production Office 365 tenant. To follow along with the examples, you should have admin access to an Office 365 tenant, preferably to a test tenant. In this article, the assumption is that you have some working knowledge of Office 365 and Azure Active Directory. You may see that both the name Microsoft 365 and Office 365 may be used interchangeably in this article. Note: The name Office 365 has been replaced with the term Microsoft 365. In this article, you will learn about controlling access to services in Microsoft Office 365 with the use of MFA and conditional policies. The point is, that preventing credential theft is better than reacting to it after it has already happened. But, they’re what helps protect you from the nasties. You don’t like it, and sometimes it is annoying. Think of MFA is like the vitamin that you take.

Something you are (biometrics face, fingerprint).

Something you have (security key, token generator).

MFA, as the name implies, employs multiple layers of authentication.

Luckily, there’s more than one layer of security available to protect Office 365 users’ identities Multi-factor Authentication MFA. A single user who is insufficiently informed about the dangers of threats like phishing could very well be the entry point for these malicious activities. Attackers are becoming more creative and smart.

Some examples of these identity attacks are phishing and password spray. Identity-related attacks are often happening and can result in compromised user accounts.

Mfa conditional access