Azure 配额管理指南：服务限制、容量验证与配额增加方法

azure-quotas by microsoft/github-copilot-for-azure

363 周安装量

160 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/microsoft/github-copilot-for-azure --skill azure-quotas

自动化云服务开发运维

🇨🇳中文介绍

Azure 配额 - 服务限制与容量管理

权威指南 — 请严格按照这些说明进行配额管理和容量验证。

概述

什么是 Azure 配额？

Azure 配额（也称为服务限制）是您可以在一个订阅中部署的资源的最大数量。配额：

防止意外过度配置
确保 Azure 上的资源公平分配
代表每个区域的可用容量
可以增加（可调整配额）或是固定的（不可调整配额）

核心概念：配额 = 资源可用性

如果您没有配额，就无法部署资源。在规划部署或选择区域时，请务必检查配额。

何时使用此技能

在以下情况下调用此技能：

规划新部署 - 在部署前验证容量
选择 Azure 区域 - 比较各区域的配额可用性
排查配额超出错误 - 检查当前使用量与限制
请求增加配额 - 通过 CLI 或门户提交增加请求
比较区域容量 - 查找具有可用配额的区域
验证配置限制 - 确保部署不会超出配额

快速参考

属性	详细信息

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

类型	可调整性	审批	示例
可调整	可通过门户/CLI/API 增加	通常自动批准	VM vCPU、公共 IP、存储账户
不可调整	固定限制	无法更改	订阅范围的硬性限制

理解资源名称映射

⚠️ 关键： ARM 资源类型与配额资源名称之间没有 1:1 的映射关系。

ARM 资源类型	配额资源名称
`Microsoft.App/managedEnvironments`	`ManagedEnvironmentCount`
`Microsoft.Compute/virtualMachines`	`standardDSv3Family`, `cores`, `virtualMachines`
`Microsoft.Network/publicIPAddresses`	`PublicIPAddresses`, `IPv4StandardSkuPublicIpAddresses`

切勿从 ARM 类型推断配额资源名称。 始终使用此工作流程：

列出资源提供程序的所有配额：

az quota list --scope /subscriptions/<id>/providers/<ProviderNamespace>/locations/<region>

通过 localizedValue（人类可读的描述）进行匹配以找到相关配额

在后续命令中使用 name 字段（而非 ARM 资源类型）：

az quota show --resource-name ManagedEnvironmentCount --scope ...
az quota usage show --resource-name ManagedEnvironmentCount --scope ...

📖 详细的映射示例和工作流程： 请参阅 commands.md - 理解资源名称映射

工作流程 1：检查特定资源的配额

场景： 在部署前验证配额限制和当前使用量

# 1. 安装配额扩展（如果尚未安装）
az extension add --name quota

# 2. 列出该提供程序的所有配额以找到配额资源名称
az quota list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus

# 3. 显示特定资源的配额限制
az quota show \
  --resource-name standardDSv3Family \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus

# 4. 显示当前使用量
az quota usage show \
  --resource-name standardDSv3Family \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus

输出示例分析：

配额限制：350 个 vCPU
当前使用量：50 个 vCPU
可用容量：300 个 vCPU (350 - 50)

📖 另请参阅： az quota show, az quota usage show

工作流程 2：跨区域比较配额

场景： 根据可用容量找到最佳部署区域

# 定义候选区域
REGIONS=("eastus" "eastus2" "westus2" "centralus")
VM_FAMILY="standardDSv3Family"
SUBSCRIPTION_ID="<subscription-id>"

# 检查跨区域的配额可用性
for region in "${REGIONS[@]}"; do
  echo "=== 检查 $region ==="
  
  # 获取限制
  LIMIT=$(az quota show \
    --resource-name $VM_FAMILY \
    --scope "/subscriptions/$SUBSCRIPTION_ID/providers/Microsoft.Compute/locations/$region" \
    --query "properties.limit.value" -o tsv)
  
  # 获取当前使用量
  USAGE=$(az quota usage show \
    --resource-name $VM_FAMILY \
    --scope "/subscriptions/$SUBSCRIPTION_ID/providers/Microsoft.Compute/locations/$region" \
    --query "properties.usages.value" -o tsv)
  
  # 计算可用量
  AVAILABLE=$((LIMIT - USAGE))
  
  echo "区域: $region | 限制: $LIMIT | 使用量: $USAGE | 可用: $AVAILABLE"
done

📖 另请参阅： 多区域比较脚本 (Bash & PowerShell)

工作流程 3：请求增加配额

场景： 当前配额不足以进行部署

