Skip to main content

Azure RBAC for Druva-managed Key Vaults

Druva now uses Azure role-based access control (Azure RBAC) to control access to the key vaults that Druva creates in your Azure subscriptions. Microsoft recommends Azure RBAC for Azure Key Vault, and it is the default for new key vaults.

What is changing?

Azure Key Vault has two permission models:

  • Vault access policy (legacy): Permissions are set inside each key vault.

  • Azure role-based access control (recommended): Permissions are granted through Azure role assignments, which you manage in one place with your other Azure access.

Druva is moving its key vaults to Azure RBAC and assigns these Microsoft built-in roles on each key vault:

  • Key Vault Secrets Officer to the Druva backup application.

  • Key Vault Secrets User to the Druva managed identity.

For details on the migration steps, see Migrate to Azure RBAC from access policies.

When it happens

  • New subscriptions: Subscriptions that you onboard on or after November 8, 2026, use Azure RBAC.

  • Existing subscriptions: Starting November 16, 2026, existing Druva-managed key vaults move non-disruptively to Azure RBAC in phases.

Date

Deployment Region / Milestone

November 8, 2026

New Onboardings: All newly onboarded Azure subscriptions enable RBAC by default.

November 16, 2026

APAC Region (ap1-console.druva.com): Automated migration begins for existing eligible subscriptions in the APAC region.

November 23, 2026

US Region (console.druva.com), AU Region (au-console.druva.com): Automated migration begins for existing eligible subscriptions in the US and AU regions.

Will this affect your backups?

No. Backup and restore jobs continue during the migration. If a migration can’t complete, your key vaults keep using vault access policies, and backups continue.

These things don’t change:

  • You don’t need to onboard your subscriptions again.

  • Your existing key vaults stay in place; no new key vaults are created.

  • Your backup policies and settings don’t change.

  • Key vaults that you created yourself are not affected.

Do you need to take any action?

Most customers don’t need to do anything.

Druva runs the migration with the Azure account that registered your tenant. That account needs:

  • A valid sign-in. It must not have expired.

  • The Owner role on each subscription.

If either is missing, update your tenant registration. For steps, see Update Azure Tenant Registration.
​

To check the account’s role:

  1. In the Azure portal, open the subscription.

  2. Select Access control (IAM) > Role assignments.

  3. Find the account and confirm that it has the Owner role.

Need help?

For help with the migration, contact Support.

Did this answer your question?