Common Errors
Issue: Auto Discovery for workspace has Not Started
Cause: The Druva application cannot verify access to the Power BI tenant.
Solution: Verify that the Service Principal is in the Azure Security Group and that the API settings are enabled in the Power BI Admin portal. See Tenant Environment Authorization.
Issue: Power BI restore to new workspace fails during target workspace creation (for example, Microsoft error code MS-248)
Cause: The tenant setting Service principals can create workspaces, connections, and deployment pipelines is not enabled for the Druva security group, or the change has not yet propagated.
Solution:
Enable the setting for security group DRUVA-SG-DPPSPN-DR in the Power BI Admin portal. See Authorizing Tenant Environments for Power Platform Protection.
Wait 15–20 minutes for the tenant setting to propagate.
If you configured Power BI protection before in-console restore became available, reinstall or reconfigure the Druva Power Platform app so updated permissions are granted.
Retry the restore job.
Issue: Restore job reports success, but expected objects are missing in the restored workspace
Cause: The missing objects were skipped or captured as metadata only during backup because of Microsoft API limitations—for example, Dataflow Gen2, apps, or reports shown as Report (metadata) / 0 bytes in the recovery point listing.
Solution:
Review the recovery point listing before restore to confirm which objects were fully backed up.
Test restore with a workspace that contains supported object types if you need a representative recovery outcome.
Error Codes
For details on the root cause and recommended action, refer to the cloud apps integration error messages.