Skip to content

Commit 98e1c1d

Browse files
committed
Add multitenancy best practice to Key Vault documentation
1 parent 4284c91 commit 98e1c1d

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/key-vault/general/best-practices.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ tags: azure-key-vault
88
ms.service: key-vault
99
ms.subservice: general
1010
ms.topic: conceptual
11-
ms.date: 01/29/2021
11+
ms.date: 09/04/2022
1212
ms.author: mbaldwin
1313
# Customer intent: As a developer who's using Key Vault, I want to know the best practices so I can implement them.
1414
---
@@ -60,5 +60,9 @@ Make sure you take regular backups of your vault. Backups should be performed wh
6060
- Turn on [soft-delete](soft-delete-overview.md).
6161
- Turn on purge protection if you want to guard against force deletion of the secrets and key vault even after soft-delete is turned on.
6262

63+
## Multitenant solutions and Key Vault
64+
65+
A multitenant solution is built on an architecture where components are used to serve multiple customers or tenants. Multitenant solutions are often used to support software as a service (SaaS) solutions. If you're building a multitenant solution that includes Key Vault, review [Multitenancy and Azure Key Vault](/azure/architecture/guide/multitenant/service/key-vault).
66+
6367
## Learn more
6468
- [Best practices for secrets management in Key Vault](../secrets/secrets-best-practices.md)

0 commit comments

Comments
 (0)