Fixing broken anchor links

Author: rothja

articles/sql-database/sql-database-instance-pools.md

@@ -121,7 +121,7 @@ If you are experiencing issues related to instance pool deployment (creation or
 
 If you are experiencing issues related to single instances or databases within a pool, you should create a regular support ticket for Azure SQL Database managed instances.
 
-To create larger managed instance deployments (with or without instance pools), you may need to obtain a larger regional quota. Use the [standard managed instance procedure for requesting a larger quota](sql-database-managed-instance-resource-limits.md#obtaining-a-larger-quota-for-sql-managed-instance), but note that if you are using instance pools, the deployment logic compares total vCore consumption *at the pool level* against your quota to determine whether you are allowed to create new resources without further increasing your quota.
+To create larger managed instance deployments (with or without instance pools), you may need to obtain a larger regional quota. For more information, see [Request quota increases for Azure SQL Database](quota-increase-request.md). Note that if you are using instance pools, the deployment logic compares total vCore consumption *at the pool level* against your quota to determine whether you are allowed to create new resources without further increasing your quota.
 
 ## Instance pool billing
 

articles/sql-database/sql-database-managed-instance-resource-limits.md

@@ -101,7 +101,7 @@ There are also instance-level limits like max log write throughput 22 MB/s, so y
 
 ## Supported regions
 
-Managed instances can be created only in [supported regions](https://azure.microsoft.com/global-infrastructure/services/?products=sql-database&regions=all). To create a managed instance in a region that is currently not supported, you can [send a support request via the Azure portal](#obtaining-a-larger-quota-for-sql-managed-instance).
+Managed instances can be created only in [supported regions](https://azure.microsoft.com/global-infrastructure/services/?products=sql-database&regions=all). To create a managed instance in a region that is currently not supported, you can [send a support request via the Azure portal](quota-increase-request.md).
 
 ## Supported subscription types
 
@@ -116,13 +116,13 @@ Managed instance currently supports deployment only on the following types of su
 
 ## Regional resource limitations
 
-Supported subscription types can contain a limited number of resources per region. Managed instance has two default limits per Azure region (that can be increased on-demand by creating a special [support request in the Azure portal](#obtaining-a-larger-quota-for-sql-managed-instance)) depending on a type of subscription type:
+Supported subscription types can contain a limited number of resources per region. Managed instance has two default limits per Azure region (that can be increased on-demand by creating a special [support request in the Azure portal](quota-increase-request.md) depending on a type of subscription type:
 
 - **Subnet limit**: The maximum number of subnets where managed instances are deployed in a single region.
 - **vCore unit limit**: The maximum number of vCore units that can be deployed across all instances in a single region. One GP vCore uses one vCore unit and one BC vCore takes 4 vCore units. The total number of instances is not limited as long as it is within the vCore unit limit.
 
 > [!Note]
-> These limits are default settings and not technical limitations. The limits can be increased on-demand by creating a special [support request in the Azure portal](#obtaining-a-larger-quota-for-sql-managed-instance) if you need more managed instances in the current region. As an alternative, you can create new managed instances in another Azure region without sending support requests.
+> These limits are default settings and not technical limitations. The limits can be increased on-demand by creating a special [support request in the Azure portal](quota-increase-request.md) if you need more managed instances in the current region. As an alternative, you can create new managed instances in another Azure region without sending support requests.
 
 The following table shows the **default regional limits** for supported subscription types (default limits can be extended using support request described below):
 

articles/sql-database/sql-database-purchase-models.md

@@ -71,7 +71,7 @@ The vCore-based purchasing model lets you independently choose compute and stora
 
 > [!IMPORTANT]
 > Compute resources, I/O, and data and log storage are charged per database or elastic pool. Backup storage is charged per each database. For more information about managed instance charges, see [managed instances](sql-database-managed-instance.md).
-> **Region limitations:** For the current list of supported regions, see [products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=sql-database&regions=all). To create a managed instance in a region that currently isn't supported, [send a support request via the Azure portal](sql-database-managed-instance-resource-limits.md#obtaining-a-larger-quota-for-sql-managed-instance).
+> **Region limitations:** For the current list of supported regions, see [products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=sql-database&regions=all). To create a managed instance in a region that currently isn't supported, [send a support request via the Azure portal](quota-increase-request.md).
 
 If your single database or elastic pool consumes more than 300 DTUs, converting to the vCore-based purchasing model might reduce your costs. You can convert by using your API of choice or by using the Azure portal, with no downtime. However, conversion isn't required and isn't done automatically. If the DTU-based purchasing model meets your performance and business requirements, you should continue using it.