您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

Azure 订阅和服务限制、配额和约束Azure subscription and service limits, quotas, and constraints

本文列出了一些最常见的 Microsoft Azure 限制,有时也称为配额。This document lists some of the most common Microsoft Azure limits, which are also sometimes called quotas. 本文当前并不涵盖所有 Azure 服务。This document doesn't currently cover all Azure services. 随着时间推移,将扩展和更新,包含更多服务列表。Over time, the list will be expanded and updated to cover more services.

若要了解有关 Azure 定价的详细信息,请参阅Azure 定价概述To learn more about Azure pricing, see Azure pricing overview. 可通过使用评估你的成本定价计算器There, you can estimate your costs by using the pricing calculator. 您也可以转到特定服务的定价详细信息页等Windows VmYou also can go to the pricing details page for a particular service, for example, Windows VMs. 有关帮助管理成本的提示,请参阅通过 Azure 计费和成本管理来防止意外成本For tips to help manage your costs, see Prevent unexpected costs with Azure billing and cost management.

备注

如果你想要提高限制或配额超出默认限制打开免费的联机客户支持请求If you want to raise the limit or quota above the default limit, open an online customer support request at no charge. 限制不能将提高到超过下表中显示的最大限制值。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.

免费试用版订阅不符合增加限制或配额。Free Trial subscriptions aren't eligible for limit or quota increases. 如果有免费试用版订阅,可将其升级到即用即付订阅。If you have a Free Trial subscription, you can upgrade to a Pay-As-You-Go subscription. 有关详细信息,请参阅将 Azure 免费试用版订阅升级到即用即付订阅免费试用版订阅常见问题解答For more information, see Upgrade your Azure Free Trial subscription to a Pay-As-You-Go subscription and the Free Trial subscription FAQ.

限制和 Azure 资源管理器Limits and Azure Resource Manager

现可以将多个 Azure 资源组合为单个 Azure 资源组。It's now possible to combine multiple Azure resources into a single Azure resource group. 当使用资源组时,在区域级别使用 Azure 资源管理器管理以前针对全局的限制。When you use resource groups, limits that once were global become managed at a regional level with Azure Resource Manager. 有关 Azure 资源组的详细信息,请参阅Azure 资源管理器概述For more information about Azure resource groups, see Azure Resource Manager overview.

在以下列表中的限制,新表时使用 Azure 资源管理器反映在限制的任何差异。In the following list of limits, a new table reflects any differences in limits when you use Azure Resource Manager. 例如,没有订阅限制表和一个订阅数限制-Azure 资源管理器表。For example, there's a Subscription limits table and a Subscription limits - Azure Resource Manager table. 当某个限制同时适用于这两种方案时,它仅显示第一个表中。When a limit applies to both scenarios, it's only shown in the first table. 除非另有说明,否则限制是跨所有区域的全局限制。Unless otherwise indicated, limits are global across all regions.

备注

Azure 资源组中的资源配额是每个区域由你的订阅,不根据订阅可访问的服务管理配额一样。Quotas for resources in Azure resource groups are per-region accessible by your subscription, not per-subscription as the service management quotas are. 让我们以 vCPU 配额为例。Let's use vCPU quotas as an example. 若要请求增加配额对 Vcpu 的支持,您必须决定你想要在哪些区域中使用多少 Vcpu。To request a quota increase with support for vCPUs, you must decide how many vCPUs you want to use in which regions. 您然后进行 Azure 资源组 vCPU 配额的特定请求的数量和所需的区域。You then make a specific request for Azure resource group vCPU quotas for the amounts and regions that you want. 如果需要使用在西欧的 30 个 Vcpu 那里运行应用程序,则专门请求在西欧的 30 个 Vcpu。If you need to use 30 vCPUs in West Europe to run your application there, you specifically request 30 vCPUs in West Europe. 只有西欧具有 30 个 vCPU 配额,不是任何其他区域-增加 vCPU 配额。Your vCPU quota isn't increased in any other region--only West Europe has the 30-vCPU quota.

因此,请考虑针对任意区域中的工作负荷来确定所需的 Azure 资源组配额,As a result, decide what your Azure resource group quotas must be for your workload in any one region. 然后在需将内容部署到其中的每个区域中请求相应的量。Then request that amount in each region into which you want to deploy. 若要了解如何确定特定区域的当前配额,请参阅排查部署问题For help in how to determine your current quotas for specific regions, see Troubleshoot deployment issues.

服务特定的限制Service-specific limits

订阅限制Subscription limits

订阅数限制-Azure 服务管理 (经典部署模型)Subscription limits - Azure Service Management (classic deployment model)

资源Resource 默认限制Default limit 最大限制Maximum limit
每个 Vcpu订阅1vCPUs per subscription1 2020 10,00010,000
共同管理员每个订阅Coadministrators per subscription 200200 200200
每个订阅的存储帐户数2Storage accounts per subscription2 100100 100100
每个订阅的云服务数Cloud services per subscription 2020 200200
每个订阅的本地网络数Local networks per subscription 1010 500500
每个订阅的 DNS 服务器DNS servers per subscription 99 100100
每个订阅的保留的 IPReserved IPs per subscription 2020 100100
每个订阅的地缘组数Affinity groups per subscription 256256 256256
订阅名称长度 (字符)Subscription name length (characters) 6464 6464

1额外小型实例计为一个 vCPU vCPU 限制,即使使用部分 CPU 核心。1Extra small instances count as one vCPU toward the vCPU limit despite using a partial CPU core.

2此存储帐户限制包括标准和高级存储帐户。2The storage account limit includes both Standard and Premium storage accounts.

订阅限制 - Azure 资源管理器Subscription limits - Azure Resource Manager

使用 Azure 资源管理器和 Azure 资源组时,以下限制适用。The following limits apply when you use Azure Resource Manager and Azure resource groups. 未列出尚未更改与 Azure 资源管理器的限制。Limits that haven't changed with Azure Resource Manager aren't listed. 请参阅上的表,了解这些限制。See the previous table for those limits.

有关资源管理器 API 读写限制的信息,请参阅限制资源管理器请求For information about Resource Manager API read and write limits, see Throttling Resource Manager requests.

资源Resource 默认限制Default limit 最大限制Maximum limit
每个订阅的 VM 数VMs per subscription 每个区域 25,000 个125,0001 per region. 每个区域 25,000 个。25,000 per region.
每个订阅的 VM 核心总数VM total cores per subscription 每个区域 20 个1201 per region. 联系支持人员。Contact support.
VM 系列(例如 Dv2 和 F)、每个订阅的核心数VM per series, such as Dv2 and F, cores per subscription 每个区域 20 个1201 per region. 联系支持人员。Contact support.
共同管理员每个订阅Coadministrators per subscription 不受限制。Unlimited. 不受限制。Unlimited.
每个订阅在每个区域中的存储帐户数Storage accounts per region per subscription 250250 250250
每个订阅的资源组数Resource groups per subscription 980980 980980
每个订阅的可用性集数Availability sets per subscription 每个区域 2,000 个。2,000 per region. 每个区域 2,000 个。2,000 per region.
Azure 资源管理器 API 请求大小Azure Resource Manager API request size 4,194,304 字节。4,194,304 bytes. 4,194,304 字节。4,194,304 bytes.
每个订阅的标记数2Tags per subscription2 不受限制。Unlimited. 不受限制。Unlimited.
每个订阅的唯一标记计算2Unique tag calculations per subscription2 10,00010,000 10,00010,000
每个订阅的云服务数Cloud services per subscription 不适用3N/A3 不适用3N/A3
每个订阅的地缘组数Affinity groups per subscription 不适用3N/A3 不适用3N/A3
订阅级别部署每个位置Subscription-level deployments per location 80048004 800800

1默认限制改变按产品类别类型,例如免费试用版和即用即付,和的系列,例如 Dv2、 F 和 g。1Default limits vary by offer category type, such as Free Trial and Pay-As-You-Go, and by series, such as Dv2, F, and G.

2每个订阅可以应用无限数量的标记。2You can apply an unlimited number of tags per subscription. 每个资源或资源组的标记数仅限 15。The number of tags per resource or resource group is limited to 15. 当标记数少于或等于 10,000 时,资源管理器仅返回订阅中唯一标记名和值的列表Resource Manager returns a list of unique tag name and values in the subscription only when the number of tags is 10,000 or less. 即使数目超过 10,000,也仍可按标记查找资源。You still can find a resource by tag when the number exceeds 10,000.

3使用 Azure 资源组和资源管理器时不再需要这些功能。3These features are no longer required with Azure resource groups and Resource Manager.

4达到 800 部署的限制,如果不再需要历史记录中删除部署。4If you reach the limit of 800 deployments, delete deployments from the history that are no longer needed. 若要删除订阅级别部署,请使用删除 AzDeploymentaz 部署删除To delete subscription level deployments, use Remove-AzDeployment or az deployment delete.

备注

虚拟机核心数存在区域总数限制。Virtual machine cores have a regional total limit. 区域大小系列(例如 Dv2 和 F)也存在限制。这些限制是单独实施的。They also have a limit for regional per-size series, such as Dv2 and F. These limits are separately enforced. 例如,某个订阅的美国东部 VM 核心总数限制为 30,A 系列核心数限制为 30,D 系列核心数限制为 30。For example, consider a subscription with a US East total VM core limit of 30, an A series core limit of 30, and a D series core limit of 30. 此订阅可以部署 30 个 A1 VM、30 个 D1 VM,或两者的组合,但总共不能超过 30 个核心。This subscription can deploy 30 A1 VMs, or 30 D1 VMs, or a combination of the two not to exceed a total of 30 cores. 例如,10 个 A1 VM 和 20 个 D1 VM 就是一种组合。An example of a combination is 10 A1 VMs and 20 D1 VMs.

资源组限制Resource group limits

资源Resource 默认限制Default limit 最大限制Maximum limit
每个资源组的资源数(按资源类型)Resources per resource group, per resource type 800800 根据资源类型而异Varies per resource type
部署历史记录中每个资源组的部署数Deployments per resource group in the deployment history 80018001 800800
每个部署的资源数Resources per deployment 800800 800800
管理锁数(按唯一的作用域)Management locks per unique scope 2020 2020
标记数(按资源或资源组)Number of tags per resource or resource group 1515 1515
标记键长度Tag key length 512512 512512
标记值长度Tag value length 256256 256256

1达到 800 部署每个资源组的限制,如果不再需要历史记录中删除部署。1If you reach the limit of 800 deployments per resource group, delete deployments from the history that are no longer needed. 从部署历史记录中删除条目不会影响已部署的资源。Deleting an entry from the deployment history doesn't affect the deployed resources. 可以使用 Azure CLI 的 az group deployment delete 或 PowerShell 中的 Remove-AzResourceGroupDeployment 删除历史记录中的条目。You can delete entries from the history with az group deployment delete for Azure CLI, or Remove-AzResourceGroupDeployment in PowerShell. 有关 PowerShell 脚本,可自动删除部署中的持续集成和持续交付 (CI/CD) 方案中,请参阅删除 deployments.ps1For a PowerShell script that automates deleting deployments in a continuous integration and continuous delivery (CI/CD) scenario, see remove-deployments.ps1.

模板限制Template limits

ValueValue 默认限制Default limit 最大限制Maximum limit
parametersParameters 256256 256256
变量Variables 256256 256256
资源(包括副本计数)Resources (including copy count) 800800 800800
OutputsOutputs 6464 6464
模板表达式Template expression 24,576 个字符24,576 chars 24,576 个字符24,576 chars
已导出模板中的资源Resources in exported templates 200200 200200
模板大小Template size 1 MB1 MB 1 MB1 MB
参数文件大小Parameter file size 64 KB64 KB 64 KB64 KB

通过使用嵌套模板,可超出某些模板限制。You can exceed some template limits by using a nested template. 有关详细信息,请参阅部署 Azure 资源时使用链接的模板For more information, see Use linked templates when you deploy Azure resources. 若要减少参数、变量或输出的数量,可以将几个值合并为一个对象。To reduce the number of parameters, variables, or outputs, you can combine several values into an object. 有关详细信息,请参阅对象即参数For more information, see Objects as parameters.

虚拟机限制Virtual Machines limits

虚拟机限制Virtual Machines limits

资源Resource 默认限制Default limit 最大限制Maximum limit
每个云服务的虚拟机数1Virtual machines per cloud service1 5050 5050
每个云服务的输入终结点数2Input endpoints per cloud service2 150150 150150

1使用经典部署模型而不是 Azure 资源管理器中创建的虚拟机都会自动存储在云服务。1Virtual machines created by using the classic deployment model instead of Azure Resource Manager are automatically stored in a cloud service. 可以向该云服务添加更多虚拟机以获得负载均衡和可用性。You can add more virtual machines to that cloud service for load balancing and availability.

2输入终结点允许从某个虚拟机的云服务外部与该虚拟机通信。2Input endpoints allow communications to a virtual machine from outside the virtual machine's cloud service. 位于同一云服务或虚拟网络中的虚拟机可以自动相互通信。Virtual machines in the same cloud service or virtual network can automatically communicate with each other. 有关详细信息,请参阅如何对虚拟机设置终结点For more information, see How to set up endpoints to a virtual machine.

虚拟机限制 - Azure 资源管理器Virtual Machines limits - Azure Resource Manager

使用 Azure 资源管理器和 Azure 资源组时,以下限制适用。The following limits apply when you use Azure Resource Manager and Azure resource groups. 未列出尚未更改与 Azure 资源管理器的限制。Limits that haven't changed with Azure Resource Manager aren't listed. 请参阅上的表,了解这些限制。See the previous table for those limits.

资源Resource 默认限制Default limit
每个可用性集的虚拟机数Virtual machines per availability set 200200
每个订阅的证书数Certificates per subscription 不受限制1Unlimited1

1使用 Azure 资源管理器时,证书将存储在 Azure 密钥保管库中。1With Azure Resource Manager, certificates are stored in the Azure Key Vault. 证书的数目不受限制的订阅。The number of certificates is unlimited for a subscription. 没有证书,每个部署,组成单个 VM 或可用性集的 1 MB 的限制。There's a 1-MB limit of certificates per deployment, which consists of either a single VM or an availability set.

有限制,对于每个订阅,使用共享映像库部署资源:There are limits, per subscription, for deploying resources using Shared Image Galleries:

  • 每个订阅,每个区域 100 共享的图像库100 shared image galleries, per subscription, per region
  • 1,000 图像定义,每个订阅,每个区域1,000 image definitions, per subscription, per region
  • 每个订阅,每个区域 10,000 映像版本10,000 image versions, per subscription, per region

虚拟机规模集限制Virtual machine scale sets limits

资源Resource 默认限制Default limit 最大限制Maximum limit
规模集中的 VM 的最大数目Maximum number of VMs in a scale set 1,0001,000 1,0001,000
最大 VM 数,具体取决于规模集中的自定义 VM 映像Maximum number of VMs based on a custom VM image in a scale set 600600 600600
区域中规模集的最大数目Maximum number of scale sets in a region 2,0002,000 2,0002,000

容器实例限制Container Instances limits

资源Resource 默认限制Default limit
每个订阅的容器组数Container groups per subscription 10011001
每个容器组的容器数Number of containers per container group 6060
每个容器组的卷数Number of volumes per container group 2020
每个 IP 的端口数Ports per IP 55
容器实例日志大小 - 正在运行的实例Container instance log size - running instance 4 MB4 MB
容器实例日志大小 - 已停止的实例Container instance log size - stopped instance 16 KB 或 1,000 行16 KB or 1,000 lines
每小时创建容器次数Container creates per hour 30013001
每 5 分钟创建容器次数Container creates per 5 minutes 10011001
每小时删除容器次数Container deletes per hour 30013001
每 5 分钟删除容器次数Container deletes per 5 minutes 10011001

1若要请求增加限制,创建Azure 支持请求1To request a limit increase, create an Azure Support request.

容器注册表限制Container Registry limits

下表详细介绍了“基本”、“标准”和“高级”服务层级的功能和限制。The following table details the features and limits of the Basic, Standard, and Premium service tiers.

资源Resource 基本Basic 标准Standard 高级Premium
存储1Storage1 10 GiB10 GiB 100 GiB100 GiB 500 GiB500 GiB
图像最大层大小Maximum image layer size 200 GiB200 GiB 200 GiB200 GiB 200 GiB200 GiB
每分钟读取操作数2、3ReadOps per minute2, 3 1,0001,000 3,0003,000 10,00010,000
每分钟写入操作数2、4WriteOps per minute2, 4 100100 500500 2,0002,000
下载带宽 (MBps)2Download bandwidth MBps2 3030 6060 100100
上传带宽 (MBps)2Upload bandwidth MBps2 1010 2020 5050
WebhookWebhooks 22 1010 100100
异地复制Geo-replication 不适用N/A 不适用N/A 受支持Supported
内容信任Content trust 不适用N/A 不适用N/A 受支持Supported

1指定的存储限制是量包含每个层的存储。1The specified storage limits are the amount of included storage for each tier. 对于超出这些限制的图像存储,将每日针对每 GiB 进行额外收费。You're charged an additional daily rate per GiB for image storage above these limits. 汇率信息,请参阅Azure 容器注册表定价For rate information, see Azure Container Registry pricing.

2读取操作数写入操作数,并且带宽是最小估计值。2ReadOps, WriteOps, and Bandwidth are minimum estimates. Azure 容器注册表致力于提高性能,使用情况。Azure Container Registry strives to improve performance as usage requires.

3A docker 拉取会转换为基于映像和清单检索中的层数的多个读取操作。3A docker pull translates to multiple read operations based on the number of layers in the image, plus the manifest retrieval.

4A docker 推送会转换为多个写入操作,根据必须推送的层数。4A docker push translates to multiple write operations, based on the number of layers that must be pushed. docker push 包含 ReadOps,用于检索现有映像的清单。A docker push includes ReadOps to retrieve a manifest for an existing image.

Azure Kubernetes 服务限制Azure Kubernetes Service limits

资源Resource 默认限制Default limit
每个订阅的最大群集Maximum clusters per subscription 100100
每个群集最大节点数Maximum nodes per cluster 100100
每个节点的最大 pod:带 Kubenet 的基本网络Maximum pods per node: Basic networking with Kubenet 110110
每个节点的最大 pod:高级网络与 Azure 容器网络接口Maximum pods per node: Advanced networking with Azure Container Networking Interface Azure CLI 部署:301Azure CLI deployment: 301
Azure 资源管理器模板:301Azure Resource Manager template: 301
门户部署:30Portal deployment: 30

1部署使用 Azure CLI 或 Resource Manager 模板的 Azure Kubernetes 服务 (AKS) 群集时,此值是可最多 250 个 pod,每个节点配置。1When you deploy an Azure Kubernetes Service (AKS) cluster with the Azure CLI or a Resource Manager template, this value is configurable up to 250 pods per node. 你已部署 AKS 群集后,或使用 Azure 门户部署群集,不能配置每个节点的最大 pod。You can't configure maximum pods per node after you've already deployed an AKS cluster, or if you deploy a cluster by using the Azure portal.

Azure 机器学习服务限制Azure Machine Learning Service limits

可在 Azure 机器学习计算配额的最新值Azure 机器学习配额页The latest values for Azure Machine Learning Compute quotas can be found in the Azure Machine Learning quota page

管理和请求 Azure 资源的配额Manage and request quotas for Azure resources

与其他 Azure 服务一样,与 Azure 机器学习服务关联的某些资源存在限制。As with other Azure services, there are limits on certain resources associated with the Azure Machine Learning service. 这些限制包括可以创建的工作区的数量上限以及用于训练或推断模型的实际基础计算的限制等。These limits range from a cap on the number of workspaces you can create to limits on the actual underlying compute that gets used for training or inferencing your models. 本文提供关于为你的订阅中各种 Azure 资源预配置的限制的更多详细信息,同时还包括为每种资源类型请求配额增加的可用链接。This article gives more details on the pre-configured limits on various Azure resources for your subscription and also contains handy links to request quota enhancements for each type of resource. 这些限制用于防止由于欺诈导致的预算超支,并且符合 Azure 容量限制。These limits are put in place to prevent budget over-runs due to fraud, and to honor Azure capacity constraints.

在设计和纵向扩展生产工作负载的 Azure 机器学习服务资源时,请记住这些配额。Keep these quotas in mind as you design and scale up your Azure Machine Learning service resources for production workloads. 例如,如果你的群集不会达到目标数指定的节点,然后你可能已达到 Azure 机器学习计算核心数限制为你的订阅。For example, if your cluster doesn't reach the target number of nodes you specified, then you might have reached an Azure Machine Learning Compute cores limit for your subscription. 如果想将限制或配额提高到默认值限制以上,可以免费打开联机客户支持请求。If you want to raise the limit or quota above the Default Limit, open an online customer support request at no charge. 由于 Azure 容量限制,无法将限制提高到超过下表中显示的最大限制值。The limits can't be raised above the Maximum Limit value shown in the following tables due to Azure Capacity constraints. 如果没有“最大限制”列,则资源没有可调整的限制。If there is no Maximum Limit column, then the resource doesn't have adjustable limits.

特殊注意事项Special considerations

  • 配额是一种信用限制,不附带容量保证。A quota is a credit limit, not a capacity guarantee. 如果有大规模容量需求,请与 Azure 支持部门联系。If you have large-scale capacity needs, contact Azure support.

  • 配额在订阅中的所有服务之间共享,包括 Azure 机器学习服务。Your quota is shared across all the services in your subscriptions including Azure Machine Learning service. 唯一的例外是 Azure 机器学习计算,它的配额独立于核心计算配额。The only exception is Azure Machine Learning compute which has a separate quota from the core compute quota. 在评估容量需求时,请务必计算所有服务的配额使用情况。Be sure to calculate the quota usage across all services when evaluating your capacity needs.

  • 默认限制根据产品/服务类别类型(例如免费试用、即用即付)和系列(例如 Dv2、F、G 等)而有所不同。Default limits vary by offer Category Type, such as Free Trial, Pay-As-You-Go, and series, such as Dv2, F, G, and so on.

默认资源配额Default resource quotas

下面是 Azure 订阅中各种资源类型的配额限制的细分条目。Here is a breakdown of the quota limits by various resource types within your Azure subscription.

