Hello Kalyan Kumar,
Thank you for posting your question in the Microsoft Q&A forum.
The error you're encountering during your first-time Databricks Metastore creation likely stems from a known backend synchronization issue in Azure Databricks, particularly with permission propagation. While a FORCE CREATE command might bypass the immediate error, it risks creating an unstable metastore if underlying permissions aren't fully resolved.
Recommended Approach you may take as below:
- Wait for Azure/Databricks Fix: If this is a confirmed backend bug, forcing creation may compound issues.
- Validate Permissions: Despite having Blob Storage Contributor, ensure your identity also has: Storage Blob Data Owner (for ACLs) and Databricks Workspace Admin rights.
- Test with Manual Debug: Use dbutils.fs.ls() to verify storage access before retrying.
If urgent, proceed with FORCE CREATE but monitor metastore stability closely.
If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated.