Plugin
power-automate
Plugin Version
2.0.0
Skill / Command
get_flow / list_flows / get_run_history / get_flow_context (any tool hitting the environment API)
Bug Description
FlowAgent MCP server cannot resolve the Power Automate API hostname for a tenant's "Default-" environment when that environment has no Dataverse instance provisioned.
Steps to Reproduce
- In a tenant whose default environment has no Dataverse instance provisioned, run list_environments -- it correctly lists the environment as "Default-" with provisioned: false.
- Call set_current_env with that environment id (succeeds), then call get_flow (or list_flows, get_run_history, get_flow_context, etc.) targeting a real flow id in that environment.
Expected Behavior
The tool should fall back to the legacy Flow API (https://api.flow.microsoft.com/providers/Microsoft.ProcessSimple/environments/{env}/flows/{flow}) for non-Dataverse-provisioned environments, or otherwise correctly resolve the environment's real regional PPAPI hostname.
Actual Behavior
Every call fails with a NetworkError such as:
Flow API 0 NetworkError: Network request failed: ENOTFOUND (hostname: <32-hex-guid-minus-last-2-chars>.<last-2-chars>.environment.api.powerplatform.com). This often means the environment ID produced an invalid PPAPI URL.
The hostname is malformed: the tool appears to take the full 32-character de-hyphenated environment GUID and split off its last 2 characters as if they were a region code, instead of resolving an actual region/cluster suffix (unavailable since there's no Dataverse instance to query it from).
A confirmed workaround: calling the legacy Flow API directly (api.flow.microsoft.com, api-version=2016-11-01) works fine for get/list/update against the same environment+flow, using the same az-login-issued token. This suggests the fix is to route non-Dataverse-provisioned "Default-" environments through the legacy API path instead of attempting PPAPI hostname construction.
Relevant Logs / Screenshots
(error message included above under Actual Behavior)
Environment
OS: macOS 26.5.2
Claude Code: 2.1.220
PAC CLI: installed but not runnable in this environment (.NET runtime missing) -- not relevant to this bug
🤖 This issue was created using the /report-issue skill.
Plugin
power-automate
Plugin Version
2.0.0
Skill / Command
get_flow / list_flows / get_run_history / get_flow_context (any tool hitting the environment API)
Bug Description
FlowAgent MCP server cannot resolve the Power Automate API hostname for a tenant's "Default-" environment when that environment has no Dataverse instance provisioned.
Steps to Reproduce
Expected Behavior
The tool should fall back to the legacy Flow API (https://api.flow.microsoft.com/providers/Microsoft.ProcessSimple/environments/{env}/flows/{flow}) for non-Dataverse-provisioned environments, or otherwise correctly resolve the environment's real regional PPAPI hostname.
Actual Behavior
Every call fails with a NetworkError such as:
The hostname is malformed: the tool appears to take the full 32-character de-hyphenated environment GUID and split off its last 2 characters as if they were a region code, instead of resolving an actual region/cluster suffix (unavailable since there's no Dataverse instance to query it from).
A confirmed workaround: calling the legacy Flow API directly (api.flow.microsoft.com, api-version=2016-11-01) works fine for get/list/update against the same environment+flow, using the same az-login-issued token. This suggests the fix is to route non-Dataverse-provisioned "Default-" environments through the legacy API path instead of attempting PPAPI hostname construction.
Relevant Logs / Screenshots
(error message included above under Actual Behavior)
Environment
OS: macOS 26.5.2
Claude Code: 2.1.220
PAC CLI: installed but not runnable in this environment (.NET runtime missing) -- not relevant to this bug
🤖 This issue was created using the
/report-issueskill.