A KeyVault seems to be tightly coupled to a single AAD instance
What guidance should I follow when I want to support Azure AD (B2C) and B2B / Work users?
I'm currently exploring this solution to help manage the independent sign in flows.
A KeyVault seems to be tightly coupled to a single AAD instance
What guidance should I follow when I want to support Azure AD (B2C) and B2B / Work users?
I'm currently exploring this solution to help manage the independent sign in flows.
According to the docs for
Set-AzureRmKeyVaultAccessPolicy
PowerShell cmdlet that gives access to an app or a user to secrets in the Key Vault:So the Key Vault will be in a subscription and that subscription is attached to a single Azure AD. Any application that is given access must be from that directory.