# 请求增加 VM 配额
az quota update \
  --resource-name standardDSv3Family \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus \
  --limit-object value=500 \
  --resource-type dedicated

# 检查请求状态
az quota request status list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus

大多数可调整配额会在几分钟内自动批准
某些请求需要人工审核（数小时到数天）
不可调整配额需要 Azure 支持工单

📖 另请参阅： az quota update, az quota request status

工作流程 4：列出所有配额以供规划

场景： 了解某个区域中资源提供程序的所有配额

# 列出美国东部所有计算配额（表格格式）
az quota list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus \
  --output table

# 列出所有网络配额
az quota list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Network/locations/eastus \
  --output table

# 列出所有容器应用配额
az quota list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.App/locations/eastus \
  --output table

📖 另请参阅： az quota list

错误	原因	解决方案
REST API "无限制"	REST API 显示误导性的“无限”值	关键："无限制" ≠ 无限！改用 CLI。参见上方警告。检查服务限制文档
REST API 失败	REST API 不可靠且具有误导性	始终使用 Azure CLI - 完整 CLI 参考请参阅 commands.md
`ExtensionNotFound`	未安装配额扩展	`az extension add --name quota`
`BadRequest`	配额 API 不支持该资源提供程序	使用 CLI（首选）或服务限制文档
`MissingRegistration`	Microsoft.Quota 提供程序未注册	`az provider register --namespace Microsoft.Quota`
`QuotaExceeded`	部署将超出配额	请求增加或选择其他区域
`InvalidScope`	范围格式不正确	使用模式：`/subscriptions/<id>/providers/<namespace>/locations/<region>`

不受支持的资源提供程序

已知不受支持的提供程序：

❌ Microsoft.DocumentDB (Cosmos DB) - 使用门户或 Cosmos DB 限制文档

已确认可用的提供程序：

✅ Microsoft.Compute (VM、磁盘、核心)
✅ Microsoft.Network (VNet、IP、负载均衡器)
✅ Microsoft.App (容器应用)
✅ Microsoft.Storage (存储账户)
✅ Microsoft.MachineLearningServices (ML 计算)

📖 另请参阅： 故障排除指南

资源	链接
CLI 命令参考	commands.md - 完整语法、参数、示例
Azure 配额概述	Microsoft Learn
服务限制文档	Azure 订阅限制
Azure 门户 - 我的配额	门户链接
请求增加配额	如何请求增加

✅ 部署前始终检查配额 - 防止配额超出错误
✅ 首先运行 az quota list - 发现正确的配额资源名称
✅ 比较区域 - 查找具有可用容量的区域
✅ 考虑增长 - 请求比即时需求多 20% 的缓冲
✅ 使用表格输出进行概览 - --output table 用于快速浏览
✅ 记录配额来源 - 跟踪是来自配额 API 还是官方文档
✅ 监控使用趋势 - 在 80% 阈值处设置警报（通过门户）

┌─────────────────────────────────────────┐
│  1. 安装配额扩展                       │
│     az extension add --name quota       │
└─────────────────┬───────────────────────┘
                  │
                  ▼
┌─────────────────────────────────────────┐
│  2. 发现配额资源名称                   │
│     az quota list --scope ...           │
│     (通过 localizedValue 匹配)          │
└─────────────────┬───────────────────────┘
                  │
                  ▼
┌─────────────────────────────────────────┐
│  3. 检查当前使用量                     │
│     az quota usage show                 │
│     --resource-name <name>              │
└─────────────────┬───────────────────────┘
                  │
                  ▼
┌─────────────────────────────────────────┐
│  4. 检查配额限制                       │
│     az quota show                       │
│     --resource-name <name>              │
└─────────────────┬───────────────────────┘
                  │
                  ▼
┌─────────────────────────────────────────┐
│  5. 验证容量                           │
│     可用 = 限制 - (使用量 + 需求)      │
└─────────────────┬───────────────────────┘
                  │
                  ▼
         ┌────────┴────────┐
         │                 │
    ✅ 充足          ❌ 不足
         │                 │
         ▼                 ▼
    继续部署         请求增加配额
                    或更改区域

🇺🇸English

Azure Quotas - Service Limits & Capacity Management

AUTHORITATIVE GUIDANCE — Follow these instructions exactly for quota management and capacity validation.

Overview

What are Azure Quotas?

Azure quotas (also called service limits) are the maximum number of resources you can deploy in a subscription. Quotas:

Prevent accidental over-provisioning
Ensure fair resource distribution across Azure
Represent available capacity in each region
Can be increased (adjustable quotas) or are fixed (non-adjustable)

Key Concept: Quotas = Resource Availability

If you don't have quota, you cannot deploy resources. Always check quotas when planning deployments or selecting regions.

When to Use This Skill

Invoke this skill when:

Planning a new deployment - Validate capacity before deployment
Selecting an Azure region - Compare quota availability across regions
Troubleshooting quota exceeded errors - Check current usage vs limits
Requesting quota increases - Submit increase requests via CLI or Portal
Comparing regional capacity - Find regions with available quota
Validating provisioning limits - Ensure deployment won't exceed quotas

Quick Reference

Property	Details
Primary Tool	Azure CLI (`az quota`) - USE THIS FIRST, ALWAYS
Extension Required	`az extension add --name quota` (MUST install first)
Key Commands	`az quota list`, `az quota show`, `az quota usage list`, `az quota usage show`

⚠️ CRITICAL: ALWAYS USE CLI FIRST

Azure CLI (az quota) is the ONLY reliable method for checking quotas. Use CLI FIRST, always.

DO NOT use REST API or Portal as your first approach. They are unreliable and misleading.

Why you must use CLI first:

REST API is unreliable and shows misleading results

REST API "No Limit" or "Unlimited" values DO NOT mean unlimited capacity

"No Limit" typically means the resource doesn't support quota API (not unlimited!)

CLI provides clear BadRequest errors when providers aren't supported

CLI has consistent output format and better error messages

Portal may show incomplete or cached data

Mandatory workflow:

FIRST: Try az quota list / az quota show / az quota usage show

If CLI returnsBadRequest: Then use Azure service limits docs

Never start with REST API or Portal - only use as last resort

If you see "No Limit" in REST API/Portal: This is NOT unlimited capacity. It means:

The quota API doesn't support that resource type, OR

The quota isn't enforced via the API, OR

Service-specific limits still apply (check documentation)

For complete CLI command reference and examples, see commands.md.

Quota Types

Type	Adjustability	Approval	Examples
Adjustable	Can increase via Portal/CLI/API	Usually auto-approved	VM vCPUs, Public IPs, Storage accounts
Non-adjustable	Fixed limits	Cannot be changed	Subscription-wide hard limits

Important: Requesting quota increases is free. You only pay for resources you actually use, not for quota allocation.

Understanding Resource Name Mapping

⚠️ CRITICAL: There is NO 1:1 mapping between ARM resource types and quota resource names.

Example Mappings

ARM Resource Type	Quota Resource Name
`Microsoft.App/managedEnvironments`	`ManagedEnvironmentCount`
`Microsoft.Compute/virtualMachines`	`standardDSv3Family`, `cores`, `virtualMachines`
`Microsoft.Network/publicIPAddresses`	`PublicIPAddresses`,

Discovery Workflow

Never assume the quota resource name from the ARM type. Always use this workflow:

List all quotas for the resource provider:

az quota list --scope /subscriptions/<id>/providers/<ProviderNamespace>/locations/<region>

Match bylocalizedValue (human-readable description) to find the relevant quota

Use thename field (not ARM resource type) in subsequent commands:

az quota show --resource-name ManagedEnvironmentCount --scope ...
az quota usage show --resource-name ManagedEnvironmentCount --scope ...

📖 Detailed mapping examples and workflow: See commands.md - Understanding Resource Name Mapping

Core Workflows

Workflow 1: Check Quota for a Specific Resource

Scenario: Verify quota limit and current usage before deployment

# 1. Install quota extension (if not already installed)
az extension add --name quota

# 2. List all quotas for the provider to find the quota resource name
az quota list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus

# 3. Show quota limit for a specific resource
az quota show \
  --resource-name standardDSv3Family \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus

# 4. Show current usage
az quota usage show \
  --resource-name standardDSv3Family \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus

Example Output Analysis:

Quota limit: 350 vCPUs
Current usage: 50 vCPUs
Available capacity: 300 vCPUs (350 - 50)

📖 See also: az quota show, az quota usage show

Workflow 2: Compare Quotas Across Regions

Scenario: Find the best region for deployment based on available capacity

# Define candidate regions
REGIONS=("eastus" "eastus2" "westus2" "centralus")
VM_FAMILY="standardDSv3Family"
SUBSCRIPTION_ID="<subscription-id>"

# Check quota availability across regions
for region in "${REGIONS[@]}"; do
  echo "=== Checking $region ==="
  
  # Get limit
  LIMIT=$(az quota show \
    --resource-name $VM_FAMILY \
    --scope "/subscriptions/$SUBSCRIPTION_ID/providers/Microsoft.Compute/locations/$region" \
    --query "properties.limit.value" -o tsv)
  
  # Get current usage
  USAGE=$(az quota usage show \
    --resource-name $VM_FAMILY \
    --scope "/subscriptions/$SUBSCRIPTION_ID/providers/Microsoft.Compute/locations/$region" \
    --query "properties.usages.value" -o tsv)
  
  # Calculate available
  AVAILABLE=$((LIMIT - USAGE))
  
  echo "Region: $region | Limit: $LIMIT | Usage: $USAGE | Available: $AVAILABLE"
done

📖 See also: Multi-region comparison scripts (Bash & PowerShell)

Workflow 3: Request Quota Increase

Scenario: Current quota is insufficient for deployment

# Request increase for VM quota
az quota update \
  --resource-name standardDSv3Family \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus \
  --limit-object value=500 \
  --resource-type dedicated

# Check request status
az quota request status list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus

Approval Process:

Most adjustable quotas are auto-approved within minutes
Some requests require manual review (hours to days)
Non-adjustable quotas require Azure Support ticket

📖 See also: az quota update, az quota request status

Workflow 4: List All Quotas for Planning

Scenario: Understand all quotas for a resource provider in a region

# List all compute quotas in East US (table format)
az quota list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Compute/locations/eastus \
  --output table

# List all network quotas
az quota list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.Network/locations/eastus \
  --output table

# List all Container Apps quotas
az quota list \
  --scope /subscriptions/<subscription-id>/providers/Microsoft.App/locations/eastus \
  --output table

📖 See also: az quota list

Troubleshooting

Common Errors

Error	Cause	Solution
REST API "No Limit"	REST API showing misleading "unlimited" values	CRITICAL: "No Limit" ≠ unlimited! Use CLI instead. See warning above. Check service limits docs
REST API failures	REST API unreliable and misleading	Always use Azure CLI - See commands.md for complete CLI reference
`ExtensionNotFound`	Quota extension not installed	`az extension add --name quota`
`BadRequest`

Unsupported Resource Providers

Known unsupported providers:

❌ Microsoft.DocumentDB (Cosmos DB) - Use Portal or Cosmos DB limits docs

Confirmed working providers:

✅ Microsoft.Compute (VMs, disks, cores)
✅ Microsoft.Network (VNets, IPs, load balancers)
✅ Microsoft.App (Container Apps)
✅ Microsoft.Storage (storage accounts)
✅ Microsoft.MachineLearningServices (ML compute)

📖 See also: Troubleshooting Guide

Additional Resources

Resource	Link
CLI Commands Reference	commands.md - Complete syntax, parameters, examples
Azure Quotas Overview	Microsoft Learn
Service Limits Documentation	Azure subscription limits
Azure Portal - My Quotas	Portal Link
Request Quota Increases	How to request increases

Best Practices

✅ Always check quotas before deployment - Prevent quota exceeded errors
✅ Runaz quota list first - Discover correct quota resource names
✅ Compare regions - Find regions with available capacity
✅ Account for growth - Request 20% buffer above immediate needs
✅ Use table output for overview - --output table for quick scanning
✅ Document quota sources - Track whether from quota API or official docs
✅ Monitor usage trends - Set up alerts at 80% threshold (via Portal)

Workflow Summary

┌─────────────────────────────────────────┐
│  1. Install quota extension             │
│     az extension add --name quota       │
└─────────────────┬───────────────────────┘
                  │
                  ▼
┌─────────────────────────────────────────┐
│  2. Discover quota resource names       │
│     az quota list --scope ...           │
│     (Match by localizedValue)           │
└─────────────────┬───────────────────────┘
                  │
                  ▼
┌─────────────────────────────────────────┐
│  3. Check current usage                 │
│     az quota usage show                 │
│     --resource-name <name>              │
└─────────────────┬───────────────────────┘
                  │
                  ▼
┌─────────────────────────────────────────┐
│  4. Check quota limit                   │
│     az quota show                       │
│     --resource-name <name>              │
└─────────────────┬───────────────────────┘
                  │
                  ▼
┌─────────────────────────────────────────┐
│  5. Validate capacity                   │
│     Available = Limit - (Usage + Need)  │
└─────────────────┬───────────────────────┘
                  │
                  ▼
         ┌────────┴────────┐
         │                 │
    ✅ Sufficient     ❌ Insufficient
         │                 │
         ▼                 ▼
    Proceed          Request increase
                     or change region

Weekly Installs

363

Repository

microsoft/githu…or-azure

GitHub Stars

160

First Seen

Mar 10, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

github-copilot349

codex54

gemini-cli53

kimi-cli45

amp45

cline45

Complete CLI Reference

IPv4StandardSkuPublicIpAddresses