Persona-Based Conditional Access | Azure AD | A Security Feature You Aren't Using

In this series we’ll be pulling from our recent webinar to highlight some of the 10 Microsoft 365 Security considerations you can’t afford to ignore, including insight on Microsoft Defender, Microsoft Purview, Microsoft Entra, Azure AD and more.
Here Microsoft MVP Ru Campbell explains how we employ Persona-Based Conditional Access (or Conditional Access for Zero Trust) for Azure AD to strengthen access security within a corporate environment.
To view the full webinar, covering all 10 areas for consideration, click the link below.
👉 www.threatscap...

[@HitemAriania]

Compared with microsofts recommended templates (CA001-CA016 set with the base being MFA for all on all apps) this persona approach is not doing much then adding more confusing to the customers. You want the amount of CA rules to remain low, with a good namingconvetion (CAxxx - BLOCK/GRANT - - - . example: CA004 - GRANT: All apps - MFA - All users). Having 8 personas will round it of around 40 CA rules if you use all licensing and recommended security CA's vs the old 10-16. Dont get me wrong, persona is good! but its not an easy feat and the administration required just to do the memberships lifecycle is a MASSIVE task (could even require a team which most customers dont have - its easier to require MFA for everyone instead and create app/role based CA that has higher requirements, such as FIDO etc).