What causes Errors on Premium capacity?

SSMS client libraries version 18.7.1 or lower do not support automatic session reconnection required by the XMLA endpoint. The Power BI Premium capacity does not have XMLA read/write access enabled in the admin settings. Email subscriptions are not triggered for semantic models refreshed via the XMLA endpoint, which is a known platform limitation. Workspace is not assigned to a Premium or Fabric capacity, making the XMLA endpoint unavailable

How do I fix Errors on Premium capacity?

Step 1: Upgrade SSMS to version 18.8 or higher to ensure client libraries support automatic session reconnection with the XMLA endpoint.. Step 2: In the Power BI Admin Portal, navigate to Capacity Settings > your Premium capacity > Workloads, and confirm that XMLA Endpoint access is set to 'Read Write'.. Step 3: Verify the target workspace is assigned to a Premium Per User, Premium capacity, or Fabric capacity — XMLA endpoint access is not available on shared capacity.. Step 4: If email subscriptions are required after XMLA-triggered refreshes, configure a separate Power Automate flow or alerting mechanism as a substitute, since XMLA refreshes do not trigger native Power BI email subscriptions.. Step 5: Capture the RootActivityId from any XMLA error message and submit it with a Microsoft support ticket if errors persist after addressing client library and capacity configuration.

High severitycapacity

Power BI Refresh Error:
Errors on Premium capacity

What does this error mean?

Connections and operations via the XMLA endpoint on Power BI Premium capacity fail, including SSMS connect-to-server errors and email subscriptions not triggering after XMLA-based refreshes. These errors span authentication, client library, and capacity configuration issues.

Common causes

1SSMS client libraries version 18.7.1 or lower do not support automatic session reconnection required by the XMLA endpoint
2The Power BI Premium capacity does not have XMLA read/write access enabled in the admin settings
3Email subscriptions are not triggered for semantic models refreshed via the XMLA endpoint, which is a known platform limitation
4Workspace is not assigned to a Premium or Fabric capacity, making the XMLA endpoint unavailable

How to fix it

1Step 1: Upgrade SSMS to version 18.8 or higher to ensure client libraries support automatic session reconnection with the XMLA endpoint.
2Step 2: In the Power BI Admin Portal, navigate to Capacity Settings > your Premium capacity > Workloads, and confirm that XMLA Endpoint access is set to 'Read Write'.
3Step 3: Verify the target workspace is assigned to a Premium Per User, Premium capacity, or Fabric capacity — XMLA endpoint access is not available on shared capacity.
4Step 4: If email subscriptions are required after XMLA-triggered refreshes, configure a separate Power Automate flow or alerting mechanism as a substitute, since XMLA refreshes do not trigger native Power BI email subscriptions.
5Step 5: Capture the RootActivityId from any XMLA error message and submit it with a Microsoft support ticket if errors persist after addressing client library and capacity configuration.

Frequently asked questions

Why don't email subscriptions fire after an XMLA refresh even though the data updated successfully?

This is a documented platform limitation — Power BI email subscriptions are only triggered by refreshes initiated through the Power BI service scheduler or manual refresh button. XMLA endpoint refreshes bypass this trigger. Use Power Automate with a datasetRefreshComplete event or a MetricSign alert as a substitute notification.

What SSMS version do I need for the XMLA endpoint to work reliably?

SSMS 18.8 or higher is required. Earlier versions (18.7.1 and below) use client libraries that do not support automatic session reconnection, which causes intermittent connection drops when working with Power BI Premium via XMLA.