On-premise gateway and dynamic host

[CDRPepijn]

Hi,

Sorry if this question has been asked before but I couldn't find any similar posts. I'm trying to make 1 connector to connect to a service for which the URL differs based on your company name. So for instance the company "Company A" would get the URL "companya.someservice.com". 

The service that I'm trying to connect to, limits access using IP filtering. So we have an on-premise gateway from a server that has an IP that is allowed to connect to 5 different companies. If I hard-code the host-url, the connection works perfectly (so via the on-premise gateway) but if I use the "Set Host URL" via a policy, the connection times out which seems to indicate that it skips the on-premise gateway.

Is this a bug or am I making a mistake here?

Thanks,

Pepijn

[PowerAutomate7]

Hi,
I have a similar question so just will add here:
If i use static host - 127.0.0.1:3000 - with on-premises gateway it works as expected.

But using a policy template as: http://@queryParameters('portalUrl')

Returns:

{
"error": {
"code": 500,
"message": "No connection could be made because the target machine actively refused it 127.0.0.1:3000",
"source": "msmanaged-na.azure-apim.net",
"path": "forward-request",
"policyId": "",
"clientRequestId": "1234"
}
}

[ErnstS]

We have the same problem, any news here?

[CDRPepijn]

Unfortunately, no. As a workaround I have created multiple connectors, one per subdomain. Not pretty but it works for now until there is a solution for this issue.

[Lietho]

Please upvote https://powerusers.microsoft.com/t5/Power-Apps-Ideas/Enable-quot-Set-Host-URL-quot-Policy-support-on.... Maybe this issue gets fixed if enough people vote up.