重要

限制随时会变化。Limits are subject to change. 始终可以在所有 Azure 的服务级别配额文档中找到最新的限制。The latest can always be found at the service-level quota document for all of Azure.

虚拟机Virtual machines

可以在 Azure 订阅上跨服务或以独立方式预配虚拟机的数量有限。There is a limit on the number of virtual machines you can provision on an Azure subscription across your services or in a standalone manner. 基于总核心数和每个系列的区域级别也同样有此限制。This limit is at the region level both on the total cores and also on a per family basis.

必须强调的是,虚拟机核心数既有区域总数限制,也有区域按大小系列(Dv2、F 等)限制,这两种限制单独实施。It is important to emphasize that virtual machine cores have a regional total limit and a regional per size series (Dv2, F, etc.) limit that are separately enforced. 例如,某个订阅的美国东部 VM 核心总数限制为 30,A 系列核心数限制为 30,D 系列核心数限制为 30。For example, consider a subscription with a US East total VM core limit of 30, an A series core limit of 30, and a D series core limit of 30. 该订阅可以部署 30 个 A1 VM,或者 30 个 D1 VM,或者同时部署这二者,但其总数不能超过 30 个核心(例如,10 个 A1 VM 和 20 个 D1 VM)。This subscription would be allowed to deploy 30 A1 VMs, or 30 D1 VMs, or a combination of the two not to exceed a total of 30 cores (for example, 10 A1 VMs and 20 D1 VMs).

资源Resource 默认限制Default limit 最大限制Maximum limit
每个订阅的 VM 数VMs per subscription 每个区域 25,000 个125,0001 per region. 每个区域 25,000 个。25,000 per region.
每个订阅的 VM 核心总数VM total cores per subscription 每个区域 20 个1201 per region. 联系支持人员。Contact support.
VM 系列(例如 Dv2 和 F)、每个订阅的核心数VM per series, such as Dv2 and F, cores per subscription 每个区域 20 个1201 per region. 联系支持人员。Contact support.
共同管理员每个订阅Coadministrators per subscription 不受限制。Unlimited. 不受限制。Unlimited.
每个订阅在每个区域中的存储帐户数Storage accounts per region per subscription 250250 250250
每个订阅的资源组数Resource groups per subscription 980980 980980
每个订阅的可用性集数Availability sets per subscription 每个区域 2,000 个。2,000 per region. 每个区域 2,000 个。2,000 per region.
Azure 资源管理器 API 请求大小Azure Resource Manager API request size 4,194,304 字节。4,194,304 bytes. 4,194,304 字节。4,194,304 bytes.
每个订阅的标记数2Tags per subscription2 不受限制。Unlimited. 不受限制。Unlimited.
每个订阅的唯一标记计算2Unique tag calculations per subscription2 10,00010,000 10,00010,000
每个订阅的云服务数Cloud services per subscription 不适用3N/A3 不适用3N/A3
每个订阅的地缘组数Affinity groups per subscription 不适用3N/A3 不适用3N/A3
订阅级别部署每个位置Subscription-level deployments per location 80048004 800800

1默认限制改变按产品类别类型,例如免费试用版和即用即付,和的系列,例如 Dv2、 F 和 g。1Default limits vary by offer category type, such as Free Trial and Pay-As-You-Go, and by series, such as Dv2, F, and G.

2每个订阅可以应用无限数量的标记。2You can apply an unlimited number of tags per subscription. 每个资源或资源组的标记数仅限 15。The number of tags per resource or resource group is limited to 15. 当标记数少于或等于 10,000 时,资源管理器仅返回订阅中唯一标记名和值的列表Resource Manager returns a list of unique tag name and values in the subscription only when the number of tags is 10,000 or less. 即使数目超过 10,000,也仍可按标记查找资源。You still can find a resource by tag when the number exceeds 10,000.

3使用 Azure 资源组和资源管理器时不再需要这些功能。3These features are no longer required with Azure resource groups and Resource Manager.

4达到 800 部署的限制,如果不再需要历史记录中删除部署。4If you reach the limit of 800 deployments, delete deployments from the history that are no longer needed. 若要删除订阅级别部署,请使用删除 AzDeploymentaz 部署删除To delete subscription level deployments, use Remove-AzDeployment or az deployment delete.

备注

虚拟机核心数存在区域总数限制。Virtual machine cores have a regional total limit. 区域大小系列(例如 Dv2 和 F)也存在限制。这些限制是单独实施的。They also have a limit for regional per-size series, such as Dv2 and F. These limits are separately enforced. 例如,某个订阅的美国东部 VM 核心总数限制为 30,A 系列核心数限制为 30,D 系列核心数限制为 30。For example, consider a subscription with a US East total VM core limit of 30, an A series core limit of 30, and a D series core limit of 30. 此订阅可以部署 30 个 A1 VM、30 个 D1 VM,或两者的组合,但总共不能超过 30 个核心。This subscription can deploy 30 A1 VMs, or 30 D1 VMs, or a combination of the two not to exceed a total of 30 cores. 例如,10 个 A1 VM 和 20 个 D1 VM 就是一种组合。An example of a combination is 10 A1 VMs and 20 D1 VMs.

有关配额限制更详细的最新列表,请在此处查看适用于 Azure 的配额文章。For a more detailed and up-to-date list of quota limits, check the Azure-wide quota article here.

Azure 机器学习计算Azure Machine Learning Compute

在 Azure 机器学习计算中,订阅中每个区域所允许的核心数和唯一计算资源数都有默认配额限制。For Azure Machine Learning Compute, there is a default quota limit on both the number of cores and number of unique compute resources allowed per region in a subscription. 该配额独立于上述的 VM 核心配额,并且核心限制目前没有在这两种资源类型之间共享。This quota is separate from the VM core quota above and the core limits are not shared currently between the two resource types.

可用资源:Available resources:

  • 每个区域的专用核心数的默认限制为 24-300 取决于你的订阅产品/服务类型。Dedicated cores per region have a default limit of 24 - 300 depending on your subscription offer type. 可增加每个订阅的专用核心数。The number of dedicated cores per subscription can be increased. 请联系 Azure 支持以讨论增加选项。Contact Azure support to discuss increase options.

  • 每个区域的低优先级核心数的默认限制为 24-300,具体取决于你的订阅产品/服务类型。Low-priority cores per region have a default limit of 24 - 300 depending on your subscription offer type. 可增加每个订阅的低优先级核心数。The number of low-priority cores per subscription can be increased. 请联系 Azure 支持以讨论增加选项。Contact Azure support to discuss increase options.

  • 每个区域的群集数默认限制为 100,最大限制为 200。Clusters per region have a default limit of 100 and a maximum limit of 200. 如果请求增加的配额超出此限制,请与 Azure 支持部门联系。Contact Azure support if you want to request an increase beyond this limit.

  • 下面是“其他严格限制”,不能超出这些限制。There are other strict limits which cannot be exceeded once hit.

资源Resource 最大限制Maximum limit
每个资源组的最大工作区数Maximum workspaces per resource group 800800
单个 Azure 机器学习计算 (AmlCompute) 资源中的最大节数点Maximum nodes in a single Azure Machine Learning Compute (AmlCompute) resource 100 个节点100 nodes
每个节点的最大 GPU MPI 进程数Maximum GPU MPI processes per node 1-41-4
每个节点的最大 GPU 辅助角色数Maximum GPU workers per node 1-41-4
最长作业生存期Maximum job lifetime 90 天190 days1
低优先级节点上的最大作业生存期Maximum job lifetime on a Low Priority Node 1 天21 day2
每个节点的最大参数服务器数Maximum parameter servers per node 1

1 最长生存期是指运行从开始到结束的时间。1 The maximum lifetime refers to the time that a run start and when it finishes. 已完成的运行会无限期保存;最长生存期内未完成的运行的数据不可访问。Completed runs persist indefinitely; data for runs not completed within the maximum lifetime is not accessible. 2低优先级节点上的作业可以抢占资源容量约束任何时间。2 Jobs on a Low Priority node could be pre-empted any time there is a capacity constraint. 建议您在工作中实施检查点。It is recommended to implement checkpointing in your job.

容器实例Container instances

可以在给定时间段内(以小时为范围)或在你的整个订阅中启动的容器实例数量也有限制。There is also a limit on the number of container instances that you can spin up in a given time period (scoped hourly) or across your entire subscription.

资源Resource 默认限制Default limit
每个订阅的容器组数Container groups per subscription 10011001
每个容器组的容器数Number of containers per container group 6060
每个容器组的卷数Number of volumes per container group 2020
每个 IP 的端口数Ports per IP 55
容器实例日志大小 - 正在运行的实例Container instance log size - running instance 4 MB4 MB
容器实例日志大小 - 已停止的实例Container instance log size - stopped instance 16 KB 或 1,000 行16 KB or 1,000 lines
每小时创建容器次数Container creates per hour 30013001
每 5 分钟创建容器次数Container creates per 5 minutes 10011001
每小时删除容器次数Container deletes per hour 30013001
每 5 分钟删除容器次数Container deletes per 5 minutes 10011001

1若要请求增加限制,创建Azure 支持请求1To request a limit increase, create an Azure Support request.

有关配额限制更详细的最新列表,请在此处查看适用于 Azure 的配额文章。For a more detailed and up-to-date list of quota limits, check the Azure-wide quota article here.

存储Storage

给定订阅中每个区域的存储帐户数量也有限制。There is a limit on the number of storage accounts per region as well in a given subscription. 默认限制数量为 200,包括标准和高级存储帐户。The default limit is 200 and includes both Standard and Premium Storage accounts. 如果在某特定区域中需要的存储帐户多于 200 个,请通过 Azure 支持提出请求。If you require more than 200 storage accounts in a given region, make a request through Azure Support. Azure 存储团队将评审业务案例,对于特定区域最多可以批准 250 个存储帐户。The Azure Storage team will review your business case and may approve up to 250 storage accounts for a given region.

查找你的配额Find your quotas

通过 Azure 门户可以轻松查看各种资源的配额,例如虚拟机、存储和网络。Viewing your quota for various resources, such as Virtual Machines, Storage, Network, is easy through the Azure portal.

  1. 在左窗格上,选择“所有服务”,然后在“一般”类别下选择“订阅”。On the left pane, select All services and then select Subscriptions under the General category.

  2. 从订阅列表中选择要查找其配额的订阅。From the list of subscriptions, select the subscription whose quota you are looking for.

    有一个警告提示,专门用于查看 Azure 机器学习计算配额。There is a caveat, specifically for viewing the Azure Machine Learning Compute quota. 如上所述,此配置独立于订阅上的计算配额。As mentioned above, that quota is separate from the compute quota on your subscription.

  3. 在左窗格中,选择机器学习服务,然后从显示的列表中选择任何工作区On the left pane, select Machine Learning service and then select any workspace from the list shown

  4. 在下一个边栏选项卡中,在“支持 + 故障排除部分”下,选择“使用情况 + 配额”以查看当前配额限制和使用情况。On the next blade, under the Support + troubleshooting section select Usage + quotas to view your current quota limits and usage.

  5. 选择订阅以查看配额限制。Select a subscription to view the quota limits. 请记住筛选到所需的区域。Remember to filter to the region you are interested in.

请求增加配额Request quota increases

如果想将限制或配额提高到默认值限制以上,可以免费打开联机客户支持请求If you want to raise the limit or quota above the default limit, open an online customer support request at no charge.

无法将限制提高到表中所示的最大限制值。The limits can't be raised above the maximum limit value shown in the tables. 如果没有最大限制,则资源没有可调整的限制。If there is no maximum limit, then the resource doesn't have adjustable limits. 这篇文章详细介绍了配额增加过程。This article covers the quota increase process in more detail.

请求配额增加时,需要选择要请求提高配额的服务,这可能是机器学习服务配额、容器实例或存储配额的服务。When requesting a quota increase, you need to select the service you are requesting to raise the quota against, which could be services such as Machine Learning service quota, Container instances or Storage quota. 此外,对于 Azure 机器学习计算,只需单击“请求配额”按钮,然后按照上述步骤查看配额。In addition for Azure Machine Learning Compute, you can simply click on the Request Quota button while viewing the quota following the steps above.

备注

免费试用版订阅不符合增加限制或配额的条件。Free Trial subscriptions are not eligible for limit or quota increases. 如果有免费试用版订阅,可将其升级到即用即付订阅。If you have a Free Trial subscription, you can upgrade to a Pay-As-You-Go subscription. 有关详细信息,请参阅将 Azure 免费试用版订阅升级到即用即付订阅免费试用版订阅常见问题解答For more information, see Upgrade Azure Free Trial to Pay-As-You-Go and Free Trial subscription FAQ.

网络限制Networking limits

以下限制仅适用于网络通过管理资源经典每个订阅的部署模型。The following limits apply only for networking resources managed through the classic deployment model per subscription. 了解如何针对订阅限制查看当前资源使用情况Learn how to view your current resource usage against your subscription limits.

资源Resource 默认限制Default limit 最大限制Maximum limit
虚拟网络Virtual networks 5050 100100
本地网络站点Local network sites 2020 联系支持人员。Contact support.
每个虚拟网络的 DNS 服务器数DNS servers per virtual network 2020 2020
每个虚拟网络的专用 IP 地址数Private IP addresses per virtual network 4,0964,096 4,0964,096
虚拟机或角色实例的单 NIC 并发 TCP 或 UDP 流数Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 如果 NIC 至少有两个,则为 500,000(至多 1,000,000)。500,000, up to 1,000,000 for two or more NICs. 如果 NIC 至少有两个,则为 500,000(至多 1,000,000)。500,000, up to 1,000,000 for two or more NICs.
网络安全组 (NSG)Network Security Groups (NSGs) 200200 200200
每个 NSG 的 NSG 规则数NSG rules per NSG 1,0001,000 1,0001,000
用户定义路由表数User-defined route tables 200200 200200
每个路由表的用户定义的路由数User-defined routes per route table 400400 400400
公共 IP 地址 (动态)Public IP addresses (dynamic) 55 联系支持人员Contact support
保留的公共 IP 地址Reserved public IP addresses 2020 联系支持人员Contact support
每个部署的公共 VIPPublic VIP per deployment 55 联系支持人员Contact support
每个部署的专用 VIP(内部负载均衡)Private VIP (internal load balancing) per deployment 1 1
终结点访问控制列表 (ACL)Endpoint access control lists (ACLs) 5050 5050

网络限制-Azure 资源管理器Networking limits - Azure Resource Manager

以下限制仅适用于网络通过管理资源Azure 资源管理器每个区域每个订阅。The following limits apply only for networking resources managed through Azure Resource Manager per region per subscription. 了解如何针对订阅限制查看当前资源使用情况Learn how to view your current resource usage against your subscription limits.

备注

我们最近将所有默认限制提高到了最大限制。We recently increased all default limits to their maximum limits. 如果没有最大限制列,则资源没有可调整的限制。If there's no maximum limit column, the resource doesn't have adjustable limits. 如果过去已通过客户支持提高了这些上限,因此在以下表中看不到更新的限制,可免费提交联机客户支持请求If you had these limits increased by support in the past and don't see updated limits in the following tables, open an online customer support request at no charge

资源Resource 默认值/最大限制Default/maximum limit
虚拟网络Virtual networks 1,0001,000
每个虚拟网络的子网数Subnets per virtual network 3,0003,000
每个虚拟网络的虚拟网络对等互连数Virtual network peerings per virtual network 500500
每个虚拟网络的 DNS 服务器数DNS servers per virtual network 2020
每个虚拟网络的专用 IP 地址数Private IP addresses per virtual network 65,53665,536
每个网络接口的专用 IP 地址数Private IP addresses per network interface 256256
每个虚拟机的专用 IP 地址数Private IP addresses per virtual machine 256256
虚拟机或角色实例的单 NIC 并发 TCP 或 UDP 流数Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 500,000500,000
网络接口卡数Network interface cards 65,53665,536
网络安全组Network Security Groups 5,0005,000
每个 NSG 的 NSG 规则数NSG rules per NSG 1,0001,000
为安全组中的源或目标指定的 IP 地址和范围数IP addresses and ranges specified for source or destination in a security group 4,0004,000
应用程序安全组Application security groups 3,0003,000
每个 IP 配置和每个 NIC 的应用程序安全组数Application security groups per IP configuration, per NIC 2020
每个应用程序安全组的 IP 配置数IP configurations per application security group 4,0004,000
可在网络安全组的所有安全规则中指定的应用程序安全组数Application security groups that can be specified within all security rules of a network security group 100100
用户定义路由表数User-defined route tables 200200
每个路由表的用户定义的路由数User-defined routes per route table 400400
每个 Azure VPN 网关的点到站点根证书数Point-to-site root certificates per Azure VPN Gateway 2020
虚拟网络 TAPVirtual network TAPs 100100
每个虚拟网络 TAP 的网络接口 TAP 配置Network interface TAP configurations per virtual network TAP 100100

公共 IP 地址限制Public IP address limits

资源Resource 默认限制Default limit 最大限制Maximum limit
公共 IP 地址数 - 动态Public IP addresses - dynamic 基本版为 1,000。1,000 for Basic. 联系支持人员。Contact support.
公共 IP 地址数 - 静态Public IP addresses - static 基本版为 1,000。1,000 for Basic. 联系支持人员。Contact support.
公共 IP 地址数 - 静态Public IP addresses - static 标准版为 200。200 for Standard. 联系支持人员。Contact support.
公共 IP 前缀大小 (预览版)Public IP prefix size (preview) /28/28 联系支持人员。Contact support.

负载均衡器限制Load balancer limits

以下限制仅适用于每个订阅按区域通过 Azure 资源管理器管理的网络资源。The following limits apply only for networking resources managed through Azure Resource Manager per region per subscription. 了解如何针对订阅限制查看当前资源使用情况Learn how to view your current resource usage against your subscription limits.

资源Resource 默认值/最大限制Default/maximum limit
负载均衡器Load balancers 1,0001,000
每个资源的规则数,基本Rules per resource, Basic 250250
每个资源的规则数,标准Rules per resource, Standard 1,5001,500
每个 IP 配置的规则数Rules per IP configuration 299299
每个 NIC 的规则数Rules per NIC 500500
前端 IP 配置数基本Front-end IP configurations, Basic 200200
前端 IP 配置数标准Front-end IP configurations, Standard 600600
后端池基本Back-end pool, Basic 100,单个可用性集中100, single availability set
后端池标准Back-end pool, Standard 1000,单个虚拟网络1,000, single virtual network
每个负载均衡器,标准的后端资源1Back-end resources per load balancer, Standard1 150150
高可用性端口标准High-availability ports, Standard 每 1 个内部前端1 per internal front-end

1限制是最多 150 种资源,采用独立虚拟机资源、可用性集资源和虚拟机规模集资源的任意组合。1The limit is up to 150 resources, in any combination of standalone virtual machine resources, availability set resources, and virtual machine scale-set resources.

ExpressRoute 限制ExpressRoute limits

资源Resource 默认值/最大限制Default/maximum limit
每个订阅的 ExpressRoute 线路数ExpressRoute circuits per subscription 1010
每个区域每个订阅,使用 Azure 资源管理器中的 ExpressRoute 线路ExpressRoute circuits per region per subscription, with Azure Resource Manager 1010
Azure 专用对等互连具有 ExpressRoute Standard 的路由的最大数目Maximum number of routes for Azure private peering with ExpressRoute Standard 4,0004,000
Azure 专用对等互连的 ExpressRoute 高级版外接程序的路由的最大数目Maximum number of routes for Azure private peering with ExpressRoute Premium add-on 10,00010,000
Azure 专用对等互连的 ExpressRoute 连接的 VNet 地址空间中的路由的最大数目Maximum number of routes for Azure private peering from the VNet address space for an ExpressRoute connection 200200
具有 ExpressRoute Standard 的 Microsoft Azure 对等互连的路由的最大数目Maximum number of routes for Microsoft Azure peering with ExpressRoute Standard 200200
最大数量的 Microsoft Azure ExpressRoute 高级版外接程序与对等互连的路由Maximum number of routes for Microsoft Azure peering with ExpressRoute Premium add-on 200200
ExpressRoute 线路链接到同一虚拟网络对等互连在同一位置的最大数目Maximum number of ExpressRoute circuits linked to the same virtual network in the same peering location 44
链接到不同对等互连位置中相同虚拟网络的最大 ExpressRoute 线路数Maximum number of ExpressRoute circuits linked to the same virtual network in different peering locations 44
每个 ExpressRoute 线路允许的虚拟网络链接数Number of virtual network links allowed per ExpressRoute circuit 请参阅下表。See the following table.

每个 ExpressRoute 线路的虚拟网络的数量Number of virtual networks per ExpressRoute circuit

线路大小Circuit size 标准的虚拟网络链接数Number of virtual network links for Standard 高级版附加组件的虚拟网络链接数Number of virtual network links with Premium add-on
50 Mbps50 Mbps 1010 2020
100 Mbps100 Mbps 1010 2525
200 Mbps200 Mbps 1010 2525
500 Mbps500 Mbps 1010 4040
1 Gbps1 Gbps 1010 5050
2 Gbps2 Gbps 1010 6060
5 Gbps5 Gbps 1010 7575
10 Gbps10 Gbps 1010 100100
40 Gbps*40 Gbps* 1010 100100
100 Gbps*100 Gbps* 1010 100100

* 仅 ExpressRoute 直接*ExpressRoute Direct Only

应用程序网关限制Application Gateway limits

除非另有说明,否则下表适用于 v1、v2、标准和 WAF SKU。The following table applies to v1, v2, Standard, and WAF SKUs unless otherwise stated.

