On-premises Data Gateway - IP Address Tags

[PeterMansion]

Hi,

I work in a pretty locked down environment whereby we need to open outbound Firewall ports / IP addresses to allow connectivity. We do this by using the FQDN's in the Gatway documentation - Adjust communication settings for the on-premises data gateway | Microsoft Learn. 

Our Gateway was working fine for a while until I started seeing the following error:

"XXX Gateway" is configured correctly but is unreachable due to local network connectivity problems.

Our Firewall log files are showing the following drops (blocked IP's).

If I take the latest drop (08:43:47) this seems to be an "AzureMonitor" IP address (which is not in the list of Tags that the Gateway reqires).

Do I need connectivity to all of the IP's for the Gateway to work?

Note that the Connectivity test in the Gateway works perfectly with no errors (I suspect this is only testing ServiceBus IP's).

Also, looking at the documentation (below) I seem to be missing the facility to test "Netwrok Status". Is this a deprecated function?

Does anyone have any tips for getting me back up and running? Obviously, I want to avoid hard coding IP addresses in case they change in the future.

Thanks in advance.

[wikkleyn]

Hi @PeterMansion  Have you looked at adding the URLs to your allowlist instead of the IPs? We did go the IP route, but the IPs change without prior knowledge and that causes outages.

[PeterMansion · Accepted solution]

Thanks for the replies. In the end, a re-install of the Gateway fixed my issue.

[PeterMansion]

Thanks. We tried that but I'm not convinced that the URL's are an exhaustive list. Have you had to add any URL's other than the ones that Microsoft advise?

[GilbertQ]

Hi @PeterMansion 

Do you mean that the HTTPS option does not work?

[PeterMansion]

Yes, we are set to "HTTPS" and it's still not working.