Skip to content

Commit c749300

Browse files
Update move-automanaged-configuration-profile.md
1 parent 467fe0b commit c749300

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/automanage/move-automanaged-configuration-profile.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,10 @@ ms.custom: subject-moving-resources
99
---
1010

1111
# Move an Azure Automanage configuration profile to a different region
12+
13+
> [!CAUTION]
14+
> On 31 August 2024, both Automation Update Management and the Log Analytics agent it uses will be retired. Migrate to Azure Update Manager before that. Refer to guidance on migrating to Azure Update Manager [here](https://learn.microsoft.com/azure/update-manager/guidance-migration-automation-update-management-azure-update-manager?WT.mc_id=Portal-Microsoft_Azure_Automation). [Migrate Now](https://ms.portal.azure.com/).
15+
1216
This article describes how to migrate an Automanage Configuration Profile to a different region. You might want to move your Configuration Profiles to another region for many reasons. For example, to take advantage of a new Azure region, to meet internal policy and governance requirements, or in response to capacity planning requirements. You may want to deploy Azure Automanage to some VMs that are in a new region. Some regions may require that you use Automanage Configuration Profiles that are local to that region.
1317

1418
## Prerequisites

0 commit comments

Comments
 (0)