Support gateways in all environments
|Enabled for||Public preview||Early access||General availability|
|Admins, makers, or analysts, automatically||-||-||Oct 23, 2019|
We've now 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. Additionally, on-premises gateway management is now available via PowerShell (preview).
The region where the gateway is installed must be the same as 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.
- If you install a gateway in the West US region and your Power Automate environment (default or non-default) is also set up in the United States, the gateway will be visible and usable in this environment.
- If you install a gateway in the West US region and your Power Automate environment (default or non-default) is set up in Canada, the gateway will not be visible or usable in this environment.
It’s possible this new feature may change whether you could view or manage existing gateways in Power Automate and Power Apps. If so, you may be able to troubleshoot based on these scenarios:
If you are using Power Automate or Power Apps and you aren't able to see one (or more) of your gateways under the Gateways menu or as an option to select in the list when creating a connection, confirm that the region where you installed the gateway matches the region in which your Power Automate or Power Apps environment is located. We do not support cross-geographic region 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 or Power Apps environment region.
You installed a gateway in a non-default environment with help from Microsoft Support
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 that gateway in Power Automate or Power Apps; however, any existing connections using that gateway in your flows should continue to work. 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 and then update your connection(s) with the new gateway.