Power Platform Community Forum Thread Details

In my power automate flow, the power bi connector does not load and I'm not able to add the action: "Run a query against a dataset". (also all other actions of this connector do not work/load).

The Error message is...
... in the new Designer: "Error fetching manifest"

... in the old Designer: "ERR_BAD_RESPONSE. Request failed with status code 500"

My environment is in the region switzerland and in environments of other regions (for example europe) the issue seems not to be present.

Can someone help me?

Categories:

Building flows

Use a different environment region (temporary bypass).
Create/run the flow in an EU/Europe (or another working) region: the Power BI actions load there because the connector manifest resolves correctly. Microsoft’s own guidance confirms envs are region-bound, so cross-region behavior like you observed is expected.
Skip the connector; call the Power BI REST API via HTTP.

All the Power BI actions you need map to REST calls and work regardless of the connector UI

Run a query against a dataset → POST https://api.powerbi.com/v1.0/myorg/datasets/{datasetId}/executeQueries (body contains your DAX).
Refresh a dataset → POST https://api.powerbi.com/v1.0/myorg/datasets/{datasetId}/refreshes.

Refer this : https://community.powerplatform.com/forums/thread/details/?threadid=affdbf01-e884-f011-b4cb-6045bdda2e5f

In your flow, add HTTP:

Auth: Use Entra ID (service principal) and enable the tenant setting “Allow service principals to use Power BI APIs”; grant the app access to the workspace.
Body example (executeQueries):

{ "queries": [{ "query": "EVALUATE TOPN(10, 'Table')" }], "serializerSettings": { "includeNulls": true } }

(Send with Content-Type: application/json and a Bearer token.)

Useful context / proof:

Multiple users report “Error reading manifest” specifically for Power BI actions in certain regions (e.g., UK); existing flows may even run but the designer still errors.
Separate thread shows Switzerland tenants seeing similar “Error fetching manifest” behavior for other connectors (Dataverse), reinforcing this is regional backend rather than your flow.
If you want to track whether it’s an active Microsoft incident for your geo, check service-health notes (there have been recent Power BI incidents scoped to Switzerland).