Q: What do I do if I haven’t implemented any secure access components yet?
Answer: Define at least two break-glass accounts, assign MFA to your privileged admin accounts, and separate user accounts from Global admin accounts.
Q: After a breach, what is the top issue that needs to be addressed first?
Answer: Be sure you’re requiring the strongest authentication for highly-exposed individuals.
Q: What happens if our privileged admins have been deactivated?
Answer: Create a Global admin account that is always kept up-to-date.
Q: What happens if there is only one global admin left and they can’t be reached?
Answer: Use one of your break-glass accounts to gain immediate privileged access.
Q: How can I protect admins within my organization?
Answer: Have admins always do their day-to-day business as standard “unprivileged” users.
Q: What are the best practices for creating admin accounts within Azure AD?
Answer: Reserve privileged access for specific admin tasks.
Q: What tools exist for reducing persistent admin access?
Answer: Privileged Identity Management (PIM) and Azure AD admin roles.
Q: What is the Microsoft position on synchronizing admin accounts to Azure AD?
Answer: Tier 0 admin accounts (including accounts, groups, and other assets that have direct or indirect administrative control of the AD forest, domains, or domain controllers, and all assets) are utilized only for on-premises AD accounts and are not typically synchronized for Azure AD for the cloud.
Q: How do we keep admins from assigning random admin access in the portal?
Answer: Use non-privileged accounts for all users and most admins. Start by developing a footprint of the organization to determine which few admin accounts should be privileged. And monitor for newly-created administrative users.
For more details: https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-admin-roles-secure?_lrsc=c71210a1-f7b7-4ff7-ac77-8cb1136f022b