Applies to: Azure Public Cloud | Azure Government
To protect your data, you must onboard your Azure Storage Account to the Druva Cloud Platform. Before configuring data protection for your Azure Blob Storage workload, Druva performs automated environment readiness prechecks. These validations verify that your Azure Key Vault, required access permissions, network routing paths, and user-assigned managed identities are accessible within your selected Azure subscription.
Precheck Severity Levels
All environment prechecks in this section are classified as Fatal. If any validation step fails, the onboarding process is halted immediately. You must fix the flagged configuration issue before the storage onboarding process can complete.
Master Storage Precheck Reference Table
Error Message | Severity | Description | Resolution |
Resource group <name> inaccessible. It may have been deleted or the assigned permissions have changed. | Fatal | Verifies the target Resource Group exists within your subscription and is not currently locked or restricted. | Select an accessible Resource Group within the target subscription. If the resource group is missing, create a new one in the Azure portal and click Sync in the Druva console to discover the update. |
Key Vault <name> inaccessible. It may have been deleted or the assigned permissions have changed. | Fatal | Validates that the selected primary Key Vault exists and is accessible within the designated Resource Group and target subscription. | Ensure the primary Key Vault exists in the Azure portal. Navigate to Settings > Networking and set the Firewalls and virtual networks configuration to "Allow public access from all networks". Ensure no private endpoint connections are blocking access. |
Key Vault <name> inaccessible. It may have been deleted or the assigned permissions have changed. | Fatal | Validates that the selected secondary Key Vault exists and is accessible within Druva’s Resource Group and target subscription. | Ensure the secondary Key Vault exists in the Azure portal. Navigate to Settings > Networking and set the Firewalls and virtual networks configuration to "Allow public access from all networks". Ensure no private endpoint connections are blocking access. |
Managed identity <name> not found. It may have been deleted or the assigned permissions have changed. | Fatal | Validates that the User-Assigned Managed Identity exists and is accessible within Druva’s Resource Group and target subscription. | Assign the required Azure RBAC role to the User-Assigned Managed Identity at the appropriate scope (Subscription or Resource Group level) via the Azure portal or CLI, then retry. |
Custom Role <name> not found. It may have been deleted or the assigned permissions have changed. | Fatal | Validates whether the Azure Custom Role exists and is accessible within the target subscription. | Verify that the Custom Role has been created at the correct scope in Azure. If it was deleted, recreate the role definition with the required permissions and sync the configuration. |
Role assignment not found. It may have been deleted or the assigned permissions have changed. | Fatal | Validates that the required Azure RBAC role assignment is actively mapped to the User-Assigned Managed Identity at the subscription or resource group scope. | Assign the required Azure RBAC role to the User-Assigned Managed Identity at the required scope, Subscription or Resource Group level, via the Azure portal or CLI, then retry the precheck.
|