Answered

Custom Connector using Gateway, Multiple Servers

(1) Share

Report

Posted on by NickTT

248

I have a custom connector that I setup to talk to an API on prem through a Gateway. I now need it to work with additional servers. TEST Server and a PROD server. Is there really no way to make this work besides making a dedicated PROD and TEST version of the custom connector?

Categories:

Using connectors

Connector development

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Suggested answer

Haque 2,427 on at

Like (1)

Report
Copy link

Link copied!
Hi @NickTT.

To my best knowledge, in Power Automate custom connectors using an on-premises data gateway, there isn’t a built-in way to dynamically switch between multiple backend servers (like TEST and PROD) within a single connector instance. Typically, each custom connector is tied to a specific backend URL configured during its setup.

We have some limited alternatives for the same:

Option-1: Create Separate Custom Connectors for Each Environment: This is the most straightforward and common approach. You create one connector configured for the TEST server and another for the PROD server. Then, in your flows, you choose which connector to use based on the environment.

Option-2: Use Environment Variables or Parameters in the Connector (Limited): While custom connectors support parameters, the base URL is usually fixed and cannot be dynamically changed at runtime. Some users try to use parameters in the connector’s host URL, but this is not officially supported for switching environments dynamically.

Option-3: Use Multiple Gateways or Gateway Clusters: You can configure multiple gateways pointing to different servers, but the connector still needs to be associated with a specific gateway and URL.

Reference:

https://learn.microsoft.com/en-us/connectors/custom-connectors/environment-variables

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

NickTT 248 on at

Like (1)

Report
Copy link

Link copied!

I think I figured out my work around then. I have my Custom Connector in a Solution that I publish to each environment through Pipelines. I would default the connector to use the TEST server host name. Then when I get to the Production environment, modify that connector, creating a solution layer, that has the production server as the host name. That way I don't have to duplicate efforts and change my current workflows.

Was this reply helpful? Yes No
Verified answer

Haque 2,427 on at

Like (1)

Report
Copy link

Link copied!

Hi @NickTT,

The solution based work around sounds good, just care should be taken when you move to prod, to "modify the connector" - a cutover task item that should be there to address it (in fact every time you do it).

Thanks for sharing.

Was this reply helpful? Yes No
11manish 2,028 on at

Like (0)

Report
Copy link

Link copied!

Your workaround using a solution layer override will work, but it is not recommended because it breaks ALM best practices, introduces hidden

configuration, and can be overwritten during future deployments.

The proper approach is to parameterize the connector and use environment variables to define the base URL per environment, ensuring

consistent, maintainable, and pipeline-safe deployments.

Was this reply helpful? Yes No
NickTT 248 on at

Like (0)

Report
Copy link

Link copied!

@11manish except you can't for the base URL with custom connectors that connect through a Gateway. Custom connector wizard won't let you save the file. Even if you go in and change it on the swagger side. I had created an environment variable but the Custom Connector wizard wouldn't let me use it. Would give you an invalid host name error. Really annoying that we can't do this with a custom connector.

If you are saying there is a way around this... please share the steps or URL to an example.

Was this reply helpful? Yes No
11manish 2,028 on at

Like (0)

Report
Copy link

Link copied!

Correct NickTT, understand your points.

When using a custom connector with an on-premises gateway, the base URL must be static and cannot be parameterized using environment

variables or Swagger modifications.

This is a platform limitation.

The supported approaches are to use multiple connections (each mapped to different gateway data sources), implement a reverse proxy or

unified endpoint to route traffic internally, or maintain separate connectors for each environment.

Was this reply helpful? Yes No
NickTT 248 on at

Like (0)

Report
Copy link

Link copied!

I wonder why the limitation. Security?

Was this reply helpful? Yes No