Block User AAD Sign-In takes HOURS…to debug
Watch me explain and suffer through this…why does it take at least 1 hour to test whether a user can no longer sign in? On Friday I helped a colleague to confirm this behavior for a customer, who wanted to remove a contractor's access to both Azure DevOps and ARM by blocking their sign-in. Sounds simple, right?
====== What happened? ======
So I could confirm that Azure DevOps behaves as expected - you're locked out as soon as your access token expires. My theory is that the customer had added the contractor directly to Azure DevOps via email, and not as member of the Azure Active Directory.
That's why I recommend groups in my other video about Azure DevOps Best Practices for identity • Azure DevOps #1 Best Practice - Ident...
====== References ======
Azure Docs: Remove and delete the Microsoft 365 license from a former employee
https://docs.microsoft.com/en-us/micr...
Azure Docs: Configurable token lifetimes in the Microsoft identity platform (preview)
https://docs.microsoft.com/en-us/azur...
====== Contents ======
00:00 Intro
00:45 Scenario, How It Works
03:13 First Attempt to Block Sam
06:45 Not Working
09:42 How to Isolate Test
10:54 Back from my Jog
12:11 Closing
14:01 Next Video
