From f67e1c6f6b36ba27ce252fc8e4f17d1090ef50b5 Mon Sep 17 00:00:00 2001 From: sofietoft Date: Fri, 31 Jan 2025 11:34:23 +0100 Subject: [PATCH 1/2] Add note about different Azure approach --- 15/umbraco-cms/extending/key-vault.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/15/umbraco-cms/extending/key-vault.md b/15/umbraco-cms/extending/key-vault.md index c3d34949363..5c3c209cfe3 100644 --- a/15/umbraco-cms/extending/key-vault.md +++ b/15/umbraco-cms/extending/key-vault.md @@ -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 Acccess Control on your Azure Key Vault. + +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). +{% 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) From b2c68dd94c9cb85a32953cd2eeab22878c1da4a6 Mon Sep 17 00:00:00 2001 From: sofietoft Date: Mon, 3 Feb 2025 10:46:34 +0100 Subject: [PATCH 2/2] Update 15/umbraco-cms/extending/key-vault.md Co-authored-by: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> --- 15/umbraco-cms/extending/key-vault.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/15/umbraco-cms/extending/key-vault.md b/15/umbraco-cms/extending/key-vault.md index 5c3c209cfe3..d0e00cc0780 100644 --- a/15/umbraco-cms/extending/key-vault.md +++ b/15/umbraco-cms/extending/key-vault.md @@ -140,9 +140,9 @@ 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 Acccess Control on your Azure Key Vault. +Alternatively, you can use Role-Based Access Control on your Azure Key Vault. -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). +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**.