XMLA Endpoint Enabled but Getting “XMLA Endpoint Feature is Disabled” Error in C# Connection

[bhavana_dfz]

Hi all,

I'm encountering an issue when trying to connect to a Power BI semantic model via the XMLA endpoint using C#, following the guidance in Microsoft’s documentation.

Despite having the XMLA endpoint enabled for our tenant, I’m still getting the following error:

Microsoft.AnalysisServices.ConnectionException: XMLA endpoint feature is disabled. Turn on Analyze in Excel feature in PowerBI.com to enable this feature.

I’ve double-checked that:

• The XMLA endpoint is indeed enabled at the tenant level via the Power BI Admin portal.

• I'm using a Premium or Premium Per User (PPU) workspace and I am the admin of the workspace.

• I have Build permissions on the dataset.

• The user account has sufficient privileges and the "Analyze in Excel" feature is enabled in PowerBI.com.
  
  i am following this documentation : Programming Power BI semantic models with the Tabular Object Model (TOM) | Microsoft Learn
  
  Does User's fabric capacity play any role in this error

[v-vpabbu]

Hi @bhavana_dfz,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,
Vinay Pabbu

[v-vpabbu]

Hi @bhavana_dfz,

Thank you for reaching out to Microsoft Fabric Community Forum.

Even if you're using a Premium or Premium Per User (PPU) workspace and are the admin, it's essential to ensure that the workspace is explicitly assigned to an active capacity. Simply being labeled as Premium/PPU doesn't guarantee XMLA endpoint access—check under the workspace settings to confirm it's tied to a valid capacity like P1 or a PPU license. If it's running on shared (Pro) capacity, the XMLA endpoint won't work even if all tenant settings are correctly enabled.

Also, in a Microsoft Fabric environment, make sure the capacity itself is not paused or overutilized, as that will block XMLA connectivity. Go to the Admin portal > Capacity settings > Fabric Capacity and check the status. Trial capacities like F64 Trial might also introduce inconsistent behavior, so using a fully provisioned capacity is recommended for reliable XMLA endpoint access.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

Regards,
Vinay Pabbu