Adding links to the new SQL DB quotas page

rothja · rothja · commit 75d90c90f04a · 2020-02-20T13:05:53.000-05:00
diff --git a/articles/sql-database/quota-increase-request.md b/articles/sql-database/quota-increase-request.md
@@ -85,7 +85,7 @@ Use the following steps to request an increase in the number of servers per subs
 
 For more information, see [SQL Database resource limits and resource governance](sql-database-resource-limits-database-server.md).
 
-### Enable subscription access to a region
+### <a id="other"></a> Enable subscription access to a region
 
 Some offer types are not available in every region. You may see an error such as the following:
 
diff --git a/articles/sql-database/sql-database-managed-instance-resource-limits.md b/articles/sql-database/sql-database-managed-instance-resource-limits.md
@@ -140,39 +140,9 @@ The following table shows the **default regional limits** for supported subscrip
 
 \*\* Larger subnet and vCore limits are available in the following regions: Australia East, East US, East US 2, North Europe, South Central US, Southeast Asia, UK South, West Europe, West US 2.
 
-## Obtaining a larger quota for SQL managed instance
+## Request a quota increase for SQL managed instance
 
-If you need more managed instances in your current regions, send a support request to extend the quota using the Azure portal.
-To initiate the process of obtaining a larger quota:
-
-1. Open **Help + support**, and click **New support request**.
-
-   ![Help and Support](media/sql-database-managed-instance-resource-limits/help-and-support.png)
-2. On the Basics tab for the new support request:
-   - For **Issue type**, select **Service and subscription limits (quotas)**.
-   - For **Subscription**, select your subscription.
-   - For **Quota type**, select **SQL Database Managed Instance**.
-   - For **Support plan**, select your support plan.
-
-     ![Issue type quota](media/sql-database-managed-instance-resource-limits/issue-type-quota.png)
-
-3. Click **Next**.
-4. On the **Problem tab** for the new support request:
-   - For **Severity**, select the severity level of the problem.
-   - For **Details**, provide additional information about your issue, including error messages.
-   - For **File upload**, attach a file with more information (up to 4 MB).
-
-     ![Problem details](media/sql-database-managed-instance-resource-limits/problem-details.png)
-
-     > [!IMPORTANT]
-     > A valid request should include:
-     > - Region in which subscription limit needs to be increased.
-     > - Required number of vCores, per service tier in existing subnets after the quota increase (if any of the existing subnets needs to be expanded.
-     > - Required number of new subnets and total number of vCores per service tier within the new subnets (if you need to deploy managed instances in new subnets).
-
-5. Click **Next**.
-6. On the Contact Information tab for the new support request, enter preferred contact method (email or phone) and the contact details.
-7. Click **Create**.
+If you need more managed instances in your current regions, send a support request to extend the quota using the Azure portal. For more information, see [Request quota increases for Azure SQL Database](quota-increase-request.md).
 
 ## Next steps
 
diff --git a/articles/sql-database/sql-database-resource-limits-database-server.md b/articles/sql-database/sql-database-resource-limits-database-server.md
@@ -32,15 +32,15 @@ This article provides an overview of the SQL Database resource limits for a SQL
 | Max pools per server | Limited by number of DTUs or vCores. For example, if each pool is 1000 DTUs, then a server can support 54 pools.|
 |||
 
-> [!NOTE]
-> To obtain more DTU/eDTU quota, vCore quota, or more servers than the default amount, a new support request can be submitted in the Azure portal for the subscription with issue type “Quota”. The DTU/eDTU quota and database limit per server constrains the number of elastic pools per server.
-
 > [!IMPORTANT]
 > As the number of databases approaches the limit per SQL Database server, the following can occur:
 >
 > - Increasing latency in running queries against the master database.  This includes views of resource utilization statistics such as sys.resource_stats.
 > - Increasing latency in management operations and rendering portal viewpoints that involve enumerating databases in the server.
 
+> [!NOTE]
+> To obtain more DTU/eDTU quota, vCore quota, or more servers than the default amount, submit a new support request in the Azure portal. For more information, see [Request quota increases for Azure SQL Database](quota-increase-request.md).
+
 ### Storage size
 
 For single databases resource storage sizes, refer to either [DTU-based resource limits](sql-database-dtu-resource-limits-single-databases.md) or [vCore-based resource limits](sql-database-vcore-resource-limits-single-databases.md) for the storage size limits per pricing tier.
diff --git a/articles/sql-database/sql-database-service-tier-hyperscale.md b/articles/sql-database/sql-database-service-tier-hyperscale.md
@@ -187,49 +187,14 @@ The Azure SQL Database Hyperscale tier is currently available in the following r
 - West US
 - West US 2
 
-If you want to create Hyperscale database in a region that is not listed as supported, you can send an onboarding request via Azure portal. We are working to expand the list of supported regions so please check back for latest region list.
+If you want to create Hyperscale database in a region that is not listed as supported, you can send an onboarding request via Azure portal. For instructions, see [Request quota increases for Azure SQL Database](quota-increase-request.md) for instructions. When submitting your request, use the following guidelines:
 
-To request the ability to create Hyperscale databases in regions not listed:
-
-1. Navigate to [Azure Help and Support Blade](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview)
-
-2. Click on [**New support request**](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest)
-
-    ![Azure Help and Support Blade](media/sql-database-service-tier-hyperscale/request-screen-1.png)
-
-3. For **Issue Type**, select **Service and subscription limits (quotas)**
-
-4. Choose the subscription you would use to create the database(s)
-
-5. For **Quota Type**, select **SQL database**
-
-6. Click **Next: Solutions**
-
-1. Click **Provide Details**
-
-    ![Problem details](media/sql-database-service-tier-hyperscale/request-screen-2.png)
-
-8. Choose **SQL Database quota type**: **Other quota request**
-
-9. Fill in the following template:
-
-    ![Quota details](media/sql-database-service-tier-hyperscale/request-screen-3.png)
-
-    In the template, provide the following information
-
-    > Request to create Azure Hyperscale SQL Database in a new region<br/> 
-    > Region: [Fill in your requested region]  <br/>
-    > Compute SKU/total cores including readable replicas <br/>
-    > Number of TB estimated 
-    >
-
-10. Choose **Severity C**
-
-11. Choose the appropriate contact method and fill in details.
-
-12. Click **Save** and **Continue**
+- Use the [Other quota request](quota-increase-request.md#other) SQL database quota type.
+- In the text details, add the compute SKU/total cores including readable replicas.
+- Also specify the estimated TB.
 
 ## Known limitations
+
 These are the current limitations to the Hyperscale service tier as of GA.  We are actively working to remove as many of these limitations as possible.
 
 | Issue | Description |
