Problem Description
Azure storage accounts are not discovered or visible within the Druva Management Console. Due to this issue, Azure VM backup and restore operations may fail, and associated Azure resources or workloads will not appear correctly in the console.
Cause
This issue occurs when Azure resource discovery fails to complete. The most common underlying causes include:
An outdated or expired Azure Tenant Registration.
Missing or incorrect Azure permissions assigned to the Druva application inside your Microsoft Entra ID.
Incomplete Azure subscription authorization configurations within the Druva environment.
As a result, Druva lacks the programmatic access required to poll and query your Azure storage accounts successfully.
Resolution
Step 1: Update Azure Tenant Registration
Log in to the Druva Management Console.
Navigate to your Azure settings page and trigger the Update Tenant Registration workflow.
Verify the following components:
All newly requested Azure permissions are granted and accepted via your global administrator prompts.
The overall tenant registration status is valid.
Target Azure subscriptions are properly authorized for backup and key vault creation.
š Reference Documentation: For a detailed breakdown of this step, please refer to Update Azure Tenant Registration.
Step 2: Validate Resource Discovery
In the Druva console, manually refresh or re-run the Azure resource discovery process.
Confirm that:
The missing storage accounts are now visible.
Azure VM resources map correctly to their target definitions.
Re-try or re-schedule the failed backup operation.