Resource-group organization should reflect common management requirements. In this case, a team places all test and prod resources in one group to reduce overhead. “Separate resources by appropriate lifecycle and ownership boundaries” would not satisfy that requirement; the supported action is “Plan resource groups and subscriptions aligned to operational boundaries”. Administrative hierarchy reduces accidental cross-environment management.

Resource groups organize management, deployment and access around related resources. In this case, a team places all test and prod resources in one group to reduce overhead. “Place related resources in one logically scoped resource group” would not satisfy that requirement; the supported action is “Plan resource groups and subscriptions aligned to operational boundaries”. Administrative hierarchy reduces accidental cross-environment management.

An initiative groups multiple policy definitions for combined assignment and reporting. In this case, a team places all test and prod resources in one group to reduce overhead. “An Azure Policy initiative with associated definitions” would not satisfy that requirement; the supported action is “Plan resource groups and subscriptions aligned to operational boundaries”. Administrative hierarchy reduces accidental cross-environment management.

Resource-group location governs its metadata, not mandatory region of all contained resources. In this case, a resource group contains multiple VMs that should share lifecycle management. “No; resource group metadata location need not equal every resource's location” would not satisfy that requirement; the supported action is “Place related resources in one logically scoped resource group”. Resource groups organize management, deployment and access around related resources.

Most Azure resource deployments select region independently of containing group metadata. In this case, a resource group contains multiple VMs that should share lifecycle management. “Specify the VM's own supported deployment location” would not satisfy that requirement; the supported action is “Place related resources in one logically scoped resource group”. Resource groups organize management, deployment and access around related resources.

Administrative hierarchy reduces accidental cross-environment management. In this case, a resource group contains multiple VMs that should share lifecycle management. “Plan resource groups and subscriptions aligned to operational boundaries” would not satisfy that requirement; the supported action is “Place related resources in one logically scoped resource group”. Resource groups organize management, deployment and access around related resources.

Administrative hierarchy reduces accidental cross-environment management. In this case, two unrelated applications share a resource group and deletion planning is confusing. “Plan resource groups and subscriptions aligned to operational boundaries” would not satisfy that requirement; the supported action is “Separate resources by appropriate lifecycle and ownership boundaries”. Resource-group organization should reflect common management requirements.

Resource-group location governs its metadata, not mandatory region of all contained resources. In this case, two unrelated applications share a resource group and deletion planning is confusing. “No; resource group metadata location need not equal every resource's location” would not satisfy that requirement; the supported action is “Separate resources by appropriate lifecycle and ownership boundaries”. Resource-group organization should reflect common management requirements.

Most Azure resource deployments select region independently of containing group metadata. In this case, two unrelated applications share a resource group and deletion planning is confusing. “Specify the VM's own supported deployment location” would not satisfy that requirement; the supported action is “Separate resources by appropriate lifecycle and ownership boundaries”. Resource-group organization should reflect common management requirements.

Resource groups organize management, deployment and access around related resources. In this case, a resource group was created in East US but contains a VM in West Europe. Is this inherently invalid? “Place related resources in one logically scoped resource group” would not satisfy that requirement; the supported action is “No; resource group metadata location need not equal every resource's location”. Resource-group location governs its metadata, not mandatory region of all contained resources.

Resource-group organization should reflect common management requirements. In this case, a resource group was created in East US but contains a VM in West Europe. Is this inherently invalid? “Separate resources by appropriate lifecycle and ownership boundaries” would not satisfy that requirement; the supported action is “No; resource group metadata location need not equal every resource's location”. Resource-group location governs its metadata, not mandatory region of all contained resources.

Subscriptions inherit controls only from their actual management-group ancestors. In this case, a resource group was created in East US but contains a VM in West Europe. Is this inherently invalid? “It is outside the targeted management group hierarchy” would not satisfy that requirement; the supported action is “No; resource group metadata location need not equal every resource's location”. Resource-group location governs its metadata, not mandatory region of all contained resources.

Resource groups organize management, deployment and access around related resources. In this case, an admin assumes the resource-group region automatically controls VM region. “Place related resources in one logically scoped resource group” would not satisfy that requirement; the supported action is “Specify the VM's own supported deployment location”. Most Azure resource deployments select region independently of containing group metadata.

Resource-group organization should reflect common management requirements. In this case, an admin assumes the resource-group region automatically controls VM region. “Separate resources by appropriate lifecycle and ownership boundaries” would not satisfy that requirement; the supported action is “Specify the VM's own supported deployment location”. Most Azure resource deployments select region independently of containing group metadata.

Subscriptions inherit controls only from their actual management-group ancestors. In this case, an admin assumes the resource-group region automatically controls VM region. “It is outside the targeted management group hierarchy” would not satisfy that requirement; the supported action is “Specify the VM's own supported deployment location”. Most Azure resource deployments select region independently of containing group metadata.

Resource-group location governs its metadata, not mandatory region of all contained resources. In this case, a global organization needs governance consistently across 12 subscriptions. “No; resource group metadata location need not equal every resource's location” would not satisfy that requirement; the supported action is “At an appropriate ancestor management group”. Management-group assignment reduces repeated per-subscription policy management.

