Problem description
When attempting to discover or add an Azure subscription within the Druva Cloud Console for backup or workload protection, the discovery process fails. This prevents the administrator from viewing or protecting Azure resources associated with that specific subscription.
This issue typically occurs during the initial setup phase or when adding a new subscription to an existing Druva environment.
Cause
The failure is caused by the Microsoft.KeyVault resource provider not being registered within the target Azure subscription. Druva requires access to this namespace to manage encryption keys and secure access during the discovery and backup lifecycle. If the namespace is "NotRegistered," Azure blocks the API calls made by Druva.
Traceback
The following error snippet is captured in the HAR logs or displayed in the
{ "code": "ConnectionSvc-1001", "message": "Codes:[MissingSubscriptionRegistration], Msg:The subscription is not registered to use namespace 'Microsoft.KeyVault'. See https://aka.ms/rps-not-found for how to register subscriptions." }Resolution
To resolve this issue, you must manually register the Microsoft.KeyVault resource provider in the Azure Portal.
Step-by-Step Procedure:
Log in to Azure: Sign in to the Azure Portal.
Access Subscriptions: Search for Subscriptions in the top search bar and select the subscription that encountered the error.
Navigate to Resource Providers: In the left-hand menu, under the Settings section, click on Resource providers.
Register KeyVault: * Search for
Microsoft.KeyVaultin the filter bar.Select the provider.
If the status is NotRegistered, click the Register button at the top of the pane.
Wait for Completion: The status will change to Registering and then to Registered. This usually takes 1–3 minutes.
Verification
In the Azure Portal, confirm that
Microsoft.KeyVaultdisplays a green checkmark and the status Registered.Return to the Druva Cloud Console.
Navigate to the Azure setup page and click Retry or initiate the Discover Subscriptions action again.
The subscription should now be discovered successfully without the
ConnectionSvc-1001error.