I have an Entra ID trial, a Windows Server forest, and a virtual lab. What are some useful things to deliberately misconfigure so I can practice troubleshooting sync, Intune, access, and governance?
What should I break in an Entra ID lab to practice troubleshooting?
Answers
Start with Conditional Access, but don't test a blocking policy on your only administrator account. Use a separate test user and check the sign-in logs to see which policy applied and why.
Try changing the targeted users or conditions, then compare the result with what you expected. Learn how emergency access accounts are configured and excluded before experimenting with admin access, otherwise you could lock yourself out of the tenant.
Reply to this answer
Make a couple of users in the on-premises directory, sync them, and give them cloud mailboxes. Add both to a shared mailbox, then change one user's surname and work through the account and email address changes.
That gives you a reason to check which attributes are managed on-premises, what reaches Entra ID, and whether mailbox access still works. You could also try excluding a test user from sync and investigate why they no longer appear as expected.
8y!gimbalstaple_526:
Worth checking the sync configuration and logs before changing attributes at random. It makes the exercise easier to diagnose and repeat.
Reply to this answer
For Intune, make a test device noncompliant and see what the device and compliance reports tell you. Then add a Conditional Access policy for a test user that requires a compliant device. You can practice separating a device compliance problem from an access policy problem.
Reply to this answer
Play with role-based access too. Give a test admin a limited role, try a task it can and can't perform, then investigate the permissions needed. Do the same through PowerShell or Azure CLI so you get used to troubleshooting more than just the portal.
Reply to this answer
Not everything has to be broken manually. Try documenting the tenant configuration with Microsoft 365 DSC, then use the Maester PowerShell module to check settings. Comparing the results before and after a lab change is a good way to learn what the tools actually report.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_a81!nexvilo.6:
If an admin gets blocked, is there always a way back in?
Ruvdano+6p:
Not necessarily. A properly configured emergency access account can provide a way back, but don't assume recovery will be quick or guaranteed if every admin is blocked.