Study guide

2.7 Identity and Governance Case Lab

AZ-104 Microsoft Azure Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Orientation and Microsoft Learn Source Control

1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log

2 Chapter 2: Identity, RBAC, and Governance Foundations

2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab

3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization

3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab

4 Chapter 4: Storage Accounts, Access, and Data Protection

4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab

5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep

5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab

6 Chapter 6: Containers, App Service, and Platform Compute

6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab

7 Chapter 7: Virtual Networking, Routing, and Secure Access

7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab

8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting

8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab

9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery

9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab

10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs

10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab

11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path

11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

2.7 Identity and Governance Case Lab

Key Takeaways Explain This Topic AI

Mixed identity and governance scenarios require separating authentication, authorization, compliance, protection, and cost signals.

The safest scope is the lowest scope that includes all required targets and excludes unrelated resources.

Portal workflows are efficient for investigation, while CLI commands are stronger for repeatable rollout and audit evidence.

Exam case studies may combine users, groups, RBAC, policy, locks, tags, budgets, and Advisor recommendations in one story.

Last updated: May 2026

Case Background

Contoso has one Microsoft Entra tenant and four Azure subscriptions: sub-platform , sub-prod-apps , sub-dev-apps , and sub-sandbox . The subscriptions are organized under management groups. sub-platform sits under mg-platform . sub-prod-apps sits under mg-production . sub-dev-apps and sub-sandbox sit under mg-nonprod .

The company has these teams:

Team Requirement

CloudOps Manage all production application resources but not tenant-wide identity settings.

NetworkOps Manage hub networks in sub-platform and read spoke network settings in production.

Helpdesk Reset passwords for cloud users and read Azure resources for support.

Developers Manage resources only in their dev application resource groups.

Vendors Read monitoring data for one production resource group for 30 days.

Finance Report costs by application, environment, and cost center.

Your job is to design the first governance pass without overgranting permissions.

Step 1: Separate Identity From Azure Authorization

Helpdesk password reset is a Microsoft Entra task. Reading Azure resources is an Azure RBAC task. Do not solve both with subscription Owner. Give Helpdesk the appropriate directory role or SSPR administrative capability for password support according to organizational policy, and separately assign Reader at the needed Azure scope. If the support team only supports production resources, Reader at mg-production may be better than tenant root or all subscriptions.

For users, check account state, user type, source, and group membership. For guests, invite the external user, verify redemption and directory context, then grant resource access through a time-bound process. AZ-104 may not test full privileged identity management configuration in depth, but it does expect you to avoid permanent broad access when a narrow temporary assignment meets the requirement.

Step 2: Choose Groups Before Assigning Roles

Create security groups that represent job functions and scopes. Examples:

Group Assignment

az-prod-cloudops-contributors Contributor at mg-production .

az-prod-access-admins User Access Administrator at mg-production if delegated access management is required.

az-platform-network-contributors Network Contributor or appropriate network role at platform network resource groups.

az-prod-network-readers Reader or Network-related reader access for production network resources.

az-dev-rg-payroll-contributors Contributor at rg-payroll-dev .

az-prod-monitor-vendors Monitoring Reader at rg-prod-orders , reviewed after 30 days.

This group-first pattern makes onboarding and offboarding cleaner. If a user leaves CloudOps, remove the user from the group. Do not hunt for ten direct role assignments scattered across resources.

Step 3: Scope The Role Assignment

Apply the lowest common parent rule. CloudOps needs all production application resources, so mg-production may be correct if that management group contains only production application subscriptions. Developers need only dev resource groups, so assign at each dev workload resource group, not at sub-dev-apps if the subscription contains shared services.

NetworkOps is more nuanced. If hub VNets are in dedicated platform resource groups, assign network administration at those resource groups. If production spoke networks live in app resource groups and NetworkOps only needs read access, assign a reader role at the production network resource groups or management group according to the resource layout.

Exam trap: the presence of a management group does not mean it is always the right scope. Use it only when every child needs the same access or policy.

Step 4: Add Policy For Compliance

Contoso requires production resources to use only eastus and centralus , include CostCenter , Application , and Environment tags, and prevent public IP creation except in approved network resource groups.

Policy design:

Requirement Control

Allowed production regions Deny policy at mg-production .

Required tags Policy requiring tags at production and nonproduction scopes.

Tag inheritance from resource group Modify or append policy where appropriate.

Public IP restriction Deny policy with exemptions or narrower scope for approved networking groups.

Existing noncompliant resources Compliance review and remediation plan.

Use initiatives when several policies form one baseline. Assign the initiative at mg-production for production controls and at mg-nonprod for less restrictive controls. Do not assign strict production policy at tenant root if sandbox subscriptions should allow experimentation.

Step 5: Protect Critical Resources With Locks

Production databases, key shared network resources, and recovery vaults may need CanNotDelete locks. A CanNotDelete lock allows authorized updates but blocks deletion. Use ReadOnly locks carefully because they can break normal service operations that require writes.

Example: Apply CanNotDelete to rg-prod-orders or directly to the production database resource if accidental deletion is the main risk. If deployments update resources in that group, a ReadOnly lock would cause deployment failures. The exam may describe a failed deployment after a ReadOnly lock; the lock is the cause even when Contributor access exists.

Step 6: Add Cost Signals

Finance needs reporting by application, environment, and cost center. Tags support this. Cost Management budgets provide alerts for each subscription or resource group. Advisor recommendations identify possible savings, such as idle or underutilized resources.

Do not confuse alerts with enforcement. A budget can notify CloudOps at 80 percent and 100 percent of forecast or actual spend, but it does not automatically prevent a developer from creating another VM. If hard prevention is required, use policy, quota strategy, automation, or approval workflows depending on the exact requirement.

Step 7: Investigation Workflow

When a user reports access failure, use this order:

Confirm the user is in the correct tenant and subscription context.

Confirm the user or guest object exists and is enabled.

Check group membership and direct assignments.

Check inherited role assignments at parent scopes.

Check locks, deny assignments, and policy compliance messages.

Check service-specific data-plane roles and network restrictions.

Wait for propagation or refresh credentials when recent changes were made.

Portal workflow: use Microsoft Entra ID > Users , then the target scope's Access control (IAM) > Check access , then Locks , then Policy > Compliance . CLI workflow: use az account show , az ad user show , az role assignment list --include-inherited , az lock list , and az policy state summarize .

Exam Simulation

Question: A vendor can sign in but cannot view metrics for rg-prod-orders . The vendor is a guest in the tenant and a member of az-prod-monitor-vendors . The group has Monitoring Reader at rg-prod-billing , not rg-prod-orders . The answer is to assign the group at the correct resource group scope or add a separate assignment for rg-prod-orders . Do not recreate the guest account.

Question: Developers cannot deploy in westus in production even though they have Contributor. The production policy allows only eastus and centralus . The answer is to deploy to an allowed region or request a policy change. Do not assign Owner as a reflex.

Question: CloudOps cannot delete a production database before a migration. They have Owner on the resource group. A CanNotDelete lock exists. The answer is to remove or modify the lock through approved change control, then delete. RBAC is already sufficient.

Question: Finance reports unallocated costs. Resources are missing CostCenter . The answer is to enforce required tags with Azure Policy and remediate existing resources. A budget alerts on spending but does not label costs.

This decomposition is the habit AZ-104 rewards. Authentication, authorization, compliance, protection, and cost management are related, but they are distinct controls.