fixing links

Author: VanMSFT

articles/sql-database/includes/sql-database-create-single-database.md

@@ -59,7 +59,7 @@ Create your resource group and single database using the Azure portal.
      - Optionally, you can also select **Change configuration** to change the hardware generation.
    - Select **Apply**.
 
-6. Select the **Networking** tab and decide if you want to **Allow Azure services and resources to access this server**, or add a [private endpoint](../../private-link/private-endpoint-overview.md).
+6. Select the **Networking** tab and decide if you want to [**Allow Azure services and resources to access this server**](../sql-database-networkaccess-overview.md), or add a [private endpoint](../../private-link/private-endpoint-overview.md).
 
    ![Networking Tab](../media/sql-database-get-started-portal/create-database-networking.png)
 

articles/sql-database/sql-database-networkaccess-overview.md

@@ -109,7 +109,7 @@ Be aware of the following Azure Networking terms as you explore Virtual Network
 
 **Subnet:** A virtual network contains **subnets**. Any Azure virtual machines (VMs) that you have are assigned to subnets. One subnet can contain multiple VMs or other compute nodes. Compute nodes that are outside of your virtual network cannot access your virtual network unless you configure your security to allow access.
 
-**Virtual Network service endpoint:** A [Virtual Network service endpoint][vm-virtual-network-service-endpoints-overview-649d] is a subnet whose property values include one or more formal Azure service type names. In this article we are interested in the type name of **Microsoft.Sql**, which refers to the Azure service named SQL Database.
+**Virtual Network service endpoint:** A [Virtual Network service endpoint](../virtual-network/virtual-network-service-endpoints-overview.md) is a subnet whose property values include one or more formal Azure service type names. In this article we are interested in the type name of **Microsoft.Sql**, which refers to the Azure service named SQL Database.
 
 **Virtual network rule:** A virtual network rule for your SQL Database server is a subnet that is listed in the access control list (ACL) of your SQL Database server. To be in the ACL for your SQL Database, the subnet must contain the **Microsoft.Sql** type name. A virtual network rule tells your SQL Database server to accept communications from every node that is on the subnet.
 
@@ -118,7 +118,7 @@ Be aware of the following Azure Networking terms as you explore Virtual Network
 
 The Azure SQL Server firewall allows you to specify IP address ranges from which communications are accepted into SQL Database. This approach is fine for stable IP addresses that are outside the Azure private network. However, virtual machines (VMs) within the Azure private network are configured with *dynamic* IP addresses. Dynamic IP addresses can change when your VM is restarted and in turn invalidate the IP-based firewall rule. It would be folly to specify a dynamic IP address in a firewall rule, in a production environment.
 
-You can work around this limitation by obtaining a *static* IP address for your VM. For details, see [Configure private IP addresses for a virtual machine by using the Azure portal][vm-configure-private-ip-addresses-for-a-virtual-machine-using-the-azure-portal-321w].However, the static IP approach can become difficult to manage, and it is costly when done at scale. 
+You can work around this limitation by obtaining a *static* IP address for your VM. For details, see [Configure private IP addresses for a virtual machine by using the Azure portal](../virtual-network/virtual-networks-static-private-ip-arm-pportal.md).However, the static IP approach can become difficult to manage, and it is costly when done at scale. 
 
 Virtual network rules are easier alternative to establish and to manage access from a specific subnet that contains your VMs.