Skip to content

Commit f67e1c6

Browse files
committed
Add note about different Azure approach
1 parent b7f2b94 commit f67e1c6

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

15/umbraco-cms/extending/key-vault.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,12 @@ A GUID will then be generated called **Object (principal) ID**. Take note of thi
139139

140140
### Update your Key Vault Access Policy
141141

142+
{% hint style="info" %}
143+
Alternatively, you can use Role-Based Acccess Control on your Azure Key Vault.
144+
145+
Learn more about this in the different between the two approaches and how to migrate between them on the [Azure Documentation platform](https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-access-policy).
146+
{% endhint %}
147+
142148
It is assumed you already have a Key Vault set up with a few Umbraco secrets inside. In your Key Vault head to **Access Policies**.
143149

144150
![image](https://user-images.githubusercontent.com/11179749/196052540-e1368016-ad7a-4b69-b05c-2875a4f11998.png)

0 commit comments

Comments
 (0)