资源Resource 默认值/最大限制Default/maximum limit 注意Note
Azure 应用程序网关Azure Application Gateway 每个订阅 1,000 个1,000 per subscription
前端 IP 配置Front-end IP configurations 22 1 个公共,1 个专用1 public and 1 private
前端端口Front-end ports 10011001
后端地址池Back-end address pools 10011001
每个池的后端服务器数Back-end servers per pool 1,2001,200
HTTP 侦听器HTTP listeners 10011001
HTTP 负载均衡规则HTTP load-balancing rules 10011001
后端 HTTP 设置Back-end HTTP settings 10011001
每个网关的实例数Instances per gateway 3232
SSL 证书数SSL certificates 10011001 每个 HTTP 侦听器 1 个1 per HTTP listeners
身份验证证书Authentication certificates 100100
受信任的根证书Trusted root certificates 100100
请求超时最小值Request timeout minimum 1 秒1 second
请求超时最大值Request timeout maximum 24 小时24 hours
站点数Number of sites 10011001 每个 HTTP 侦听器 1 个1 per HTTP listeners
每个侦听器的 URL 映射数URL maps per listener 1
每个 URL 映射基于路径的最大规则数Maximum path-based rules per URL map 100100
重定向配置数Redirect configurations 10011001
并发的 WebSocket 连接数Concurrent WebSocket connections 中型网关 20kMedium gateways 20k
大型网关 50kLarge gateways 50k
最大 URL 长度Maximum URL length 8,0008,000
最大文件上传大小:标准Maximum file upload size, Standard 2 GB2 GB
最大文件上传大小 WAFMaximum file upload size WAF 中型 WAF 网关,100 MBMedium WAF gateways, 100 MB
大型 WAF 网关,500 MBLarge WAF gateways, 500 MB
WAF 正文大小限制,不带文件WAF body size limit, without files 128 KB128 KB

1 对于启用了 WAF 的 SKU,建议将资源数限制为 40 以实现最佳性能。1 In case of WAF-enabled SKUs, we recommend that you limit the number of resources to 40 for optimal performance.

网络观察程序限制Network Watcher limits

资源Resource 默认限制Default limit 最大限制Maximum limit 注意Note
Azure 网络观察程序Azure Network Watcher 每个区域 1 个1 per region 每个区域 1 个1 per region 创建网络观察程序以启用对服务的访问。Network Watcher is created to enable access to the service. 需要每个订阅每个区域只有一个网络观察程序实例。Only one instance of Network Watcher is required per subscription per region.
数据包捕获会话Packet capture sessions 每个区域 100 个100 per region 10,00010,000 捕获的会话数,不会保存。Number of sessions only, not saved captures.

流量管理器限制Traffic Manager limits

资源Resource 默认值/最大限制Default/maximum limit
每个订阅的配置文件数Profiles per subscription 200200
每个配置文件的终结点数Endpoints per profile 200200

Azure DNS 限制Azure DNS limits

资源Resource 默认限制Default limit
每个订阅的区域数Zones per subscription 100 1100 1
每个区域的记录集数Record sets per zone 5,000 15,000 1
每个记录集的记录数Records per record set 2020

1如果需要增加这些限制,请联系 Azure 支持部门。1If you need to increase these limits, contact Azure Support.

Azure 防火墙限制Azure Firewall limits

资源Resource 默认限制Default limit
数据吞吐量Data throughput 30 Gbps130 Gbps1
规则Rules 10000,所有规则类型组合。10,000, all rule types combined.
最小 AzureFirewallSubnet 大小Minimum AzureFirewallSubnet size /26/26
网络和应用程序规则的端口范围Port range in network and application rules 0-64,000。0-64,000. 目前正在努力放宽此限制。Work is in progress to relax this limitation.
路由表Route table 默认情况下,AzureFirewallSubnet 0.0.0.0/0 路由的 NextHopType 值设置为InternetBy default, AzureFirewallSubnet has a 0.0.0.0/0 route with the NextHopType value set to Internet.

Azure 防火墙必须具有直接 Internet 连接。Azure Firewall must have direct Internet connectivity. 如果你 AzureFirewallSubnet 了解到通过 BGP 将本地网络的默认路由,则必须使用 0.0.0.0/0 UDR 用于覆盖这NextHopType值设置为Internet维护直接Internet 连接。If your AzureFirewallSubnet learns a default route to your on-premises network via BGP, you must override this with a 0.0.0.0/0 UDR with the NextHopType value set as Internet to maintain direct Internet connectivity. 默认情况下,Azure 防火墙不支持强制隧道连接到本地网络。By default, Azure Firewall doesn't support forced tunneling to an on-premises network.

但是,如果你的配置要求强制隧道连接到本地网络,Microsoft 将支持其上具体情况。However, if your configuration requires forced tunneling to an on-premises network, Microsoft will support it on a case by case basis. 联系支持人员,以便我们可以查看您的案例。Contact Support so that we can review your case. 如果接受,我们将你的订阅的白名单,并确保维持所需的防火墙的 Internet 连接。If accepted, we'll whitelist your subscription and ensure the required firewall Internet connectivity is maintained.

1如果需要增加这些限制,请联系 Azure 支持部门。1If you need to increase these limits, contact Azure Support.

Azure Front Door 服务限制Azure Front Door Service limits

资源Resource 默认值/最大限制Default/maximum limit
每个订阅的 azure 第一道防线服务资源Azure Front Door Service resources per subscription 100100
前端主机,其中包括每个资源的自定义域Front-end hosts, which includes custom domains per resource 100100
每个资源的路由规则数Routing rules per resource 100100
每个资源的后端池Back-end pools per resource 5050
每个后端池的后端Back ends per back-end pool 100100
要匹配路由规则的路径模式数Path patterns to match for a routing rule 2525
每个策略的自定义 Web 应用程序防火墙规则数Custom web application firewall rules per policy 1010
每个资源的 Web 应用程序防火墙策略数Web application firewall policy per resource 100100

超时值Timeout values

客户端到 Front DoorClient to Front Door

  • Front Door 的空闲 TCP 连接超时为 61 秒。Front Door has an idle TCP connection timeout of 61 seconds.

到应用程序后端的第一道防线Front Door to application back-end

  • 如果分块的响应进行响应,或如果收到第一个区块后返回 200。If the response is a chunked response, a 200 is returned if or when the first chunk is received.
  • HTTP 请求转发到后端后,第一道防线等待 30 秒钟,从后端的第一个数据包。After the HTTP request is forwarded to the back end, Front Door waits for 30 seconds for the first packet from the back end. 然后它将 503 错误返回到客户端。Then it returns a 503 error to the client.
  • 从后端收到的第一个数据包后,等待第一道防线的空闲超时 30 秒。After the first packet is received from the back end, Front Door waits for 30 seconds in an idle timeout. 然后它将 503 错误返回到客户端。Then it returns a 503 error to the client.
  • 第一道防线到后端 TCP 会话超时为 30 分钟。Front Door to the back-end TCP session timeout is 30 minutes.

上传和下载数据限制Upload and download data limit

使用 chunked 传输编码 (CTE)With chunked transfer encoding (CTE) 不 HTTP 分块Without HTTP chunking
下载Download 对下载大小没有任何限制。There's no limit on the download size. 对下载大小没有任何限制。There's no limit on the download size.
上载Upload 没有任何限制,只要每个 CTE 上传为不超过 2 GB。There's no limit as long as each CTE upload is less than 2 GB. 大小不能大于 2 GB。The size can't be larger than 2 GB.

存储限制Storage limits

下表描述了使 Azure 常规用途 v1 和 v2,Blob 存储帐户的默认限制。The following table describes default limits for Azure general-purpose v1, v2, and Blob storage accounts. “传入”限制是指请求中发送到存储帐户的所有数据。The ingress limit refers to all data from requests that are sent to a storage account. “传出”限制是指响应中从存储帐户接收的所有数据。The egress limit refers to all data from responses that are received from a storage account.

资源Resource 默认限制Default limit
每个订阅每个区域的存储帐户数,包括标准帐户和高级帐户Number of storage accounts per region per subscription, including both standard and premium accounts 250250
最大存储帐户容量Maximum storage account capacity 2 PB 针对美国和欧洲,对于所有其他区域,其中包括英国 500 TB2 PB for US and Europe, 500 TB for all other regions, which includes the UK
每个存储帐户的 Blob 容器、Blob、文件共享、表、队列、实体或消息数上限Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account 无限制No limit
每个存储帐户的最大请求速率1Maximum request rate1 per storage account 每秒 20,000 个请求20,000 requests per second
最大入口1每个存储帐户 (美国区域)Maximum ingress1 per storage account (US regions) 如果已启用 RA-GRS/GRS 的 10 Gbps,20 Gbps; 对于 LRS/ZRS210 Gbps if RA-GRS/GRS is enabled, 20 Gbps for LRS/ZRS2
最大入口1每个存储帐户 (非美国区域)Maximum ingress1 per storage account (non-US regions) 如果已启用 RA-GRS/GRS,则为 5 Gbps,10 Gbps; 对于 LRS/ZRS25 Gbps if RA-GRS/GRS is enabled, 10 Gbps for LRS/ZRS2
对于常规用途 v2 和 Blob 存储帐户 (所有区域) 的最大出口Maximum egress for general-purpose v2 and Blob storage accounts (all regions) 50 Gbps50 Gbps
常规用途 v1 存储帐户 (美国区域) 的最大出口Maximum egress for general-purpose v1 storage accounts (US regions) 如果启用 RA-GRS/GRS,则为 20 Gbps、 30 Gbps; 对于 LRS/ZRS220 Gbps if RA-GRS/GRS is enabled, 30 Gbps for LRS/ZRS2
常规用途 v1 存储帐户 (非美国区域) 的最大出口Maximum egress for general-purpose v1 storage accounts (non-US regions) 如果已启用 RA-GRS/GRS 的 10 Gbps,15 Gbps; 对于 LRS/ZRS210 Gbps if RA-GRS/GRS is enabled, 15 Gbps for LRS/ZRS2

1 Azure 标准存储帐户根据请求支持更高的入口上限。1Azure Standard Storage accounts support higher limits for ingress by request. 若要请求提高帐户入口上限,请与 Azure 支持联系。To request an increase in account limits for ingress, contact Azure Support.

2 Azure 存储复制选项包括:2 Azure Storage replication options include:

  • RA-GRS:读取访问异地冗余存储。RA-GRS: Read-access geo-redundant storage. 如果已启用 RA-GRS,辅助位置的出口目标与主要位置的出口目标相同。If RA-GRS is enabled, egress targets for the secondary location are identical to those for the primary location.
  • GRS:异地冗余存储。GRS: Geo-redundant storage.
  • ZRS:区域冗余存储。ZRS: Zone-redundant storage.
  • LRS:本地冗余存储。LRS: Locally redundant storage.

备注

大多数情况下,建议使用常规用途 v2 存储帐户。We recommend that you use a general-purpose v2 storage account for most scenarios. 可以轻松将常规用途 v1 或 Azure Blob 存储帐户升级到常规用途 v2 帐户,无需停机且无需复制数据。You can easily upgrade a general-purpose v1 or an Azure Blob storage account to a general-purpose v2 account with no downtime and without the need to copy data.

有关 Azure 存储帐户的详细信息,请参阅存储帐户概述For more information on Azure Storage accounts, see Storage account overview.

如果应用程序的需求超过单个存储帐户的伸缩性目标,则可以构建使用多个存储帐户的应用程序。If the needs of your application exceed the scalability targets of a single storage account, you can build your application to use multiple storage accounts. 然后,可以将数据对象分布到这些存储帐户中。You can then partition your data objects across those storage accounts. 有关批量定价的信息,请参阅 Azure 存储定价For information on volume pricing, see Azure Storage pricing.

所有存储帐户都在扁平网络拓扑上运行,无论它们创建于何时,都支持本文所述的可伸缩性和性能目标。All storage accounts run on a flat network topology and support the scalability and performance targets outlined in this article, regardless of when they were created. 有关 Azure 存储的扁平网络体系结构和可伸缩性的详细信息,请参阅 Microsoft Azure 存储:具有非常一致性的高可用云存储服务For more information on the Azure Storage flat network architecture and on scalability, see Microsoft Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency.

有关存储帐户限制的详细信息,请参阅Azure 存储可伸缩性和性能目标For more information on storage account limits, see Azure Storage scalability and performance targets.

存储资源提供程序限制Storage resource provider limits

仅当与 Azure 存储配合使用 Azure 资源管理器执行管理操作时,以下限制适用。The following limits apply only when you perform management operations by using Azure Resource Manager with Azure Storage.

资源Resource 默认限制Default limit
存储帐户管理操作数(读取)Storage account management operations (read) 每 5 分钟 800 次800 per 5 minutes
存储帐户管理操作数(写入)Storage account management operations (write) 每小时 200 次200 per hour
存储帐户管理操作数(列出)Storage account management operations (list) 每 5 分钟 100 次100 per 5 minutes

Azure Blob 存储限制Azure Blob storage limits

资源Resource 确定目标Target
单个 Blob 容器的最大大小Maximum size of single blob container 与最大存储帐户容量相同Same as maximum storage account capacity
块 Blob 或附加 Blob 中的块数上限Maximum number of blocks in a block blob or append blob 50,000 块50,000 blocks
块 Blob 中块的最大大小Maximum size of a block in a block blob 100 MiB100 MiB
块 Blob 的最大大小Maximum size of a block blob 50,000 X 100 MiB(大约 4.75 TiB)50,000 X 100 MiB (approximately 4.75 TiB)
附加 Blob 中块的最大大小Maximum size of a block in an append blob 4 MiB4 MiB
附加 Blob 的最大大小Maximum size of an append blob 50,000 x 4 MiB(大约 195 GiB)50,000 x 4 MiB (approximately 195 GiB)
页 Blob 的最大大小Maximum size of a page blob 8 TiB8 TiB
每个 Blob 容器存储的访问策略的最大数目Maximum number of stored access policies per blob container 55
单个 Blob 的目标吞吐量Target throughput for single blob 最多存储帐户入口/出口限制1Up to storage account ingress/egress limits1

1单个对象吞吐量取决于多种因素,包括但不是限于: 并发性、 请求大小、 性能层、 上传,源和目标下载的速度。1 Single object throughput depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. 若要充分利用高吞吐量块 blob性能增强功能,使用的放置 Blob 或放置块的请求大小为 > 4 MiB (> 256 KiB 高级性能数据块 blob 存储或数据湖存储第 2 代)。To take advantage of high-throughput block blob performance enhancements, use a Put Blob or Put Block request size of > 4 MiB (> 256 KiB for premium-performance block blob storage or for Data Lake Storage Gen2).

Azure 文件限制Azure Files limits

有关 Azure 文件限制的详细信息,请参阅Azure 文件可伸缩性和性能目标For more information on Azure Files limits, see Azure Files scalability and performance targets.

资源Resource 标准文件共享Standard file shares 高级文件共享(预览版)Premium file shares (preview)
文件共享的最小大小Minimum size of a file share 没有最小值;现用现付No minimum; pay as you go 100 giB;预配100 GiB; provisioned
文件共享的最大大小Maximum size of a file share 5 TiB5 TiB 100 TiB100 TiB
文件共享中文件的最大大小Maximum size of a file in a file share 1 TiB1 TiB 1 TiB1 TiB
文件共享中的文件数上限Maximum number of files in a file share 无限制No limit 无限制No limit
每个共享的最大 IOPSMaximum IOPS per share 1,000 IOPS1,000 IOPS 100,000 IOPS100,000 IOPS
每个文件共享的存储的访问策略的最大数目Maximum number of stored access policies per file share 55 55
单个文件共享的目标吞吐量Target throughput for a single file share 最多 60 MiB/秒Up to 60 MiB/sec 请参阅高级文件共享入口和出口值See premium file share ingress and egress values
单个文件共享的最大出口Maximum egress for a single file share 请参阅标准文件共享的目标吞吐量See standard file share target throughput 高达 6,204 MiB/秒Up to 6,204 MiB/s
单个文件共享的最大入口Maximum ingress for a single file share 请参阅标准文件共享的目标吞吐量See standard file share target throughput 高达 4,136 MiB/秒Up to 4,136 MiB/s
每个文件打开图柄的最大数目Maximum open handles per file 2,000 个打开句柄2,000 open handles 2,000 个打开句柄2,000 open handles
共享快照的最大数目Maximum number of share snapshots 200 个共享快照200 share snapshots 200 个共享快照200 share snapshots
最大对象(目录和文件)名称长度Maximum object (directories and files) name length 2,048 个字符2,048 characters 2,048 个字符2,048 characters
最大路径名组成部分(在路径 \A\B\C\D 中,每个字母是一个组成部分)Maximum pathname component (in the path \A\B\C\D, each letter is a component) 255 个字符255 characters 255 个字符255 characters

Azure 文件同步限制Azure File Sync limits

资源Resource 确定目标Target 硬限制Hard limit
每个区域的存储同步服务数Storage Sync Services per region 20 个存储同步服务20 Storage Sync Services Yes
每个存储同步服务的同步组数Sync groups per Storage Sync Service 100 个同步组100 sync groups Yes
每个存储同步服务的已注册服务器Registered servers per Storage Sync Service 99 台服务器99 servers Yes
每个同步组的云终结点Cloud endpoints per sync group 1 个云终结点1 cloud endpoint Yes
每个同步组的服务器终结点Server endpoints per sync group 50 个服务器终结点50 server endpoints No
每个服务器的服务器终结点数Server endpoints per server 30 个服务器终结点30 server endpoints Yes
终结点大小Endpoint size 4 TiB4 TiB No
每个同步组的文件系统对象数(目录和文件)File system objects (directories and files) per sync group 2500 万个对象25 million objects No
目录中的最大文件系统对象(目录和文件)数Maximum number of file system objects (directories and files) in a directory 1 亿个对象1 million objects Yes
最大对象(目录和文件)安全描述符大小Maximum object (directories and files) security descriptor size 64 KiB64 KiB Yes
文件大小File size 100 GiB100 GiB No
要进行分层的文件的最小文件大小Minimum file size for a file to be tiered 64 KiB64 KiB Yes
并发同步会话Concurrent sync sessions V4 代理及更高版本:根据可用系统资源限制而异。V4 agent and later: The limit varies based on available system resources.
V3 代理:每个处理器或最多为每个服务器的八个活动的同步会话的两个活动的同步会话。V3 agent: Two active sync sessions per processor or a maximum of eight active sync sessions per server.
Yes

Azure 队列存储限制Azure Queue storage limits

资源Resource 目标Target
单个队列的最大大小Maximum size of a single queue 500 TiB500 TiB
在队列中消息的最大大小Maximum size of a message in a queue 64 KiB64 KiB
每个队列的存储的访问策略的最大数目Maximum number of stored access policies per queue 55
每个存储帐户的最大请求速率Maximum request rate per storage account 20,000 条消息 / 秒,假定 1 KiB 消息大小20,000 messages per second, which assumes a 1-KiB message size
单个队列 (1 KiB 消息) 的目标吞吐量Target throughput for a single queue (1-KiB messages) 每秒最多 2,000 条消息Up to 2,000 messages per second

Azure 表存储限制Azure Table storage limits

资源Resource 目标Target
单个表的最大大小Maximum size of a single table 500 TiB500 TiB
表实体的最大大小Maximum size of a table entity 1 MiB1 MiB
中的表实体属性的最大数目Maximum number of properties in a table entity 255,其中包括三个系统属性:PartitionKey、 RowKey 和 Timestamp255, which includes three system properties: PartitionKey, RowKey, and Timestamp
每个表的存储的访问策略的最大数目Maximum number of stored access policies per table 55
每个存储帐户的最大请求速率Maximum request rate per storage account 20,000 事务 / 秒,假定实体大小为 1 KiB20,000 transactions per second, which assumes a 1-KiB entity size
单个表分区 (1 KiB 实体) 的目标吞吐量Target throughput for a single table partition (1 KiB-entities) 最多 2,000 条实体数 / 秒Up to 2,000 entities per second

虚拟机磁盘限制Virtual machine disk limits

可以将多个数据磁盘附加到 Azure 虚拟机。You can attach a number of data disks to an Azure virtual machine. 根据 VM 的数据磁盘的可伸缩性和性能目标,可以确定的数量和类型满足性能和容量要求所需的磁盘。Based on the scalability and performance targets for a VM's data disks, you can determine the number and type of disk that you need to meet your performance and capacity requirements.

重要

为了获得最佳性能,需要限制附加到虚拟机的、重度使用的磁盘数,以避免可能的性能限制。For optimal performance, limit the number of highly utilized disks attached to the virtual machine to avoid possible throttling. 如果所有附加的磁盘不高利用率在同一时间,虚拟机可以支持更多的磁盘。If all attached disks aren't highly utilized at the same time, the virtual machine can support a larger number of disks.

Azure 托管磁盘:For Azure managed disks:

下表说明了默认值和每个区域每个订阅的资源数的最大限制The following table illustrates the default and maximum limits of the number of resources per region per subscription

资源Resource 默认限制Default limit 最大限制Maximum limit
标准托管磁盘Standard managed disks 25,00025,000 50,00050,000
标准 SSD 托管磁盘Standard SSD managed disks 25,00025,000 50,00050,000
高级托管磁盘Premium managed disks 25,00025,000 50,00050,000
Standard_LRS 快照Standard_LRS snapshots 25,00025,000 50,00050,000
Standard_ZRS 快照Standard_ZRS snapshots 25,00025,000 50,00050,000
托管的映像Managed image 25,00025,000 50,00050,000
  • 对于标准存储帐户: 标准存储帐户的总请求率上限为 20,000 IOPS。For Standard storage accounts: A Standard storage account has a maximum total request rate of 20,000 IOPS. 在所有标准存储帐户中虚拟机磁盘的 IOPS 总数不应超过此限制。The total IOPS across all of your virtual machine disks in a Standard storage account should not exceed this limit.

    大致可以计算支持的基于请求速率限制单个标准存储帐户的利用率较高的磁盘数。You can roughly calculate the number of highly utilized disks supported by a single Standard storage account based on the request rate limit. 例如,对于基本层 VM,重度使用磁盘的最大数目是大约 66,即每个磁盘 20000/300 IOPS。For example, for a Basic tier VM, the maximum number of highly utilized disks is about 66, which is 20,000/300 IOPS per disk. 标准层 VM 的磁盘利用率较高的最大数目是约为 40,即每个磁盘 20000/500 IOPS。The maximum number of highly utilized disks for a Standard tier VM is about 40, which is 20,000/500 IOPS per disk.

  • 高级存储帐户: 高级存储帐户的总吞吐量速率上限为 50 Gbps。For Premium storage accounts: A Premium storage account has a maximum total throughput rate of 50 Gbps. 所有 VM 磁盘的总吞吐量不应超过此限制。The total throughput across all of your VM disks should not exceed this limit.

