Links: Azure (2021-03) - 8

Author: DCtheGeek

articles/mysql/concepts-connectivity-architecture.md

@@ -105,7 +105,7 @@ Only Gateway nodes will be decommissioned. When users connect to their servers,
 ### How can you validate if your connections are going to old gateway nodes or new gateway nodes?
 Ping your server’s FQDN, for example  ``ping xxx.mysql.database.azure.com``. If the returned IP address is one of the IPs listed under Gateway IP addresses (decommissioning) in the document above, it means your connection is going through the old gateway. Contrarily, if the returned Ip address is one of the IPs listed under Gateway IP addresses, it means your connection is going through the new gateway.
 
-You may also test by [PSPing](https://docs.microsoft.com/sysinternals/downloads/psping) or TCPPing the database server from your client application with port 3306 and ensure that return IP address isn't one of the decommissioning IP addresses
+You may also test by [PSPing](/sysinternals/downloads/psping) or TCPPing the database server from your client application with port 3306 and ensure that return IP address isn't one of the decommissioning IP addresses
 
 ### How do I know when the maintenance is over and will I get another notification when old IP addresses are decommissioned?
 You will receive an email to inform you when we will start the maintenance work. The maintenance can take up to one month depending on the number of servers we need to migrate in al regions. Please prepare your client to connect to the database server using the FQDN or using the new IP address from the table above. 

articles/network-watcher/migrate-to-connection-monitor-from-network-performance-monitor.md

@@ -26,7 +26,7 @@ You can migrate tests from Network Performance Monitor (NPM) to new, improved Co
 
 The migration helps produce the following results:
 
-* On-premises agents and firewall settings work as is. No changes are required. Log Analytics agents that are installed on Azure virtual machines need to be replaced with the [Network Watcher extension](https://docs.microsoft.com/azure/virtual-machines/extensions/network-watcher-windows).
+* On-premises agents and firewall settings work as is. No changes are required. Log Analytics agents that are installed on Azure virtual machines need to be replaced with the [Network Watcher extension](../virtual-machines/extensions/network-watcher-windows.md).
 * Existing tests are mapped to Connection Monitor > Test Group > Test format. By selecting **Edit**, you can view and modify the properties of the new Connection Monitor, download a template to make changes to it, and submit the template via Azure Resource Manager.
 * Agents send data to both the Log Analytics workspace and the metrics.
 * Data monitoring:
@@ -74,4 +74,4 @@ After the migration, be sure to:
 
 To learn more about Connection Monitor, see:
 * [Migrate from Connection Monitor (classic) to Connection Monitor](./migrate-to-connection-monitor-from-connection-monitor-classic.md)
-* [Create Connection Monitor by using the Azure portal](./connection-monitor-create-using-portal.md)
+* [Create Connection Monitor by using the Azure portal](./connection-monitor-create-using-portal.md)