INFO.STORAGETABLECOLUMNS() Function access using Published Semantic Model - Need help

Add the build permission to the user for that semantc model.

Step 1: Confirm the workspace is Premium (or PPU)

Without Premium / PPU / Fabric, DISCOVER DMVs are not supported.

Step 2: Enable Read/Write XMLA endpoints

In the workspace settings:

• Set "XMLA Endpoint" = Read/Write"
  (Read-only will not allow DISCOVER DMVs.)

  Step 3: Add yourself as Dataset Admin

  Even Workspace Admin is not enough for some DMV operations.

  Go to the dataset's permissions and add yourself as Admin.

  Step 4: Reconnect to the model via XMLA

  Use Power BI Desktop, Tabular Editor, or SSMS, connecting with the dataset’s XMLA endpoint.

  Then execute:

   

   

  EVALUATE INFO.STORAGETABLECOLUMNS()

  It will now work.

   

  Note: AI helped me to format this response.

satishorre20

Thankyou, Thomaslleblanc, for your response.

Hi satishorre20,

Thank you for confirming that the Build permission has already been granted. Since the error “The user does not have permission to call the Discover method” persists, the issue may not be related to dataset level permissions.

Based on my understanding, INFO.STORAGETABLECOLUMNS() depends on a DISCOVER metadata call through the XMLA endpoint. This call is restricted unless your tenant and workspace explicitly permit XMLA metadata discovery. That is why the function works in Power BI Desktop (which has full local engine access) but fails on the published semantic model.

Please verify the following steps, as they may help resolve the issue:

1. In the Admin Portal, under Tenant settings, ensure that “Allow XMLA Endpoints” and “Analyze in Excel” are enabled for your user or group.
2. DISCOVER operations are permitted only in Premium or Fabric workspaces. Go to the Workspace settings and confirm that the Capacity is set to Premium or Fabric.
3. After updating Build or XMLA permissions, refresh the desktop token by choosing Power BI Desktop → File → Options → Data source settings → Sign out → Sign in again.
4. Try connecting to the workspace XMLA endpoint using the same user credentials via SSMS: powerbi://api.powerbi.com/v1.0/myorg/<workspaceName>. If SSMS also fails with a DISCOVER error, XMLA metadata access is still blocked at the tenant or capacity level.

For further reference, please refer the links below:
Semantic model connectivity and management with the XMLA endpoint in Power BI - Microsoft Fabric | Microsoft Learn
What is Power BI Premium? - Microsoft Fabric | Microsoft Learn
Semantic model connectivity and management with the XMLA endpoint in Power BI - Microsoft Fabric | Microsoft Learn

We hope the information helps to resolve the issue. If you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.

Hi satishorre20,

We would like to follow up and see whether the details we shared have resolved your problem. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.

Thank you.

Hi Thomaslleblanc , Greetings,

Thank you so much for providing such a detailed explanation on this matter. My understanding is that the XMLA endpoint is enabled, which is great news. I was able to perform partitioning on the table of the published semantic model, but for thoroughness, I will double-check one more time to ensure everything is in order.

I will keep you posted with my findings. Once again, I truly appreciate your time and assistance.

Best regards,
Satish Orre

Hi satishorre20,

We are following up to inquire whether you have had an opportunity to cross-check the settings from your end and resolve the issue. If not, could you please provide an estimated time of arrival (ETA) for your findings.
If you have any further queries, please feel free to contact the Microsoft Fabric Community.

Thank you.

Greetings,

 I will review these and will update with my findings by 12/12/2025

Thank you,

Satish 

Hi satishorre20,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.