有关详细信息,请参阅虚拟机大小For more information, see Virtual machine sizes.

托管虚拟机磁盘Managed virtual machine disks

标准 HDD 托管磁盘

标准磁盘类型Standard Disk Type S4S4 S6S6 S10S10 S15S15 S20S20 S30S30 S40S40 S50S50 S60S60 S70S70 S80S80
磁盘大小 (GiB)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0954,095 8,1928,192 16,38416,384 32,76732,767
每个磁盘的 IOPSIOPS per disk 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 1,300Up to 1,300 最多 2,000Up to 2,000 最多 2,000Up to 2,000
每个磁盘的吞吐量Throughput per disk 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 300 MiB/秒Up to 300 MiB/sec 最多 500 MiB/秒Up to 500 MiB/sec 最多 500 MiB/秒Up to 500 MiB/sec
Standard HDD managed disks
标准磁盘类型Standard Disk Type S4S4 S6S6 S10S10 S15S15 S20S20 S30S30 S40S40 S50S50 S60S60 S70S70 S80S80
磁盘大小 (GiB)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0954,095 8,1928,192 16,38416,384 32,76732,767
每个磁盘的 IOPSIOPS per disk 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 1,300Up to 1,300 最多 2,000Up to 2,000 最多 2,000Up to 2,000
每个磁盘的吞吐量Throughput per disk 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 300 MiB/秒Up to 300 MiB/sec 最多 500 MiB/秒Up to 500 MiB/sec 最多 500 MiB/秒Up to 500 MiB/sec

标准 SSD 托管磁盘

标准 SSD 大小Standard SSD sizes E4E4 E6E6 E10E10 E15E15 E20E20 E30E30 E40E40 E50E50 E60E60 E70E70 E80E80
磁盘大小 (GiB)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0954,095 8,1928,192 16,38416,384 32,76732,767
每个磁盘的 IOPSIOPS per disk 最多 120Up to 120 最多 240Up to 240 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 2,000Up to 2,000 最多 4,000 个Up to 4,000 最多 6000Up to 6,000
每个磁盘的吞吐量Throughput per disk 最多 25 MiB/秒Up to 25 MiB/sec 最多 50 MiB/秒Up to 50 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 400 台 MiB/秒Up to 400 MiB/sec 达 600 个 MiB/秒Up to 600 MiB/sec 最多 750 MiB/秒Up to 750 MiB/sec
Standard SSD managed disks
标准 SSD 大小Standard SSD sizes E4E4 E6E6 E10E10 E15E15 E20E20 E30E30 E40E40 E50E50 E60E60 E70E70 E80E80
磁盘大小 (GiB)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0954,095 8,1928,192 16,38416,384 32,76732,767
每个磁盘的 IOPSIOPS per disk 最多 120Up to 120 最多 240Up to 240 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 2,000Up to 2,000 最多 4,000 个Up to 4,000 最多 6000Up to 6,000
每个磁盘的吞吐量Throughput per disk 最多 25 MiB/秒Up to 25 MiB/sec 最多 50 MiB/秒Up to 50 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 400 台 MiB/秒Up to 400 MiB/sec 达 600 个 MiB/秒Up to 600 MiB/sec 最多 750 MiB/秒Up to 750 MiB/sec

高级 SSD 托管磁盘:每个磁盘的限制

高级 SSD 大小Premium SSD sizes  P4P4 P6P6 P10P10 P15P15 P20P20 P30P30 P40P40 P50P50 P60P60 P70P70 P80P80
磁盘大小 (GiB)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0954,095 8,1928,192 16,38416,384 32,76732,767
每个磁盘的 IOPSIOPS per disk 最多 120Up to 120 最多 240Up to 240 最多 500Up to 500 最多 1,100Up to 1,100 最多 2,300Up to 2,300 最多 5,000Up to 5,000 最多 7,500Up to 7,500 最多 7,500Up to 7,500 最多 16,000Up to 16,000 最多 18,000Up to 18,000 最多 20,000Up to 20,000
每个磁盘的吞吐量Throughput per disk 最多 25 MiB/秒Up to 25 MiB/sec 最多 50 MiB/秒Up to 50 MiB/sec 最多 100 MiB/秒Up to 100 MiB/sec 最多 125 MiB/秒Up to 125 MiB/sec 最多 150 MiB/秒Up to 150 MiB/sec 最多 200 MiB/秒Up to 200 MiB/sec 最多 250 MiB/秒Up to 250 MiB/sec 最多 250 MiB/秒Up to 250 MiB/sec 最多 500 MiB/秒Up to 500 MiB/sec 最多 750 MiB/秒Up to 750 MiB/sec 最多 900 MiB/秒Up to 900 MiB/sec
Premium SSD managed disks: Per-disk limits
高级 SSD 大小Premium SSD sizes  P4P4 P6P6 P10P10 P15P15 P20P20 P30P30 P40P40 P50P50 P60P60 P70P70 P80P80
磁盘大小 (GiB)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0954,095 8,1928,192 16,38416,384 32,76732,767
每个磁盘的 IOPSIOPS per disk 最多 120Up to 120 最多 240Up to 240 最多 500Up to 500 最多 1,100Up to 1,100 最多 2,300Up to 2,300 最多 5,000Up to 5,000 最多 7,500Up to 7,500 最多 7,500Up to 7,500 最多 16,000Up to 16,000 最多 18,000Up to 18,000 最多 20,000Up to 20,000
每个磁盘的吞吐量Throughput per disk 最多 25 MiB/秒Up to 25 MiB/sec 最多 50 MiB/秒Up to 50 MiB/sec 最多 100 MiB/秒Up to 100 MiB/sec 最多 125 MiB/秒Up to 125 MiB/sec 最多 150 MiB/秒Up to 150 MiB/sec 最多 200 MiB/秒Up to 200 MiB/sec 最多 250 MiB/秒Up to 250 MiB/sec 最多 250 MiB/秒Up to 250 MiB/sec 最多 500 MiB/秒Up to 500 MiB/sec 最多 750 MiB/秒Up to 750 MiB/sec 最多 900 MiB/秒Up to 900 MiB/sec

高级 SSD 托管磁盘:每个 VM 的限制Premium SSD managed disks: Per-VM limits

资源Resource 默认限制Default limit
每个 VM 的最大 IOPSMaximum IOPS Per VM GS5 VM 为 80,000 IOPS80,000 IOPS with GS5 VM
每个 VM 的最大吞吐量Maximum throughput per VM GS5 VM 为 2,000 MB/秒2,000 MB/s with GS5 VM

非托管虚拟机磁盘Unmanaged virtual machine disks

标准非托管的虚拟机磁盘:每个磁盘的限制Standard unmanaged virtual machine disks: Per-disk limits

VM 层VM tier 基本层 VMBasic tier VM 标准层 VMStandard tier VM
磁盘大小Disk size 4,095 GB4,095 GB 4,095 GB4,095 GB
每个持久性磁盘最大 8 KB IOPSMaximum 8-KB IOPS per persistent disk 300300 500500
最大执行的最大 IOPS 的磁盘数Maximum number of disks that perform the maximum IOPS 6666 4040

高级非托管的虚拟机磁盘:每个帐户限制Premium unmanaged virtual machine disks: Per-account limits

资源Resource 默认限制Default limit
每个帐户的总磁盘容量Total disk capacity per account 35 TB35 TB
每个帐户的总快照容量Total snapshot capacity per account 10 TB10 TB
每个帐户 (传入 + 传出) 的最大带宽1Maximum bandwidth per account (ingress + egress)1 <=50 Gbps<=50 Gbps

1入口指发送到存储帐户的请求中的所有数据。1Ingress refers to all data from requests that are sent to a storage account. 出口指从存储帐户接收的响应中的所有数据。Egress refers to all data from responses that are received from a storage account.

高级非托管的虚拟机磁盘:每个磁盘的限制Premium unmanaged virtual machine disks: Per-disk limits

高级存储磁盘类型Premium storage disk type P10P10 P20P20 P30P30 P40P40 P50P50
磁盘大小Disk size 128 GiB128 GiB 512 GiB512 GiB 1,024 giB (1 TB)1,024 GiB (1 TB) 2,048 giB (2 TB)2,048 GiB (2 TB) 4,095 giB (4 TB)4,095 GiB (4 TB)
每个磁盘的最大 IOPSMaximum IOPS per disk 500500 2,3002,300 5,0005,000 7,5007,500 7,5007,500
每个磁盘的最大吞吐量Maximum throughput per disk 100 MB/秒100 MB/sec 150 MB/秒150 MB/sec 200 MB/秒200 MB/sec 250 MB/秒250 MB/sec 250 MB/秒250 MB/sec
每个存储帐户磁盘数上限Maximum number of disks per storage account 280280 7070 3535 1717 88

高级非托管的虚拟机磁盘:每个 VM 的限制Premium unmanaged virtual machine disks: Per-VM limits

资源Resource 默认限制Default limit
每个 VM 的最大 IOPSMaximum IOPS per VM GS5 VM 为 80,000 IOPS80,000 IOPS with GS5 VM
每个 VM 的最大吞吐量Maximum throughput per VM GS5 vm 2,000 MB/秒2,000 MB/sec with GS5 VM

Azure 云服务限制Azure Cloud Services limits

资源Resource 默认限制Default limit 最大限制Maximum limit
每个部署的 web 或辅助角色1Web or worker roles per deployment1 2525 2525
实例输入终结点每个部署Instance input endpoints per deployment 2525 2525
输入终结点每个部署Input endpoints per deployment 2525 2525
内部终结点每个部署Internal endpoints per deployment 2525 2525
每个部署的托管服务证书数Hosted service certificates per deployment 199199 199199

1每个 Azure 云服务中使用 web 或辅助角色可以有两个部署,一个用于生产,一个用于过渡。1Each Azure Cloud Service with web or worker roles can have two deployments, one for production and one for staging. 此限制是指不同的角色,即配置数量。This limit refers to the number of distinct roles, that is, configuration. 此限制不是指每个角色,实例数,即缩放。This limit doesn't refer to the number of instances per role, that is, scaling.

应用服务限制App Service limits

以下应用服务限制包括 Web 应用、移动应用、API 应用的限制。The following App Service limits include limits for Web Apps, Mobile Apps, and API Apps.

资源Resource 免费Free 共享Shared 基本Basic 标准Standard 高级 (v2)Premium (v2) 隔离Isolated
Web、 移动或 API 应用每个Azure 应用服务计划1Web, mobile, or API apps per Azure App Service plan1 1010 100100 无限制2Unlimited2 无限制2Unlimited2 无限制2Unlimited2 无限制2Unlimited2
应用服务计划App Service plan 每个区域仅 10 个10 per region 每个资源组 10 个10 per resource group 每个资源组 100 个100 per resource group 每个资源组 100 个100 per resource group 每个资源组 100 个100 per resource group 每个资源组 100 个100 per resource group
计算实例类型Compute instance type 共享Shared 共享Shared 专用3Dedicated3 专用3Dedicated3 专用3Dedicated3

专用3Dedicated3
向外扩展(最大实例数)Scale out (maximum instances) 1 个共享1 shared 1 个共享1 shared 3 个专用33 dedicated3 10 个专用310 dedicated3 20 个专用320 dedicated3 100 个专用4100 dedicated4
存储5Storage5 1 GB51 GB5 1 GB51 GB5 10 GB510 GB5 50 GB550 GB5 250 GB5250 GB5

1 TB51 TB5
CPU 时间 (5 分钟)6CPU time (5 minutes)6 3 分钟3 minutes 3 分钟3 minutes 无限制,按标准费率付费Unlimited, pay at standard rates 无限制,按标准费率付费Unlimited, pay at standard rates 无限制,按标准费率付费Unlimited, pay at standard rates 无限制,按标准费率付费Unlimited, pay at standard rates
CPU 时间(天)6CPU time (day)6 60 分钟60 minutes 240 分钟240 minutes 无限制,按标准费率付费Unlimited, pay at standard rates 无限制,按标准费率付费Unlimited, pay at standard rates 无限制,按标准费率付费Unlimited, pay at standard rates 无限制,按标准费率付费Unlimited, pay at standard rates
内存(1 小时)Memory (1 hour) 每个应用服务计划 1024 MB1,024 MB per App Service plan 每个应用 1024 MB1,024 MB per app 不适用N/A 不适用N/A 不适用N/A 不适用N/A
带宽Bandwidth 165 MB165 MB 无限制,收取数据传输费Unlimited, data transfer rates apply 无限制,收取数据传输费Unlimited, data transfer rates apply 无限制,收取数据传输费Unlimited, data transfer rates apply 无限制,收取数据传输费Unlimited, data transfer rates apply 无限制,收取数据传输费Unlimited, data transfer rates apply
应用程序体系结构Application architecture 32 位32-bit 32 位32-bit 32 位/64 位32-bit/64-bit 32 位/64 位32-bit/64-bit 32 位/64 位32-bit/64-bit 32 位/64 位32-bit/64-bit
Web 套接字,每个实例7Web sockets per instance7 55 3535 350350 无限制Unlimited 不受限制Unlimited 不受限制Unlimited
每个应用程序的并发调试器连接数Concurrent debugger connections per application 1 11 11 55 55 55
每个订阅的应用服务证书10App Service Certificates per subscription10 不支持Not supported 不支持Not supported 1010 1010 1010 1010
每个应用的自定义域数Custom domains per app 0(仅 azurewebsites.net 子域)0 (azurewebsites.net subdomain only) 500500 500500 500500 500500 500500
自定义域 SSL 支持Custom domain SSL support 不受支持,通配符证书为 *。 默认情况下可用的 azurewebsites.netNot supported, wildcard certificate for *.azurewebsites.net available by default 不受支持,通配符证书为 *。 默认情况下可用的 azurewebsites.netNot supported, wildcard certificate for *.azurewebsites.net available by default 无限制的 SNI SSL 连接Unlimited SNI SSL connections 包含无限制的 SNI SSL 连接和 1 个 IP SSL 连接Unlimited SNI SSL and 1 IP SSL connections included 包含无限制的 SNI SSL 连接和 1 个 IP SSL 连接Unlimited SNI SSL and 1 IP SSL connections included 包含无限制的 SNI SSL 连接和 1 个 IP SSL 连接Unlimited SNI SSL and 1 IP SSL connections included
集成的负载均衡器Integrated load balancer XX XX XX XX X9X9
始终打开Always On XX XX XX XX
计划的备份Scheduled backups 计划的备份每隔 2 小时,最多为 12 个备份每日 (手动 + 计划)Scheduled backups every 2 hours, a maximum of 12 backups per day (manual + scheduled) 计划的备份每隔一小时,最多 50 个备份每日 (手动 + 计划)Scheduled backups every hour, a maximum of 50 backups per day (manual + scheduled) 计划的备份每隔一小时,最多 50 个备份每日 (手动 + 计划)Scheduled backups every hour, a maximum of 50 backups per day (manual + scheduled)
自动缩放Autoscale XX XX XX
WebJobs8WebJobs8 XX XX XX XX XX XX
Azure 计划程序支持Azure Scheduler support XX XX XX XX XX
终结点监视Endpoint monitoring XX XX XX XX
过渡槽Staging slots 55 2020 2020
SLASLA 99.9%99.9% 99.95%99.95% 99.95%99.95% 99.95%99.95%

1除非特别说明,否则应用和存储配额依每个应用服务计划为准。1Apps and storage quotas are per App Service plan unless noted otherwise.
2可以在这些计算机上托管的应用的实际数目取决于应用的活动、计算机实例的大小和相应的资源利用率。2The actual number of apps that you can host on these machines depends on the activity of the apps, the size of the machine instances, and the corresponding resource utilization.
3专用实例可有不同的大小。3Dedicated instances can be of different sizes. 有关详细信息,请参阅应用服务定价For more information, see App Service pricing.
4根据请求允许使用的详细信息。4More are allowed upon request.
5存储限制是跨相同应用服务计划中所有应用的内容总大小。5The storage limit is the total content size across all apps in the same App Service plan.
6这些资源受到专用实例上的物理资源(实例大小和实例数)的限制。6These resources are constrained by physical resources on the dedicated instances (the instance size and the number of instances).
7如果将基本层的某个应用扩展为两个实例,则其中每个实例有 350 个并发连接。7If you scale an app in the Basic tier to two instances, you have 350 concurrent connections for each of the two instances.
8按需、按计划或作为应用服务实例内的后台任务连续运行自定义可执行文件和/或脚本。8Run custom executables and/or scripts on demand, on a schedule, or continuously as a background task within your App Service instance. 连续执行 WebJob 需要使用“始终打开”。Always On is required for continuous WebJobs execution. 计划的 WebJob 需要使用 Azure 计划程序免费或标准版。Azure Scheduler Free or Standard is required for scheduled WebJobs. 可在应用服务实例中运行的 web 作业的数量没有预定义的限制。There's no predefined limit on the number of WebJobs that can run in an App Service instance. 没有实际限制,取决于应用程序代码正在尝试执行操作。There are practical limits that depend on what the application code is trying to do.
9应用服务独立 Sku 能够实现内部负载均衡 (ILB) 与 Azure 负载均衡器,因此没有公共从 internet 连接。9App Service Isolated SKUs have the ability to be internally load balanced (ILB) with Azure Load Balancer, so there's no public connectivity from the internet. 因此,必须从能够直接访问 ILB 网络终结点的计算机使用 ILB 独立应用服务的某些功能。As a result, some features of an ILB Isolated App Service must be used from machines that have direct access to the ILB network endpoint.
10可以通过对最大限制为 200 的支持请求增加每个订阅的应用服务证书配额限制。10The App Service Certificate quota limit per subscription can be increased via a support request to a maximum limit of 200.

计划程序限制Scheduler limits

下表描述 Azure 计划程序中各主要的配额、限制、默认值和中止值。The following table describes each of the major quotas, limits, defaults, and throttles in Azure Scheduler.

资源Resource 限制说明Limit description
作业大小Job size 最大作业大小为 16,000。The maximum job size is 16,000. 如果 PUT 或 PATCH 操作生成的作业大小超过此限制,则返回 400 错误请求状态代码。If a PUT or a PATCH operation results in a job size larger than this limit, a 400 Bad Request status code is returned.
作业集合数Job collections 每个 Azure 订阅的最大作业集合数为 200,000 个。The maximum number of job collections per Azure subscription is 200,000.
每个集合的作业数Jobs per collection 默认情况下,最大作业数在免费作业集合中为 5 个作业,在标准作业集合中为 50 个作业。By default, the maximum number of jobs is five jobs in a free job collection and 50 jobs in a standard job collection.

在作业集合上,可更改作业的最大数目。You can change the maximum number of jobs on a job collection. 作业集合中的所有作业均限制为对作业集合设置的值。All jobs in a job collection are limited to the value set on the job collection. 如果尝试创建超过最大作业配额数目的更多作业,则请求会失败并且具有 409 冲突状态代码。If you attempt to create more jobs than the maximum jobs quota, the request fails with a 409 Conflict status code.

距离开始时间的时间Time to start time 最大“距离开始时间的时间”为 18 个月。The maximum "time to start time" is 18 months.
重复间隔Recurrence span 最大重复间隔为 18 个月。The maximum recurrence span is 18 months.
频率Frequency 默认情况下,最大频率配额在免费作业集合中为 1 小时,在标准作业集合中为 1 分钟。By default, the maximum frequency quota is one hour in a free job collection and one minute in a standard job collection.

可以使作业集合上的最高频率低于最大值。You can make the maximum frequency on a job collection lower than the maximum. 作业集合中的所有作业均限制为对作业集合设置的值。All jobs in the job collection are limited to the value set on the job collection. 如果尝试创建其频率高于针对作业集合的最大频率的作业,则请求会失败并且具有 409 冲突状态代码。If you attempt to create a job with a higher frequency than the maximum frequency on the job collection, the request fails with a 409 Conflict status code.

正文大小Body size 请求的最大正文大小为 8192 个字符。The maximum body size for a request is 8,192 chars.
请求 URL 大小Request URL size 请求 URL 的最大大小为 2048 个字符。The maximum size for a request URL is 2,048 chars.
标头计数Header count 最大标头计数为 50 个标头。The maximum header count is 50 headers.
聚合标头大小Aggregate header size 最大聚合标头大小为 4096 个字符。The maximum aggregate header size is 4,096 chars.
超时Timeout 请求超时是静态的也就是说,不可配置。The request timeout is static, that is, not configurable. 并为 60 秒的 HTTP 操作。and is 60 seconds for HTTP actions. 对于运行时间较长的操作,请遵循 HTTP 异步协议。For longer running operations, follow the HTTP asynchronous protocols. 例如,立即返回 202 但继续在后台工作。For example, return a 202 immediately but continue working in the background.
作业历史记录Job history 作业历史记录中存储的最大响应正文为 2048 个字节。The maximum response body stored in job history is 2,048 bytes.
作业历史记录保留期Job history retention 作业历史记录是保持为最多两个月,或者到的最后 1000 个的执行。Job history is kept for up to two months or up to the last 1,000 executions.
已完成和出错作业的保留期Completed and faulted job retention 完成的作业和出错的作业保留 60 天。Completed and faulted jobs are kept for 60 days.

Batch 限制Batch limits

资源Resource 默认限制Default limit 最大限制Maximum limit
每个区域每个订阅的 azure Batch 帐户Azure Batch accounts per region per subscription 1-31-3 5050
每个批处理帐户的专用核心数Dedicated cores per Batch account 10-10010-100 不适用1N/A1
每个批处理帐户的低优先级核心数Low-priority cores per Batch account 10-10010-100 N/A2N/A2
每个批处理帐户的活动作业和作业计划数3Active jobs and job schedules3 per Batch account 100-300100-300 1,00041,0004
每个 Batch 帐户的池数Pools per Batch account 20-10020-100 50045004

备注

默认限制因用于创建 Batch 帐户的订阅类型而异。Default limits vary depending on the type of subscription you use to create a Batch account. 显示的核心配额适用于 Batch 服务模式下的 Batch 帐户。Cores quotas shown are for Batch accounts in Batch service mode. 查看 Batch 帐户中的配额View the quotas in your Batch account.

