Azure Policy and Resource Compliance
Azure Policy is a service that creates, assigns, and manages policies enforcing rules on Azure resources. Think of it as guardrails ensuring resources comply with corporate standards and regulatory requirements.
How Azure Policy Works
Policies enforce naming conventions, require specific tags on resources, mandate encryption standards, or prevent resource creation in certain regions. When you assign a policy, Azure evaluates your resources against the policy rules. Non-compliant resources are flagged, and the policy can automatically remediate issues or simply report violations.
Policy Initiatives and Compliance Scanning
Policy initiatives are groups of policies bundled together to address specific compliance requirements, such as HIPAA or PCI-DSS. For example, a company might create an initiative combining policies that require encryption, enforce network security groups, and mandate resource tagging.
Policies evaluate resources at three stages:
- During resource creation
- Through compliance scanning of existing resources
- Continuously for ongoing compliance
You can view compliance status in the Azure portal, seeing which resources are compliant, non-compliant, or exempt. This proactive approach prevents misconfigurations before they become security or compliance issues.
Role-Based Access Control (RBAC) and Identity Management
Role-Based Access Control (RBAC) is Azure's authorization system determining what actions users and applications can perform on Azure resources. RBAC operates on three core elements: security principals, role definitions, and scope.
Core RBAC Elements
Three key components make up RBAC:
- Security principals: Users, groups, service principals, or managed identities
- Role definitions: Sets of permissions that can be performed
- Scope: The level at which the role applies (subscription, resource group, or individual resource)
Built-In Roles and Their Permissions
Azure provides three primary built-in roles. Owner has full access to all resources and can manage permissions. Contributor can create and manage resources but cannot grant access to others. Reader can only view resources without making changes.
Organizations can create custom roles tailored to specific needs. Service-specific roles like Virtual Machine Contributor or Storage Account Contributor provide granular permissions within particular services.
Scope Hierarchy and Least Privilege
Scope is hierarchical, meaning permissions granted at the subscription level apply to all resource groups and resources within that subscription. Resource group-level assignments only affect resources in that group. This principle of least privilege is fundamental to security governance. A developer might be assigned Contributor access on development resources but only Reader access on production environments.
Azure tracks role assignments in the Access Control (IAM) blade, showing exactly who has what permissions at each scope level. Using managed identities for applications eliminates storing credentials in code, improving security significantly.
Cost Management and Resource Optimization
Cost governance in Azure involves monitoring spending, understanding cost drivers, and optimizing resource usage to maximize return on investment. Azure Cost Management and Billing is the primary tool for tracking, analyzing, and optimizing cloud expenses.
Monitoring and Budget Alerts
Cost Management provides cost analysis views showing spending by department, resource type, service, or location. Budgets can be set to trigger alerts when spending approaches or exceeds thresholds, helping prevent unexpected bills. Machine learning automatically detects spending anomalies to identify unusual usage patterns.
Optimization Recommendations
Cost Management recommends rightsizing virtual machines if they are consistently underutilized. It identifies development and test resources that can be turned off outside business hours. Reserved Instances for predictable workloads offer significant discounts, up to 72% for one or three-year commitments on compute resources. Spot VMs offer steep discounts for non-critical workloads that can tolerate interruptions.
Tags for Cost Governance
Tags are essential for cost governance, allowing you to categorize resources by cost center, project, or department. Track spending per business unit by tagging all development resources with 'Environment: Dev' and production resources with 'Environment: Production,' then analyze costs by these tags. Regularly reviewing Azure Advisor recommendations helps organizations identify quick wins like removing unattached disks or consolidating databases.
Compliance, Audit, and Governance Tools
Azure provides comprehensive tools for maintaining compliance and auditing resource activity. These tools work together to create a complete governance framework that ensures regulatory requirements are met while enabling controlled innovation.
Monitoring and Activity Tracking
Azure Monitor collects telemetry data from Azure resources, applications, and infrastructure, providing insights into performance and health. Activity Log tracks all control plane operations on Azure resources, showing who did what, when, and from where. This is essential for compliance audits and security investigations.
Resource Discovery and Compliance Assessment
Azure Resource Graph allows querying resource properties across subscriptions using KQL (Kusto Query Language), enabling governance teams to discover resources that do not meet standards. For example, you could query for all storage accounts without encryption enabled or all network security groups with overly permissive rules.
Compliance Manager helps organizations assess their cloud compliance status against standards like ISO 27001, HIPAA, GDPR, and PCI-DSS. It provides templates, assessment tools, and recommendations for improving compliance posture.
Repeatable Governance Frameworks
Azure Blueprints enable organizations to define a repeatable set of Azure resources, including policies, role assignments, and resource deployments. When an organization needs to create consistent, compliant environments, blueprints automate deployment of approved architectures. Blueprint versioning allows rolling back to previous compliant states if needed.
Governance Best Practices and Study Strategies
Mastering Azure governance requires understanding both theoretical concepts and practical implementation. Start by grasping the fundamental principle that governance enables organizations to maintain control while enabling innovation.
Conceptual Learning Framework
Focus on learning the relationships between services. Understand how Azure Policy enforces compliance, RBAC controls who can do what, and Cost Management ensures financial accountability. Create a mental model of the governance hierarchy from organization level down to individual resources.
Practice thinking through real-world scenarios such as setting up a new development team with appropriate access, ensuring a specific resource group complies with company encryption standards, or investigating unusual cloud spending.
Flashcard Strategy for Governance Topics
Flashcards are particularly effective for governance topics because they help you memorize specific roles, policy effects, RBAC scope levels, and compliance frameworks. Break complex topics into manageable cards, such as separate cards for each built-in role definition, each policy effect type, and each compliance framework.
Use spaced repetition to review cards regularly, strengthening neural pathways essential for exam success. Connect abstract concepts to concrete examples by creating scenario cards with a situation on the front and the governance solution on the back.
Hands-On Practice
For the AZ-900 exam, you will need to recognize governance scenarios and identify which tools and approaches apply. Practice labs in Azure's free tier help cement understanding by showing policies in action and RBAC decisions affecting resource access. Studying governance with spaced repetition systems maximizes long-term retention while building confidence in your knowledge.
