Skip to content

Commit 003b5bf

Browse files
authored
Update delete-workspace.md
Fixed the note that wasn't rendering properly and made some minor language and format changes.
1 parent 00e1c6a commit 003b5bf

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

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

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -57,26 +57,26 @@ PS C:\>Remove-AzOperationalInsightsWorkspace -ResourceGroupName "resource-group-
5757

5858
## Permanent workspace delete
5959

60-
The soft-delete method may not fit in some scenarios such as development and testing, where you need to repeat a deployment with the same settings and workspace name. You can permanently delete your workspace and override the soft-delete period. The permanent workspace delete operation releases the workplace name and you can create a new workspace using the same name.
60+
The soft-delete method may not fit in some scenarios such as development and testing, where you need to repeat a deployment with the same settings and workspace name. You can permanently delete your workspace and override the soft-delete period. The permanent workspace delete operation releases the workplace name, and you can create a new workspace using the same name.
6161

62-
> [!Important]
63-
> Use cautious when permanently deleting your workspace since the operation is irreversible and your workspace and its data won’t be recoverable.
62+
> [!IMPORTANT]
63+
> Use caution when permanently deleting your workspace since the operation is irreversible, and your workspace and its data won’t be recoverable.
6464
65-
The permanent workspace delete can be performed via REST API currently.
65+
The permanent workspace delete can currently be performed via REST API.
6666

67-
> [Information]
67+
> [!NOTE]
6868
> Any API request must include a Bearer authorization token in the request header.
6969
>
7070
> You can acquire the token using:
7171
> - [App registrations](https://docs.microsoft.com/graph/auth/auth-concepts#access-tokens)
72-
> - Navigate to Azure portal in “developer tool” (F12), look in one of the batch? instances and look for the authentication string under Request Headers” – it looks like this: “authorization: Bearer <token>. Copy and add it to your API call as shown in the examples.
73-
> - Navigate to Azure REST documentation sitepress Try it on any API and copy the Bearer token and add it to your API call.
72+
> - Navigate to Azure portal using the developer's console (F12) in the browser. Look in one of the **batch?** instances for the authentication string under **Request Headers**. This will be in the pattern *authorization: Bearer <token>*. Copy and add this to your API call as shown in the examples.
73+
> - Navigate to the Azure REST documentation site. press **Try it** on any API, copy the Bearer token, and add it to your API call.
7474
To permanently delete your workspace, use the [Workspaces - Delete REST]( https://docs.microsoft.com/rest/api/loganalytics/workspaces/delete) API call with a force tag:
75-
76-
```rst
77-
DELETE https://management.azure.com/subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/Microsoft.OperationalInsights/workspaces/<workspace-name>?api-version=2015-11-01-preview&force=true
78-
Authorization: Bearer eyJ0eXAiOiJKV1Qi….
79-
```
75+
>
76+
> ```rst
77+
> DELETE https://management.azure.com/subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/Microsoft.OperationalInsights/workspaces/<workspace-name>?api-version=2015-11-01-preview&force=true
78+
> Authorization: Bearer eyJ0eXAiOiJKV1Qi….
79+
> ```
8080
8181
## Recover workspace
8282

0 commit comments

Comments
 (0)