Skip to content

Commit 20add9a

Browse files
Merge pull request #233227 from EdB-MSFT/autoscale-move-region
add back moving to a different region
2 parents 7049d4d + dc029db commit 20add9a

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

articles/azure-monitor/autoscale/autoscale-get-started.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -140,6 +140,25 @@ Autoscale uses a cool-down period with is the amount of time to wait after a sca
140140

141141
Flapping refers to a loop condition that causes a series of opposing scale events. Flapping happens when one scale event triggers an opposite scale event. For example, scaling in reduces the number of instances causing the CPU to rise in the remaining instances. This in turn triggers scale out event, which causes CPU usage to drop, repeating the process. For more information, see [Flapping in Autoscale](autoscale-flapping.md) and [Troubleshooting autoscale](autoscale-troubleshoot.md)
142142

143+
## Move autoscale to a different region
144+
145+
This section describes how to move Azure autoscale to another region under the same subscription and resource group. You can use REST API to move autoscale settings.
146+
147+
### Prerequisites
148+
149+
- Ensure that the subscription and resource group are available and the details in both the source and destination regions are identical.
150+
- Ensure that Azure autoscale is available in the [Azure region you want to move to](https://azure.microsoft.com/global-infrastructure/services/?products=monitor&regions=all).
151+
152+
### Move
153+
154+
Use [REST API](/rest/api/monitor/autoscalesettings/createorupdate) to create an autoscale setting in the new environment. The autoscale setting created in the destination region will be a copy of the autoscale setting in the source region.
155+
156+
[Diagnostic settings](../essentials/diagnostic-settings.md) that were created in association with the autoscale setting in the source region can't be moved. You'll need to re-create diagnostic settings in the destination region, after the creation of autoscale settings is completed.
157+
158+
### Learn more about moving resources across Azure regions
159+
160+
To learn more about moving resources between regions and disaster recovery in Azure, see [Move resources to a new resource group or subscription](../../azure-resource-manager/management/move-resource-group-and-subscription.md).
161+
143162
## Next steps
144163

145164
- [Create an activity log alert to monitor all autoscale engine operations on your subscription](https://github.com/Azure/azure-quickstart-templates/tree/master/demos/monitor-autoscale-alert)

0 commit comments

Comments
 (0)