Skip to content

Commit 2adffdd

Browse files
authored
Update performance-diagnostics.md
1 parent 1fd2af9 commit 2adffdd

File tree

1 file changed

+9
-24
lines changed

1 file changed

+9
-24
lines changed

support/azure/virtual-machines/windows/performance-diagnostics.md

Lines changed: 9 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ tags: ''
1010
ms.service: azure-virtual-machines
1111
ms.workload: infrastructure-services
1212
ms.topic: troubleshooting
13-
ms.date: 05/08/2025
13+
ms.date: 06/03/2025
1414
ms.custom: sap:VM Performance
1515
ms.reviewer: guywild, poharjan
1616
ms.author: anandh
@@ -45,34 +45,19 @@ This article explains how to use Performance Diagnostics and what the continuous
4545
4646
## Permissions required
4747

48-
| Action | Permissions required |
49-
|:-----------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
50-
| Run Performance Diagnostics | The **Owner** role on the VM and an Azure role that includes the `Microsoft.Storage/storageAccounts/listkeys/action` permission on the storage account. |
51-
| View Performance Diagnostics | An Azure role that includes the `Microsoft.Storage/storageAccounts/listkeys/action` permission on the storage account or the **Storage Table Data Reader** role on the storage account. |
52-
| Download Performance Diagnostics reports | An Azure role that includes the **Storage Table Data Reader** and the **Storage Blob Data Reader** role on the storage account. |
48+
| Action | Authentication type | Permissions required |
49+
|:-|:-|:-|
50+
| Run Performance Diagnostics | Storage Account Access Keys | The **Owner** role on the VM and an Azure role that includes the **Microsoft.Storage/storageAccounts/listkeys/action** permission on the storage account. |
51+
| Run Performance Diagnostics | Managed Identities (System-assigned and User-assigned) | The **Owner** role on the VM and an Azure role that includes the **Microsoft.Storage/storageAccounts/providers/roleAssignments/write** permission on the storage account. |
52+
| View Performance Diagnostics | Storage Account Access Keys | An Azure role that includes the **Microsoft.Storage/storageAccounts/listkeys/action** permission on the storage account or the **Storage Table Data Reader** role on the storage account. |
53+
| View Performance Diagnostics | Managed Identities (System-assigned and User-assigned) | An Azure role that includes the **Storage Table Data Reader** role on the storage account. |
54+
| Download Performance Diagnostics reports | All | An Azure role that includes the **Storage Table Data Reader** role and the **Storage Blob Data Reader** role on the storage account. |
55+
5356

5457
For detailed information about built-in roles for Azure Storage, refer to [Azure built-in roles for Storage](/azure/role-based-access-control/built-in-roles/storage).
5558

5659
For more information about storage account settings, see [view and manage storage account and stored data](performance-diagnostics.md#view-and-manage-storage-account-and-stored-data).
5760

58-
### Known issue
59-
60-
Some users who previously ran Performance Diagnostics successfully encounter the following error when attempting to run it again:
61-
62-
> 'Authorization failed for template resource '\<resource>' of type 'Microsoft.Storage/storageAccounts/providers/roleAssignments'. The client '\<client>' with object id '\<ID>' does not have permission to perform action 'Microsoft.Authorization/roleAssignments/write' at scope '\<scope>'.
63-
64-
#### Cause
65-
66-
A recent rollout has a bug that tries to grant the write permission to the storage account for the current user when initiating a run from the Azure portal. An Azure role that includes the `Microsoft.Storage/storageAccounts/listkeys/action` permission isn't enough to grant this permission, causing the run to fail.
67-
68-
#### Status
69-
70-
A fix is being deployed.
71-
72-
#### Workaround
73-
74-
If users still encounter this issue, grant the `Microsoft.Authorization/roleAssignments/write` permission to the storage account with the **Role Based Access Control Administrator** or **User Access Administrator** role. The latter role can grant higher permissions.
75-
7661
## Supported operating systems
7762

7863
### Windows

0 commit comments

Comments
 (0)