Skip to content

Commit f5a280b

Browse files
committed
fix links
1 parent e6aa986 commit f5a280b

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

articles/azure-resource-manager/management/azure-subscription-service-limits.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,6 @@ This document lists some of the most common Microsoft Azure limits, which are al
1313

1414
To learn more about Azure pricing, see [Azure pricing overview](https://azure.microsoft.com/pricing/). There, you can estimate your costs by using the [pricing calculator](https://azure.microsoft.com/pricing/calculator/). You also can go to the pricing details page for a particular service, for example, [Windows VMs](https://azure.microsoft.com/pricing/details/virtual-machines/#Windows). For tips to help manage your costs, see [Prevent unexpected costs with Azure billing and cost management](../../billing/billing-getting-started.md).
1515

16-
For limits on resource names, see [Naming rules and restrictions for Azure resources](resource-name-rules.md).
17-
1816
## Managing limits
1917

2018
If you want to raise the limit or quota above the default limit, [open an online customer support request at no charge](../templates/error-resource-quota.md). The limits can't be raised above the maximum limit value shown in the following tables. If there's no maximum limit column, the resource doesn't have adjustable limits.
@@ -29,12 +27,14 @@ As a result, decide what your Azure resource group quotas must be for your workl
2927

3028
## General limits
3129

30+
For limits on resource names, see [Naming rules and restrictions for Azure resources](resource-name-rules.md).
31+
32+
For information about Resource Manager API read and write limits, see [Throttling Resource Manager requests](request-limits-and-throttling.md).
33+
3234
### Subscription limits
3335

3436
The following limits apply when you use Azure Resource Manager and Azure resource groups.
3537

36-
For information about Resource Manager API read and write limits, see [Throttling Resource Manager requests](request-limits-and-throttling.md).
37-
3838
[!INCLUDE [azure-subscription-limits-azure-resource-manager](../../../includes/azure-subscription-limits-azure-resource-manager.md)]
3939

4040
### Resource group limits

articles/virtual-machines/linux/migration-classic-resource-manager-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ For this step you'll need to switch to `arm` mode. Do this with the following co
8181
azure config mode arm
8282
```
8383

84-
You can use the following CLI command to check the current number of vCPUs you have in Azure Resource Manager. To learn more about vCPU quotas, see [Limits and the Azure Resource Manager](../../azure-resource-manager/management/azure-subscription-service-limits.md#limits-and-azure-resource-manager)
84+
You can use the following CLI command to check the current number of vCPUs you have in Azure Resource Manager. To learn more about vCPU quotas, see [Limits and the Azure Resource Manager](../../azure-resource-manager/management/azure-subscription-service-limits.md#managing-limits).
8585

8686
```
8787
azure vm list-usage -l "<Your VNET or Deployment's Azure region"

articles/virtual-machines/windows/migration-classic-resource-manager-ps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ Set your Azure subscription for the current session. This example sets the defau
122122
<br>
123123

124124
## Step 5: Have enough Resource Manager VM vCPUs
125-
Make sure that you have enough Azure Resource Manager virtual machine vCPUs in the Azure region of your current deployment or virtual network. You can use the following PowerShell command to check the current number of vCPUs you have in Azure Resource Manager. To learn more about vCPU quotas, see [Limits and the Azure Resource Manager](../../azure-resource-manager/management/azure-subscription-service-limits.md#limits-and-azure-resource-manager).
125+
Make sure that you have enough Azure Resource Manager virtual machine vCPUs in the Azure region of your current deployment or virtual network. You can use the following PowerShell command to check the current number of vCPUs you have in Azure Resource Manager. To learn more about vCPU quotas, see [Limits and the Azure Resource Manager](../../azure-resource-manager/management/azure-subscription-service-limits.md#managing-limits).
126126

127127
This example checks the availability in the **West US** region. Replace the example region name with your own.
128128

0 commit comments

Comments
 (0)