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
In this article, you'll learn the steps to move Log Analytics workspace to another resource group or subscription in the same region. You can learn more about moving Azure resources through the Azure portal, PowerShell, the Azure CLI, or the REST API. at [Move resources to a new resource group or subscription](../../azure-resource-manager/management/move-resource-group-and-subscription.md).
13
16
14
17
> [!IMPORTANT]
15
-
> You can't move a workspace to a different region.
18
+
> You can't move a workspace to a different region using this procedure. Follow [move a Log Analytics workspace to another region](./move-workspace-region.md) article to move workspace across regions.
16
19
17
20
## Verify Active Directory tenant
18
21
The workspace source and destination subscriptions must exist within the same Azure Active Directory tenant. Use Azure PowerShell to verify that both subscriptions have the same tenant ID.
@@ -23,9 +26,9 @@ The workspace source and destination subscriptions must exist within the same Az
23
26
```
24
27
25
28
## Workspace move considerations
26
-
- Managed solutions that are installed in the workspace will be moved with the Log Analytics workspace move operation.
29
+
- Managed solutions that are installed in the workspace will be moved in this operation.
27
30
- Workspace keys (both primary and secondary) are re-generated with workspace move operation. If you keep a copy of your workspace keys in key vault, update them with the new keys generated after the workspace move.
28
-
- Connected agents will remain connected and keep send data to the workspace after the move.
31
+
- Connected [MMA agents](../agents/log-analytics-agent.md) will remain connected and keep send data to the workspace after the move. [AMA agents](../agents/azure-monitor-agent-overview.md) via DCR will be disconnected during the move and should be reconfigured after the move.
29
32
- Since the move operation requires that there are no Linked Services from the workspace, solutions that rely on that link must be removed to allow the workspace move. Solutions that must be removed before you can unlink your automation account:
30
33
- Update Management
31
34
- Change Tracking
@@ -57,7 +60,7 @@ Use the following procedure to remove the solutions using the Azure portal:
57
60
2. Select the solutions to remove.
58
61
3. Click **Delete Resources** and then confirm the resources to be removed by clicking **Delete**.
@@ -102,7 +105,7 @@ Use the following procedure to move your workspace using the Azure portal:
102
105
4. Select a destination **Subscription** and **Resource group**. If you're moving the workspace to another resource group in the same subscription, you won't see the **Subscription** option.
103
106
5. Click **OK** to move the workspace and selected resources.
104
107
105
-

108
+
[](media/move-workspace/portal.png#lightbox)
106
109
107
110
### PowerShell
108
111
To move your workspace using PowerShell, use the [Move-AzResource](/powershell/module/AzureRM.Resources/Move-AzureRmResource) as in the following example:
0 commit comments