Virtual gateway monitoring

[MikeSar]

We have connected an on premise local network with an Azure VPN via virtual gateway. 

At Azure VPN we have a database. We can connect at this database from the on premise local network.

Due to remote working, many employees connect to on premise local network via a VPN client. 

Those users are unable to connect at the Azure database.

The address space of the local network is 192.168.1.0/24.

The address space for the remote users is 10.212.135/24.

We have added both address spaces at the local network gateway.

Do we have to configure anything else on the Azure side?

How can we log or monitor the traffic at Azure Gateway and VPN?

[#2]

@MikeSar 

Configure some additional settings on the Azure side to allow the remote users to connect to the Azure database.

• Azure Network Security Group (NSG) Rules: You'll need to create an inbound rule in the Azure NSG that is associated with the virtual network to allow incoming traffic from the remote users' subnet (10.212.135.0/24) to reach the database subnet.
• Azure Virtual Network (VNet) Routing: You'll need to configure the virtual network's routing table to forward traffic between the remote users' subnet and the database subnet.

For logging and monitoring the traffic at the Azure gateway and VPN, you have several options:

• Azure Monitor: You can use Azure Monitor to monitor the performance and availability of your VPN gateways and virtual networks. Follow the article Azure Monitor  
• Azure Network Watcher: You can use Azure Network Watcher to monitor the health and performance of your virtual network and VPN gateways.  Follow the article Azure Network Watcher 
• Azure Log Analytics: You can use Azure Log Analytics to view and analyze log data from various Azure resources, including VPN gateways and virtual networks. You can create custom log queries to view specific data, such as network traffic logs.Follow the article Log Analytics in Azure Monitor 

[#3]

Hi @Robina,

thank you for your answer. 

We have opened port 3306 from anywhere just to verify that the remote users can access the database but they still do not have access.

We have also peered a local gateway network with the address spaces of the IPs that the remote users gets at the on premise network and still nothing.

Just to remind you. A local user at our on premise network has access to the database but a user that is remotely connected to our on premise network via VPN client does not have access to the database.