1可以增加的每个批处理帐户的专用核心数,但未指定最大数目。1The number of dedicated cores per Batch account can be increased, but the maximum number is unspecified. 若要讨论增加选项,请联系 Azure 支持。To discuss increase options, contact Azure Support.

2可以增加每个批处理帐户的低优先级核心数,但不指定最大数目。2The number of low-priority cores per Batch account can be increased, but the maximum number is unspecified. 若要讨论增加选项,请联系 Azure 支持。To discuss increase options, contact Azure Support.

3已完成的作业和作业计划不受限制。3Completed jobs and job schedules aren't limited.

4若要请求增加的配额超出此限制,请联系 Azure 支持部门。4To request an increase beyond this limit, contact Azure Support.

BizTalk 服务限制BizTalk Services limits

下表显示了 Azure BizTalk 服务的限制。The following table shows the limits for Azure BizTalk Services.

资源Resource 免费(预览版)Free (Preview) 开发人员Developer 基本Basic 标准Standard 高级Premium
横向扩展Scale out 不适用N/A 不适用N/A 可扩展,增量为 1 个基本版单位Yes, in increments of 1 Basic unit 可扩展,增量为 1 个标准版单位Yes, in increments of 1 Standard unit 可扩展,增量为 1 个高级版单位Yes, in increments of 1 Premium unit
缩放限制Scale limit 不适用N/A 不适用N/A 最多 8 个单位Up to 8 units 最多 8 个单位Up to 8 units 最多 8 个单位Up to 8 units
每个单位的 EAI 桥数EAI bridges per unit 不适用N/A 2525 2525 125125 500500
每个单位的 EDI 协议EDI agreements per unit 不适用N/A 1010 5050 250250 1,0001,000
每个单位的混合连接Hybrid connections per unit 55 55 1010 5050 100100
每个单位的混合连接数据传输 (Gb)Hybrid connection data transfer (GBs) per unit 55 55 5050 250250 500500
每个单位使用 BizTalk 适配器服务的连接数Number of connections that use BizTalk Adapter Service per unit 不适用N/A 11 22 55 2525
存档Archiving 不适用N/A 可用Available 不适用N/A 不适用N/A 可用Available
高可用性High availability 不适用N/A 不适用N/A 可用Available 可用Available 可用Available

Azure Cosmos DB 限制Azure Cosmos DB limits

Azure Cosmos DB 是全局缩放数据库,可对吞吐量和存储进行缩放,以处理应用程序的任何需求。Azure Cosmos DB is a global scale database in which throughput and storage can be scaled to handle whatever your application requires. 如果你有 Azure Cosmos DB 提供的规模有任何疑问,发送电子邮件发送到askcosmosdb@microsoft.com。If you have any questions about the scale Azure Cosmos DB provides, send email to askcosmosdb@microsoft.com.

Azure Database for MySQLAzure Database for MySQL

有关 Azure Database for MySQL 限制,请参阅 Azure Database for MySQL 中的限制For Azure Database for MySQL limits, see Limitations in Azure Database for MySQL.

Azure Database for PostgreSQLAzure Database for PostgreSQL

有关 Azure Database for PostgreSQL 限制,请参阅 Azure Database for PostgreSQL 中的限制For Azure Database for PostgreSQL limits, see Limitations in Azure Database for PostgreSQL.

Azure 搜索限制Azure Search limits

定价层决定了搜索服务的容量和限制。Pricing tiers determine the capacity and limits of your search service. 层包括:Tiers include:

  • 免费多租户服务,与其他 Azure 订户共享仅用于评估和小型开发项目。Free multitenant service, shared with other Azure subscribers, is intended for evaluation and small development projects.
  • 基本层为规模较小的生产工作负荷提供专用计算资源,并为高可用查询工作负荷提供最多 3 个副本。Basic provides dedicated computing resources for production workloads at a smaller scale, with up to three replicas for highly available query workloads.
  • 标准,其中包括 S1、 S2、 S3 和 S3 High Density 为更大的生产工作负荷。Standard, which includes S1, S2, S3, and S3 High Density, is for larger production workloads. 以便你可以选择最符合您工作负荷的配置文件的资源配置的标准层中有多个级别。Multiple levels exist within the Standard tier so that you can choose a resource configuration that best matches your workload profile.

基于订阅的限制Limits per subscription

可以创建一个订阅中的多个服务。You can create multiple services within a subscription. 每个可以在特定层预配。Each one can be provisioned at a specific tier. 限制是仅允许每个层的服务数。You're limited only by the number of services allowed at each tier. 例如,在同一订阅中,最多可以在基本层创建 12 个服务,在 S1 层也创建 12 个服务。For example, you could create up to 12 services at the Basic tier and another 12 services at the S1 tier within the same subscription. 有关层的详细信息,请参阅为 Azure 搜索选择 SKU 或层For more information about tiers, see Choose an SKU or tier for Azure Search.

最大服务数限制可以根据请求提高。Maximum service limits can be raised upon request. 如果需要在同一订阅中的更多服务,请联系 Azure 支持。If you need more services within the same subscription, contact Azure Support.

资源Resource 免费1Free1 基本Basic S1S1 S2S2 S3S3 S3 HDS3 HD L1L1 L2L2
最大服务数Maximum services 1 1616 1616 88 66 66 66 66
搜索单位 (SU) 中的最大缩放2Maximum scale in search units (SU)2 不适用N/A 3 SU3 SU 36 个 SU36 SU 36 个 SU36 SU 36 个 SU36 SU 36 个 SU36 SU 36 个 SU36 SU 36 个 SU36 SU

1 免费层基于共享资源,而不基于专用资源。1 Free is based on shared, not dedicated, resources. 共享资源不支持纵向扩展。Scale-up is not supported on shared resources.

2搜索单位即计费单位,为分配副本分区2 Search units are billing units, allocated as either a replica or a partition. 进行存储、索引和查询操作同时需要这两个资源。You need both resources for storage, indexing, and query operations. 若要了解有关 SU 计算的详细信息,请参阅缩放查询和索引工作负荷的资源级别To learn more about SU computations, see Scale resource levels for query and index workloads.

基于搜索服务的限制Limits per search service

存储受磁盘空间限制,或者受索引、文档或其他高级资源的最大数目的硬性限制,具体取决于哪一个限制先实施。Storage is constrained by disk space or by a hard limit on the maximum number of indexes, document, or other high-level resources, whichever comes first. 下表描述了存储限制。The following table documents storage limits. 有关索引、 文档和其他对象的最大限制,请参阅按资源限制For maximum limits on indexes, documents, and other objects, see Limits by resource.

资源Resource 免费Free 基本1Basic1 S1S1 S2S2 S3S3 S3 HD2S3 HD2 L1L1 L2L2
服务级别协议 (SLA)3Service level agreement (SLA)3 No Yes Yes Yes Yes Yes Yes Yes
每个分区的存储Storage per partition 50 MB50 MB 2 GB2 GB 25 GB25 GB 100 GB100 GB 200 GB200 GB 200 GB200 GB 1 TB1 TB 2 TB2 TB
每个服务的分区数Partitions per service 不适用N/A 1 1212 1212 1212 33 1212 1212
分区大小Partition size 不适用N/A 2 GB2 GB 25 GB25 GB 100 GB100 GB 200 GB200 GB 200 GB200 GB 1 TB1 TB 2 TB2 TB
副本Replicas 不适用N/A 33 1212 1212 1212 1212 1212 1212

1 基本层有一个固定分区。1 Basic has one fixed partition. 在此层中,为提高的查询工作负荷分配更多副本使用附加搜索单位。At this tier, additional search units are used for allocating more replicas for increased query workloads.

2 S3 HD 的硬限制为三个分区,低于 S3 的分区限制。2 S3 HD has a hard limit of three partitions, which is lower than the partition limit for S3. 施加的分区限制较低是因为 S3 HD 的索引计数要高得多。The lower partition limit is imposed because the index count for S3 HD is substantially higher. 由于计算资源(存储和处理)和内容(索引和文档)都存在服务限制,因此会先达到内容限制。Given that service limits exist for both computing resources (storage and processing) and content (indexes and documents), the content limit is reached first.

3服务级别协议提供专用资源上的可计费服务。3 Service level agreements are offered for billable services on dedicated resources. 免费服务和预览功能没有 SLA。Free services and preview features have no SLA. 对于可计费服务,SLA 将在用户为服务预配足够冗余时生效。For billable services, SLAs take effect when you provision sufficient redundancy for your service. 查询 (读取) Sla 需要两个或多个副本。Two or more replicas are required for query (read) SLAs. 用于查询和索引 (读-写) Sla 需要三个或多个副本。Three or more replicas are required for query and indexing (read-write) SLAs. 分区数不是一个 SLA 的考虑因素。The number of partitions isn't an SLA consideration.

若要更详细地了解关于限制的详细信息(如文档大小、每秒查询数、密钥、请求和响应),请参阅 Azure 搜索中的服务限制To learn more about limits on a more granular level, such as document size, queries per second, keys, requests, and responses, see Service limits in Azure Search.

媒体服务限制Media Services limits

备注

对于不固定的资源,请打开支持票证以请求增加配额中。For resources that aren't fixed, open a support ticket to ask for an increase in the quotas. 不尝试获取更高的限制中创建更多 Azure 媒体服务帐户。Don't create additional Azure Media Services accounts in an attempt to obtain higher limits.

资源Resource 默认限制Default limit
单个订阅中的 azure 媒体服务帐户Azure Media Services accounts in a single subscription 25(固定)25 (fixed)
媒体保留单位,每个媒体服务帐户Media reserved units per Media Services account 25 (S1)25 (S1)
10 (S2, S3)110 (S2, S3)1
每个媒体服务帐户的作业数Jobs per Media Services account 50,000250,0002
每个作业的链接任务数Chained tasks per job 30(固定)30 (fixed)
每个媒体服务帐户的资产Assets per Media Services account 1,000,0001,000,000
每个任务的资产数Assets per task 5050
每个作业的资产数Assets per job 100100
一次与一个资产关联的唯一定位符数Unique locators associated with an asset at one time 5454
每个媒体服务帐户的实时频道数Live channels per Media Services account 55
每个频道的停止状态节目数Programs in stopped state per channel 5050
每个频道的运行状态节目数Programs in running state per channel 33
流式处理终结点已停止的或运行每个媒体服务帐户Streaming endpoints that are stopped or running per Media Services account 22
每个流式处理终结点的流式处理单位数Streaming units per streaming endpoint 1010
存储帐户Storage accounts 1,0005(固定)1,0005 (fixed)
策略Policies 1,000,00061,000,0006
文件大小File size 在某些情况下,支持在媒体服务中处理的最大文件大小没有限制。7In some scenarios, there's a limit on the maximum file size supported for processing in Media Services.7

1如果更改类型,例如,从 s2 切换到 S1,最大保留的单位限制会重置。1If you change the type, for example, from S2 to S1, the maximum reserved unit limits are reset.

2此数字包括已排队、 已完成、 活动和已取消作业。2This number includes queued, finished, active, and canceled jobs. 它不包括删除的作业。It doesn't include deleted jobs. 可以通过删除旧作业IJob.Delete删除HTTP 请求。You can delete old jobs by using IJob.Delete or the DELETE HTTP request.

截至 2017 年 4 月 1 日,任何在你的帐户 90 天以前是自动删除作业记录,及其关联的任务记录。As of April 1, 2017, any job record in your account older than 90 days is automatically deleted, along with its associated task records. 即使记录总数低于最大配额,则自动删除。Automatic deletion occurs even if the total number of records is below the maximum quota. 要存档的作业和任务的信息,请使用代码中所述使用媒体服务.NET SDK 管理资产To archive the job and task information, use the code described in Manage assets with the Media Services .NET SDK.

3请求列表作业实体时,每个请求返回 1,000 个作业最多。3When you make a request to list job entities, a maximum of 1,000 jobs is returned per request. 若要跟踪的所有已提交的作业,请使用顶部或跳过的查询中所述OData 系统查询选项To keep track of all submitted jobs, use the top or skip queries as described in OData system query options.

4定位符不用于管理每个用户的访问控制。4Locators aren't designed for managing per-user access control. 若要提供给单个用户的不同访问权限,使用数字版权管理 (DRM) 解决方案。To give different access rights to individual users, use digital rights management (DRM) solutions. 有关详细信息,请参阅使用 Azure 媒体服务保护内容For more information, see Protect your content with Azure Media Services.

5的存储帐户必须是从同一 Azure 订阅。5The storage accounts must be from the same Azure subscription.

6为 1,000,000 个不同的媒体服务策略的限制。6There's a limit of 1,000,000 policies for different Media Services policies. 例如,对于定位器策略或 ContentKeyAuthorizationPolicy。An example is for the Locator policy or ContentKeyAuthorizationPolicy.

备注

如果始终使用相同的日期和访问权限,则使用相同的策略 id。If you always use the same days and access permissions, use the same policy ID. 有关信息和示例,请参阅使用媒体服务.NET SDK 管理资产For information and an example, see Manage assets with the Media Services .NET SDK.

7对单个 blob 目前最多为 5 TB,在 Azure Blob 存储中受支持的最大大小。7The maximum size supported for a single blob is currently up to 5 TB in Azure Blob Storage. 媒体服务基于服务使用的 VM 大小应用其他限制。Additional limits apply in Media Services based on the VM sizes that are used by the service. 大小限制适用于你上传的文件以及导致处理 (编码或分析) 的媒体服务获取生成的文件。The size limit applies to the files that you upload and also the files that get generated as a result of Media Services processing (encoding or analyzing). 如果源文件大于 260 GB,作业可能会失败。If your source file is larger than 260-GB, your Job will likely fail.

下表显示了对媒体保留单位的 S1、 S2 和 s3 版的限制。The following table shows the limits on the media reserved units S1, S2, and S3. 如果源文件大于表中所定义的限制,查看编码作业将失败。If your source file is larger than the limits defined in the table, your encoding job fails. 如果编码的持续时间长的 4k 分辨率源时,您需要使用 S3 媒体保留单位来实现所需的性能。If you encode 4K resolution sources of long duration, you're required to use S3 media reserved units to achieve the performance needed. 如果有大于 S3 媒体保留单位的 260 GB 限制的 4k 内容,请联系我们:amshelp@microsoft.com有关可能的缓解措施来支持你的方案。If you have 4K content that's larger than the 260-GB limit on the S3 media reserved units, contact us at amshelp@microsoft.com for potential mitigations to support your scenario.

媒体保留单位类型Media reserved unit type 最大输入的大小 (GB)Maximum input size (GB)
S1S1 2626
S2S2 6060
S3S3 260260

内容交付网络限制Content Delivery Network limits

资源Resource 默认限制Default limit
Azure 内容交付网络配置文件Azure Content Delivery Network profiles 2525
每个配置文件的内容交付网络终结点Content Delivery Network endpoints per profile 2525
每个终结点的自定义域数Custom domains per endpoint 2525

内容交付网络订阅可以包含一个或多个内容交付网络配置文件。A Content Delivery Network subscription can contain one or more Content Delivery Network profiles. 内容交付网络配置文件可以包含一个或多个内容交付网络终结点。A Content Delivery Network profile can contain one or more Content Delivery Network endpoints. 您可能想要使用多个配置文件来组织你的内容交付网络终结点的 internet 域、 web 应用程序或某些其他条件。You might want to use multiple profiles to organize your Content Delivery Network endpoints by internet domain, web application, or some other criteria.

移动服务限制Mobile Services limits

Tier 免费Free 基本Basic 标准Standard
API 调用API calls 500,000500,000 每个单位 150 万条1.5 million per unit 每个单位 1500 万个15 million per unit
活动设备Active devices 500500 不受限制Unlimited 不受限制Unlimited
缩放Scale 不适用N/A 最多 6 个单位Up to 6 units 单位数不受限制Unlimited units
推送通知Push notifications Azure 通知中心免费层包括,最多 1 万次推送Azure Notification Hubs Free tier included, up to 1 million pushes 包含通知中心基本层,最多 1000 万次推送Notification Hubs Basic tier included, up to 10 million pushes 包含通知中心标准层,最多 1000 万次推送Notification Hubs Standard tier included, up to 10 million pushes
实时消息传送 /Real-time messaging/
Web 套接字Web Sockets
受限制Limited 350 / 移动服务350 per mobile service 不受限制Unlimited
脱机同步Offline synchronizations 受限制Limited 附送Included 附送Included
计划的作业Scheduled jobs 受限制Limited 附送Included 附送Included
Azure SQL 数据库 (必需)Azure SQL Database (required)
对其他容量收取标准资费Standard rates apply for additional capacity
附送 20 MB20 MB included 附送 20 MB20 MB included 附送 20 MB20 MB included
CPU 容量CPU capacity 60 分钟 / 天60 minutes per day 不受限制Unlimited 不受限制Unlimited
出站数据传输Outbound data transfer 165 MB / 天 (日常累积转入)165 MB per day (daily rollover) 附送Included 附送Included

有关限制和定价的详细信息,请参阅Azure 移动服务定价For more information on limits and pricing, see Azure Mobile Services pricing.

监视限制Monitor limits

资源Resource 默认限制Default limit 最大限制Maximum limit
自动缩放设置Autoscale settings 每个区域每个订阅 100。100 per region per subscription. 默认值相同。Same as default.
指标警报 (经典)Metric alerts (classic) 每个订阅 100 活动警报规则。100 active alert rules per subscription. 致电支持人员。Call support.
指标警报Metric alerts 每个订阅 100 活动警报规则。100 active alert rules per subscription. 致电支持人员。Call support.
活动日志警报Activity log alerts 每个订阅 100 活动警报规则。100 active alert rules per subscription. 默认值相同。Same as default.
日志警报Log alerts 512512 致电支持人员。Call support.
操作组Action groups 每个订阅的 2,000 个操作组。2,000 action groups per subscription. 致电支持人员。Call support.

操作组特定的限制Action group-specific limits

资源Resource 默认限制Default limit 最大限制Maximum limit
Azure 应用推送Azure app push 每个操作组的 10 个 azure 应用操作。10 Azure app actions per action group. 致电支持人员。Call support.
电子邮件Email 一个操作组中的 1,000 电子邮件操作。1,000 email actions in an action group. 另请参阅速率限制信息Also see the rate limiting information. 致电支持人员。Call support.
ITSMITSM 一个操作组中的 10 个 ITSM 操作。10 ITSM actions in an action group. 致电支持人员。Call support.
逻辑应用Logic app 一个操作组中的 10 个逻辑应用操作。10 logic app actions in an action group. 致电支持人员。Call support.
RunbookRunbook 一个操作组中的 10 个 runbook 操作。10 runbook actions in an action group. 致电支持人员。Call support.
SMSSMS 一个操作组中的 10 个短信操作。10 SMS actions in an action group. 另请参阅速率限制信息Also see the rate limiting information. 致电支持人员。Call support.
语音Voice 一个操作组中的 10 个语音操作。10 voice actions in an action group. 另请参阅速率限制信息Also see the rate limiting information. 致电支持人员。Call support.
WebhookWebhook 一个操作组中的 10 个 webhook 操作。10 webhook actions in an action group. Webhook 调用最大数量为 1500 每分钟每个订阅。Maximum number of webhook calls is 1500 per minute per subscription. 其他限制目前特定于操作的信息Other limits are available at action-specific information. 致电支持人员。Call support.

通知中心限制Notification Hubs limits

Tier 免费Free 基本Basic 标准Standard
包括的推送数Included pushes 1 百万1 million 1 千万10 million 1 千万10 million
活动设备Active devices 500500 200,000200,000 1 千万10 million
每个安装或注册的标记配额Tag quota per installation or registration 6060 6060 6060

有关限制和定价的详细信息,请参阅通知中心定价For more information on limits and pricing, see Notification Hubs pricing.

事件中心限制Event Hubs limits

下表列出了特定于 Azure 事件中心的配额和限制。The following table lists quotas and limits specific to Azure Event Hubs. 有关事件中心定价的信息,请参阅事件中心定价For information about Event Hubs pricing, see Event Hubs pricing.

限制Limit 范围Scope 说明Notes Value
每个订阅的事件中心命名空间数Number of Event Hubs namespaces per subscription 订阅Subscription - 100100
每个命名空间的事件中心数Number of event hubs per namespace 命名空间Namespace 创建新事件中心的后续请求会被拒绝。Subsequent requests for creation of a new event hub are rejected. 1010
每个事件中心的分区数Number of partitions per event hub 实体Entity - 3232
每个事件中心的使用者组数Number of consumer groups per event hub 实体Entity - 2020
每个命名空间的 AMQP 连接数Number of AMQP connections per namespace 命名空间Namespace 系统会拒绝后续的附加连接请求,且调用代码会收到异常。Subsequent requests for additional connections are rejected, and an exception is received by the calling code. 5,0005,000
事件中心事件的最大大小Maximum size of Event Hubs event 实体Entity - 1 MB1 MB
事件中心名称的最大大小Maximum size of an event hub name 实体Entity - 50 个字符50 characters
每个使用者组的非 epoch 接收者数Number of non-epoch receivers per consumer group 实体Entity - 55
事件数据的最长保留期限Maximum retention period of event data 实体Entity - 1-7 天1-7 days
最大吞吐量单位Maximum throughput units 命名空间Namespace 超出吞吐量单位限制会导致数据受到限制,并生成服务器忙异常Exceeding the throughput unit limit causes your data to be throttled and generates a server busy exception. 若要请求更多的标准层的吞吐量单位,文件支持请求To request a larger number of throughput units for a Standard tier, file a support request. 额外的吞吐量单位将基于承诺的购买以大小为 20 个单位的块的形式提供。Additional throughput units are available in blocks of 20 on a committed purchase basis. 2020
每个命名空间的授权规则数量Number of authorization rules per namespace 命名空间Namespace 将拒绝后续的授权规则创建请求。Subsequent requests for authorization rule creation are rejected. 1212

服务总线限制Service Bus limits

下表列出了特定于 Azure 服务总线消息传送配额信息。The following table lists quota information specific to Azure Service Bus messaging. 有关定价的信息和其他服务总线配额,请参阅服务总线定价For information about pricing and other quotas for Service Bus, see Service Bus pricing.

