Skip to content

Commit d7e419d

Browse files
Merge pull request #17039 from alkohli/secrot
Added steps to rotate cluster witness SA access key
2 parents 512c943 + bdd188b commit d7e419d

File tree

1 file changed

+44
-1
lines changed

1 file changed

+44
-1
lines changed

azure-local/manage/manage-secrets-rotation.md

Lines changed: 44 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article describes how to manage internal secret rotation on Az
44
author: alkohli
55
ms.author: alkohli
66
ms.topic: how-to
7-
ms.date: 02/03/2025
7+
ms.date: 02/11/2025
88
ms.service: azure-local
99
---
1010

@@ -59,6 +59,49 @@ WARNING: Please close this session and log in again.
5959
PS C:\Users\MGMT>
6060
```
6161

62+
## Change cluster witness storage account key
63+
64+
This section describes how you can change the storage account key for the cluster witness storage account.
65+
66+
1. Sign in to one of the Azure Local nodes using deployment user credentials.
67+
68+
1. Configure the witness quorum using the secondary storage account key:
69+
70+
```powershell
71+
Set-ClusterQuorum -CloudWitness -AccountName <storage account name> -AccessKey <storage account secondary key>
72+
```
73+
74+
1. Rotate the storage account primary key.
75+
76+
1. Configure the witness quorum using the rotated storage account key:
77+
78+
```powershell
79+
Set-ClusterQuorum -CloudWitness -AccountName <storage account name> -AccessKey <storage account primary key>
80+
```
81+
82+
1. Rotate the storage account secondary key.
83+
84+
1. Update the storage account primary key in the ECE store:
85+
86+
```powershell
87+
$SecureSecretText = ConvertTo-SecureString -String "<Replace Storage account key>" -AsPlainText -Force
88+
$WitnessCred = New-Object -Type PSCredential -ArgumentList "WitnessCredential,$SecureSecretText"
89+
Set-ECEServiceSecret -ContainerName WitnessCredential -Credential $WitnessCred
90+
```
91+
92+
## Revoke SAS token for storage account used for Arc VM images
93+
94+
This section describes how you can revoke the Shared Access Signature (SAS) token for the storage account used for Arc VM images.
95+
96+
| SAS policy | SAS expired? | Steps to revoke |
97+
|---------|---------|---------|
98+
| Any SAS | Yes | No action is required as the SAS is no longer valid. |
99+
| Ad hoc SAS signed with an account key | No | [Manually rotate or regenerate Storage account key](/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#manually-rotate-access-keys) used to create SAS. |
100+
| Ad hoc SAS signed with a user delegation key | No | To revoke user delegation key or change role assignments, see [Revoke a user delegation SAS](/rest/api/storageservices/create-user-delegation-sas#revoke-a-user-delegation-sas). |
101+
| SAS with stored access policy | No | To update the expiration time to a past date or time, or delete the stored access policy, see [Modify or revoke a stored access policy](/rest/api/storageservices/define-stored-access-policy#modify-or-revoke-a-stored-access-policy). |
102+
103+
For more information, see [Revoke a SAS](/rest/api/storageservices/create-service-sas#revoke-a-sas).
104+
62105
## Change deployment service principal
63106
64107
This section describes how you can change the service principal used for deployment.

0 commit comments

Comments
 (0)