Skip to content

Commit af101aa

Browse files
author
Simonx Xu
authored
Merge pull request #8887 from AmandaAZ/Branch-CI5733
AB#5733: Add a known issue
2 parents d8ac353 + db97346 commit af101aa

File tree

1 file changed

+21
-1
lines changed

1 file changed

+21
-1
lines changed

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

Lines changed: 21 additions & 1 deletion
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/02/2025
13+
ms.date: 05/08/2025
1414
ms.custom: sap:VM Performance
1515
ms.reviewer: guywild, poharjan
1616
ms.author: anandh
@@ -53,6 +53,26 @@ This article explains how to use Performance Diagnostics and what the continuous
5353

5454
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).
5555

56+
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).
57+
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+
5676
## Supported operating systems
5777

5878
### Windows

0 commit comments

Comments
 (0)