What do you do when too many people have access to production environments, or worse—when you aren’t sure who has access to what? In this episode of the #AzureEnablementShow, David and Magnus tackle the very important topic of how to establish and monitor access to various environments within your org. Be sure to watch part one of this episode as well. Resources • Role Based Access Control https://learn.microsoft.com/en-us/azure/active-directory/develop/howto-implement-rbac-for-apps • Privileged Identity Management https://learn.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-configure Related episodes • The Cloud Clinic: Establishing and monitoring access to different environments (part 1) https://aka.ms/azenable/122 • Catch all the Cloud Clinic episodes https://aka.ms/TheCloudClinic • Watch The Azure Enablement Show https://aka.ms/azenable Chapters 0:00 Introduction 1:25 There are two remedies to consider: Role Based Access Control and Privileged Identity Management 2:05 Role Based Access Control enables you to grant access to specific security groups instead of individuals 4:05 Privileged Identity Management is a premium Active Directory feature that allows you to preconfigure access that can be activated only when needed 5:10 Use multi-factor authentication to further strengthen security 5:28 Manager approval is another method for controlling access to production 6:29 Having limited access also provides useful audit logs so that you can determine who had access to certain environments at specific times