[Power Platform blocker] service URL and API key required for connector connection

[edithatogo]

Current gap

The deployed MCHS Power Platform connector and runtime path are not yet executable because the service-boundary endpoint and connection reference values are missing or still placeholders.

Observed evidence as of 2026-05-26:

• PAC is authenticated against environment 611bca65-0b2a-eaa1-9e74-23bbba8eeec4.
• Managed solution mchs_alm_orchestration version 0.2.2.0 is present.
• Custom connector MCHS Service Boundary exists as connector ID 0f3d6edc-9653-f111-bec6-00224893a0e1.
• Downloaded connector definition still points to https://example.invalid/.
• pac connection list does not show a live custom connector connection for MCHS Service Boundary / new_mchs-20service-20boundary.
• Browser/app-player runtime smoke is not proven.

Closure evidence required

Close this only after recording:

• real mchs_api_base_url / connector host for the target environment,
• live custom connector connection ID,
• populated connection reference value for the app/flow,
• app-player smoke result showing runtime execution reaches the app,
• flow run or connector call evidence for a synthetic request,
• DLP policy placement for the custom connector.

Source evidence

• power-platform/solution/runtime-evidence-20260525.md
• power-platform/evidence/tenant-cli-observation-20260525.json
• power-platform/evidence/powerapp-runtime-launch-20260525.json
• power-platform/evidence/runtime-smoke-evidence-template.json
• power-platform/evidence/connection-reference-evidence-template.json

Confirmations

• I have not claimed production readiness or blocker resolution.
• I am using repository evidence as the source of truth; this issue tracks the external closure work.

[edithatogo]

Correction/additional Power Platform check on 2026-05-26:

• pac connection list still shows only generic Microsoft/Dataverse/Office connectors and no MCHS Service Boundary / new_mchs-20service-20boundary custom connector connection.
• Repo search found no real service-boundary host; connector source and downloaded deployed connector definition continue to use example.invalid.
• pac connection create requires tenant ID, connection name, application ID, and client secret, so it cannot be safely completed without external tenant/application credentials and an approved endpoint.
• pac connector update is available, but updating the deployed connector would require a real endpoint/configuration value that is not present in current repo or environment evidence.

The previous comment was mangled by shell interpolation. This is the corrected evidence.

[edithatogo]

Live recheck after PR #154 merge on 2026-05-25T14:54Z: PAC auth is active and the environment still lists custom connector 0f3d6edc-9653-f111-bec6-00224893a0e1 (MCHS Service Boundary), but pac connection list still shows no custom connector connection for the MCHS Service Boundary API. This remains blocked on a real service endpoint plus connection/reference values or the credentials required to create the connection.

[edithatogo]

Rechecked with authenticated pac on 2026-05-26. PAC auth is active and the MCHS Service Boundary custom connector exists, but pac connection list still shows no connection for /providers/Microsoft.PowerApps/apis/new_mchs-20service-20boundary; the deployed connector definition still points at placeholder example.invalid; and the candidate Smithery/runtime URL still returns server_not_found. This remains blocked on a real reachable service host plus a custom connector connection/connection reference, not on local PAC authentication.

[edithatogo]

Additional deployed connector inspection on 2026-05-25T15:06Z:

• pac connector download succeeds for connector 0f3d6edc-9653-f111-bec6-00224893a0e1 (MCHS Service Boundary).
• Downloaded apiDefinition.json still has host: example.invalid, basePath: /, and schemes: [https].
• Downloaded apiProperties.json already defines the expected connection parameters: baseUrl (Service base URL) and api_key (Service API key).

Conclusion: the connector shape is not the blocker. The blocker is still operational configuration: a real reachable service boundary URL plus the API key/connection values needed to create or bind the custom connector connection.

[edithatogo]

Live recheck on 2026-05-26 after Smithery closure:

• PAC authentication is active in the target Power Platform environment.
• Custom connector MCHS Service Boundary still exists as new_mchs-20service-20boundary / connector ID 0f3d6edc-9653-f111-bec6-00224893a0e1.
• pac connection list still shows no connection whose API ID is /providers/Microsoft.PowerApps/apis/new_mchs-20service-20boundary; only standard Microsoft/Dataverse/Office connectors are connected.
• Repository/source connector configuration still uses placeholder example.invalid for the service-boundary host; no real mchs_api_base_url or API-key value is present in committed evidence.
• Current PAC CLI does not expose an envvar command in this install, so I did not mutate environment variable values through PAC.

Conclusion remains unchanged: local auth and connector shape are present, but the blocker is external operational configuration. Closure still needs a real reachable HTTPS service boundary URL plus API key/connection-reference values before creating the custom connector connection or claiming app/flow runtime smoke.

[edithatogo]

Live recheck on 2026-05-26 after the latest registry evidence updates:

• pac auth list is authenticated as Dylan.Mordaunt@health.nsw.gov.au against Dylan Mordaunt (Illawarra Shoalhaven LHD)'s Environment.
• pac connector list still shows the custom connector MCHS Service Boundary as new_mchs-20service-20boundary with connector ID 0f3d6edc-9653-f111-bec6-00224893a0e1.
• pac connection list still does not show any connection whose API ID is /providers/Microsoft.PowerApps/apis/new_mchs-20service-20boundary; only standard Microsoft/Dataverse/Office connectors are connected.

Conclusion remains unchanged: the connector exists, but closure still requires the real service-boundary URL/API key and a live custom connector connection/connection reference before app/flow runtime smoke can be claimed.

[edithatogo]

Live PAC recheck on 2026-05-26:

• Target environment 611bca65-0b2a-eaa1-9e74-23bbba8eeec4 is active in PAC.
• pac connector list still shows MCHS Service Boundary / new_mchs-20service-20boundary / connector ID 0f3d6edc-9653-f111-bec6-00224893a0e1.
• pac connector download succeeded, but downloaded apiDefinition.json still has host: example.invalid, basePath: /, and schemes: [https]; downloaded apiProperties.json exposed no populated connection parameters.
• pac connection list still shows no connection for /providers/Microsoft.PowerApps/apis/new_mchs-20service-20boundary.

Evidence is recorded in power-platform/evidence/tenant-cli-observation-20260526.json. The blocker remains a real reachable HTTPS service-boundary URL plus API key/custom connector connection and connection-reference binding.