Skip to content

Commit 070c148

Browse files
Merge pull request #221631 from msmbaldwin/patch-176
Update best-practices.md
2 parents 4f946a3 + c5d42b7 commit 070c148

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,10 @@ A multitenant solution is built on an architecture where components are used to
5858
### Can I use Key Vault role-based access control (RBAC) permission model object-scope assignments to provide isolation for application teams within Key Vault?
5959
No. RBAC permission model allows to assign access to individual objects in Key Vault to user or application, but any administrative operations like network access control, monitoring, and objects management require vault level permissions which will then expose secure information to operators across application teams.
6060

61-
## Learn more
61+
## Next steps
62+
63+
Learn more about key management best practices:
6264
- [Best practices for secrets management in Key Vault](../secrets/secrets-best-practices.md)
65+
- [Best practices for Azure Managed HSM](../managed-hsm/best-practices.md)
6366

6467

0 commit comments

Comments
 (0)