Configure Azure Policy Flashcards
Create management groups
Organizations that use multiple subscriptions need a way to efficiently manage access, policies, and compliance. Azure management groups provide a level of scope and control above your subscriptions. You can use management groups as containers to manage access, policy, and compliance across your subscriptions.
Consider the following characteristics of Azure management groups:
By default, all new subscriptions are placed under the top-level management group, or root group.
All subscriptions within a management group automatically inherit the conditions applied to that management group.
A management group tree can support up to six levels of depth.
Azure role-based access control authorization for management group operations isn’t enabled by default.
Consider custom hierarchies and groups
Align your Azure subscriptions by using custom hierarchies and grouping that meet your company’s organizational structure and business scenarios. You can use management groups to target policies and spending budgets across subscriptions.
Consider policy inheritance.
Control the hierarchical inheritance of access and privileges in policy definitions. All subscriptions within a management group inherit the conditions applied to the management group. You can apply policies to a management group to limit the regions available for creating virtual machines (VMs). The policy can be applied to all management groups, subscriptions, and resources under the initial management group, to ensure VMs are created only in the specified regions.
Consider compliance rules
Organize your subscriptions into management groups to help meet compliance rules for individual departments and teams.
Consider cost reporting.
Use management groups to do cost reporting by department or for specific business scenarios. You can use management groups to report on budget details across subscriptions.
Create management groups
You can create a management group with Azure Policy by using the Azure portal, PowerShell, or the Azure CLI
A management group has a directory unique identifier (ID) and a display name. The ID is used to submit commands on the management group. The ID value can’t be changed after it’s created because it’s used throughout the Azure system to identify the management group. The display name for the management group is optional and can be changed at any time.
Azure Policy Enforce rules and compliance
Enable built-in policies, or build custom policies for all resource types. Support real-time policy evaluation and enforcement, and periodic or on-demand compliance evaluation.
Azure Policy Apply policies at scale
Apply policies to a management group with control across your entire organization. Apply multiple policies and aggregate policy states with policy initiative. Define an exclusion scope.
Azure Policy Perform remediation
Conduct real-time remediation, and remediation on your existing resources.
Azure Policy Exercise governance
Implement governance tasks for your environment:
- Support multiple engineering teams (deploying to and operating in the environment)
- Manage multiple subscriptions
- Standardize and enforce how cloud resources are configured
- Manage regulatory compliance, cost control, security, and design consistency
Consider deployable resources
Specify the resource types that your organization can deploy by using Azure Policy. You can specify the set of virtual machine SKUs that your organization can deploy.
Consider location restrictions
Restrict the locations your users can specify when deploying resources. You can choose the geographic locations or regions that are available to your organization.
Consider rules enforcement
Enforce compliance rules and configuration options to help manage your resources and user options. You can enforce a required tag on resources and define the allowed values.
Consider inventory audits
Use Azure Policy with Azure Backup service on your VMs and run inventory audits.