Skip to content

Commit 43e0d4b

Browse files
authored
Merge pull request #89392 from musa-57/hanaadocslocal
OMS workspace region creation
2 parents d66f554 + 57f5022 commit 43e0d4b

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

articles/migrate/concepts-dependency-visualization.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,12 +39,15 @@ Azure Migrate uses the [Service Map](../operations-management-suite/operations-m
3939
![Add workspace](./media/how-to-create-group-machine-dependencies/workspace.png)
4040

4141
- While associating a workspace, you will get the option to create a new workspace or attach an existing one:
42-
- When you create a new workspace, you need to specify a name for the workspace. The workspace is then created in a region in the same [Azure geography](https://azure.microsoft.com/global-infrastructure/geographies/) as the migration project.
42+
- When you create a new workspace, you need to specify a name for the workspace. You can choose the [region](https://azure.microsoft.com/global-infrastructure/regions/) in which the workspace will be created.
4343
- When you attach an existing workspace, you can pick from all the available workspaces in the same subscription as the migration project. Note that only those workspaces are listed which were created in a region where [Service Map is supported](../azure-monitor/insights/vminsights-enable-overview.md#prerequisites). To be able to attach a workspace, ensure that you have 'Reader' access to the workspace.
4444

4545
> [!NOTE]
4646
> Once you have attached a workspace to a project, you cannot change it later.
4747
48+
> [!NOTE]
49+
> Azure Migrate currently supports creation of OMS workspace in East US, Southeast Asia and West Europe regions. If the workspace is created outside of Azure Migrate in any other region, it currently cannot be associated with an Azure Migrate project.
50+
4851
- The associated workspace is tagged with the key **Migration Project**, and value **Project name**, which you can use to search in the Azure portal.
4952
- To navigate to the workspace associated with the project, you can go to **Essentials** section of the project **Overview** page and access the workspace
5053

articles/migrate/how-to-create-group-machine-dependencies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Attach a workspace as follows:
5757

5858
![Add workspace](./media/how-to-create-group-machine-dependencies/workspace.png)
5959

60-
- After you specify a name for a new workspace, it's created in the same geography as the Azure Migrate project.
60+
- After you specify a name for a new workspace, you can choose the [region](https://azure.microsoft.com/global-infrastructure/regions/) in which the workspace will be created.
6161
- When you attach an existing workspace, you can pick from all the available workspaces in the same subscription as the migration project.
6262
- You need Reader access to the workspace to be able to attach it.
6363
- You can't modify the workspace associated with a project after it's attached.

0 commit comments

Comments
 (0)