Hi @Shivaprasad,

You generally should not create a standalone materialised view from an all-purpose cluster. Databricks documents that CREATE MATERIALIZED VIEW is supported from a Pro or Serverless SQL warehouse, or within a pipeline. For standalone materialised views, Databricks also documents that you can create them from a Databricks SQL warehouse or from a notebook running on serverless general compute.

So if you are trying this from an all-purpose cluster, that part is already a problem. A SQL warehouse is the correct route.

The second part is the important one... even when you issue the command from a SQL warehouse, Databricks creates and uses a serverless backing pipeline for the create/refresh path. Databricks explicitly says that create and refresh operations for materialised views are powered by serverless Lakeflow pipelines, and that a serverless pipeline is automatically created for Databricks SQL materialised views.

That is why the error you shared does not appear to be a simple SQL warehouse permission issue. The error is a 403 against the Unity Catalog managed storage path under __unitystorage/.../_delta_log, which strongly suggests that the backing serverless pipeline cannot access the Azure Data Lake Storage location used by Unity Catalog.

A few things you can check...

First of all, make sure you are using a Pro or Serverless SQL warehouse for CREATE MATERIALIZED VIEW, not an all-purpose cluster. 

On Azure, check that Unity Catalog storage access is configured using the correct Databricks-managed identity / Access Connector path, and that the required role is assigned to that identity. The Azure Databricks guidance for Unity Catalog storage access calls out assigning the role to the managed identity, not just relying on a user-level permission.

Also, double check the exact Azure RBAC role. The documented role is Storage Blob Data Contributor, which is different from "Storage Blob Contributor".

Lastly, if the storage account is behind firewall rules, Private Link, or a VNet-injected setup, you should also verify that serverless access is configured correctly for that storage account. Databricks documents additional setup for managed identity trusted access and serverless private connectivity.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.