You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/devtest-labs/how-to-move-labs.md
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,13 +8,14 @@ author: RoseHJM
8
8
ms.date: 09/30/2023
9
9
---
10
10
11
-
# Move DevTest Labs and schedules to another region
11
+
# Move DevTest Labs and Schedules
12
12
13
-
You can move DevTest Labs and their associated schedules to another region. To move a lab, create a copy of an existing lab in another region. When you've moved your lab, and you have a virtual machine (VM) in the target region, you can move your lab schedules.
13
+
You can move DevTest Labs and their associated schedules to another region or resource group. You can move resource groups through the Azure Portal. To move a lab, create a copy of an existing lab in another region. When you've moved your lab, and you have a virtual machine (VM) in the target region, you can move your lab schedules..
14
14
15
15
In this article, you learn how to:
16
16
> [!div class="checklist"]
17
17
> >
18
+
> - Move resources to different resource groups.
18
19
> - Export an Azure Resource Manager (ARM) template of your lab.
19
20
> - Modify the template by adding or updating the target region and other parameters.
20
21
> - Deploy the template to create the new lab in the target region.
@@ -39,11 +40,18 @@ In this article, you learn how to:
39
40
40
41
## Move a lab
41
42
42
-
The following section describes how to create and customize an ARM template to move a lab from one region to another.
43
+
The following section describes how to move resources to a different resource group and create and customize an ARM template to move a lab from one region to another.
43
44
44
45
You can move a schedule without moving a lab, if you have a VM in the target region. If you want to move a schedule without moving a lab, see [Move a schedule](#move-a-schedule).
45
46
46
-
### Prepare to move a lab
47
+
### Move Resource Groups using Azure Portal
48
+
Moving resources between resource groups in different locations is now seamlessly enabled in DevTest Labs. You can effortlessly transfer any resource from one group to another within the same subscription.
49
+
50
+
To begin, select the resource you wish to move. On the resource's **Overview** page, you'll find the current **Resource Group** displayed at the top. Next to the resource group name, you'll see the word `(move)` in parentheses.
51
+
52
+
Click the hyperlinked `move` text, which will direct you to a new page where you can relocate the resource to any other resource group within the same subscription. Please note that moving the resource will not change its location, even if the destination resource group is in a different location. If you're not moving resources through the Azure Portal or if you're transferring to a resource group in a different subscription, alternative methods using ARM are outlined below.
53
+
54
+
### Move Labs to a Different Region
47
55
48
56
When you move a lab, there are some steps you must take to prepare for the move. You need to:
49
57
@@ -314,7 +322,7 @@ Use the following steps to export and redeploy your schedule in another Azure re
314
322
315
323
## Discard or clean up
316
324
317
-
After the deployment, if you want to start over, you can delete the target lab, and repeat the steps described in the [Prepare](#prepare-to-move-a-lab) and [Move](#deploy-the-template-to-move-the-lab) sections of this article.
325
+
After the deployment, if you want to start over, you can delete the target lab, and repeat the steps described in the [Prepare](#move-labs-to-a-different-region) and [Move](#deploy-the-template-to-move-the-lab) sections of this article.
318
326
319
327
To commit the changes and complete the move, you must delete the original lab.
0 commit comments