Supporting on-premises data gateways in non-default environments

We recently added support for on-premises data gateways in non-default environments. Previously, you could only install and connect to a gateway in the Power Automate and Power Apps default environment. After much feedback, you can now view and use gateways in your other environments as well.

*On-Premises data gateways in non-default environments is not yet supported for GCC but is planned and should be available soon. Gateways installed in the default environment are supported for GCC.

One thing to note is the region where the gateway is installed must map to the region of your Power Automate and Power Apps environment in order to view, connect to, and manage the gateway in that environment. Scenarios that cross geographic boundaries are not supported.

For example:

• You install a gateway in the West US region. Your Power Automate environment (default or non-default) is also set up in the United States. This gateway will be visible and usable in this environment.
• You install a gateway in the West US region. Your Power Automate environment (default or non-default) is set up in Canada. This gateway will not be visible or usable in this environment.

Support

It’s possible this new feature may have changed whether you could view or manage existing gateways in Power Automate and Power Apps. If so, you may be able to troubleshoot why based on the scenarios below.

Why can’t I see my gateway(s)?

If you are in the Power Automate or Power Apps portal and are not able to see one (or many) of your gateways listed under the “Gateways” menu item or as an option to select in the dropdown when creating a connection, check to ensure the region where you installed the gateway matches the region of your Power Automate/Power Apps environment. We do not support cross-geo scenarios so if they do not match, you will not be able to view or use that gateway(s) in that environment. You will need to install a new gateway in the region that matches your Power Automate/Power Apps environment region.

Prior to this feature, did you create a support ticket to install a gateway in non-default environment?

If you got an exception to install a gateway in a non-default environment before this feature was available, depending on the region that gateway was installed in, you may no longer be able to view or manage (e.g., edit, delete) that gateway in Power Automate/Power Apps (as mentioned above). However, any existing connections using that gateway in your flows should continue to work. In order to be able to view and manage the gateway used in your flows and apps, you’ll need to install a new gateway in the appropriate region then update your connection(s) with the new gateway.

As always, we’d love to hear any feedback you have for this feature as well as other capabilities you’d love to see in the future. Thanks!