Skip to content

Commit 57fa44a

Browse files
Merge pull request #289379 from usanth/patch-3
Update how-to-move-labs.md
2 parents a697050 + 6e9f13c commit 57fa44a

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

articles/devtest-labs/how-to-move-labs.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,14 @@ author: RoseHJM
88
ms.date: 09/30/2023
99
---
1010

11-
# Move DevTest Labs and schedules to another region
11+
# Move DevTest Labs and Schedules
1212

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..
1414

1515
In this article, you learn how to:
1616
> [!div class="checklist"]
1717
> >
18+
> - Move resources to different resource groups.
1819
> - Export an Azure Resource Manager (ARM) template of your lab.
1920
> - Modify the template by adding or updating the target region and other parameters.
2021
> - Deploy the template to create the new lab in the target region.
@@ -39,11 +40,18 @@ In this article, you learn how to:
3940

4041
## Move a lab
4142

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.
4344

4445
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).
4546

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
4755

4856
When you move a lab, there are some steps you must take to prepare for the move. You need to:
4957

@@ -314,7 +322,7 @@ Use the following steps to export and redeploy your schedule in another Azure re
314322

315323
## Discard or clean up
316324

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.
318326

319327
To commit the changes and complete the move, you must delete the original lab.
320328

0 commit comments

Comments
 (0)