配额名称Quota name 范围Scope 说明Notes Value
每个 Azure 订阅的基本或标准命名空间的最大数目Maximum number of Basic or Standard namespaces per Azure subscription 命名空间Namespace 通过 Azure 门户将拒绝更多基本或标准命名空间的后续请求。Subsequent requests for additional Basic or Standard namespaces are rejected by the Azure portal. 100100
每个 Azure 订阅的高级命名空间的最大数目Maximum number of Premium namespaces per Azure subscription 命名空间Namespace 更多高级命名空间的后续请求会被门户拒绝。Subsequent requests for additional Premium namespaces are rejected by the portal. 2525
队列或主题大小Queue or topic size 实体Entity 创建队列或主题时定义。Defined upon creation of the queue or topic.

将拒绝后续的传入消息,且调用代码会收到异常。Subsequent incoming messages are rejected, and an exception is received by the calling code.
1、2、3、4 GB 或 5 GB。1, 2, 3, 4 GB or 5 GB.

在高级 SKU,并使用标准 SKU分区启用,最大队列或主题大小是 80 GB。In the Premium SKU, and the Standard SKU with partitioning enabled, the maximum queue or topic size is 80 GB.
命名空间上的并发连接数Number of concurrent connections on a namespace 命名空间Namespace 系统会拒绝后续的附加连接请求,且调用代码会收到异常。Subsequent requests for additional connections are rejected, and an exception is received by the calling code. REST 操作不计入并发 TCP 连接。REST operations don't count toward concurrent TCP connections. NetMessaging:1,000.NetMessaging: 1,000.

AMQP:5,000.AMQP: 5,000.
并发接收队列、 主题或订阅实体上的请求数Number of concurrent receive requests on a queue, topic, or subscription entity 实体Entity 后续的接收请求被拒绝,并且调用代码会收到异常。Subsequent receive requests are rejected, and an exception is received by the calling code. 此配额适用于一个主题上所有订阅的并发接收操作总数。This quota applies to the combined number of concurrent receive operations across all subscriptions on a topic. 5,0005,000
每个命名空间的队列或主题的数量Number of topics or queues per namespace 命名空间Namespace 系统将拒绝后续的在命名空间中创建新主题或队列的请求。Subsequent requests for creation of a new topic or queue on the namespace are rejected. 因此,如果是通过 Azure 门户配置的,将生成错误消息。As a result, if configured through the Azure portal, an error message is generated. 如果是通过管理 API 调用的,调用代码将收到异常。If called from the management API, an exception is received by the calling code. 基本或标准层为 1000。1,000 for the Basic or Standard tier. 主题和队列的命名空间中的总数必须小于或等于 1,000。The total number of topics and queues in a namespace must be less than or equal to 1,000.

为高级层中,每个消息传送单元 (MU) 为 1000。For the Premium tier, 1,000 per messaging unit (MU). 最大限制为 4,000。Maximum limit is 4,000.
分区队列或主题每个命名空间Number of partitioned topics or queues per namespace 命名空间Namespace 系统将拒绝后续的在命名空间中创建新分区主题或队列的请求。Subsequent requests for creation of a new partitioned topic or queue on the namespace are rejected. 因此,如果是通过 Azure 门户配置的,将生成错误消息。As a result, if configured through the Azure portal, an error message is generated. 如果是通过管理 API,异常调用QuotaExceededException调用代码会收到。If called from the management API, the exception QuotaExceededException is received by the calling code. 基本和标准层:100。Basic and Standard tiers: 100.

中不受支持分区的实体高级层。Partitioned entities aren't supported in the Premium tier.

每个分区的队列或主题计入每个命名空间的 1,000 个实体的配额。Each partitioned queue or topic counts toward the quota of 1,000 entities per namespace.
任一消息实体路径的最大大小:队列或主题Maximum size of any messaging entity path: queue or topic 实体Entity - 260 个字符。260 characters.
任一消息实体名称的最大大小:命名空间、订阅或订阅规则Maximum size of any messaging entity name: namespace, subscription, or subscription rule 实体Entity - 50 个字符。50 characters.
消息 ID 的最大大小Maximum size of a message ID 实体Entity - 128128
最大消息大小会话 IDMaximum size of a message session ID 实体Entity - 128128
队列、 主题或订阅实体的消息大小Message size for a queue, topic, or subscription entity 实体Entity 将拒绝超过这些配额的传入消息,且调用代码会收到异常。Incoming messages that exceed these quotas are rejected, and an exception is received by the calling code. 最大消息大小:256 KB标准层,为 1MB高级层Maximum message size: 256 KB for Standard tier, 1 MB for Premium tier.

由于系统开销,此限制小于这些值。Due to system overhead, this limit is less than these values.

最大标头大小:64 KB。Maximum header size: 64 KB.

属性包中的标头属性的最大数目:字节/int。MaxValueMaximum number of header properties in property bag: byte/int.MaxValue.

属性包中属性的最大大小:没有明确限制。Maximum size of property in property bag: No explicit limit. 受最大标头大小限制。Limited by maximum header size.
消息队列、 主题或订阅实体的属性大小Message property size for a queue, topic, or subscription entity 实体Entity 异常SerializationException生成。The exception SerializationException is generated. 每个属性的最大消息属性大小为 32,000。Maximum message property size for each property is 32,000. 所有属性的累计大小不能超过 64000。Cumulative size of all properties can't exceed 64,000. 此限制适用于整个标头BrokeredMessage,其中具有用户属性和系统属性,如SequenceNumber标签,并且MessageIdThis limit applies to the entire header of the BrokeredMessage, which has both user properties and system properties, such as SequenceNumber, Label, and MessageId.
每个主题的订阅数Number of subscriptions per topic 实体Entity 系统将拒绝后续的为主题创建更多订阅的请求。Subsequent requests for creating additional subscriptions for the topic are rejected. 因此,如果是通过门户配置的,会显示错误消息。As a result, if configured through the portal, an error message is shown. 如果是通过管理 API 调用的,调用代码将收到异常。If called from the management API, an exception is received by the calling code. 标准层:每个订阅计入 1,000 个实体的配额,即队列、 主题和订阅,每个命名空间。Standard tier: Each subscription counts against the quota of 1,000 entities, that is, queues, topics, and subscriptions, per namespace.

高级层:2,000.Premium tier: 2,000.
每个主题的 SQL 筛选器数Number of SQL filters per topic 实体Entity 本主题的更多筛选器中创建的后续请求将拒绝,且调用代码会收到异常。Subsequent requests for creation of additional filters on the topic are rejected, and an exception is received by the calling code. 2,0002,000
每个主题的相关性筛选器数Number of correlation filters per topic 实体Entity 本主题的更多筛选器中创建的后续请求将拒绝,且调用代码会收到异常。Subsequent requests for creation of additional filters on the topic are rejected, and an exception is received by the calling code. 100,000100,000
SQL 筛选器或操作的大小Size of SQL filters or actions 命名空间Namespace 将拒绝更多筛选器中创建的后续请求,且调用代码会收到异常。Subsequent requests for creation of additional filters are rejected, and an exception is received by the calling code. 筛选器条件字符串的最大长度:1024 (1K)。Maximum length of filter condition string: 1,024 (1 K).

规则操作字符串的最大长度:1024 (1K)。Maximum length of rule action string: 1,024 (1 K).

每个规则操作的最大表达式数:32.Maximum number of expressions per rule action: 32.
每个命名空间、队列或主题的 SharedAccessAuthorizationRule 规则数Number of SharedAccessAuthorizationRule rules per namespace, queue, or topic 实体、命名空间Entity, namespace 将拒绝后续的创建附加规则请求,且调用代码会收到异常。Subsequent requests for creation of additional rules are rejected, and an exception is received by the calling code. 最大规则数:12.Maximum number of rules: 12.

在服务总线命名空间中配置的规则适用于该命名空间中的所有队列和主题。Rules that are configured on a Service Bus namespace apply to all queues and topics in that namespace.
每个事务的消息数Number of messages per transaction 事务Transaction 系统将拒绝其他传入消息,并收到如下异常消息"无法发送超过 100 个消息在单个事务中"时调用的代码。Additional incoming messages are rejected, and an exception stating "Cannot send more than 100 messages in a single transaction" is received by the calling code. 100100

适用于 Send() 和 SendAsync() 操作。For both Send() and SendAsync() operations.

IoT 中心限制IoT Hub limits

下表列出了与不同服务层 S1、 S2、 S3 和 F1 关联的限制。The following table lists the limits associated with the different service tiers S1, S2, S3, and F1. 有关每个成本有关的信息单元在每个层中,请参阅Azure IoT 中心定价For information about the cost of each unit in each tier, see Azure IoT Hub pricing.

资源Resource S1 标准S1 Standard S2 标准S2 Standard S3 标准S3 Standard F1 免费F1 Free
消息/天Messages/day 400,000400,000 6,000,0006,000,000 300,000,000300,000,000 8,0008,000
最大单位数Maximum units 200200 200200 1010 1

备注

如果希望在 S1 或 S2 层的中心使用 200 多个单位,或者在 S3 层的中心使用 10 个单位,请联系 Microsoft 支持部门。If you anticipate using more than 200 units with an S1 or S2 tier hub or 10 units with an S3 tier hub, contact Microsoft Support.

下表列出了适用于 IoT 中心资源的限制。The following table lists the limits that apply to IoT Hub resources.

资源Resource 限制Limit
每个 Azure 订阅的付费 IoT 中心数上限Maximum paid IoT hubs per Azure subscription 5050
每个 Azure 订阅的免费 IoT 中心数上限Maximum free IoT hubs per Azure subscription 1
设备 ID 的最大字符数Maximum number of characters in a device ID 128128
设备标识的最大数目Maximum number of device identities
在单个调用中返回returned in a single call
1,0001,000
IoT 中心消息的设备到云消息的最长保留期IoT Hub message maximum retention for device-to-cloud messages 7 天7 days
设备到云消息的最大大小Maximum size of device-to-cloud message 256 KB256 KB
设备到云消息批的最大大小Maximum size of device-to-cloud batch AMQP 和 HTTP:整个批为 256 KBAMQP and HTTP: 256 KB for the entire batch
MQTT:每条消息为 256 KBMQTT: 256 KB for each message
设备到云消息批中的消息数上限Maximum messages in device-to-cloud batch 500500
云到设备的消息数上限Maximum size of cloud-to-device message 64 KB64 KB
云到设备消息的最大 TTLMaximum TTL for cloud-to-device messages 2 天2 days
云到设备消息的最大传送计数Maximum delivery count for cloud-to-device
计数messages
100100
反馈消息的最大传送计数Maximum delivery count for feedback messages
(响应云到设备消息时)in response to a cloud-to-device message
100100
反馈消息的最大 TTLMaximum TTL for feedback messages in
(响应云到设备消息时)response to a cloud-to-device message
2 天2 days
设备孪生的最大大小Maximum size of device twin
(标记、报告的属性和所需属性)(tags, reported properties, and desired properties)
8 KB8 KB
设备孪生字符串值的最大大小Maximum size of device twin string value 4 KB4 KB
设备孪生中对象的最大深度Maximum depth of object in device twin 55
直接方法有效负载的最大大小Maximum size of direct method payload 128 KB128 KB
作业历史记录最长保留期Job history maximum retention 30 天30 days
最大并发作业数Maximum concurrent jobs 10(适用于 S3)、5(适用于 S2)、1(适用于 S1)10 (for S3), 5 for (S2), 1 (for S1)
额外终结点最大数目Maximum additional endpoints 10(适用于 S1、S2、S3)10 (for S1, S2, and S3)
最大消息路由规则数Maximum message routing rules 100(适用于 S1、S2、S3)100 (for S1, S2, and S3)
最大并发连接设备流数Maximum number of concurrently connected device streams 50(仅适用于 S1、S2、S3 和 F1)50 (for S1, S2, S3, and F1 only)
最大设备流数据传输Maximum device stream data transfer 300 MB/天(仅适用于 S1、S2、S3 和 F1)300 MB per day (for S1, S2, S3, and F1 only)

备注

如果需要 50 多个 Azure 订阅中的付费的 IoT 中心,请联系 Microsoft 支持部门。If you need more than 50 paid IoT hubs in an Azure subscription, contact Microsoft Support.

备注

目前,可以连接到单个 IoT 中心的设备的最大数目是 1,000,000。Currently, the maximum number of devices you can connect to a single IoT hub is 1,000,000. 如果想要增加此限制,请联系 Microsoft 支持If you want to increase this limit, contact Microsoft Support.

超过以下配额时,IoT 中心将限制请求。IoT Hub throttles requests when the following quotas are exceeded.

限制Throttle 每个中心的值Per-hub value
标识注册表操作Identity registry operations
(创建、检索、列出、更新、删除);(create, retrieve, list, update, and delete),
单个或批量导入/导出individual or bulk import/export
83.33/秒/单位(5,000/分钟/单位)(适用于 S3)。83.33/sec/unit (5,000/min/unit) (for S3).
1.67/秒/单位(100/分钟/单位)(适用于 S1 和 S2)。1.67/sec/unit (100/min/unit) (for S1 and S2).
设备连接Device connections 6,000/秒/单位(适用于 S3),120/秒/单位(适用于 S2),12/秒/单位(适用于 S1)。6,000/sec/unit (for S3), 120/sec/unit (for S2), 12/sec/unit (for S1).
最小值为 100/秒。Minimum of 100/sec.
设备到云的发送Device-to-cloud sends 6,000/秒/单位(适用于 S3),120/秒/单位(适用于 S2),12/秒/单位(适用于 S1)。6,000/sec/unit (for S3), 120/sec/unit (for S2), 12/sec/unit (for S1).
最小值为 100/秒。Minimum of 100/sec.
云到设备的发送Cloud-to-device sends 83.33/秒/单位(5,000/分钟/单位)(适用于 S3),1.67/秒/单位(100/分钟/单位)(适用于 S1 和 S2)。83.33/sec/unit (5,000/min/unit) (for S3), 1.67/sec/unit (100/min/unit) (for S1 and S2).
云到设备的接收Cloud-to-device receives 833.33/秒/单位(50,000/分钟/单位)(适用于 S3),16.67/秒/单位(1,000/分钟/单位)(适用于 S1 和 S2)。833.33/sec/unit (50,000/min/unit) (for S3), 16.67/sec/unit (1,000/min/unit) (for S1 and S2).
文件上传操作File upload operations 83.33 个文件上传通知/秒/单位(5,000/分钟/单位)(适用于 S3),1.67 个文件上传通知/秒/单位(100/分钟/单位)(适用于 S1 和 S2)。83.33 file upload notifications/sec/unit (5,000/min/unit) (for S3), 1.67 file upload notifications/sec/unit (100/min/unit) (for S1 and S2).
Azure 存储帐户一次可传出 10,000 个 SAS URI。10,000 SAS URIs can be out for an Azure Storage account at one time.
一次可传出 10 个 SAS URI/设备。10 SAS URIs/device can be out at one time.
直接方法Direct methods 24 MB/秒/单位(适用于 S3),480 KB/秒/单位(适用于 S2),160 KB/秒/单位(适用于 S1)。24 MB/sec/unit (for S3), 480 KB/sec/unit (for S2), 160 KB/sec/unit (for S1).
基于 8-KB 限制计量大小。Based on 8-KB throttling meter size.
设备孪生读取Device twin reads 500/秒/单位(适用于 S3),最大为 100/秒或 10/秒/单位(适用于 S2),100/秒(适用于 S1)500/sec/unit (for S3), Maximum of 100/sec or 10/sec/unit (for S2), 100/sec (for S1)
设备孪生更新Device twin updates 250/秒/单位(适用于 S3),最大为 50/秒或 5/秒/单位(适用于 S2),50/秒(适用于 S1)250/sec/unit (for S3), Maximum of 50/sec or 5/sec/unit (for S2), 50/sec (for S1)
作业操作Jobs operations
(创建、更新、列表、删除)(create, update, list, and delete)
83.33/秒/单位(5,000/分钟/单位)(适用于 S3),1.67/秒/单位(100/分钟/单位)(适用于 S2),1.67/秒/单位(100/分钟/单位)(适用于 S1)。83.33/sec/unit (5,000/min/unit) (for S3), 1.67/sec/unit (100/min/unit) (for S2), 1.67/sec/unit (100/min/unit) (for S1).
作业每设备操作吞吐量Jobs per-device operation throughput 50/秒/单位(适用于 S3),最大为 10/秒或 1/秒/单位(适用于 S2),10/秒(适用于 S1)。50/sec/unit (for S3), maximum of 10/sec or 1/sec/unit (for S2), 10/sec (for S1).
设备流启动率Device stream initiation rate 5 个新流/秒(仅适用于 S1、S2、S3 和 F1)。5 new streams/sec (for S1, S2, S3, and F1 only).

IoT 中心设备预配服务限制IoT Hub Device Provisioning Service limits

下表列出了适用于 Azure IoT 中心设备预配服务资源的限制。The following table lists the limits that apply to Azure IoT Hub Device Provisioning Service resources.

资源Resource 限制Limit
每个 Azure 订阅的最大设备预配服务数Maximum device provisioning services per Azure subscription 1010
最大登记数Maximum number of enrollments 1,000,0001,000,000
最大注册数Maximum number of registrations 1,000,0001,000,000
最大登记组数Maximum number of enrollment groups 100100
最大 CA 数Maximum number of CAs 2525

备注

若要增加订阅中的实例数目,请联系Microsoft 支持部门To increase the number of instances in your subscription, contact Microsoft Support.

备注

若要增加数目注册和预配服务上的注册,请联系Microsoft 支持部门To increase the number of enrollments and registrations on your provisioning service, contact Microsoft Support.

超过以下配额时,设备预配服务将限制请求。The Device Provisioning Service throttles requests when the following quotas are exceeded.

限制Throttle 每单位值Per-unit value
操作Operations 200/分钟/服务200/min/service
设备注册数Device registrations 200/分钟/服务200/min/service
设备轮询操作Device polling operation 5/10 秒/设备5/10 sec/device

数据工厂限制Data Factory limits

Azure 数据工厂是一个具有以下默认限制到位,以确保客户订阅不会受到彼此工作负荷的多租户服务。Azure Data Factory is a multitenant service that has the following default limits in place to make sure customer subscriptions are protected from each other's workloads. 若要将提升到你的订阅的最大限制,请联系支持。To raise the limits up to the maximum for your subscription, contact support.

版本 2Version 2

资源Resource 默认限制Default limit 最大限制Maximum limit
Azure 订阅中的数据工厂Data factories in an Azure subscription 5050 联系支持人员Contact support.
实体,例如管道、 数据集、 触发器、 链接的服务和集成运行时,数据工厂中的总数Total number of entities, such as pipelines, data sets, triggers, linked services, and integration runtimes, within a data factory 5,0005,000 联系支持人员Contact support.
Azure SSIS 集成运行时的一个订阅下的总 CPU 内核Total CPU cores for Azure-SSIS Integration Runtimes under one subscription 256256 联系支持人员Contact support.
每在工厂中的所有管道之间共享的数据工厂的并行管道运行Concurrent pipeline runs per data factory that's shared among all pipelines in the factory 10,00010,000 联系支持人员Contact support.
每个管道,其中包括用于容器的内部活动的最大活动Maximum activities per pipeline, which includes inner activities for containers 4040 4040
可以针对单个自承载的集成运行时创建的链接的集成运行时的最大数目Maximum number of linked integration runtimes that can be created against a single self-hosted integration runtime 100100 联系支持人员Contact support.
每个管道的最大参数Maximum parameters per pipeline 5050 5050
ForEach 项ForEach items 100,000100,000 100,000100,000
ForEach 并行度ForEach parallelism 2020 5050
每个表达式的字符数Characters per expression 8,1928,192 8,1928,192
最小的翻转窗口触发器间隔Minimum tumbling window trigger interval 15 分钟15 min 15 分钟15 min
最大超时为管道活动运行Maximum timeout for pipeline activity runs 7 天7 days 7 天7 days
每个管道对象的对象的字节1Bytes per object for pipeline objects1 200 KB200 KB 200 KB200 KB
每个数据集的对象和链接的服务对象的字节数1Bytes per object for dataset and linked service objects1 100 KB100 KB 2,000 KB2,000 KB
每个复制活动运行的数据集成单位3Data integration units per copy activity run3 256256 联系支持人员Contact support.
编写 API 调用Write API calls 2500/h2,500/h

此限制是由 Azure 资源管理器而不是 Azure 数据工厂所强加的。This limit is imposed by Azure Resource Manager, not Azure Data Factory.
联系支持人员Contact support.
读取 API 调用Read API calls 12500/h12,500/h

此限制是由 Azure 资源管理器而不是 Azure 数据工厂所强加的。This limit is imposed by Azure Resource Manager, not Azure Data Factory.
联系支持人员Contact support.
每分钟监视的查询数Monitoring queries per minute 1,0001,000 联系支持人员Contact support.
每分钟的实体 CRUD 操作数Entity CRUD operations per minute 5050 联系支持人员Contact support.

版本 1Version 1

资源Resource 默认限制Default limit 最大限制Maximum limit
Azure 订阅中的数据工厂Data factories in an Azure subscription 5050 联系支持人员Contact support.
数据工厂中的管道Pipelines within a data factory 2,5002,500 联系支持人员Contact support.
数据工厂中的数据集Data sets within a data factory 5,0005,000 联系支持人员Contact support.
每个数据集的并发切片数Concurrent slices per data set 1010 1010
每个管道对象的对象的字节1Bytes per object for pipeline objects1 200 KB200 KB 200 KB200 KB
每个对象的数据的字节集和链接服务对象1Bytes per object for data set and linked service objects1 100 KB100 KB 2,000 KB2,000 KB
在订阅中的 azure HDInsight 按需群集核心2Azure HDInsight on-demand cluster cores within a subscription2 6060 联系支持人员Contact support.
云数据移动单位,每个复制活动运行3Cloud data movement units per copy activity run3 3232 联系支持人员Contact support.
管道活动运行的重试次数Retry count for pipeline activity runs 1,0001,000 MaxInt(32 位)MaxInt (32 bit)

