Forum Discussion
Issue with adding gateway to cluster
They are on different Azure subscriptions and resource groups, but same Azure region and tenant.wait what?! Enterprise Gateways are supposed to be on-premise VMs, not Azure. You should be using VNet gateways for Azure.
On the new cluster member install SSMS and verify that you can see all the databases from there.
I might be mistaken but isn't that still only in preview? And only in some regions?
https://learn.microsoft.com/en-us/data-integration/vnet/overview
And we've been using Azure VMs to provide secure gateway to Azure PaaS since 2018:
We're doing the same, Azure VMs for gateways. We tested the connections via SSMS and ended up standing up two identical VMs on the same Vnet, same subscription and same configuration, then clustering those together. It looks like the vastly different OS versions between the two were causing compatibility issues. Either that, or the different vnets were causing firewall issues with our data sources. Either way, it's working better now.
Ah great, thanks for replying, that's interesting to know. We're wanting to automate joining the second VM into the gateway cluster but it seems you can't do it using the PS cmdlets. Did you install yours manually or have you managed to automate? (I've asked separately here)