Skip to content

Add note about different Azure approach #6837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 3, 2025
Merged

Add note about different Azure approach #6837

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f67e1c6
Add note about different Azure approach
sofietoft Jan 31, 2025
b2c68dd
Update 15/umbraco-cms/extending/key-vault.md
sofietoft Feb 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions 15/umbraco-cms/extending/key-vault.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,12 @@ A GUID will then be generated called **Object (principal) ID**. Take note of thi

### Update your Key Vault Access Policy

{% hint style="info" %}
Alternatively, you can use Role-Based Access Control on your Azure Key Vault.

Learn more about the difference 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).
{% endhint %}

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**.

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