pac code add-data-source -a dataverse -t <entity-logical-name> returns getaddrinfo ENOTFOUND <environmentid>.[2 digit from environment guid]. environment.api.powerplatform.com

[sumbharti]

We have observed

pac code add-data-source constructs malformed API endpoint URL by incorrectly extracting a segment from the environment GUID and inserting it as a subdomain in the URL.

Example:

• Environment GUID containing b5 → URL becomes .b5.environment.api.powerplatform.com
• Environment GUID containing b4 → URL becomes .b4.environment.api.powerplatform.com
  Both URLs are unreachable/non-existent

This leads to error: getaddrinfo ENOTFOUND

What we explored so far -

• pac auth create/list.. etc. commands work in system and returns the correct environment url.

• There is no error in pac-log file during execution of pac code add-data-source command

• Proxy is configured correctly in system and Node runtime is able to fetch this correctly.

• Latest version of pac cli is being used: 2.2.1

Please suggest if there is a fix for this or if this is a known issue.

[tggagne]

Adding a second data point from a different command in the npm Code Apps CLI.

I am seeing the same hostname-construction failure with npx power-apps list-flows, not just with pac code add-data-source.

Command:

npx power-apps list-flows --environment-id ccf552bb-xxxx-xxxx-xxxx-ac10490fd326

Error:

Network request failed for GET
https://ccf552bbxxxxxxxxxxxxac10490fd3.26.environment.api.powerplatform.com/powerapps/environment?api-version=1&$filter=name eq 'ccf552bb-xxxx-xxxx-xxxx-ac10490fd326'. DNS lookup failed - unable to resolve hostname. Details: getaddrinfo ENOTFOUND ccf552bbxxxxxxxxxxxxac10490fd3.26.environment.api.powerplatform.com

A few details that may help narrow it down:

1. The environment ID came from pac env list.
2. The environment is real and accessible in the browser. I can open a flow in that environment successfully in Power Automate.
3. The failure is specifically in the npm CLI path when it generates the *.environment.api.powerplatform.com host.
4. I also tested another environment ID visible to the same account. That one did not produce ENOTFOUND; list-flows completed and returned []. So this does not look like a general auth or network failure in my setup.

Versions:

• @microsoft/power-apps: 1.1.9
• @microsoft/power-apps-cli: 0.11.6

Question:

Is npx power-apps list-flows --environment-id <guid-from-pac-env-list> expected to work with the GUID returned by pac env list? If so, is there a known bug in environment-host construction for some environment IDs?