Governance to enforce security and compliance
Azure Policy security controls, regulatory compliance and standards in Defender for Cloud, locks, built-in and custom roles, overprivileged access, backup security and infrastructure as code.
- 22 min
- 9 concepts
- Try it yourself
- 4-question check
Learn
Security governance turns security standards into enforced rules, measures compliance, keeps privileges tight and protects backups, so the estate stays secure as it grows.
- 1
Implement and configure security controls by using Azure Policy, including built-in and custom policy definitions
Assign built-in security policies (for example 'Storage accounts should disable public network access', 'Allowed locations', 'Key Vault should have purge protection') with Deny, Audit, Modify or DeployIfNotExists effects. Write custom definitions in JSON with an
ifcondition using resource aliases and atheneffect. Group them in initiatives and assign at management group scope.Remember: Custom policy = if (alias condition) then (effect).
- 2
Evaluate regulatory compliance by using Microsoft Defender for Cloud
The regulatory compliance dashboard shows pass/fail per control for assigned standards such as ISO 27001, NIST SP 800-53, PCI DSS and CIS. Add standards, download reports, and drill into failing resources. Manual controls can be attested.
Remember: Download compliance reports for auditors from the dashboard.
- 3
Implement and configure security controls in Defender for Cloud, including security standards and recommendations
The Microsoft cloud security benchmark is the default standard. Add others or create custom standards and custom recommendations (KQL-based in Defender CSPM). Remediate recommendations with Fix, Enforce (create a deny policy) or exemptions, assign owners and due dates with governance rules.
Remember: Governance rules give recommendations owners and deadlines.
- 4
Implement resource locks
CanNotDelete and ReadOnly locks apply to everyone, including Owners, and are inherited. ReadOnly can block operations that look like reads but are POST calls (such as listing storage account keys). Removing a lock needs Microsoft.Authorization/locks/delete permission.
Remember: ReadOnly on a storage account blocks listing keys.
- 5
Manage Azure built-in role assignments
Assign built-in roles to groups at the narrowest scope. Prefer job-function roles (Virtual Machine Contributor, Network Contributor, Security Admin, Security Reader) over Owner or Contributor. Remember Owner and User Access Administrator can grant access to others. Use role assignment conditions to limit what a delegated admin can assign.
Remember: Delegate role assignment safely with conditions.
- 6
Manage custom roles, including Azure roles and Microsoft Entra roles
Azure custom roles are JSON with
Actions,NotActions,DataActions,NotDataActionsandAssignableScopes. NotActions subtracts from Actions but isn't a deny. Entra custom roles pick directory permissions (P1 required). Keep custom roles few and documented.Remember: NotActions isn't a deny; another role can still grant it.
- 7
Evaluate and remediate overprivileged access assignments by using Azure role-based access control (RBAC)
Review Access control (IAM) role assignments and Check access for a principal. Use Entra access reviews for Azure roles, PIM alerts, and Defender for Cloud recommendations (for example too many owners, external accounts with owner permissions, deprecated accounts). Remove permanent assignments, replace broad roles with narrower ones.
Remember: Defender for Cloud flags external accounts with owner rights.
- 8
Configure security controls for backup protection by using Azure Backup security features
Protect backups from ransomware and insiders with soft delete (enhanced, always-on), immutable vaults (locked), multi-user authorization with Resource Guard (a second team must approve critical operations), private endpoints, customer-managed keys and alerts on destructive operations.
Remember: MUA: a Resource Guard owned by another team approves risky changes.
- 9
Implement and configure security controls by using infrastructure as code
Bake security into Bicep or Terraform templates (private endpoints, TLS 1.2, disabled public access, diagnostic settings). Scan templates in pipelines with Defender for Cloud DevOps security (IaC scanning, secrets scanning), enforce with Azure Policy, and protect deployed resources with deployment stacks deny settings.
Remember: Scan IaC before it deploys; Policy catches what slips through.
From standard to enforcement
- StandardMCSB, ISO, PCI, or custom.
- AssessDefender for Cloud recommendations.
- Assign ownersGovernance rules with due dates.
- RemediateFix, Enforce or exempt.
- PreventAzure Policy deny and IaC scanning.
Try it
Choose an Azure Policy effect and see how new and existing resources are treated.
This interactive part needs JavaScript.
In the portal
- Regulatory complianceAzure portal: Microsoft Defender for Cloud > Regulatory compliance
- Policy definitionsAzure portal: Policy > Authoring > Definitions
- Resource GuardAzure portal: Resource Guards > Create
- Check accessAzure portal: your resource > Access control (IAM) > Check access
Key terms
Click a card to see the definition.
Check your understanding
4 questions. Score 80% or more and these skills are marked as confident in your SC-500 study plan.
Which effect blocks non-compliant deployments?
Deny prevents the request.
What is Microsoft's default standard in Defender for Cloud?
MCSB is assigned by default.
What does NotActions do in a custom role?
It only subtracts from that role.
Which feature requires a separate team's approval to disable backup protection?
MUA uses a Resource Guard.
Sources
- Microsoft Learn: Azure Policy definition structure
- Microsoft Learn: Regulatory compliance in Defender for Cloud
- Microsoft Learn: Azure custom roles
- Microsoft Learn: Multi-user authorization for Azure Backup
- Microsoft Learn: Defender for Cloud DevOps security
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.