What's changed: Deepened AZ-500 Chapter 4 (ja figures; comparison tables/scenarios/FAQ/traps/deep paragraphs in all sections)
4.3Governance and Compliance
Understand Azure Policy to technically enforce organizational rules, Azure Blueprints to apply bundled configuration templates (note: deprecated and slated for retirement in July 2026; the successor is Azure Deployment Stacks with Azure Policy), and Defender for Cloud’s regulatory compliance to visualize alignment with standards. Keep large environments consistently secure.
In large environments, manual checks can’t ensure consistency. Use Azure Policy to enforce rules technically and continuously evaluate compliance.
4.3.1Governance mechanisms
- Azure Policy: define rules and assign to a scope, continuously evaluating compliant/non-compliant.
- effect: deny (block non-compliant creation), audit (record only), deployIfNotExists (auto-remediate), etc.
- Initiative: a bundle of multiple policies; assign coverage for a standard (e.g., ISO/PCI) all at once.
- Blueprints / regulatory compliance: deploy configuration templates together and visualize alignment to standards in Defender for Cloud.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.