Skip to content

Commit 0bfff38

Browse files
authored
Update how-to-move-schedule-to-new-region.md
Transferring updates from dtl branch
1 parent ae0eca2 commit 0bfff38

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

articles/devtest-labs/how-to-move-schedule-to-new-region.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,25 @@
11
---
2-
title: How to move a Microsoft.DevtestLab/schedules to another region
3-
description: This article explains how to move Microsoft.DevtestLab/schedules to another Azure region.
2+
title: How to move a schedule to another region
3+
description: This article explains how to move schedules to another Azure region.
44
ms.topic: how-to
55
ms.author: rosemalcolm
66
author: RoseHJM
77
ms.date: 05/09/2022
88
---
9-
# Move Microsoft.DevtestLab/schedules to another region
9+
# Move schedules to another region
1010

11-
Microsoft.DevtestLab/schedules apply only to Compute Virtual Machines (VMs). They are often referred to as top level schedules, or simply schedules. In this article, you'll learn how to move schedules.
11+
In this article, you'll learn how to move schedules by using an Azure Resource Manager (ARM) template.
1212

13-
Microsoft.DevTestLab/labs/schedules apply only to DevTest Labs (DTL) VMs. They are often referred to as Lab schedules. This type of schedule is not covered in this article.
13+
DevTest Labs supports two types of schedules.
1414

15-
To move schedules, use an Azure Resource Manager (ARM) template to create a copy of the existing schedules in another region.
15+
- Schedules apply only to compute virtual machines (VMs): schedules are stored as microsoft.devtestlab/schedules resources, and often referred to as top level schedules, or simply schedules.
16+
17+
- Lab schedules apply only to DevTest Labs (DTL) VMs: lab schedules They are stored as microsoft.devtestlab/labs/schedules resources. This type of schedule is not covered in this article.
1618

1719
In this article, you'll learn how to:
1820
> [!div class="checklist"]
1921
> >
20-
> - Export an ARM template that contains your Microsoft.DevtestLab/schedules.
22+
> - Export an ARM template that contains your schedules.
2123
> - Modify the template by adding or updating the target region and other parameters.
2224
> - Delete the resources in the source region.
2325
@@ -41,7 +43,7 @@ Use the following steps to export and redeploy your schedule in another Azure re
4143

4244
3. On the **Resource Group Overview** page, under **Resources**, select **Show hidden types**.
4345

44-
4. Select all resources with the type **Microsoft.DevTestLab/Schedules**.
46+
4. Select all resources with the type **microsoft.devtestlab/schedules**.
4547

4648
5. Select **Export template**.
4749

@@ -78,7 +80,7 @@ Now you can choose to clean up the original schedules if they're longer used. Go
7880

7981
## Next steps
8082

81-
In this article, you moved a schedule from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, refer to:
83+
In this article, you moved a schedule from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, refer to:
8284

8385
- [Move a DevTest Labs to another region](./how-to-move-labs.md).
8486
- [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).

0 commit comments

Comments
 (0)