Rediģēt

Kopīgot, izmantojot

Azure landing zone governance guide: Migrate Azure landing zone policies to Azure built-in policies

  • Raksts

Over time, Azure landing zone custom policies and policy initiatives might be deprecated or superseded by Azure built-in policies. If so, they should be removed or migrated. This article describes how to migrate Azure landing zone custom policies and policy initiatives to Azure built-in policies.

The guidance in this document describes the manual, high-level steps for your policies migration. It also provides references on how to process implementations managed through the Azure landing zone Terraform module or ALZ-Bicep.

The following infographic shows the update process flow.

Diagram that shows the policy update process flow going from Azure landing zone custom policies to built-in policies.

Manual update steps for Azure landing zone environments

This section describes the generic, high-level steps to migrate Azure landing zone custom policies and initiatives to Azure built-in policies.

Detect updates for Azure landing zone policies

You can detect that one or more Azure landing zone policies are superseded by built-in Azure policies with the following options:

Migration steps for Azure landing zone policies

You can migrate Azure landing zone environments with the following steps:

  1. Determine if the Azure landing zone policies in scope for migration are currently assigned at any scope in your Azure estate. If you're using the Azure Governance Visualizer, you can determine policy scope by checking the TenantSummary.
  2. Check if the Azure landing zone policies being migrated are part of a landing zone custom policy initiative that should be updated.
  3. See if Azure landing zone custom policy initiatives in scope for migration are currently assigned at any scope in your Azure estate.

Depending on the results of your investigation, take the following actions.

Policies not assigned and not part of Azure landing zone custom policy initiative

If the policy being migrated isn't assigned in your Azure estate, and isn't part of an existing Azure landing zone custom policy initiative, you:

  • Delete the Azure landing zone policy definition from the Azure landing zone intermediate root management group (for example, Contoso).

If an Azure landing zone custom policy initiative is fully superseded by a built-in policy initiative and isn't assigned in your Azure estate, you:

  • Delete the Azure landing zone custom policy initiative from the Azure landing zone intermediate root management group (for example, Contoso).

Policies assigned and not part of Azure landing zone custom policy initiative

If the policy to be migrated is assigned to any scope in your Azure estate, and isn't part of an existing Azure landing zone custom policy initiative, do these steps:

  1. Create new policy assignments at the same scopes using the Azure built-in policies with matching settings as per the assignment of the previous Azure landing zone custom policy definition.
  2. Delete existing Azure landing zone policy assignment at all scopes, where assigned.
  3. Delete the Azure landing zone policy definition from the Azure landing zone intermediate root management group (for example Contoso).

For detailed guidance on how to do the previous steps, see Migrate single Azure landing zone custom policy.

Policies assigned through Azure landing zone custom policy initiative

If the policy to be migrated is part of an Azure landing zone custom policy initiative and is assigned through it at any scope in your Azure estate, follow these steps:

  1. Update the Azure landing zone custom policy initiative definition with the appropriate policy references. You can find the updated initiatives here with a generic contoso scope for custom policies.
  2. When you update the policy references, remember to change the contoso scope for policy definition IDs to your management group hierarchy pseudo root name. Also, update the metadata information on the Azure landing zone custom policy initiative.

For detailed guidance on how to do the previous steps, see How to update child definitions in Azure landing zone custom initiatives.

If an Azure landing zone custom policy initiative is fully superseded by a built-in policy initiative, and assigned at any scope in your Azure estate, follow these steps:

  1. Create new policy initiative assignments at the same scopes. Use the Azure built-in policy initiative with matching settings per the assignment of the previous Azure landing zone custom policy initiative.
  2. Delete existing Azure landing zone policy initiative assignment at all scopes, where assigned.
  3. Delete the Azure landing zone custom policy initiative from the Azure landing zone intermediate root management group (for example, Contoso).

Update steps for Azure landing zone Terraform module deployments

If you're using the Azure landing zone Terraform module to manage your Azure landing zone deployment, this section references resources on how to migrate Azure landing zone custom policies and initiatives to Azure built-in policies.

Detect updates for Terraform module changes

Use the methods described in Detect updates for Azure landing zone policies to determine whether policies have changed in the Terraform module. You'll also see changes to policies in the Azure landing zone Terraform releases page. See an example here.

Migration steps for Azure landing zone Terraform module

The Azure landing zone Terraform module provides update guidance when deploying breaking changes. Follow the upgrade guidance available for your specific version here at the bottom of the page.

Update steps for ALZ-Bicep deployments

If you're using the ALZ-Bicep to manage your Azure landing zone deployment, this section references resources on how to migrate Azure landing zone custom policies and initiatives to Azure built-in policies.

Detect updates for ALZ-Bicep policy changes

Use the methods described in Detect updates for Azure landing zone policies to determine whether policies have changed in ALZ-Bicep. You'll also see changes to policies in ALZ-Bicep releases.

Migration steps for ALZ-Bicep policies

ALZ-Bicep provides generic guidance for migrating policies from Azure landing zone custom policies to Azure built-in policies. For more information, see How to migrate Azure landing zone custom policies to Azure built-in policies.

Next steps

Regardless of whether you use Azure portal, Bicep, or Terraform to manage your Azure landing zone infrastructure, policies change over time. You'll need to manage them. Use the flow described in this article as a starting point to develop processes around policy management for your specific Azure landing zone implementation.