1 min read

Azure – You can now use FQDN name to define your Local Network Gateway

cubesys : Oct 22, 2020 12:00:00 AM

Azure Security

As you know, you can setup a Site-to-Site VPN between your on-premises infrastructure and Azure.

This VPN connectivity involves the creation of a Local Network Gateway (LNG).

Until now, you add to configure a public IP for your LNG.

Well, good news you can now use a Fully Qualified Domain Name (FQDN) instead of the public IP. This is quite handy if you have to connect branch offices which may use a dynamic public IP.

To start using this new capability, logon to your Azure portal (https://portal.azure.com) and create a new LNG

image_thumb

Then you can switch to FQDN for the endpoint definition

image_thumb[1]  image_thumb[2]

NOTES

  • Only 1 public IP is support when using FQDN. If the FQDN resolves to multiple IP’s, Azure VPN will then use the first IP returned.
  • Azure VPN is caching DNS resolution for 5 minutes, which may lead to temporary disconnection when the public IP is updated
  • The gateway tries to resolve FQDN only for disconnected tunnels (or if you reset the gateway)

Azure – Azure Firewall Manager can now integrate with virtual networks

cubesys : Feb 19, 2020 12:00:00 AM

As introduced some time ago, Azure Firewall Manager (AFM) is the central configuration and management point for Azure Firewall.

Azure Security
Read More

Azure – You can now resize your peered virtual network with no downtime (preview)

cubesys : Aug 16, 2021 12:00:00 AM

As you know, you can create virtual network (vNet) on Azure.

Azure
Read More

Azure AD – You can now use GPS coordinates for better accuracy on Named Location

cubesys : May 13, 2021 12:00:00 AM

As you know, you can configure Named Location on Azure AD for use with Conditional Access either based on public IP address or country.

Azure AD Security
Read More