Azure resource move operations have resource-type and dependency restrictions. In this case, a global organization needs governance consistently across 12 subscriptions. “Check resource type move support and dependencies before moving” would not satisfy that requirement; the supported action is “At an appropriate ancestor management group”. Management-group assignment reduces repeated per-subscription policy management.

Most Azure resource deployments select region independently of containing group metadata. In this case, a global organization needs governance consistently across 12 subscriptions. “Specify the VM's own supported deployment location” would not satisfy that requirement; the supported action is “At an appropriate ancestor management group”. Management-group assignment reduces repeated per-subscription policy management.

Resource-group location governs its metadata, not mandatory region of all contained resources. In this case, a new subscription is excluded from central governance unexpectedly. “No; resource group metadata location need not equal every resource's location” would not satisfy that requirement; the supported action is “It is outside the targeted management group hierarchy”. Subscriptions inherit controls only from their actual management-group ancestors.

Azure resource move operations have resource-type and dependency restrictions. In this case, a new subscription is excluded from central governance unexpectedly. “Check resource type move support and dependencies before moving” would not satisfy that requirement; the supported action is “It is outside the targeted management group hierarchy”. Subscriptions inherit controls only from their actual management-group ancestors.

Most Azure resource deployments select region independently of containing group metadata. In this case, a new subscription is excluded from central governance unexpectedly. “Specify the VM's own supported deployment location” would not satisfy that requirement; the supported action is “It is outside the targeted management group hierarchy”. Subscriptions inherit controls only from their actual management-group ancestors.

Management-group assignment reduces repeated per-subscription policy management. In this case, a subscription administrator needs to move resources between supported resource groups. “At an appropriate ancestor management group” would not satisfy that requirement; the supported action is “Check resource type move support and dependencies before moving”. Azure resource move operations have resource-type and dependency restrictions.

Subscriptions inherit controls only from their actual management-group ancestors. In this case, a subscription administrator needs to move resources between supported resource groups. “It is outside the targeted management group hierarchy” would not satisfy that requirement; the supported action is “Check resource type move support and dependencies before moving”. Azure resource move operations have resource-type and dependency restrictions.

Policy evaluation applies to compliant deployments independent of template syntax. In this case, a subscription administrator needs to move resources between supported resource groups. “Choose a policy-permitted region instead of bypassing governance” would not satisfy that requirement; the supported action is “Check resource type move support and dependencies before moving”. Azure resource move operations have resource-type and dependency restrictions.

Policy evaluation applies to compliant deployments independent of template syntax. In this case, a VM cannot be moved because its attached networking dependency is in an incompatible scope. “Choose a policy-permitted region instead of bypassing governance” would not satisfy that requirement; the supported action is “Supported move requirements for the VM and associated resources”. Moving an Azure resource can require moving related dependent resources together.

Templates must satisfy effective policy, not merely have valid JSON. In this case, a VM cannot be moved because its attached networking dependency is in an incompatible scope. “Parameterize location to select an approved region” would not satisfy that requirement; the supported action is “Supported move requirements for the VM and associated resources”. Moving an Azure resource can require moving related dependent resources together.

Subscriptions inherit controls only from their actual management-group ancestors. In this case, a VM cannot be moved because its attached networking dependency is in an incompatible scope. “It is outside the targeted management group hierarchy” would not satisfy that requirement; the supported action is “Supported move requirements for the VM and associated resources”. Moving an Azure resource can require moving related dependent resources together.

Tagging and cost allocation do not automatically create notification delivery. In this case, an enterprise enforces region placement via an allowed-locations policy. “Budget notification configuration and contact recipients” would not satisfy that requirement; the supported action is “Parameterize location to select an approved region”. Templates must satisfy effective policy, not merely have valid JSON.

Cost Management budget notifications can route threshold emails to recipients. In this case, an enterprise enforces region placement via an allowed-locations policy. “Budget alert notification contact settings” would not satisfy that requirement; the supported action is “Parameterize location to select an approved region”. Templates must satisfy effective policy, not merely have valid JSON.

Moving an Azure resource can require moving related dependent resources together. In this case, an enterprise enforces region placement via an allowed-locations policy. “Supported move requirements for the VM and associated resources” would not satisfy that requirement; the supported action is “Parameterize location to select an approved region”. Templates must satisfy effective policy, not merely have valid JSON.

Tagging and cost allocation do not automatically create notification delivery. In this case, a Bicep deployment is technically valid but denied in an unapproved region. “Budget notification configuration and contact recipients” would not satisfy that requirement; the supported action is “Choose a policy-permitted region instead of bypassing governance”. Policy evaluation applies to compliant deployments independent of template syntax.

Cost Management budget notifications can route threshold emails to recipients. In this case, a Bicep deployment is technically valid but denied in an unapproved region. “Budget alert notification contact settings” would not satisfy that requirement; the supported action is “Choose a policy-permitted region instead of bypassing governance”. Policy evaluation applies to compliant deployments independent of template syntax.

Moving an Azure resource can require moving related dependent resources together. In this case, a Bicep deployment is technically valid but denied in an unapproved region. “Supported move requirements for the VM and associated resources” would not satisfy that requirement; the supported action is “Choose a policy-permitted region instead of bypassing governance”. Policy evaluation applies to compliant deployments independent of template syntax.