1管道、 数据集和链接的服务对象表示工作负荷的逻辑分组。1Pipeline, data set, and linked service objects represent a logical grouping of your workload. 这些对象的限制不相关的使用 Azure 数据工厂可以移动和处理的数据量。Limits for these objects don't relate to the amount of data you can move and process with Azure Data Factory. 数据工厂可进行扩展以处理千万亿字节的数据。Data Factory is designed to scale to handle petabytes of data.

2 按需 HDInsight 核心数从包含数据工厂的订阅中分配。2On-demand HDInsight cores are allocated out of the subscription that contains the data factory. 因此,以前的限制是针对按需 HDInsight 核心强制数据工厂执行核心数限制。As a result, the previous limit is the Data Factory-enforced core limit for on-demand HDInsight cores. 它是不同于与你的 Azure 订阅相关联的核心限制。It's different from the core limit that's associated with your Azure subscription.

3云到云复制操作中使用的数据集成单位 (DIU) 版本 2 或版本 1 的云数据移动单位 (DMU)。3The data integration unit (DIU) for version 2 or the cloud data movement unit (DMU) for version 1 is used in a cloud-to-cloud copy operation. 它是度量值,代表单个单位在数据工厂的能力。It's a measure that represents the power of a single unit in Data Factory. 它结合了 CPU、 内存和网络资源分配。It combines the CPU, memory, and network resource allocations. 就某些方案来说,使用更多 DMU 可以提高复制吞吐量。You can achieve higher copy throughput by using more DMUs for some scenarios. 有关详细信息,请参阅数据集成单位 (第 2 版)云数据移动单位 (版本 1)For more information, see Data integration units (version 2) and Cloud data movement units (version 1). 有关计费的更多信息,请参阅Azure 数据工厂定价For information on billing, see Azure Data Factory pricing.

4integration runtime (IR) 是 Azure 数据工厂用于在不同的网络环境中,数据移动、 调度活动来计算服务,如之间提供数据集成功能的计算基础结构和SSIS 包的执行。4The integration runtime (IR) is the compute infrastructure used by Azure Data Factory to provide data integration capabilities across different network environments, such as data movement, dispatching activities to compute services, and execution of SSIS packages. 有关详细信息,请参阅集成运行时概述For more information, see Integration runtime overview.

资源Resource 默认下限Default lower limit 最小限制Minimum limit
计划间隔Scheduling interval 15 分钟15 minutes 15 分钟15 minutes
重试尝试之间的间隔Interval between retry attempts 1 秒1 second 1 秒1 second
重试超时值Retry timeout value 1 秒1 second 1 秒1 second

Web 服务调用限制Web service call limits

Azure 资源管理器限制 API 调用。Azure Resource Manager has limits for API calls. 可以根据 Azure 资源管理器 API 限制中规定的频率执行 API 调用。You can make API calls at a rate within the Azure Resource Manager API limits.

Data Lake Analytics 限制Data Lake Analytics limits

Azure Data Lake Analytics 让管理分布式基础结构和简单的复杂代码等复杂任务。Azure Data Lake Analytics makes the complex task of managing distributed infrastructure and complex code easy. 动态预配资源,并可用来进行分析百亿亿字节的数据。It dynamically provisions resources, and you can use it to do analytics on exabytes of data. 作业完成后,它自动释放资源。When the job completes, it winds down resources automatically. 您只需支付所用的处理能力。You pay only for the processing power that was used. 增加或减少存储数据的大小或使用的计算量时,不需要重写代码。As you increase or decrease the size of data stored or the amount of compute used, you don’t have to rewrite code. 若要将你的订阅的默认限制,请联系支持。To raise the default limits for your subscription, contact support.

资源Resource 默认限制Default limit 注释Comments
最大并发作业数Maximum number of concurrent jobs 2020
最大分析单位 (Au) 每个帐户数Maximum number of analytics units (AUs) per account 250250 使用 AU 的任意组合,在 20 个作业中的 AU 最大可以为 250。Use any combination of up to a maximum of 250 AUs across 20 jobs. 若要增加此限制,请联系 Microsoft 支持部门。To increase this limit, contact Microsoft Support.
提交作业时的最大脚本大小Maximum script size for job submission 3 MB3 MB
每个区域每个订阅的 Data Lake Analytics 帐户的最大数目Maximum number of Data Lake Analytics accounts per region per subscription 55 若要增加此限制,请联系 Microsoft 支持部门。To increase this limit, contact Microsoft Support.

Data Lake Store 限制Data Lake Store limits

Azure Data Lake Storage Gen1 是一个企业范围的超大规模存储库,适用于大数据分析工作负载。Azure Data Lake Storage Gen1 is an enterprise-wide hyper-scale repository for big data analytic workloads. 数据湖存储 Gen1 可用于捕获在单个位置进行操作和探索性分析任何大小、 类型和引入速度的数据。You can use Data Lake Storage Gen1 to capture data of any size, type, and ingestion speed in one single place for operational and exploratory analytics. 可以在数据湖存储 Gen1 帐户中存储的数据量没有限制。There's no limit to the amount of data you can store in a Data Lake Storage Gen1 account.

资源Resource 默认限制Default limit 注释Comments
数据湖存储 Gen1 帐户,每个订阅,每个区域最大数量Maximum number of Data Lake Storage Gen1 accounts, per subscription, per region 1010 若要请求增加此限制,请联系支持。To request an increase for this limit, contact support.
每个文件或文件夹的访问 Acl,最大数目Maximum number of access ACLs, per file or folder 3232 这是硬性限制。This is a hard limit. 使用组来管理更少项的访问权限。Use groups to manage access with fewer entries.
默认 Acl,每个文件或文件夹的最大数目Maximum number of default ACLs, per file or folder 3232 这是硬性限制。This is a hard limit. 使用组来管理更少项的访问权限。Use groups to manage access with fewer entries.

数据库迁移服务限制Database Migration Service Limits

Azure 数据库迁移服务是完全托管的服务,旨在实现从多个数据库源到 Azure 数据平台停机时间最短的无缝迁移。Azure Database Migration Service is a fully managed service designed to enable seamless migrations from multiple database sources to Azure data platforms with minimal downtime.

资源Resource 默认限制Default limit 注释Comments
每个区域每个订阅的最大服务数Maximum number of services per subscription, per region 22 若要请求增加此限制,请联系支持。To request an increase for this limit, contact support.

流分析限制Stream Analytics limits


限制标识符Limit identifier 限制Limit 注释Comments
每个订阅每个区域的流式处理单位的最大数目Maximum number of streaming units per subscription per region 200200 若要请求增加流式处理单位数超过 200 订阅,请联系Microsoft 支持部门To request an increase in streaming units for your subscription beyond 200, contact Microsoft Support.
每个作业的最大输入数目Maximum number of inputs per job 6060 不存在 60 个输入每个 Azure Stream Analytics 作业硬限制。There's a hard limit of 60 inputs per Azure Stream Analytics job.
每个作业的最大输出数目Maximum number of outputs per job 6060 没有 60 每个 Stream Analytics 作业输出的硬性限制。There's a hard limit of 60 outputs per Stream Analytics job.
每个作业的最大函数数目Maximum number of functions per job 6060 没有每个 Stream Analytics 作业 60 函数的硬性限制。There's a hard limit of 60 functions per Stream Analytics job.
每个作业的流式处理单位的最大数目Maximum number of streaming units per job 120120 没有每个 Stream Analytics 作业 120 流式处理单位的硬性限制。There's a hard limit of 120 streaming units per Stream Analytics job.
每个区域的最大作业数目Maximum number of jobs per region 1,5001,500 每个地理区域,每个订阅可以有最多包含 1,500 位作业。Each subscription can have up to 1,500 jobs per geographical region.
引用数据 blob MBReference data blob MB 300300 引用数据 blob 不能为大于 300 MB。Reference data blobs can't be larger than 300 MB each.

Active Directory 限制Active Directory limits

下面是 Azure Active Directory (Azure AD) 服务的使用限制和其他服务限制。Here are the usage constraints and other service limits for the Azure Active Directory (Azure AD) service.

类别Category 限制Limits
目录Directories 单个用户最多可以是 500 个 Azure AD 目录的成员或来宾。A single user can belong to a maximum of 500 Azure AD directories as a member or a guest.
单个用户最多可以创建 20 个目录。A single user can create a maximum of 20 directories.
Domains 可以添加不超过 900 个的托管域名。You can add no more than 900 managed domain names. 如果将所有域设置为与本地 Active Directory 联合,则可在每个目录中添加不超过 450 个域名。If you set up all of your domains for federation with on-premises Active Directory, you can add no more than 450 domain names in each directory.
对象Objects
  • Azure Active Directory 免费版用户最多可以在单个目录中创建 500,000 个对象。A maximum of 500,000 objects can be created in a single directory by users of the Free edition of Azure Active Directory.
  • 非管理员用户最多可以创建 250 个对象。A non-admin user can create no more than 250 objects. 活动的对象以及已删除但可用于还原的对象都会计入此配额中。Both active objects and deleted objects that are available to restore count toward this quota. 只有那些已删除但删除的时间不到 30 天的对象可以用来还原。Only deleted objects that were deleted fewer than 30 days ago are available to restore. 在 30 天的时间内,已删除且不再能够用来还原的对象在计入此配额时,其值按四分之一计算。Deleted objects that are no longer available to restore count toward this quota at a value of one-quarter for 30 days. 也许可以向那些可能会在执行日常任务的过程中反复超过此配额的非管理员用户分配管理员角色Perhaps assign an administrator role to non-admin users who are likely to repeatedly exceed this quota in the course of their regular duties.
架构扩展Schema extensions
  • 字符串类型扩展最多只能有 256 个字符。String-type extensions can have a maximum of 256 characters.
  • 二进制类型扩展限制在 256 字节以内。Binary-type extensions are limited to 256 bytes.
  • 只能将 100 个扩展值(包括所有类型和所有应用程序)写入到任何单一对象中。Only 100 extension values, across all types and all applications, can be written to any single object.
  • 仅“用户”、“组”、“TenantDetail”、“设备”、“应用程序”和“ServicePrincipal”实体可以用字符串类型或二进制类型单一值属性进行扩展。Only User, Group, TenantDetail, Device, Application, and ServicePrincipal entities can be extended with string-type or binary-type single-valued attributes.
  • 架构扩展仅在 Graph API 1.21 预览版中可用。Schema extensions are available only in the Graph API version 1.21 preview. 必须授予应用程序编写访问注册扩展的权限。The application must be granted write access to register an extension.
应用程序Applications 最多有 100 位用户可以是单一应用程序的所有者。A maximum of 100 users can be owners of a single application.
Groups
  • 最多有 100 位用户可以是单一组的所有者。A maximum of 100 users can be owners of a single group.
  • 任意数量的对象都可以是单个组的成员。Any number of objects can be members of a single group.
  • 一个用户可以是任意数量的组的成员。A user can be a member of any number of groups.
  • 使用 Azure AD Connect 时,一个小组中从本地 Active Directory 同步到 Azure Active Directory 的成员数目仅限 50,000。The number of members in a group that you can synchronize from your on-premises Active Directory to Azure Active Directory by using Azure AD Connect is limited to 50,000 members.
访问面板Access Panel
  • 对于可以在访问面板中按用户查看的应用程序,其数量没有限制。There's no limit to the number of applications that can be seen in the Access Panel per user. 这适用于 Azure AD Premium 或企业移动性套件的用户分配许可证。This applies to users assigned licenses for Azure AD Premium or the Enterprise Mobility Suite.
  • 每位用户最多可以在访问面板中看到 10 个应用磁贴。A maximum of 10 app tiles can be seen in the Access Panel for each user. 此限制适用于获得免费版或 Azure AD 基本版 Azure Active Directory 许可证的用户。This limit applies to users who are assigned licenses for Free or Azure AD Basic editions of Azure Active Directory. Box、Salesforce、Dropbox 都是应用磁贴的示例。Examples of app tiles include Box, Salesforce, or Dropbox. 此限制不适用于管理员帐户。This limit doesn't apply to administrator accounts.
