Power Platform Community Forum Thread Details

We have developed a number of solutions and Power Automate flows that depend on connections and virtual tables connected to an on-premises SQL database. We're using the On Premises Data Gateway to facilitate this connection.

However, our test and production environments are geolocated in a different region than our default environment (to improve latency and performance). We've configured virtual network data gateways to replace the OPDG and they work fine in the default environment, but we are unable to use them in the other environments. Because I cannot install more than one OPDG on a given server host, I would have to create another server to host the other region's OPDG for the test and prod environments. Here is the relevant documentation for vnet data gateway support for on-premises SQL database connections:

Create virtual network (VNet) data gateways | Microsoft Learn

VNet Data Gateway support for SQL Server and custom connectors (Preview) | Microsoft Learn

Check if gateway is in the right region - Power Automate | Microsoft Learn

Instead of randomly selecting or creating new server hosts to host the OPDG, it would be better if the vnet data gateways could be used in other regions. Right now, what we're considering doing is to move all our current OPDG connections to vnet data gateways and reconfigure the OPDG for the other region environment.

Does anybody know of a way to configure network resources in Azure to make vnet data gateways accessible in non-default environments? Or if MS plans for vnet data gateways includes having this functionality?

Categories:

Microsoft Dataverse with Power Apps