Officially since last summer –and fully functional since a couple of months– the on-premises data gateway can be shared across multiple subscriptions.
While at first glance this seems to be something trivial, it is in fact a very useful enhancement.
Before this feature was made available whenever you wanted to separate your resources into different subscriptions based on the environment and if these resources required access to on-premises resources, you were required to install 1 on-premises data gateway per environment, as you can only register each on-prem gateway once in Azure.
This also meant that, since you can only install a single gateway per machine, you were required to have at least 1 server, whether this was physical or virtual didn’t matter, per environment, even if all of those were pointing towards the same resource, e.g. a file-share.
With this feature this is no longer required. Simply install an on-premises data gateway onto a server within your network, register it within 1 of your Azure subscriptions and you will be able to connect from all your subscriptions within the same tenant.
Or, at least, you should be able to connect.
If you want to create a new ApiConnection from the designer view, you will be able to select your registered gateway from any of the subscriptions available to you, within the same tenant.
However, if you’ve registered the on-premises data gateway within a subscription that hasn’t been used for anything else yet, you might run into the following error-message when attempting to create an ApiConnection: ‘/subscriptions/{SubscriptionId}/resourceGroups/{ResourceGroup}/providers/Microsoft.Web/connections/filesystem’. Encountered internal server error. The tracking Id is ’67bec0fd-a8d5-49a2-9d84-48481c3c68bf’.
