Skip to content

Commit b2357ea

Browse files
authored
Merge pull request #101067 from yossi-y/patch-37
Added recovery powershell
2 parents 35b1ef4 + 49c0608 commit b2357ea

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

articles/azure-monitor/platform/delete-workspace.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.subservice: logs
66
ms.topic: conceptual
77
author: bwren
88
ms.author: bwren
9-
ms.date: 10/28/2019
9+
ms.date: 01/14/2020
1010

1111
---
1212

@@ -52,7 +52,7 @@ You can delete a workspace using [PowerShell](https://docs.microsoft.com/powersh
5252

5353
### PowerShell
5454
```PowerShell
55-
PS C:\>Remove-AzOperationalInsightsWorkspace -ResourceGroupName "ContosResourceGroup" -Name "MyWorkspace"
55+
PS C:\>Remove-AzOperationalInsightsWorkspace -ResourceGroupName "resource-group-name" -Name "workspace-name"
5656
```
5757

5858
## Recover workspace
@@ -66,6 +66,12 @@ You can recover a workspace by re-creating it using the following workspace crea
6666
* Workspace name
6767
* Region
6868

69+
### PowerShell
70+
```PowerShell
71+
PS C:\>Select-AzSubscription "subscription-name-the-workspace-was-in"
72+
PS C:\>New-AzOperationalInsightsWorkspace -ResourceGroupName "resource-group-name-the-workspace-was-in" -Name "deleted-workspace-name" -Location "region-name-the-workspace-was-in"
73+
```
74+
6975
The workspace and all its data are brought back after the recovery operation. Solutions and linked services were permanently removed from the workspace when it was deleted and these should be reconfigured to bring the workspace to its previously configured state. Some of the data may not be available for query after the workspace recovery until the associated solutions are re-installed and their schemas are added to the workspace.
7076

7177
> [!NOTE]

0 commit comments

Comments
 (0)