Study guide
3.5 Policy, Initiative, Assignment, and Remediation
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
3.5 Policy, Initiative, Assignment, and Remediation
Key Takeaways Explain This Topic AI
Azure Policy evaluates resource compliance and can audit, deny, modify, append, or deploy related configuration depending on the effect.
An initiative groups multiple policy definitions so a baseline can be assigned and reported as one package.
Assignments define the scope, parameters, exclusions, enforcement behavior, and managed identity needs for a policy or initiative.
Remediation tasks are required when deployIfNotExists or modify policies must fix existing resources.
Last updated: May 2026
Policy objects and how they relate
Azure Policy uses a few related objects. A policy definition describes a rule and an effect. An initiative definition groups multiple policy definitions into a set. A policy assignment applies a definition or initiative to a scope. Parameters make definitions reusable. Exemptions and exclusions reduce or waive evaluation for specific needs. Compliance results show whether resources match the assigned rules. Policy definition: Require a tag named CostCenter
- Initiative definition: Corporate baseline with tags, allowed regions, diagnostics, and SKU rules
- Assignment: Apply Corporate baseline to the Prod management group
- Parameters: Allowed locations = eastus, westus2; required tag = CostCenter
- Remediation: Add missing diagnostic settings to existing resources
The hierarchy matters. A definition sitting in the policy library does nothing until assigned. An assignment at a management group can affect all child subscriptions. An assignment at a resource group affects that group and resources below it. A resource can be evaluated by multiple assignments from different scopes, and the most restrictive practical result may control deployment.
Effects administrators must recognize
The policy effect determines behavior. Audit records noncompliance but allows the request. Deny blocks noncompliant create or update operations. Disabled turns off evaluation. Append adds fields to a request in supported scenarios. Modify can add or update properties such as tags. DeployIfNotExists deploys a related resource or configuration when a condition is missing. AuditIfNotExists reports when related configuration is missing.
- Effect Typical use Exam cue
- Audit Report missing tag or insecure setting Need visibility without blocking
- Deny Block public IPs, regions, or SKUs Need prevention at deployment time
- Modify Add or correct tags Need automatic metadata correction
- DeployIfNotExists Deploy diagnostics or security agent settings Need related configuration created
- AuditIfNotExists Report missing diagnostics Need compliance report only
- Disabled Keep assignment but stop evaluation Need temporary off switch
Effects that change resources need permissions. A modify or deployIfNotExists assignment usually requires a managed identity and role assignment so policy can remediate resources. If the identity lacks rights, compliance may show noncompliance and remediation may fail. This is a common AZ-104 troubleshooting point.
Assignments, parameters, exclusions, and exemptions
When assigning a policy or initiative, choose the scope carefully. If the requirement says all current and future subscriptions under production need the same allowed regions, assign at the production management group. If only one application resource group needs a rule, assign at that resource group. Do not over-scope deny policies because inherited denies can block legitimate platform work.
Parameters make assignments flexible. A single allowed locations definition can be assigned with eastus and westus2 for production, but eastus , westus2 , and centralus for development. A required tag definition can require CostCenter in one assignment and DataClass in another.
Exclusions remove specific scopes from an assignment. Exemptions can document a waiver, often with a reason and expiration. For exams, if a workload must be temporarily allowed to violate a policy while the rest of the scope remains governed, use an exemption or exclusion rather than deleting the assignment for everyone.
Remediation workflow
Policy evaluation does not always fix existing resources. If a deny policy is assigned today, it blocks future noncompliant creates or updates but does not delete existing noncompliant resources. If a modify policy is assigned today, existing resources may need a remediation task. If deployIfNotExists is used for diagnostic settings, existing resources typically need remediation so the related settings are deployed. Remediation workflow
1. Assign policy or initiative at the correct scope.
2. Configure parameters and assignment identity when needed.
3. Wait for or trigger compliance evaluation.
4. Review noncompliant resources and reasons.
5. Create a remediation task for modify or deployIfNotExists effects.
6. Verify the managed identity has required permissions.
7. Recheck compliance and troubleshoot failures.
Portal path: Policy > Assignments , Policy > Compliance , and Policy > Remediation . CLI and PowerShell can also create assignments and remediation tasks, but AZ-104 usually tests the conceptual operation and failure modes.
Scenario workflow
A security team requires all storage accounts to disable public network access and all resources to have a CostCenter tag. Use an initiative containing at least two definitions: one deny or audit policy for storage network configuration and one tag policy. Assign the initiative at the target management group or subscription. Parameterize the tag name and any allowed values. For existing resources, review compliance. If the storage policy is audit-only, it will report existing noncompliance. If tag correction uses modify, create a remediation task and ensure the assignment identity can write tags.
If a deployment fails after the assignment, inspect the deployment error. Azure Policy denial messages usually identify the assignment and definition that blocked the request. The fix is not to grant Owner to the user if the policy denies the request. Owner does not bypass Azure Policy. The fix is to change the deployment to comply, adjust policy parameters, add an exemption, or move the deployment to a scope where the rule does not apply.
Exam traps
Policy is not RBAC. RBAC answers who can perform an action. Policy answers what resource configurations are allowed or reported. A Contributor can still be blocked by a deny policy. A Reader can still see resources but cannot fix noncompliance unless given write permissions.
Policy is also not a lock. A lock prevents delete or write operations at a scope regardless of resource configuration. Policy evaluates rules. If the requirement is prevent deletion of this resource group , use a delete lock. If the requirement is prevent public IP creation , use deny policy. If the requirement is audit all VMs missing diagnostics , use auditIfNotExists or deployIfNotExists depending on whether you only report or also deploy settings.