We’ve covered what Authentication Contexts are, why they matter, and how they help us strengthen access and data security in Microsoft 365. Now it’s time to answer the next question - how do we monitor and report on their usage? Unfortunately, there’s no built-in way to gain that visibility today. Neither Entra ID nor Microsoft 365 provides a simple method to inventory or audit Authentication Contexts across our estate including Conditional Access, PIM and Sensitivity labels

With identities and access strengthened in part 2 , it’s time to turn our focus to real-world data protection  with Authentication Contexts. One of the more underused capabilities of Authentication Contexts is their power to secure data across the environment, whether through direct enforcement using Sensitivity Labels or by protecting user sessions via Microsoft Defender for Cloud Apps. In this post, we’ll explore exactly that: how to secure organizational data using Authent

In Part 1 of this mini-series, we explored the what, why, and how of Microsoft Entra Authentication Contexts, laying the foundation for what they are and how they work. In this second part, we’ll build on that foundation with real-world examples of how Authentication Contexts can secure user access and critical actions. Along the way, we’ll walk through configurations, share recommendations, and look at the Conditional Access policies that tie it all together. So, let’s dive

Over my last few posts, I’ve casually mentioned Authentication Context a few times, so I thought it was about time we gave the feature a proper spotlight. Within Microsoft Entra, we sometimes encounter scenarios where we need to enforce specific conditions for certain sub-actions or unique requirements. While Conditional Access can directly enforce conditions in most cases, there are times when it’s trickier — especially if we want to enforce a condition for a single  action

Managing external users is one of the most tedious—but also critical—challenges in a Microsoft Business Premium environment. With...

In Part 02 , we explored authentication , the process of verifying user identities—ensuring users are who they claim to be. Today we’ll...

In my last post I covered how to monitor the GOD Mode in Azure (Coined by the great John Savill ). While visibility and monitoring are...

In the first part of this series, we laid the foundation for securing Microsoft Business Premium environments, covering the core security...

Protecting highly critical configurations in our Entra tenants has never been easier! Join me as we explore Protected Actions  in...

As the countdown for my series draws to a close, there are still a few final points I’d like to explore, and hopefully, you’ll join me...

I’ve gathered the Conditional Access tributes from nearly every district, and today, we’re collecting the final ones as we approach the...

Today, we’re donning our coolest black shades, pulling on leather jackets, and proudly proclaiming, “We’ll be back!” —for when our...

Now that we’ve covered the baseline essentials, it’s time to focus our Conditional Access policy deployment a bit more. As I mentioned in...

Welcome to Microsoft Entra, where Zero Trust, permissions, and the infamous policy change await. Buckle up—this rabbit hole goes deep!...

Understanding the authentication flow for Microsoft Entra  is essential when working with IAM in a Microsoft environment. Like the...