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
description: Describes how to view Azure Resource Manager deployment operations with the portal, PowerShell, Azure CLI, and REST API.
4
4
tags: top-support-issue
5
5
ms.topic: conceptual
6
-
ms.date: 05/13/2019
6
+
ms.date: 11/25/2019
7
7
---
8
8
# View deployment history with Azure Resource Manager
9
9
10
10
Azure Resource Manager enables you to view your deployment history and examine specific operations in past deployments. You can see the resources that were deployed, and get information about any errors.
11
11
12
12
For help with resolving particular deployment errors, see [Resolve common errors when deploying resources to Azure with Azure Resource Manager](resource-manager-common-deployment-errors.md).
13
13
14
-
## Portal
14
+
## Get deployment
15
+
16
+
To get details about a deployment from the deployment history use portal, PowerShell, Azure CLI, or REST API.
15
17
16
-
To get details about a deployment from the deployment history.
18
+
#### [Browser](#tab/browser)
17
19
18
20
1. Select the resource group you want to examine.
19
21
@@ -25,123 +27,31 @@ To get details about a deployment from the deployment history.
1. A summary of the deployment is displayed, including the correlation ID. The correlation ID is used to track related events, and can be helpful when working with technical support to troubleshoot a deployment.
To get the overall status of a deployment, use the **Get-AzResourceGroupDeployment** command.
36
+
To list all deployments for a resource group, use the [Get-AzResourceGroupDeployment](/powershell/module/az.resources/Get-AzResourceGroupDeployment) command.
The correlation ID is used to track related events, and can be helpful when working with technical support to troubleshoot a deployment. To get the correlation ID, use:
Each deployment includes multiple operations. Each operation represents a step in the deployment process. To discover what went wrong with a deployment, you usually need to see details about the deployment operations. You can see the status of the operations with **Get-AzResourceGroupDeploymentOperation**.
Note the serviceRequestId and the trackingId for the operation. The serviceRequestId can be helpful when working with technical support to troubleshoot a deployment. You'll use the trackingId in the next step to focus on a particular operation.
119
-
120
-
To get the status message of a particular failed operation, use the following command:
48
+
The correlation ID is used to track related events. It can be helpful when working with technical support to troubleshoot a deployment. To get the correlation ID, use:
DnsRecordInUse DNS record dns.westus.cloudapp.azure.com is already used by another public IP. {}
132
-
```
133
-
134
-
Every deployment operation in Azure includes request and response content. During deployment, you can use **DeploymentDebugLogLevel** parameter to specify that the request and/or response are logged.
135
-
136
-
You get that information from the log, and save it locally by using the following PowerShell commands:
To get the overall status of a deployment, use the **azure group deployment show** command.
147
57
@@ -155,13 +65,7 @@ The correlation ID is used to track related events, and can be helpful when work
155
65
az group deployment show -g ExampleGroup -n ExampleDeployment --query properties.correlationId
156
66
```
157
67
158
-
To see the operations for a deployment, use:
159
-
160
-
```azurecli-interactive
161
-
az group deployment operation list -g ExampleGroup -n ExampleDeployment
162
-
```
163
-
164
-
## REST
68
+
#### [HTTP](#tab/http)
165
69
166
70
The following example shows how to get information about a deployment. For documentation about the latest API version, see the [Deployments - Get](/rest/api/resources/deployments/get) operation.
167
71
@@ -186,6 +90,41 @@ In the response, note in particular the **provisioningState**, **correlationId**
186
90
}
187
91
```
188
92
93
+
---
94
+
95
+
## Get deployment operations
96
+
97
+
To get details about a deployment from the deployment history use portal, PowerShell, Azure CLI, or REST API.
98
+
99
+
#### [Browser](#tab/browser)
100
+
101
+
1. To see deployment operations, select **Operation details**.
Each deployment includes multiple operations. Each operation represents a step in the deployment process. To discover what went wrong with a deployment, you usually need to see details about the deployment operations. You can see the status of the operations with **Get-AzResourceGroupDeploymentOperation**.
az group deployment operation list -g ExampleGroup -n ExampleDeployment
124
+
```
125
+
126
+
#### [HTTP](#tab/http)
127
+
189
128
The following example shows how to get deployment operations. For documentation about the latest API version, see the [Deployment Operations - List](/rest/api/resources/deploymentoperations/list) operation.
190
129
191
130
```
@@ -219,7 +158,76 @@ The response includes request and/or response information based on what you spec
219
158
}
220
159
```
221
160
161
+
---
162
+
163
+
## Portal
164
+
165
+
166
+
1. If your deployment failed, you see an error message. Select the error message for more details.
Note the serviceRequestId and the trackingId for the operation. The serviceRequestId can be helpful when working with technical support to troubleshoot a deployment. You'll use the trackingId in the next step to focus on a particular operation.
204
+
205
+
To get the status message of a particular failed operation, use the following command:
DnsRecordInUse DNS record dns.westus.cloudapp.azure.com is already used by another public IP. {}
217
+
```
218
+
219
+
Every deployment operation in Azure includes request and response content. During deployment, you can use **DeploymentDebugLogLevel** parameter to specify that the request and/or response are logged.
220
+
221
+
You get that information from the log, and save it locally by using the following PowerShell commands:
* For help with resolving particular deployment errors, see [Resolve common errors when deploying resources to Azure with Azure Resource Manager](resource-manager-common-deployment-errors.md).
224
232
* To learn about using the activity logs to monitor other types of actions, see [View activity logs to manage Azure resources](resource-group-audit.md).
225
233
* To validate your deployment before executing it, see [Deploy a resource group with Azure Resource Manager template](resource-group-template-deploy.md).
0 commit comments