报告Reports 在报告中最多可查看或下载 1,000 行。A maximum of 1,000 rows can be viewed or downloaded in any report. 系统会截断其他任何数据。Any additional data is truncated.
管理单元Administrative units 对象可以是不超过 30 个管理单位的成员。An object can be a member of no more than 30 administrative units.
管理员角色和权限Admin roles and permissions
  • 无法将组添加为所有者。A group can't be added as an owner.
  • 无法将组分配给角色。A group can't be assigned to a role.
  • 无法更改租户开关(Azure AD 中的用户设置)之外的默认用户权限。Default user permissions can't be changed except for tenant switches, which are user settings in Azure AD.
  • 事件网格限制Event Grid limits

    以下限制适用于 Azure 事件网格系统主题和自定义主题事件域。The following limits apply to Azure Event Grid system topics and custom topics, not event domains.

    资源Resource 限制Limit
    每个 Azure 订阅的自定义主题数Custom topics per Azure subscription 100100
    每个主题的事件订阅数Event subscriptions per topic 500500
    自定义主题的发布速率(入口)Publish rate for a custom topic (ingress) 每个主题每秒 5,000 个事件5,000 events per second per topic

    以下限制适用于事件的域。The following limits apply to event domains only.

    资源Resource 限制Limit
    每个事件域的主题Topics per event domain 公开预览期间为 1,000 个1,000 during public preview
    每个域中的主题的事件订阅Event subscriptions per topic within a domain 公开预览期间为 50 个50 during public preview
    域作用域的事件订阅Domain scope event subscriptions 公开预览期间为 50 个50 during public preview
    发布事件域 (入口) 的速率Publish rate for an event domain (ingress) 公开预览期间为每秒 5,000 个事件5,000 events per second during public preview

    Azure Maps 限制Azure Maps limits

    下表显示了 Azure Maps S0 定价层的使用情况限制。The following table shows the usage limit for the Azure Maps S0 pricing tier. 使用限制取决于定价层。Usage limit depends on the pricing tier.

    资源Resource S0 定价层限制S0 pricing tier limit
    每个订阅的最大请求速率Maximum request rate per subscription 每秒 50 个请求50 requests per second

    下表显示了 Azure Maps 的数据大小限制。The following table shows the data size limit for Azure Maps. Azure Maps 数据服务将仅位于 S1 定价层。The Azure Maps data service is available only at the S1 pricing tier.

    资源Resource 限制Limit
    数据的最大大小Maximum size of data 50 MB50 MB

    有关定价层 Azure Maps 的详细信息,请参阅Azure Maps 定价For more information on the Azure Maps pricing tiers, see Azure Maps pricing.

    Azure Policy 限制Azure Policy limits

    没有 Azure 策略的每个对象类型的最大计数。There's a maximum count for each object type for Azure Policy. _作用域_条目是指订阅或管理组An entry of Scope means either the subscription or the management group.

    其中Where 对象What 最大计数Maximum count
    范围Scope 策略定义Policy definitions 250250
    范围Scope 计划定义Initiative definitions 100100
    租户Tenant 计划定义Initiative definitions 1,0001,000
    范围Scope 策略或计划分配Policy or initiative assignments 100100
    策略定义Policy definition parametersParameters 2020
    计划定义Initiative definition 策略Policies 100100
    计划定义Initiative definition parametersParameters 100100
    策略或计划分配Policy or initiative assignments 排除项 (notScopes)Exclusions (notScopes) 250250
    策略规则Policy rule 嵌套的条件语句Nested conditionals 512512

    StorSimple 系统限制StorSimple System limits

    限制标识符Limit identifier 限制Limit 注释Comments
    存储帐户凭据的最大数目Maximum number of storage account credentials 6464
    卷容器的最大数目Maximum number of volume containers 6464
    队列的最大数目Maximum number of volumes 255255
    每个带宽模板的最大计划数Maximum number of schedules per bandwidth template 168168 计划每隔一小时,每个日期是星期几。A schedule for every hour, every day of the week.
    物理设备上分层卷的大小上限Maximum size of a tiered volume on physical devices StorSimple 8100 和 StorSimple 8600 的 64 TB64 TB for StorSimple 8100 and StorSimple 8600 StorSimple 8100 和 StorSimple 8600 是物理设备。StorSimple 8100 and StorSimple 8600 are physical devices.
    Azure 中虚拟设备上的分层卷的大小上限Maximum size of a tiered volume on virtual devices in Azure 30 TB for StorSimple 801030 TB for StorSimple 8010
    64 TB for StorSimple 802064 TB for StorSimple 8020
    StorSimple 8010 和 StorSimple 8020 是分别使用标准存储和高级存储的虚拟设备在 Azure 中。StorSimple 8010 and StorSimple 8020 are virtual devices in Azure that use Standard storage and Premium storage, respectively.
    物理设备上本地固定卷的大小上限Maximum size of a locally pinned volume on physical devices 9 TB for StorSimple 81009 TB for StorSimple 8100
    24 TB for StorSimple 860024 TB for StorSimple 8600
    StorSimple 8100 和 StorSimple 8600 是物理设备。StorSimple 8100 and StorSimple 8600 are physical devices.
    iSCSI 连接的最大数目Maximum number of iSCSI connections 512512
    来自发起程序的 iSCSI 连接的最大数目Maximum number of iSCSI connections from initiators 512512
    每个设备的访问控制记录的最大数目Maximum number of access control records per device 6464
    每个备份策略的卷的最大数目Maximum number of volumes per backup policy 2424
    每个备份策略保留的备份的最大数目Maximum number of backups retained per backup policy 6464
    每个备份策略的最大计划数Maximum number of schedules per backup policy 1010
    每个卷可保留的任何类型快照的最大数目Maximum number of snapshots of any type that can be retained per volume 256256 此数量包括本地快照和云快照。This amount includes local snapshots and cloud snapshots.
    任何设备中可以存在的快照的最大数目Maximum number of snapshots that can be present in any device 10,00010,000
    可以并行处理以实现备份、还原或克隆的卷的最大数目Maximum number of volumes that can be processed in parallel for backup, restore, or clone 1616
    • 如果有超过 16 个卷,它们是依序处理处理槽可用。If there are more than 16 volumes, they're processed sequentially as processing slots become available.
    • 在完成操作之前,不会发生新的克隆的备份或还原的分层的卷。New backups of a cloned or a restored tiered volume can't occur until the operation is finished. 对于本地卷,卷处于联机状态后可以备份。For a local volume, backups are allowed after the volume is online.
    分层卷的还原和克隆恢复时间Restore and clone recover time for tiered volumes < 2 分钟<2 minutes
    • 卷完成后还原或克隆操作,而不考虑卷大小的 2 分钟内可用。The volume is made available within 2 minutes of a restore or clone operation, regardless of the volume size.
    • 卷性能一开始可能比正常的因为大部分数据和元数据仍驻留在云中慢。The volume performance might initially be slower than normal as most of the data and metadata still resides in the cloud. 为数据流从云到 StorSimple 设备可能会改善性能。Performance might increase as data flows from the cloud to the StorSimple device.
    • 下载元数据的总时间取决于分配的卷大小。The total time to download metadata depends on the allocated volume size. 在后台,元数据会自动以 5 分钟 1 TB 已分配卷数据的速率载入设备中。Metadata is automatically brought into the device in the background at the rate of 5 minutes per TB of allocated volume data. 此速率可能受到云的 Internet 带宽。This rate might be affected by Internet bandwidth to the cloud.
    • 当所有元数据都位于设备上时,还原或克隆操作即告完成。The restore or clone operation is complete when all the metadata is on the device.
    • 不能执行备份操作,直到还原或克隆操作完全完成。Backup operations can't be performed until the restore or clone operation is fully complete.
    本地固定卷的还原恢复时间Restore recover time for locally pinned volumes < 2 分钟<2 minutes
    • 卷在完成还原操作后的 2 分钟内可用,无论卷大小如何。The volume is made available within 2 minutes of the restore operation, regardless of the volume size.
    • 卷性能一开始可能比正常的因为大部分数据和元数据仍驻留在云中慢。The volume performance might initially be slower than normal as most of the data and metadata still resides in the cloud. 为数据流从云到 StorSimple 设备可能会改善性能。Performance might increase as data flows from the cloud to the StorSimple device.
    • 下载元数据的总时间取决于分配的卷大小。The total time to download metadata depends on the allocated volume size. 在后台,元数据会自动以 5 分钟 1 TB 已分配卷数据的速率载入设备中。Metadata is automatically brought into the device in the background at the rate of 5 minutes per TB of allocated volume data. 此速率可能受到云的 Internet 带宽。This rate might be affected by Internet bandwidth to the cloud.
    • 与分层卷不同如果有本地固定的卷,卷数据也会下载本地设备上。Unlike tiered volumes, if there are locally pinned volumes, the volume data is also downloaded locally on the device. 将所有卷数据下载到设备后,还原操作即告完成。The restore operation is complete when all the volume data has been brought to the device.
    • 还原操作可能很费时,完成还原的总时间取决于预配本地卷、 Internet 带宽和设备上的现有数据的大小。The restore operations might be long and the total time to complete the restore will depend on the size of the provisioned local volume, your Internet bandwidth, and the existing data on the device. 在还原操作过程中,允许在本地固定卷上进行备份操作。Backup operations on the locally pinned volume are allowed while the restore operation is in progress.
    精简还原可用性Thin-restore availability 上次故障转移Last failover
    最大客户端读取/写入吞吐量,从 SSD 层 * 提供服务时Maximum client read/write throughput, when served from the SSD tier* 单一 10 吉比特以太网网络接口使用 920/720 MB/秒920/720 MB/sec with a single 10-gigabit Ethernet network interface 使用 MPIO 和两个网络接口的最多两次。Up to two times with MPIO and two network interfaces.
    最大客户端读取/写入吞吐量,从 HDD 层 * 提供服务时Maximum client read/write throughput, when served from the HDD tier* 120/250 MB/秒120/250 MB/sec
    最大客户端读取/写入吞吐量,从云层 * 提供服务时Maximum client read/write throughput, when served from the cloud tier* 11/41 MB/秒11/41 MB/sec 读取吞吐量取决于生成和维护足够的 I/O 队列深度的客户端。Read throughput depends on clients generating and maintaining sufficient I/O queue depth.

    *每个 I/O 类型的最大吞吐量使用 100%读取方案和 100%写入方案进行测量。*Maximum throughput per I/O type was measured with 100 percent read and 100 percent write scenarios. 实际吞吐量可能会较低,取决于 I/O 混用和网络条件。Actual throughput might be lower and depends on I/O mix and network conditions.

    Log Analytics 限制Log Analytics limits

    以下限制适用于每个订阅的 Azure Log Analytics 资源。The following limits apply to Azure Log Analytics resources per subscription.

    资源Resource 默认限制Default limit 注释Comments
    每个订阅的免费工作区数目Number of free workspaces per subscription 1010 不能增加此限制。This limit can't be increased.
    每个订阅的付费工作区数目Number of paid workspaces per subscription 不适用N/A 限制是资源组中的资源数和每个订阅的资源组的数目。You're limited by the number of resources within a resource group and the number of resource groups per subscription.

    备注

    截至 2018 年 4 月 2 日,新的订阅中的新工作区自动使用每个 GB定价计划。As of April 2, 2018, new workspaces in a new subscription automatically use the Per GB pricing plan. 对于在 4 月 2 日之前创建的现有订阅或绑定到现有企业协议注册的订阅,可以继续从新的工作区的三个定价层中进行选择。For existing subscriptions created before April 2, or a subscription that was tied to an existing Enterprise Agreement enrollment, you can continue to choose from the three pricing tiers for new workspaces.

    以下限制适用于每个 Log Analytics 工作区。The following limits apply to each Log Analytics workspace.

    免费Free 标准Standard 高级Premium 独立Standalone OMSOMS 每 GBPer GB
    每天收集的数据量Data volume collected per day 500 MB1500 MB1 None None None None None
    数据保留期Data retention period 7 天7 days 1 个月1 month 12 个月12 months 1 个月21 month2 1 个月21 month2 1 个月21 month2

    1当客户达到其 500 MB 每日数据传输限制、 数据分析将停止,并在恢复第二天的开始。1When customers reach their 500-MB daily data transfer limit, data analysis stops and resumes at the start of the next day. 日期基于 UTC。A day is based on UTC.

    2独立、 OMS 和定价计划的每个 GB 的数据保留期可以增加到 730 天。2The data retention period for the Standalone, OMS, and Per GB pricing plans can be increased to 730 days.

    类别Category 限制Limits 注释Comments
    数据收集器 APIData Collector API 单个发布的最大大小为 30 MB。Maximum size for a single post is 30 MB.
    字段值的最大大小为 32 KB。Maximum size for field values is 32 KB.
    将较大的卷拆分为多个帖子。Split larger volumes into multiple posts.
    超过 32 KB 的字段会被截断。Fields longer than 32 KB are truncated.
    搜索 APISearch API 对于非聚合数据返回 5000 条记录。5,000 records returned for non-aggregated data.
    聚合数据的 500,000 条记录。500,000 records for aggregated data.
    聚合的数据是一种搜索包含summarize命令。Aggregated data is a search that includes the summarize command.

    备份限制Backup limits

    以下限制适用于 Azure 备份。The following limits apply to Azure Backup.

    限制Limit 默认Default
    服务器或可以在保管库中注册的计算机。Servers or machines that can be registered in a vault. Windows Server/Windows 客户端/System Center Data Protection Manager:50。Windows Server/Windows Client/System Center Data Protection Manager: 50.

    IaaS VM:1,000.IaaS VMs: 1,000.
    保管库存储中的数据源的大小。Size of a data source in vault storage. 54,400 GB 最大值。54,400-GB maximum. 此限制不适用于 IaaS VM 备份。The limit doesn't apply to IaaS VM backup.
    Azure 订阅中的备份保管库。Backup vaults in an Azure subscription. 每个区域 500 个保管库。500 vaults per region.
    计划每日备份。Schedule daily backups. Windows Server/客户端:每天三次。Windows Server/Client: Three a day.
    System Center DPM:两个一天。System Center DPM: Two a day.
    IaaS VM:每天一次。IaaS VMs: Once a day.
    数据磁盘附加到 Azure VM 备份。Data disks attached to an Azure VM for backup. 1616
    单个数据磁盘附加到 Azure VM 备份。Individual data disk attached to Azure VM for backup. 4,095 GB4,095 GB

    Azure SignalR 服务限制Azure SignalR Service limits

    资源Resource 默认限制Default limit 最大限制Maximum limit
    Azure SignalR 服务单位,每个实例免费层Azure SignalR Service units per instance for Free tier 1 1
    Azure SignalR 服务单位,每个实例用于标准层Azure SignalR Service units per instance for Standard tier 100100 100100
    Azure SignalR 服务单位,每个订阅每个区域免费层Azure SignalR Service units per subscription per region for Free tier 55 55
    Azure SignalR 服务单位总量对每个订阅每个区域进行计数Total Azure SignalR Service unit counts per subscription per region 150150 不受限制Unlimited
    免费层每天每个单元的连接数Connections per unit per day for Free tier 2020 2020
    标准层每天每个单元的连接数Connections per unit per day for Standard tier 1,0001,000 1,0001,000
    免费层每天每个单元包含的消息数Included messages per unit per day for Free tier 20,00020,000 20,00020,000
    标准层每天每个单元包含的消息数Included messages per unit per day for Standard tier 1,000,0001,000,000 1,000,0001,000,000

    若要请求更新订阅的默认限制,请开具支持票证。To request an update to your subscription's default limits, open a support ticket.

    站点恢复限制Site Recovery limits

    以下限制适用于 Azure Site Recovery。The following limits apply to Azure Site Recovery.

    限制标识符Limit identifier 默认限制Default limit
    每个订阅的保管库数Number of vaults per subscription 500500
    每个 Azure 保管库的服务器数Number of servers per Azure vault 250250
    每个 Azure 保管库的保护组数Number of protection groups per Azure vault 无限制No limit
    每个 Azure 保管库的恢复计划数Number of recovery plans per Azure vault 无限制No limit
    每个保护组的服务器数Number of servers per protection group 无限制No limit
    每个恢复计划的服务器数Number of servers per recovery plan 5050

    Application Insights 限制Application Insights limits

    有一些限制的度量值和每个应用程序,事件数,即每个检测密钥。There are some limits on the number of metrics and events per application, that is, per instrumentation key. 限制取决于选择的定价计划Limits depend on the pricing plan that you choose.

    资源Resource 默认限制Default limit 注意Note
    每日的总数据量Total data per day 100 GB100 GB 可以通过设置一个上限来减少数据。You can reduce data by setting a cap. 如果需要更多数据,可以在门户中最多将上限提高到 1,000 GB。If you need more data, you can increase the limit in the portal, up to 1,000 GB. 容量大于 1,000 GB,将发送电子邮件发送到AIDataCap@microsoft.com。For capacities greater than 1,000 GB, send email to AIDataCap@microsoft.com.
    限制Throttling 32,000 事件/秒32,000 events/second 限制按分钟计量。The limit is measured over a minute.
    数据保留Data retention 90 天90 days 此资源适用于搜索分析指标资源管理器This resource is for Search, Analytics, and Metrics Explorer.
    可用性多步骤测试详细结果保留Availability multi-step test detailed results retention 90 天90 days 此资源提供了每个步骤的详细结果。This resource provides detailed results of each step.
    最大事件大小Maximum event size 64,00064,000
    属性和指标名称长度Property and metric name length 150150 请参阅类型架构See type schemas.
    属性值字符串长度Property value string length 8,1928,192 请参阅类型架构See type schemas.
    跟踪和异常消息长度Trace and exception message length 32,76832,768 请参阅类型架构See type schemas.
    每个应用的可用性测试计数Availability tests count per app 100100
    探查器数据保留期Profiler data retention 5 天5 days
    每天发送的探查器数据量Profiler data sent per day 10 GB10 GB

    有关详细信息,请参阅关于 Application Insights 中的定价和配额For more information, see About pricing and quotas in Application Insights.

    API 管理限制API Management limits

    资源Resource 限制Limit
    最大缩放单位数Maximum number of scale units 每个区域 10 个110 per region1
    缓存大小Cache size 每个单位 5 GB25 GB per unit2
    后端的并发连接3每个 HTTP 颁发机构Concurrent back-end connections3 per HTTP authority 每个单位 204842,048 per unit4
    最大缓存响应大小Maximum cached response size 2 MB2 MB
    最大策略文档大小Maximum policy document size 256 KB5256 KB5
    每个服务实例的最大自定义网关域6Maximum custom gateway domains per service instance6 2020
    最大数量的每个服务实例的 CA 证书Maximum number of CA certificates per service instance 1010
    每个订阅的最大服务实例数7Maximum number of service instances per subscription7 2020
    每个服务实例的最大订阅数7Maximum number of subscriptions per service instance7 500500
    每个服务实例的最大客户端证书数7Maximum number of client certificates per service instance7 5050
    每个服务实例的最大 API 数7Maximum number of APIs per service instance7 5050
    每个服务实例的最大 API 操作数7Maximum number of API operations per service instance7 1,0001,000
    最大总请求持续时间7Maximum total request duration7 30 秒30 seconds
    最大缓冲有效负载大小7Maximum buffered payload size7 2 MB2 MB

    1缩放限制取决于定价层。1Scaling limits depend on the pricing tier. 若要查看定价层及其缩放限制,请参阅API 管理定价To see the pricing tiers and their scaling limits, see API Management pricing.
    2每单位缓存大小取决于定价层。2Per unit cache size depends on the pricing tier. 若要查看定价层及其缩放限制,请参阅API 管理定价To see the pricing tiers and their scaling limits, see API Management pricing.
    3连接建立池连接,除非显式关闭由后端中重复使用。3Connections are pooled and reused unless explicitly closed by the back end.
    4此限制是每个单位的基本、 标准和高级层。4This limit is per unit of the Basic, Standard, and Premium tiers. 开发人员层被限制为 1,024。The Developer tier is limited to 1,024. 此限制不适用于消耗层。This limit doesn't apply to the Consumption tier.
    5此限制适用于基本、 标准和高级层。 5This limit applies to the Basic, Standard, and Premium tiers. 在消耗层中,策略文档大小被限制为 4 KB。In the Consumption tier, policy document size is limited to 4 KB.
    6此资源是仅高级层中可用。6This resource is available in the Premium tier only.
    7此资源适用于仅消耗级别。7This resource applies to the Consumption tier only.

    Azure Redis 缓存限制Azure Cache for Redis limits

    资源Resource 限制Limit
    缓存大小Cache size 530 GB530 GB
    数据库Databases 6464
    最大连接的客户端Maximum connected clients 40,00040,000
    Azure 缓存的 Redis 副本,以实现高可用性Azure Cache for Redis replicas, for high availability 1
    启用群集的高级缓存中的分片数Shards in a premium cache with clustering 1010

    每个定价层的 Azure Redis 缓存限制和大小都不相同。Azure Cache for Redis limits and sizes are different for each pricing tier. 若要查看定价层及其关联的大小,请参阅Azure 缓存的 Redis 定价To see the pricing tiers and their associated sizes, see Azure Cache for Redis pricing.

    有关 Azure Redis 缓存配置限制的详细信息,请参阅默认 Redis 服务器配置For more information on Azure Cache for Redis configuration limits, see Default Redis server configuration.

    由于 Azure Redis 缓存实例的配置和管理是由 Microsoft 执行的,因此 Azure Redis 缓存并非支持所有 Redis 命令。Because configuration and management of Azure Cache for Redis instances is done by Microsoft, not all Redis commands are supported in Azure Cache for Redis. 有关详细信息,请参阅 Azure Redis 缓存不支持的 Redis 命令For more information, see Redis commands not supported in Azure Cache for Redis.

    密钥保管库限制Key Vault limits

    密钥事务 (每个区域保管库在 10 秒内,每个允许的最大事务1):Key transactions (maximum transactions allowed in 10 seconds, per vault per region1):

    密钥类型Key type HSM 密钥HSM key
    创建密钥CREATE key
    HSM 密钥HSM key
    所有其他事务All other transactions
    软件密钥Software key
    创建密钥CREATE key
    软件密钥Software key
    所有其他事务All other transactions
    RSA 2048 位RSA 2,048-bit 55 1,0001,000 1010 2,0002,000
    RSA 3072 位RSA 3,072-bit 55 250250 1010 500500
    RSA 4096 位RSA 4,096-bit 55 125125 1010 250250
    ECC P-256ECC P-256 55 1,0001,000 1010 2,0002,000
    ECC P-384ECC P-384 55 1,0001,000 1010 2,0002,000
    ECC P-521ECC P-521 55 1,0001,000 1010 2,0002,000
    ECC SECP256K1ECC SECP256K1 55 1,0001,000 1010 2,0002,000

    备注

    在上表中,我们看到,对于 RSA 2048 位软件密钥,允许每 10 秒 2,000 个获取事务。In the previous table, we see that for RSA 2,048-bit software keys, 2,000 GET transactions per 10 seconds are allowed. 对于 RSA 2048 位的 HSM 密钥,允许每 10 秒的 1,000 个获取事务。For RSA 2,048-bit HSM-keys, 1,000 GET transactions per 10 seconds are allowed.

    限制阈值时权重,并强制位于其总和。The throttling thresholds are weighted, and enforcement is on their sum. 例如上, 表中所示,请执行 GET 操作在 RSA HSM 密钥时它是八倍更昂贵,若要使用 4096 位密钥相比 2,048 位密钥。For example, as shown in the previous table, when you perform GET operations on RSA HSM-keys, it's eight times more expensive to use 4,096-bit keys compared to 2,048-bit keys. 这是因为 1,000/125 = 8。That's because 1,000/125 = 8.

    在给定的 10 秒间隔内,Azure 密钥保管库客户端可以执行只有一个的以下操作之前遇到429限制 HTTP 状态代码:In a given 10-second interval, an Azure Key Vault client can do only one of the following operations before it encounters a 429 throttling HTTP status code:

    • 2,000 个 RSA 2048 位软件密钥获取事务2,000 RSA 2,048-bit software-key GET transactions
    • 1,000 个 RSA 2048 位 HSM 密钥获取事务1,000 RSA 2,048-bit HSM-key GET transactions
    • 125 RSA 4096 位 HSM 密钥获取事务125 RSA 4,096-bit HSM-key GET transactions
    • 124 RSA 4096 位的 HSM 密钥获取事务和 8 RSA 2048 位 HSM 密钥获取事务124 RSA 4,096-bit HSM-key GET transactions and 8 RSA 2,048-bit HSM-key GET transactions

    机密、 托管的存储帐户密钥和保管库事务:Secrets, managed storage account keys, and vault transactions:

    事务类型Transactions type 每个区域保管库在 10 秒内,每个允许的最大事务1Maximum transactions allowed in 10 seconds, per vault per region1
    所有事务All transactions 2,0002,000

    有关如何处理限制时超出这些限制的信息,请参阅Azure Key Vault 限制指南For information on how to handle throttling when these limits are exceeded, see Azure Key Vault throttling guidance.

    1的所有事务类型的订阅范围限制为五次每个密钥保管库的限制。1 A subscription-wide limit for all transaction types is five times per key vault limit. 例如,每个订阅的 HSM-其他事务在 10 秒内每个订阅仅限于 5,000 个事务。For example, HSM-other transactions per subscription are limited to 5,000 transactions in 10 seconds per subscription.

    多重身份验证限制Multi-Factor Authentication limits

    资源Resource 默认限制Default limit 最大限制Maximum limit
    受信任的 IP 地址或范围的最大数目每个订阅Maximum number of trusted IP addresses or ranges per subscription 00 5050
    记住我的设备的天数Remember my devices, number of days 1414 6060
    应用密码的最大数目Maximum number of app passwords 00 无限制No limit
    MFA 调用期间允许 X 次尝试Allow X attempts during MFA call 1 9999
    双向文本消息超时秒数Two-way text message timeout seconds 6060 600600
    默认一次性跳过秒数Default one-time bypass seconds 300300 1,8001,800
    X 次连续 MFA 拒绝后锁定用户帐户Lock user account after X consecutive MFA denials 未设置Not set 9999
    X 分钟后重置帐户锁定计数器Reset account lockout counter after X minutes 未设置Not set 9,9999,999
    X 分钟后解锁帐户Unlock account after X minutes 未设置Not set 9,9999,999

    自动化限制Automation limits

    流程自动化Process automation

    资源Resource 最大限制Maximum limit 说明Notes
    每个 Azure 自动化帐户每 30 秒可以提交的新作业的最大数量(非计划的作业)Maximum number of new jobs that can be submitted every 30 seconds per Azure Automation account (nonscheduled jobs) 100100 达到此限制时,后续作业创建请求会失败。When this limit is reached, the subsequent requests to create a job fail. 客户端会收到错误响应。The client receives an error response.
    每个自动化帐户相同时间实例并发运行的作业的最大数量(非计划的作业)Maximum number of concurrent running jobs at the same instance of time per Automation account (nonscheduled jobs) 200200 达到此限制时,后续作业创建请求会失败。When this limit is reached, the subsequent requests to create a job fail. 客户端会收到错误响应。The client receives an error response.
    30 天滚动期内作业元数据的最大存储大小Maximum storage size of job metadata for a 30-day rolling period 10 GB(约 400 万个作业)10 GB (approximately 4 million jobs) 达到此限制时,后续作业创建请求会失败。When this limit is reached, the subsequent requests to create a job fail.
    最大作业流限制Maximum job stream limit 1MB1MB 单个流不能大于 1 MB。A single stream cannot be larger than 1 MB.
    每个自动化帐户每 30 秒可以导入的模块的最大数量Maximum number of modules that can be imported every 30 seconds per Automation account 55
    模块的最大大小Maximum size of a module 100 MB100 MB
    作业运行时间,免费层Job run time, Free tier 每个订阅每个日历月 500 分钟500 minutes per subscription per calendar month
    每个沙盒允许的最大磁盘空间1Maximum amount of disk space allowed per sandbox1 1 GB1 GB 仅适用于 Azure 沙盒。Applies to Azure sandboxes only.
    沙盒的最大内存量1Maximum amount of memory given to a sandbox1 400 MB400 MB 仅适用于 Azure 沙盒。Applies to Azure sandboxes only.
    每个沙盒允许的最大网络套接字数量1Maximum number of network sockets allowed per sandbox1 1,0001,000 仅适用于 Azure 沙盒。Applies to Azure sandboxes only.
    每个 runbook 允许的最大运行时1Maximum runtime allowed per runbook1 3 小时3 hours 仅适用于 Azure 沙盒。Applies to Azure sandboxes only.
    订阅中自动化帐户的最大数目Maximum number of Automation accounts in a subscription 无限制No limit
    最大数量的每个自动化帐户的混合辅助角色组Maximum number of Hybrid Worker Groups per Automation Account 4,0004,000
    可以在单个的混合 Runbook 辅助角色运行的并发作业的最大数目Maximum number of concurrent jobs that can be run on a single Hybrid Runbook Worker 5050
    Runbook 作业参数大小上限Maximum runbook job parameter size 512 千比特512 kilobits
    Runbook 参数数量上限Maximum runbook parameters 5050 如果达到 50 个参数的限制,则可将 JSON 或 XML 字符串传递给参数,并使用 Runbook 对其进行分析。If you reach the 50-parameter limit, you can pass a JSON or XML string to a parameter and parse it with the runbook.
    Webhook 有效负载大小上限Maximum webhook payload size 512 千比特512 kilobits
    保留作业数据的最大天数Maximum days that job data is retained 30 天30 days
    PowerShell 工作流状态大小上限Maximum PowerShell workflow state size 5 MB5 MB 执行检查点工作流时适用于 PowerShell 工作流 runbook。Applies to PowerShell workflow runbooks when checkpointing workflow.

    1沙盒是可以由多个作业使用的共享环境。1A sandbox is a shared environment that can be used by multiple jobs. 使用同一沙盒的作业受沙盒的资源限制约束。Jobs that use the same sandbox are bound by the resource limitations of the sandbox.

    更改跟踪和清单Change tracking and inventory

    下表显示了每台计算机进行更改跟踪的跟踪的项限制。The following table shows the tracked item limits per machine for change tracking.

    资源Resource 限制Limit 说明Notes
    文件File 500500
    注册表Registry 250250
    Windows 软件Windows software 250250 不包括软件更新。Doesn't include software updates.
    Linux 包Linux packages 1,2501,250
    服务Services 250250
    守护程序Daemon 250250

    标识管理器限制Identity Manager limits

    类别Category 限制Limit
    用户分配管理的标识User-assigned managed identities
    • 当你创建用户分配托管标识,仅字母数字字符 (0-9、 a 到 z 和 A-Z) 和连字符 (-) 支持。When you create user-assigned managed identities, only alphanumeric characters (0-9, a-z, and A-Z) and the hyphen (-) are supported. 分配给虚拟机或虚拟机规模集才能正常工作,名称仅限于 24 个字符。For the assignment to a virtual machine or virtual machine scale set to work properly, the name is limited to 24 characters.
    • 如果使用托管的标识虚拟机扩展,支持的限制为 32 用户分配的托管的标识。If you use the managed identity virtual machine extension, the supported limit is 32 user-assigned managed identities. 而无需托管的标识虚拟机扩展,支持的限制为 512 用户分配的标识。Without the managed identity virtual machine extension, the supported limit is 512 user-assigned identities.

    基于角色的访问控制限制Role-based access control limits

    资源Resource 限制Limit
    每个 Azure 订阅的 Azure 资源角色分配数Role assignments for Azure resources per Azure subscription 2,0002,000
    每个租户的 Azure 资源自定义角色数Custom roles for Azure resources per tenant 2,0002,000

    SQL 数据库限制SQL Database limits

    有关 SQL 数据库限制,请参阅单一数据库的 SQL 数据库资源限制弹性池和入池的数据库的 SQL 数据库资源限制,和SQL 数据库资源限制托管实例For SQL Database limits, see SQL Database resource limits for single databases, SQL Database resource limits for elastic pools and pooled databases, and SQL Database resource limits for managed instances.

    SQL 数据仓库限制SQL Data Warehouse limits

    有关 SQL 数据仓库限制,请参阅SQL 数据仓库资源限制For SQL Data Warehouse limits, see SQL Data Warehouse resource limits.

    另请参阅See also