Authentication Strengths in Microsoft Entra ID allows you to granularly define authentication requirements for different situations. Before authentication strengths were available, authentication requirements were defined globally for the entire tenant, and then conditional access policies could just say that multi-factor authentication was required, for example. But it was not possible to define what type of multifactor authentication was required. So anything that was available globally could be used by all users in all situations. Which was not optimal. There are situations where a less secure authentication method like SMS or TOTP might be enough. But there are situations where we only want to use very secure authentication methods like FIDO2 when someone is logging into a global admin account for example. Such granularity was not possible before. If SMS authentication was enabled for a given tenant, even the global admin could use SMS for authentication. Watch my YouTube video bellow for more details 👇 👇 youtu.be/8sIX19pbdho #cswrld #cybersecurity #entraid #authentication #authenticationstrength #conditionalaccess

HOW TO SECURE MICROSOFT ENTRA ID TENANT Microsoft Entra ID has a huge amount of configuration. Unfortunately, the default configuration for new tenants is not optimal from a security perspective. And many organizations don’t change the default configuration, or change it only slightly, but don’t apply all the optimal settings from a security perspective. I routinely see settings in customer tenants that are very risky and could be a source for a future security incident. Let’s take a look at the most important settings in my video 👇👇 youtu.be/ucTuBEu22PM #cswrld #entraid #security #configuration #tips #videotutorial