Vibe Cannot See my Custom Connector

Question

Vibe Cannot See my Custom Connector

Corin Douglas 0

Custom connector MoC App Approvals Relay exists in the same environment, has a connected connection owned by me, and tests successfully with HTTP 200 returning { success, message, flowRunId }. However, Vibe’s connection picker only shows shared_a365mcpservers, so I cannot register or call the custom connector from the app. Any help would be appreciated.

Regards Corin.

Ashlesha Pawar (Tata Consultancy Services Limited) 365 Reputation points Microsoft External Staff

2026-08-17T05:28:53.6833333+00:00

Hello Corin,

Thank you for the detailed information. Your successful connector test confirms that the connection and backend operation are working. However, the new Power Apps vibe experience is currently in preview and its built-in connection picker doesn’t yet support registering arbitrary Power Platform custom connectors.

The shared_a365mcpservers entry is the internal API name for the supported Microsoft 365 MCP server connection. A custom connector existing in the same environment, being owned by you, and having a working connection doesn’t currently cause it to appear in this picker.

Custom connectors are supported by standard Power Apps code apps. As an alternative, you can create or maintain the application as a standard code app and add the connector by using Power Platform CLI:

pac connection list --environment <environment-url> pac code add-data-source -a <custom-connector-api-name> -c <connection-id>

The app and connector must belong to the same Power Platform environment. Cross-environment data-source references aren’t supported.

Please also note that exporting a vibe app and redeploying it through the CLI creates a separate code app and disconnects it from the original vibe plan. Therefore, this isn’t presently a supported way to modify the existing vibe app in place.

Custom connector support in the vibe picker would currently be a feature request rather than a problem with your connector.

Your answer

Ashlesha Pawar (Tata Consultancy Services Limited) 365 Reputation points Microsoft External Staff

2026-08-17T05:28:53.6833333+00:00

Hello Corin,

Thank you for the detailed information. Your successful connector test confirms that the connection and backend operation are working. However, the new Power Apps vibe experience is currently in preview and its built-in connection picker doesn’t yet support registering arbitrary Power Platform custom connectors.

The shared_a365mcpservers entry is the internal API name for the supported Microsoft 365 MCP server connection. A custom connector existing in the same environment, being owned by you, and having a working connection doesn’t currently cause it to appear in this picker.

Custom connectors are supported by standard Power Apps code apps. As an alternative, you can create or maintain the application as a standard code app and add the connector by using Power Platform CLI:

pac connection list --environment <environment-url> pac code add-data-source -a <custom-connector-api-name> -c <connection-id>

The app and connector must belong to the same Power Platform environment. Cross-environment data-source references aren’t supported.

Please also note that exporting a vibe app and redeploying it through the CLI creates a separate code app and disconnects it from the original vibe plan. Therefore, this isn’t presently a supported way to modify the existing vibe app in place.

Custom connector support in the vibe picker would currently be a feature request rather than a problem with your connector.