您现在访问的是微软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 of the platform.

若要了解有关 Azure 定价的详细信息,请访问 Azure 定价概述Please visit Azure Pricing Overview to learn more about Azure pricing. 在那里,可以使用定价计算器或访问某服务(例如,Windows VM)的详情页面预估所需的成本。There, you can estimate your costs using the Pricing Calculator or by visiting the pricing details page for a 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 is no Maximum Limit column, then the resource doesn't have adjustable limits.

免费试用版订阅不符合增加限制或配额的条件。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.

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

现在可以将多个 Azure 资源合并到单个 Azure 资源组中。It is now possible to combine multiple Azure resources in to a single Azure Resource Group. 在使用资源组时,以前针对全局的限制会通过 Azure 资源管理器在区域级别进行管理。When using Resource Groups, limits that once were global become managed at a regional level with the Azure Resource Manager. 有关 Azure 资源组的详细信息,请参阅 Azure 资源管理器概述For more information about Azure Resource Groups, see Azure Resource Manager overview.

在下面的限制中,添加了一个新表以反映在使用 Azure 资源管理器时限制中的任何差异。In the limits below, a new table has been added to reflect any differences in limits when using the Azure Resource Manager. 例如,会存在一个订阅限制表和一个订阅数限制 - Azure 资源管理器表。For example, there is a Subscription Limits table and a Subscription Limits - Azure Resource Manager table. 如果某个限制同时适用于这两种方案,它将仅显示在第一个表中。When a limit applies to both scenarios, it is only shown in the first table. 除非另有说明,否则限制是跨所有区域的全局限制。Unless otherwise indicated, limits are global across all regions.

备注

请务必强调 Azure 资源组中的资源配额是用户的订阅可以访问的每个区域,而不像服务管理配额那样是可以访问的每个订阅。It is important to emphasize that quotas for resources in Azure Resource Groups are per-region accessible by your subscription, and are not per-subscription, as the service management quotas are. 让我们以 vCPU 配额为例。Let's use vCPU quotas as an example. 如果要根据对 vCPU 的支持请求增加配额,则需要决定要在哪些区域中使用多少 vCPU,然后针对所需的 Azure 资源组 vCPU 配额的数量和区域发出特定请求。If you need to request a quota increase with support for vCPUs, you need to decide how many vCPUs you want to use in which regions, and then make a specific request for Azure Resource Group vCPU quotas for the amounts and regions that you want. 因此,如果需要在西欧使用 30 个 vCPU 以在那里运行应用程序,则应专门在西欧请求 30 个 vCPU。Therefore, if you need to use 30 vCPUs in West Europe to run your application there, you should specifically request 30 vCPUs in West Europe. 但这不会增加任何其他区域的 vCPU 配额 - 仅西欧会有 30 个 vCPU 配额。But you will not have a vCPU quota increase in any other region -- only West Europe will have the 30-vCPU quota.

因此,你可能会发现考虑决定你在任何一个区域中的工作负荷所需的 Azure 资源组配额数量,以及请求你考虑在其中进行部署的每个区域的数量很有用。As a result, you may find it useful to consider deciding what your Azure Resource Group quotas need to be for your workload in any one region, and request that amount in each region into which you are considering deployment. 请参阅部署问题疑难解答,了解有关发现你特定区域的当前配额的更多帮助。See troubleshooting deployment issues for more help discovering your current quotas for specific regions.

服务特定的限制Service-specific limits

订阅限制Subscription limits

订阅限制Subscription limits

资源Resource 默认限制Default Limit 最大限制Maximum Limit
每个订阅的核心数 1Cores per subscription 1 2020 10,00010,000
每个订阅的共同管理员数Co-administrators per subscription 200200 200200
每个订阅在每个区域中的存储帐户数2Storage accounts per region per subscription2 200200 250250
每个订阅的云服务数Cloud services per subscription 2020 200200
每个订阅的本地网络数Local networks per subscription 1010 500500
每个订阅的 SQL 数据库服务器数SQL Database servers per subscription 66 150150
每个订阅的 DNS 服务器DNS servers per subscription 99 100100
每个订阅的保留的 IPReserved IPs per subscription 2020 100100
每个订阅的托管服务证书数Hosted service certificates per subscription 199199 199199
每个订阅的地缘组数Affinity groups per subscription 256256 256256

1特小实例作为一项核心至核心限制计数,即使使用了部分核心。1Extra Small instances count as one core towards the core limit despite using a partial core.

2此存储帐户限制包括标准和高级存储帐户。2The storage account limit includes both Standard and Premium storage accounts. 如果在单个区域中需要的存储帐户多于 200 个,请通过 Azure 支持提出请求。If you require more than 200 storage accounts in a single 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.

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

使用 Azure 资源管理器和 Azure 资源组时,以下限制适用。The following limits apply when using the Azure Resource Manager and Azure Resource Groups. 未使用 Azure 资源管理器更改的限制不会在下面列出。Limits that have not changed with the Azure Resource Manager are not listed below. 请参阅上表了解这些限制。Please refer to the previous table for those limits.

有关处理资源管理器请求限制的信息,请参阅限制资源管理器请求For information about handling limits on Resource Manager requests, see Throttling Resource Manager requests.

资源Resource 默认限制Default Limit 最大限制Maximum Limit
每个订阅的 VM 数VMs per subscription 每个区域 10,000 个110,000 1 per Region 每个区域 10,000 个10,000 per Region
每个订阅的 VM 核心总数VM total cores per subscription 每个区域 20 个1201 per Region 联系支持人员Contact support
每个订阅的 VM 按系列(Dv2、F 等)核心数VM per series (Dv2, F, etc.) cores per subscription 每个区域 20 个1201 per Region 联系支持人员Contact support
每个订阅的共同管理员数Co-administrators per subscription 不受限制Unlimited 不受限制Unlimited
每个订阅的存储帐户数Storage accounts per subscription 200200 20022002
每个订阅的资源组数Resource Groups per subscription 800800 800800
每个订阅的可用性集数Availability Sets per subscription 每个区域 2,000 个2,000 per Region 每个区域 2,000 个2,000 per Region
Resource Manager API 读取次数Resource Manager API Reads 每小时 15,000 次15,000 per hour 每小时 15,000 次15,000 per hour
Resource Manager API 写入次数Resource Manager API Writes 每小时 1,200 次1,200 per hour 每小时 1,200 次1,200 per hour
Resource Manager API 请求大小Resource Manager API request size 4,194,304 字节4,194,304 bytes 4,194,304 字节4,194,304 bytes
每个订阅的标记数3Tags per subscription3 不受限制unlimited 不受限制unlimited
每个订阅的唯一标记计算3Unique tag calculations per subscription3 10,00010,000 10,00010,000
每个订阅的云服务数Cloud services per subscription 不适用4Not Applicable4 不适用4Not Applicable4
每个订阅的地缘组数Affinity groups per subscription 不适用4Not Applicable4 不适用4Not Applicable4

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

2这包括标准和高级存储帐户。2This includes both Standard and Premium storage accounts. 如果需要的存储帐户超过 100 个,请通过 Azure 支持提出请求。If you require more than 200 storage accounts, 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.

3每个订阅可以应用无限数量的标记。3You 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 仅返回订阅中唯一标记名和值的列表Resource Manager only returns a list of unique tag name and values in the subscription when the number of tags is 10,000 or less. 不过,即使数目超过 10,000,也仍可通过标记查找资源。However, you can still find a resource by tag when the number exceeds 10,000.

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

备注

必须强调的是,虚拟机核心数既有区域总数限制,也有区域按大小系列(Dv2、F 等)限制,这两种限制单独实施。It is important to emphasize that virtual machine cores have a regional total limit as well as 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 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 800800 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

模板限制Template limits

Value 默认限制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 Using linked templates when deploying 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.

如果达到每个资源组的部署数限制 800,则会从历史记录中删除不再需要的部署。If you reach the limit of 800 deployments per resource group, delete deployments from the history that are no longer needed. 可以使用 Azure CLI 的 az group deployment delete 或 PowerShell 中的 Remove-AzureRmResourceGroupDeployment 删除历史记录中的条目。You can delete entries from the history with az group deployment delete for Azure CLI, or Remove-AzureRmResourceGroupDeployment in PowerShell. 从部署历史记录中删除条目不会影响部署资源。Deleting an entry from the deployment history does not affect the deploy resources.

虚拟机限制Virtual Machines limits

虚拟机限制Virtual Machine limits

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

1在服务管理(而不是 Resource Manager )中创建的虚拟机会自动存储在云服务中。1Virtual machines created in Service Management (instead of 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. 请参阅如何设置虚拟机的终结点See How to Set Up Endpoints to a Virtual Machine.

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

使用 Azure 资源管理器和 Azure 资源组时,以下限制适用。The following limits apply when using the Azure Resource Manager and Azure Resource Groups. 未使用 Azure 资源管理器更改的限制不会在下面列出。Limits that have not changed with the Azure Resource Manager are not listed below. 请参阅上表了解这些限制。Please refer to 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. 虽然订阅的证书数不受限制,但每个部署仍有 1 MB 的证书限制(包含单个 VM 或可用性集)。Although the number of certificates is unlimited for a subscription, there is still a 1 MB limit of certificates per deployment (which consists of either a single VM or an availability set).

虚拟机规模集限制Virtual Machine Scale Sets limits

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

容器实例限制Container Instances limits

资源Resource 默认限制Default Limit
每个订阅的容器组数Container groups per subscription 201201
每个容器组的容器数Number of containers per container group 6060
每个容器组的卷数Number of volumes per container group 2020
每个 IP 的端口数Ports per IP 55
每小时创建容器次数Container creates per hour 601601
每 5 分钟创建容器次数Container creates per 5 minutes 201201
每小时删除容器次数Container deletes per hour 15011501
每 5 分钟删除容器次数Container deletes per 5 minutes 501501
每个容器组多个容器Multiple containers per container group 仅限 Linux2Linux only2
Azure 文件卷Azure Files volumes 仅限 Linux2Linux only2
GitRepo 卷GitRepo volumes 仅限 Linux2Linux only2
机密卷Secret volumes 仅限 Linux2Linux only2

1 创建 Azure 支持请求可请求提高上限。1 Create an Azure support request to request a limit increase.
2 计划提供对此功能的 Windows 支持。2 Windows support for this feature is planned.

容器注册表限制Container Registry limits

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

资源Resource 基本Basic 标准Standard 高级Premium
存储Storage 10 GiB10 GiB 100 GiB100 GiB 500 GiB500 GiB
每分钟读取操作数1、2ReadOps per minute1, 2 10001000 30003000 1000010000
每分钟写入操作数1、3WriteOps per minute1, 3 100100 500500 20002000
下载带宽 (MBps)1Download bandwidth MBps1 3030 6060 100100
上传带宽 (MBps)1Upload bandwidth MBps1 1010 2020 5050
WebhookWebhooks 22 1010 100100
异地复制Geo-replication 不适用N/A 不适用N/A 支持(预览版)Supported (preview)

1读取操作数、写入操作数和带宽是最小估计值。1 ReadOps, WriteOps, and Bandwidth are minimum estimates. ACR 旨在随使用情况增多提升性能。ACR strives to improve performance as usage requires.

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

3docker push 根据必须推送的层数转换为多个写入操作。3 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.

容器服务 (AKS) 限制Container Service (AKS) limits

资源Resource 默认限制Default Limit
每个群集的最大节点数Max nodes per cluster 100100
每个节点的最大 Pod 数Max pods per node 110110
每个订阅的最大群集数Max cluster per subscription 201201

1 创建 Azure 支持请求可请求提高上限。1 Create an Azure support request to request a limit increase.

网络限制Networking limits

ExpressRoute 限制ExpressRoute Limits

下列限制适用于每个订阅的 ExpressRoute 资源。The following limits apply to ExpressRoute resources per subscription.

资源Resource 默认限制Default Limit
每个订阅的 ExpressRoute 线路数ExpressRoute circuits per subscription 1010
ARM 的每个订阅每个区域的 ExpressRoute 线路数ExpressRoute circuits per region per subscription for ARM 1010
具有 ExpressRoute Standard 的 Azure 私用对等互连的最大路由数Maximum number of routes for Azure private peering with ExpressRoute standard 4,0004,000
具有 ExpressRoute Premium 附加设备的 Azure 私用对等互连的最大路由数Maximum number of routes for Azure private peering with ExpressRoute premium add-on 10,00010,000
具有 ExpressRoute Standard 的 Azure 公共对等互连的最大路由数Maximum number of routes for Azure public peering with ExpressRoute standard 200200
具有 ExpressRoute Premium 附加设备的 Azure 公共对等互连的最大路由数Maximum number of routes for Azure public peering with ExpressRoute premium add-on 200200
具有 ExpressRoute Standard 的 Azure Microsoft 对等互连的最大路由数Maximum number of routes for Azure Microsoft peering with ExpressRoute standard 200200
具有 ExpressRoute Premium 附加设备的 Azure Microsoft 对等互连的最大路由数Maximum number of routes for Azure Microsoft peering with ExpressRoute premium add-on 200200
每个 ExpressRoute 线路允许的虚拟网络链接数Number of virtual network links allowed per ExpressRoute circuit 请参阅下表see table below

每个 ExpressRoute 线路的虚拟网络数Number of Virtual Networks per ExpressRoute circuit

线路大小Circuit Size 标准版 VNet 链接数Number of VNet links for standard 高级版附加设备的 VNet 链接数Number of VNet 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

网络限制Networking limits

以下限制仅适用于每个订阅通过经典部署模型托管的网络资源。The following limits apply only for networking resources managed through the classic deployment model per subscription.

资源Resource 默认限制Default limit 最大限制Maximum limit
虚拟网络Virtual networks 5050 100100
本地网络站点Local network sites 2020 联系支持人员contact support
每个虚拟网络的 DNS 服务器数DNS Servers per virtual network 2020 100100
每个虚拟网络的专用 IP 地址数Private IP Addresses per virtual network 40964096 40964096
虚拟机或角色实例的单 NIC 并发 TCP 或 UDP 流数Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 500K500K 500K500K
网络安全组 (NSG)Network Security Groups (NSG) 100100 200200
每个 NSG 的 NSG 规则数NSG rules per NSG 200200 400400
用户定义路由表数User defined route tables 100100 200200
每个路由表的用户定义的路由数User defined routes per route table 100100 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 (ILB)Private VIP (ILB) per deployment 11 11
终结点访问控制列表 (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.

资源Resource 默认限制Default limit 最大限制Maximum Limit
虚拟网络Virtual networks 5050 10001000
每个虚拟网络的子网数Subnets per virtual network 10001000 1000010000
每个虚拟网络的虚拟网络对等互连数Virtual network peerings per Virtual Network 1010 5050
每个虚拟网络的 DNS 服务器数DNS Servers per virtual network 99 2525
每个虚拟网络的专用 IP 地址数Private IP Addresses per virtual network 40964096 81928192
每个网络接口的专用 IP 地址数Private IP Addresses per network interface 256256 10241024
虚拟机或角色实例的单 NIC 并发 TCP 或 UDP 流数Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 500K500K 500K500K
网络接口 (NIC)Network Interfaces (NIC) 350350 2000020000
网络安全组 (NSG)Network Security Groups (NSG) 100100 50005000
每个 NSG 的 NSG 规则数NSG rules per NSG 200200 10001000
为安全组中的源或目标指定的 IP 地址和范围数IP addresses and ranges specified for source or destination in a security group 20002000 40004000
应用程序安全组Application security groups 200200 500500
每个 IP 配置和每个 NIC 的应用程序安全组数Application security groups per IP configuration, per NIC 1010 2020
每个应用程序安全组的 IP 配置数IP configurations per application security group 10001000 40004000
可在网络安全组的所有安全规则中指定的应用程序安全组数Application security groups that can be specified within all security rules of a network security group 5050 100100
用户定义路由表数User defined route tables 100100 200200
每个路由表的用户定义的路由数User defined routes per route table 100100 400400
公共 IP 地址数 - 动态Public IP addresses - dynamic (基本)60(Basic) 60 联系支持人员contact support
公共 IP 地址数 - 静态Public IP addresses - static (基本)20(Basic) 20 联系支持人员contact support
公共 IP 地址数 - 静态Public IP addresses - static (标准)20(Standard) 20 联系支持人员contact support
每个 VPN 网关的点到站点根证书Point-to-Site Root Certificates per VPN Gateway 2020 2020

负载均衡器限制Load Balancer limits

资源Resource 默认限制Default limit 最大限制Maximum Limit
负载均衡器Load Balancers 100100 10001000
每个资源的规则数,基本Rules per resource, Basic 150150 250250
每个资源的规则数,标准Rules per resource, Standard 12501250 15001500
每个 IP 配置的规则数Rules per IP configuration 299299 299299
前端 IP 配置数,基本Frontend IP configurations, Basic 1010 200200
前端 IP 配置数,标准Frontend IP configurations, Standard 1010 600600
后端池数,基本Backend pool, Basic 100,单个可用性集100, single Availability Set 100,单个可用性集100, single Availability Set
后端池数,标准Backend pool, Standard 1000,单个 VNet1000, single VNet 1000,单个 VNet1000, single VNet
HA 端口数,标准HA Ports, Standard 每个内部前端 1 个1 per internal frontend 每个内部前端 1 个1 per internal frontend

如果需要在默认值的基础上提高限制,请与支持人员联系Contact support in case you need to increase limits from default.

应用程序网关限制Application Gateway limits

资源Resource 默认限制Default limit 注意Note
应用程序网关Application Gateway 每个订阅 50 个50 per subscription 最大为 100Maximum 100
前端 IP 配置数Frontend IP Configurations 22 1 个公共,1 个专用1 public and 1 private
前端端口数Frontend Ports 2020
后端地址池数Backend Address Pools 2020
每个池的后端服务器数Backend Servers per pool 100100
HTTP 侦听器数HTTP Listeners 2020
HTTP 负载均衡规则数HTTP load balancing rules 200200 HTTP 侦听器数 * n,默认情况下 n=10# of HTTP Listeners * n, n=10 Default
后端 HTTP 设置数Backend HTTP settings 2020 每个后端地址池 1 个1 per Backend Address Pool
每个网关的实例数Instances per gateway 1010 如需更多实例,请开具支持票证For more instances, open support ticket
SSL 证书数SSL certificates 2020 每个 HTTP 侦听器 1 个1 per HTTP Listeners
身份验证证书Authentication certificates 55 最大值 10Maximum 10
最短请求超时Request time out min 1 秒1 second
最长请求超时Request time out max 24 小时24 hrs
站点数Number of sites 2020 每个 HTTP 侦听器 1 个1 per HTTP Listeners
每个侦听器的 URL 映射数URL Maps per listener 11
最大文件上传大小标准Maximum file upload size Standard 2 GB2 GB
最大文件上传大小 WAFMaximum file upload size WAF 100 MB100 MB

网络观察程序限制Network Watcher limits

资源Resource 默认限制Default limit 注意Note
网络观察程序Network Watcher 每个区域 1 个1 per region
数据包捕获会话Packet Capture sessions 每个区域仅 10 个10 per region 只是会话数,不是保存的捕获数# of sessions only, not saved captures

流量管理器限制Traffic Manager limits

资源Resource 默认限制Default limit
每个订阅的配置文件数Profiles per subscription 200 1200 1
每个配置文件的终结点数Endpoints per profile 200200

1如果需要增加这些限制,请与支持人员联系。1Contact support in case you need to increase these limits.

DNS 限制DNS limits

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

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

存储限制Storage limits

有关存储帐户限制的详细信息,请参阅 Azure 存储可伸缩性和性能目标For additional details on storage account limits, see Azure Storage Scalability and Performance Targets.

资源Resource 默认限制Default Limit
每个区域的存储帐户数Number of storage accounts per region 20012001
最大存储帐户容量Max storage account capacity 500 TiB2500 TiB2
每个存储帐户的 Blob 容器、Blob、文件共享、表、队列、实体或消息数上限Max number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account 无限制No limit
每个存储帐户的最大请求速率Maximum request rate per storage account 每秒 20,000 个请求220,000 requests per second2
每个存储帐户的最大入口 3(美国区域)Max ingress3 per storage account (US Regions) 如果已启用 RA-GRS/GRS,则为 10 Gbps;对于 LRS/ZRS,为 20 Gbps410 Gbps if RA-GRS/GRS enabled, 20 Gbps for LRS/ZRS4
每个存储帐户的最大出口 3(美国区域)Max egress3 per storage account (US Regions) 如果已启用 RA-GRS/GRS,则为 20 Gbps;对于 LRS/ZRS,为 30 Gbps420 Gbps if RA-GRS/GRS enabled, 30 Gbps for LRS/ZRS4
每个存储帐户的最大入口3(非美国区域)Max ingress3 per storage account (Non-US regions) 如果已启用 RA-GRS/GRS,则为 5 Gbps;对于 LRS/ZRS,为 10 Gbps45 Gbps if RA-GRS/GRS enabled, 10 Gbps for LRS/ZRS4
每个存储帐户的最大出口3(非美国区域)Max egress3 per storage account (Non-US regions) 如果已启用 RA-GRS/GRS,则为 10 Gbps;对于 LRS/ZRS,为 15 Gbps410 Gbps if RA-GRS/GRS enabled, 15 Gbps for LRS/ZRS4

1包括标准和高级存储帐户。1Includes both Standard and Premium storage accounts. 如果需要的存储帐户超过 100 个,请通过 Azure 支持提出请求。If you require more than 200 storage accounts, 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.

2 如果需要扩大存储帐户的限制,请联系 Azure 支持2 If you need expanded limits for your storage account, please contact Azure Support. Azure 存储团队会对请求进行审核,根据具体情况批准提高限制的请求。The Azure Storage team will review the request and may approve higher limits on a case by case basis. 通用和 Blob 存储帐户请求支持都可按请求提高容量、流入量/流出量和请求速率。Both general-purpose and Blob storage accounts support increased capacity, ingress/egress, and request rate by request. 有关 Blob 存储帐户的新最大值,请参阅宣布推出更大、更高规模的存储帐户For the new maximums for Blob storage accounts, see Announcing larger, higher scale storage accounts.

3 仅受帐户的传入/传出限制的限制。3 Capped only by the account's ingress/egress limits. 传入是指发送到存储帐户的所有数据(请求)。Ingress refers to all data (requests) being sent to a storage account. “传出”是指从存储帐户接收的所有数据(响应)。Egress refers to all data (responses) being received from a storage account.

4Azure 存储冗余选项包括:4Azure Storage redundancy 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.

只使用 Azure 资源管理器执行管理操作时,以下限制适用。The following limits apply when performing management operations using the Azure Resource Manager only.

资源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 容器的最大大小Max size of single blob container 500 TiB500 TiB
块 Blob 或附加 Blob 中的块数上限Max number of blocks in a block blob or append blob 50,000 块50,000 blocks
块 Blob 中块的最大大小Max size of a block in a block blob 100 MiB100 MiB
块 Blob 的最大大小Max size of a block blob 50,000 X 100 MiB(约 4.75 TiB)50,000 X 100 MiB (approx. 4.75 TiB)
追加 Blob 中块的最大大小Max size of a block in an append blob 4 MiB4 MiB
追加 Blob 的最大大小Max size of an append blob 50,000 X 4 MiB(约 195 GiB)50,000 x 4 MiB (approx. 195 GiB)
页 Blob 的最大大小Max size of a page blob 8 TiB8 TiB
每个 blob 容器存储的访问策略的最大数目Max number of stored access policies per blob container 55
单个 Blob 的目标吞吐量Target throughput for single blob 每秒最多 60 MiB,或每秒最多 500 个请求Up to 60 MiB per second, or up to 500 requests per second

Azure 文件限制Azure Files limits

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

资源Resource 目标Target
文件共享的最大大小Max size of a file share 5 TiB5 TiB
文件共享中文件的最大大小Max size of a file in a file share 1 TiB1 TiB
文件共享中的文件数上限Max number of files in a file share 无限制No limit
每个共享的最大 IOPSMax IOPS per share 1000 IOPS1000 IOPS
每个文件共享的存储的访问策略的最大数目Max number of stored access policies per file share 55
每个存储帐户的最大请求速率Maximum request rate per storage account 对于任何有效大小的文件,每秒 20,000 个请求320,000 requests per second for files of any valid size3
单个文件共享的目标吞吐量Target throughput for single file share 最高每秒 60 MiBUp to 60 MiB per second
每个文件打开图柄的最大数目Maximum open handles for per file 2000 个打开图柄2000 open handles
共享快照的最大数目Maximum number of share snapshots 200 个共享快照200 share snapshots

Azure 文件同步限制Azure File Sync limits

资源Resource 目标Target 硬限制Hard limit
每个订阅的存储同步服务数Storage Sync Services per subscription 15 个存储同步服务15 Storage Sync Services No
每个存储同步服务的同步组数Sync groups per Storage Sync Service 30 个同步组30 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 33 到 99 个服务器终结点33-99 server endpoints 是,但因配置而异Yes, but varies based on configuration
终结点大小Endpoint size 4 TiB4 TiB No
每个同步组的文件系统对象数(目录和文件)File system objects (directories and files) per sync group 600 万个对象6 million objects No
文件大小File size 100 GiB100 GiB No
要进行分层的文件的最小文件大小Minimum file size for a file to be tiered 64 KiB64 KiB Yes

Azure 队列存储限制Azure Queue storage limits

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

Azure 表存储限制Azure Table storage limits

资源Resource 目标Target
单个表的最大大小Max size of single table 500 TiB500 TiB
表实体的最大大小Max size of a table entity 1 MiB1 MiB
表实体中属性的最大数目Max number of properties in a table entity 252252
每个表存储的访问策略的最大数目Max number of stored access policies per table 55
每个存储帐户的最大请求速率Maximum request rate per storage account 20,000 事务/秒(假定实体大小为 1 KiB)20,000 transactions per second (assuming 1 KiB entity size)
单个表分区的目标吞吐量(1 KiB 实体)Target throughput for single table partition (1 KiB entities) 每秒最多 2000 个实体Up to 2000 entities per second

虚拟机磁盘限制Virtual machine disk limits

Azure 虚拟机支持附加许多的数据磁盘。An Azure virtual machine supports attaching a number of data disks. 本文介绍 VM 的数据磁盘的可伸缩性和性能目标。This article describes scalability and performance targets for a VM's data disks. 使用这些目标可帮助确定满足性能和容量要求所需的磁盘数量和磁盘类型。Use these targets to help decide 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 are not highly utilized at the same time, then the virtual machine can support a larger number of disks.

  • 对于 Azure 托管磁盘:托管磁盘按区域和按磁盘类型进行磁盘限制。For Azure Managed Disks: The disk limit for managed disks is per region and per disk type. 一个订阅的最大限制(也是默认限制)为每个区域、每个磁盘类型 10,000 个托管磁盘。The maximum limit, and also the default limit, is 10,000 managed disks per region and per disk type for a subscription. 例如,可以在每个订阅及一个区域中最多创建 10,000 个标准托管磁盘和 10,000 个高级托管磁盘。For example, you can create up to 10,000 standard managed disks and also 10,000 premium managed disks in a region, per subscription.

    托管的快照和映像计入托管磁盘限制。Managed snapshots and images count against the managed disks limit.

  • 标准存储帐户:标准存储帐户的总请求率上限为 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(每个磁盘 20,000/300 IOPS);对于标准层 VM,约为 40(每个磁盘 20,000/500 IOPS)。For example, for a Basic Tier VM, the maximum number of highly utilized disks is about 66 (20,000/300 IOPS per disk), and for a Standard Tier VM, it is about 40 (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.

有关其他详细信息,请参阅虚拟机大小See Virtual machine sizes for additional details.

托管虚拟机磁盘Managed virtual machine disks

标准托管虚拟机磁盘Standard managed virtual machine disks

标准磁盘类型Standard Disk Type S4S4 S6S6 S10S10 S20S20 S30S30 S40S40 S50S50
磁盘大小Disk size 32 GB32 GB 64 GB64 GB 128 GB128 GB 512 GB512 GB 1024 GB (1 TB)1024 GB (1 TB) 2048 GB (2 TB)2048 GB (2TB) 4095 GB (4 TB)4095 GB (4 TB)
每个磁盘的 IOPSIOPS per disk 500500 500500 500500 500500 500500 500500 500500
每个磁盘的吞吐量Throughput per disk 60 MB/秒60 MB/sec 60 MB/秒60 MB/sec 60 MB/秒60 MB/sec 60 MB/秒60 MB/sec 60 MB/秒60 MB/sec 60 MB/秒60 MB/sec 60 MB/秒60 MB/sec

高级托管虚拟机磁盘:每个磁盘的限制Premium managed virtual machine disks: per disk limits

高级磁盘类型Premium Disks Type P4P4 P6P6 P10P10 P20P20 P30P30 P40P40 P50P50
磁盘大小Disk size 32 GB32 GB 64 GB64 GB 128 GB128 GB 512 GB512 GB 1024 GB (1 TB)1024 GB (1 TB) 2048 GB (2 TB)2048 GB (2 TB) 4095 GB (4 TB)4095 GB (4 TB)
每个磁盘的 IOPSIOPS per disk 120120 240240 500500 23002300 50005000 75007500 75007500
每个磁盘的吞吐量Throughput per disk 25 MB/秒25 MB/sec 50 MB/秒50 MB/sec 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

高级托管虚拟机磁盘:每台 VM 的限制Premium managed virtual machine disks: per VM limits

资源Resource 默认限制Default Limit
每个 VM 的最大 IOPSMax IOPS Per VM GS5 VM 为 80,000 IOPS80,000 IOPS with GS5 VM
每个 VM 的最大吞吐量Max 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 4095 GB4095 GB 4095 GB4095 GB
每个持久性磁盘最大 8 KB IOPSMax 8 KB IOPS per persistent disk 300300 500500
执行最大 IOPS 的磁盘数上限Max number of disks performing max 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
每个帐户的最大带宽(传入 + 传出1Max bandwidth per account (ingress + egress1) <=50 Gbps<=50 Gbps

1“传入”是指发送到存储帐户的所有数据(请求)。1Ingress refers to all data (requests) being sent to a storage account. “传出”是指从存储帐户接收的所有数据(响应)。Egress refers to all data (responses) being 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 1024 GiB (1 TB)1024 GiB (1 TB) 2048 GiB (2 TB)2048 GiB (2 TB) 4095 GiB (4 TB)4095 GiB (4 TB)
每个磁盘的最大 IOPSMax IOPS per disk 500500 23002300 50005000 75007500 75007500
每个磁盘的最大吞吐量Max throughput per disk 100 MB/秒100 MB/s 150 MB/秒150 MB/s 200 MB/秒200 MB/s 250 MB/秒250 MB/s 250 MB/秒250 MB/s
每个存储帐户的磁盘的最大数目Max number of disks per storage account 280280 7070 3535 1717 88

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

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

云服务限制Cloud Services limits

资源Resource 默认限制Default Limit 最大限制Maximum Limit
每个部署的 Web/辅助角色数1Web/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

1包含 Web/辅助角色的每个云服务可以有两个部署,一个用于生产,一个用于过渡。1Each Cloud Service with Web/Worker roles can have two deployments, one for production and one for staging. 另请注意,此限制与不同的角色数目(配置)相关,而不是与每个角色的实例数目(缩放)相关。Also note that this limit refers to the number of distinct roles (configuration) and not the number of instances per role (scaling).

应用服务限制App Service limits

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

资源Resource 免费Free 共享(预览)Shared (Preview) 基本Basic 标准Standard 高级Premium
每个应用服务计划Web 应用、移动应用或 API 应用数1Web, mobile, or API apps per App Service plan1 1010 100100 无限制2Unlimited2 无限制2Unlimited2 无限制2Unlimited2
每个应用服务计划逻辑应用数1Logic apps per App Service plan1 1010 1010 1010 每个核心 20 个20 per core 每个核心 20 个20 per core
应用服务计划App Service plan 每个区域 1 个1 per region 每个资源组 10 个10 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

横向扩展(最大实例数)Scale-Out (max instances) 1 个共享1 shared 1 个共享1 shared 3 个专用33 dedicated3 10 个专用310 dedicated3 20 个专用(50 个在 ASE 中)3,420 dedicated (50 in ASE)3,4
存储5Storage5 1 GB51 GB5 1 GB51 GB5 10 GB510 GB5 50 GB550 GB5 500 GB4,5500 GB4,5

CPU 时间(5 分钟)6CPU time (5 min)6 3 分钟3 minutes 3 分钟3 minutes 无限制,按标准费率付费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
内存(1 小时)Memory (1 hour) 每个应用服务计划 1024 MB1024 MB per App Service plan 每个应用 1024 MB1024 MB per app 不适用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
应用程序体系结构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
每个实例的 Web 套接字数7Web Sockets per instance7 55 3535 350350 不受限制Unlimited 不受限制Unlimited
每个应用程序的并发调试器连接数Concurrent debugger connections per application 11 11 11 55 55
带 FTP/S 和 SSL 的 azurewebsites.net 子域azurewebsites.net subdomain with FTP/S and SSL XX XX XX XX XX
自定义域支持Custom domain support XX XX XX XX
自定义域 SSL 支持Custom domain SSL support 无限制的 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
集成负载均衡器Integrated Load Balancer XX XX XX XX
始终打开Always On XX XX XX
计划备份Scheduled Backups 计划每 2 小时备份一次,每天最多 12 个备份(手动 + 计划)Scheduled backups every 2 hours, a max of 12 backups per day (manual + scheduled) 计划每小时备份一次,每天最多 50 个备份(手动 + 计划)Scheduled backups every hour, a max of 50 backups per day (manual + scheduled)
自动缩放Auto Scale XX XX
WebJobs8WebJobs8 XX XX XX XX XX
Azure 计划程序支持Azure Scheduler support XX XX XX XX
终结点监视Endpoint monitoring XX XX XX
过渡槽Staging Slots 55 2020
每个应用的自定义域数Custom domains per app 500500 500500 500500 500500
SLASLA

99.9%99.9% 99.95%1099.95%10 99.95%999.95%9

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. 有关详细信息,请参阅应用服务定价See App Service Pricing for more details.
4高级层在使用应用服务环境时最多允许 50 个计算实例(取决于可用性)和 500 GB 的磁盘空间,否则为 20 个计算实例和 250 GB 的存储。4Premium tier allows up to 50 computes instances (subject to availability) and 500 GB of disk space when using App Service Environments, and 20 compute instances and 250 GB storage otherwise.
5存储限制是跨相同应用服务计划中所有应用的内容总大小。5The storage limit is the total content size across all apps in the same App Service plan. 应用服务环境中提供了更多存储选项More storage options are available in App Service Environment
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. 可以在应用服务实例中运行的 WebJob 的数量没有预定义的限制,但是存在实际限制,这些限制取决于应用程序代码尝试执行的任务。There is no predefined limit on the number of WebJobs that can run in an App Service instance, but there are practical limits that depend on what the application code is trying to do.
9向使用多个实例和为故障转移配置的 Azure 流量管理器的部署提供 99.95% 的 SLA。9SLA of 99.95% provided for deployments that use multiple instances with Azure Traffic Manager configured for failover.

计划程序限制Scheduler limits

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

资源Resource 限制说明Limit Description
作业大小Job size 最大作业大小为 16K。Maximum job size is 16K. 如果某个作业中的 PUT 或 PATCH 结果大于这些限制,则返回 400 错误请求状态代码。If a PUT or a PATCH results in a job larger than these limits, a 400 Bad Request status code is returned.
请求 URL 大小Request URL size 请求 URL 的最大大小为 2048 个字符。Maximum size of the request URL is 2048 chars.
聚合标头大小Aggregate header size 最大聚合标头大小为 4096 个字符。Maximum aggregate header size is 4096 chars.
标头计数Header count 最大标头计数为 50 个标头。Maximum header count is 50 headers.
正文大小Body size 最大正文大小为 8192 个字符。Maximum body size is 8192 chars.
重复间隔Recurrence span 最大重复间隔为 18 个月。Maximum recurrence span is 18 months.
距离开始时间的时间Time to start time 最大“距离开始时间的时间”为 18 个月。Maximum “time to start time” is 18 months.
作业历史记录Job history 作业历史记录中存储的最大响应正文为 2048 个字节。Maximum response body stored in job history is 2048 bytes.
频率Frequency 默认的最大频率配额在免费作业集合中为 1 小时,在标准作业集合中为 1 分钟。The default max frequency quota is 1 hour in a free job collection and 1 minute in a standard job collection. 在作业集合上,最大频率可配置为小于该最大值。The max frequency is configurable on a job collection to be lower than the maximum. 作业集合中的所有作业都受到对作业集合设置的该值的限制。All jobs in the job collection are limited 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 then request will fail with a 409 Conflict status code.
作业Jobs 默认的最大作业配额在免费作业集合中为 5 个作业,在标准作业集合中为 50 个作业。The default max jobs quota is 5 jobs in a free job collection and 50 jobs in a standard job collection. 在作业集合上,可配置作业的最大数目。The maximum number of jobs is configurable on a job collection. 作业集合中的所有作业都受到对作业集合设置的该值的限制。All jobs in the job collection are limited the value set on the job collection. 如果尝试创建超过最大作业配额数目的更多作业,则请求会失败并且具有 409 冲突状态代码。If you attempt to create more jobs than the maximum jobs quota, then the request fails with a 409 Conflict status code.
作业集合数Job collections 每个订阅的最大作业集合数为 200,000 个。Maximum number of job collection per subscription is 200,000.
作业历史记录保留期Job history retention 作业历史记录保留最多 2 个月或最后 1000 次执行。Job history is retained for up to 2 months or up to the last 1000 executions.
已完成和出错作业的保留期Completed and faulted job retention 完成的作业和出错的作业保留 60 天。Completed and faulted jobs are retained for 60 days.
超时Timeout HTTP 操作的静态(不可配置)请求超时为 60 秒。There’s a static (not configurable) request timeout of 60 seconds for HTTP actions. 对于长时间运行的操作,将遵循 HTTP 异步协议;例如,立即返回 202 但在后台继续工作。For longer running operations, follow HTTP asynchronous protocols; for example, return a 202 immediately but continue working in the background.

Batch 限制Batch limits

资源Resource 默认限制Default Limit 最大限制Maximum Limit
每个区域每个订阅的 Batch 帐户数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 20 - 10020 - 100 5000450004
每个 Batch 帐户的池数Pools per Batch account 20 - 10020 - 100 25002500

备注

默认限制因用于创建 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 可以增加每个批处理帐户的专用核心数,但不指定其最大数目。1 The number of dedicated cores per Batch account can be increased, but the maximum number is unspecified. 请联系 Azure 支持以讨论增加选项。Contact Azure support to discuss increase options.

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

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

4 如果请求增加的配额超出此限制,请与 Azure 支持部门联系。4 Contact Azure support if you want to request an increase beyond this limit.

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 10001000
每个单位的混合连接数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 using 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, please send email to askcosmosdb@microsoft.com.

Mobile Engagement 限制Mobile Engagement limits

资源Resource 最大限制Maximum Limit
应用集合用户App Collection Users 每个应用集合 5 个5 per App Collection
平均数据点数Average Data points 每个活动用户 200 个/天200 per Active User/Day
平均应用信息集数Average App-Info set 每个活动用户 50 个/天50 per Active User/Day
平均推送消息数Average Messages pushed 每个活动用户 20 个/天20 per Active User/Day
段数Segments 每个应用 100 个100 per app
每个段的条件数Criteria per segment 1010
活动推送营销活动数Active Push Campaigns 每个应用 50 个50 per app
推送营销活动总数(包括活动的和已完成的)Total Push Campaigns (includes Active & Completed) 每个应用 1000 个1000 per app

搜索限制Search limits

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

  • 免费层为多租户服务,可与其他 Azure 订阅用户共享,仅用于评估和小型开发项目。Free multi-tenant service, shared with other Azure subscribers, 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 高密度)适用于较大型生产工作负荷。Standard (S1, S2, S3, 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 provisioned at a specific tier, 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 a SKU or tier for Azure Search.

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

资源Resource 免费 1Free 1 基本Basic S1S1 S2S2 S3S3 S3 HDS3 HD
最大服务数Maximum services 11 1212 1212 66 66 66
最大规模(以 SU 为单位) 2Maximum scale in SU 2 不适用N/A 3 SU3 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 搜索单位 (SU) 即计费单位,以副本分区形式分配。2 Search units (SU) 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 基本 1Basic 1 S1S1 S2S2 S3S3 S3 HD 2S3 HD 2
服务级别协议 (SLA) 3Service Level Agreement (SLA) 3 No 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
每个服务的分区数Partitions per service 不适用N/A 11 1212 1212 1212 33
分区大小Partition size 不适用N/A 2 GB2 GB 25 GB25 GB 100 GB100 GB 200 GB200 GB 200 GB200 GB
副本Replicas 不适用N/A 33 1212 1212 1212 1212

1 基本层有一个固定分区。1 Basic has one fixed partition. 此层可以使用额外的 SU,以便在查询工作负荷增加时分配更多的副本。At this tier, additional SUs are used for allocating more replicas for increased query workloads.

2 S3 HD 的硬性限制为 3 个分区,低于 S3 的分区限制。2 S3 HD has a hard limit of 3 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 为可计费服务提供了针对专用资源的服务级别协议 (SLA)。3 Service level agreements (SLAs) 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) SLA. 查询和索引(读-写)SLA 需要不少于三个副本。Three or more replicas are required for query and indexing (read-write) SLA. 分区数不属于 SLA 相关考虑因素。The number of partitions is not 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 are not fixed, you may ask for the quotas to be raised, by opening a support ticket. 不要创建更多的 Azure 媒体服务帐户以求获取更高的限制。Do not create additional Azure Media Services accounts in an attempt to obtain higher limits.

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

1 如果更改类型(例如,从 S1 更改为 S2),则会重置最大 RU 限制。1 If you change the type (for example, from S2 to S1,) the max RU limits are reset.

2 这个数字包括已排队的、已完成的、活动的和已取消的作业。2 This number includes queued, finished, active, and canceled jobs. 不包括已删除的作业。It does not include deleted jobs. 可以使用 IJob.DeleteDELETE HTTP 请求删除旧作业。You can delete the old jobs 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 will be automatically deleted, along with its associated Task records, even if the total number of records is below the maximum quota. 在需要时,可使用此处所述的代码存档作业/任务信息。If you need to archive the job/task information, you can use the code described here.

3 发出列出作业实体的请求时,每个请求最多返回 1,000 个作业。3 When making a request to list Job entities, a maximum of 1,000 jobs is returned per request. 如果需要跟踪所有已提交的作业,可以使用 top/skip,如 OData 系统查询选项中所述。If you need to keep track of all submitted Jobs, you can use top/skip as described in OData system query options.

4 定位符不用于管理按用户的访问控制。4 Locators are not designed for managing per-user access control. 要为不同用户提供不同的访问权限,请使用数字权限管理 (DRM) 解决方案。To give different access rights to individual users, use Digital Rights Management (DRM) solutions. 有关详细信息,请参阅部分。For more information, see this section.

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

6 不同的 AMS 策略限制为 1,000,000 个(例如,对于定位器策略或 ContentKeyAuthorizationPolicy)。6 There is a limit of 1,000,000 policies for different AMS policies (for example, for Locator policy or ContentKeyAuthorizationPolicy).

备注

如果经常使用相同的天数/访问权限等,则应使用相同的策略 ID。有关信息和示例,请参阅部分。You should use the same policy ID if you are always using the same days / access permissions / etc. For information and an example, see this section.

7如果要将内容上传到 Azure 媒体服务中的资产,并且意图是要使用 Microsoft 服务中的媒体处理器之一(例如,Media Encoder Standard 和 Media Encoder Premium Workflow 等编码器,或者 Face Detector 等分析引擎)对此内容进行处理,则应注意支持的最大大小约束。7If you are uploading content to an Asset in Azure Media Services to process it with one of the media processors in the service (that is, encoders like Media Encoder Standard and Media Encoder Premium Workflow, or analysis engines like Face Detector), then you should be aware of the constraints on the maximum file sizes supported.

在 Azure Blob 存储中,单个 Blob 目前支持的最大大小为 5 TB。The maximum size supported for a single blob is currently up to 5 TB in Azure Blob Storage. 但是,Azure 媒体服务会根据服务使用的 VM 大小应用其他限制。However, additional limits apply in Azure Media Services based on the VM sizes that are used by the service. 下表显示了每个媒体保留单位(S1、S2、S3)的限制。如果源文件大于表中定义的限制,则编码作业将会失败。The following table shows the limits on each of the Media Reserved Units (S1, S2, S3.) If your source file is larger than the limits defined in the table, your encoding job will fail. 编码持续时间较长的 4K 分辨率源时,需要使用 S3 媒体保留单位才能达到所需的性能。If you are encoding 4K resolution sources of long duration, you are required to use S3 Media Reserved Units to achieve the performance needed. 如果 4K 内容超过了针对 S3 媒体保留单位应用的 260 GB 限制,请通过 amshelp@microsoft.com 联系我们,我们会提供可能的缓解措施来支持你的方案。If you have 4K content that is larger than 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 325325
S2S2 640640
S3S3 260260

CDN 限制CDN limits

资源Resource 默认限制Default limit 最大限制Maximum limit
CDN 配置文件CDN profiles 2525 2525
每个配置文件的 CDN 终结点数CDN endpoints per profile 1010 2525
每个终结点的自定义域数Custom domains per endpoint 1010 2525

一个 CDN 订阅可以包含一个或多个 CDN 配置文件,一个 CDN 配置文件可以包含一个或多个 CDN 终结点。A CDN subscription can contain one or more CDN profiles and a CDN profile can contain one or more CDN endpoints. 可能希望通过 Internet 域、Web 应用程序或某些其他条件来使用多个配置文件,以组织 CDN 终结点。You may wish to use multiple profiles to organize your CDN endpoints by internet domain, web application, or some other criteria.

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

移动服务限制Mobile Services limits

层:TIER: 免费FREE 基本BASIC 标准STANDARD
API 调用API Calls 500 K500 K 1.5 M/单位1.5 M / unit 15 M/单位15 M / unit
活动设备数Active Devices 500500 不受限制Unlimited 不受限制Unlimited
缩放Scale 不适用N/A 最多 6 个单位Up to 6 units 单位数不受限制Unlimited units
推送通知Push Notifications 包含通知中心免费层,最多 100 万次推送Notification Hubs Free Tier included, up to 1 M pushes 包含通知中心基本层,最多 1000 万次推送Notification Hubs Basic Tier included, up to 10 M pushes 包含通知中心标准层,最多 1000 万次推送Notification Hubs Standard Tier included, up to 10 M pushes
实时消息传送/Real time messaging/
Web 套接字Web Sockets
受限制Limited 350 / 移动服务350 / mobile service 不受限制Unlimited
脱机同步Offline synchronizations 受限制Limited 附送Included 附送Included
计划的作业Scheduled jobs 受限制Limited 附送Included 附送Included
SQL 数据库(必需)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 / day 不受限制Unlimited 不受限制Unlimited
出站数据传输Outbound data transfer 每天 165 MB(每日滚动更新)165 MB per day (daily Rollover) 附送Included 附送Included

有关这些限制的更多详细信息以及有关定价的信息,请参阅移动服务定价For additional details on these limits and for information on pricing, see Mobile Services Pricing.

监视限制Monitor limits

资源Resource 默认限制Default Limit 最大限制Maximum Limit
自动缩放设置Autoscale Settings 每个区域每个订阅的 100 个数目100 per region per subscription 与默认值相同same as default
指标警报Metric Alerts 每个订阅 100 个活动警报规则100 active alert rules per subscription 致电支持人员call support
准实时警报(预览版)Near-Real Time Alerts (Preview) 每个订阅 20 个活动警报规则20 active alert rules per subscription 在预览期间的默认值相同same as default during preview

通知中心服务限制Notification Hub Service limits

层:TIER: 免费FREE 基本BASIC 标准STANDARD
包括的推送数Included Pushes 100 万1 Million 1000 万10 Million 1000 万10 Million
活动设备数Active Devices 500500 200,000200,000 1 千万10 million
每次安装/注册的标记配额Tag quota per installation/registration 6060 6060 6060

有关这些限制的更多详细信息以及有关定价的信息,请参阅通知中心定价For additional details on these limits and for information on 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 per namespace 命名空间Namespace 创建新事件中心的后续请求会被拒绝。Subsequent requests for creation of a new event hub will be 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 will be rejected and an exception is received by the calling code. 5,0005,000
事件中心事件的最大大小Maximum size of Event Hubs event 实体Entity - 256 KB256 KB
事件中心名称的最大大小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 超出吞吐量单位限制会导致数据受到限制,并生成 ServerBusyExceptionExceeding the throughput unit limit causes your data to be throttled and generates a ServerBusyException. 可以通过填写支持请求为标准层请求更多的吞吐量单位。You can request a larger number of throughput units for a Standard tier by filing 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 will be rejected. 1212

服务总线限制Service Bus limits

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

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

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

如果已启用分区,最大队列/主题大小是 80 GB。If partitioning is enabled, the maximum queue/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 do not count towards concurrent TCP connections. NetMessaging:1,000NetMessaging: 1,000

AMQP:5,000AMQP: 5,000
队列/主题/订阅实体上的并发接收请求数Number of concurrent receive requests on a queue/topic/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/queues per service namespace 命名空间Namespace 系统将拒绝后续的在服务命名空间中创建新主题或队列的请求。Subsequent requests for creation of a new topic or queue on the service 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. 10,00010,000

服务命名空间中主题和队列的数目之和必须小于或等于 10,000。The total number of topics plus queues in a service namespace must be less than or equal to 10,000.
这不适用于高级层,因为其中的所有实体已分区。This is not applicable to Premium as all entities are partitioned.
每个服务命名空间的分区主题/队列数Number of partitioned topics/queues per service namespace 命名空间Namespace 系统将拒绝后续的在服务命名空间中创建新分区主题或队列的请求。Subsequent requests for creation of a new partitioned topic or queue on the service 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, a QuotaExceededException exception is received by the calling code. 基本和标准层 - 100Basic and Standard Tiers - 100
高级 - 1,000(每个消息传送单元)Premium - 1,000 (per messaging unit)

在每个命名空间中,每个分区队列或主题的实体配额不会超过 10,000 个。Each partitioned queue or topic counts towards the quota of 10,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
队列/主题/订阅实体的消息大小Message size for a queue/topic/subscription entity 实体Entity 会拒绝超过这些配额的传入消息,且调用代码会收到异常。Incoming messages that exceed these quotas are rejected and an exception is received by the calling code. 最大消息大小:256 KB(标准层)/1 MB(高级层)。Maximum message size: 256 KB (Standard tier) / 1 MB (Premium tier).

注意由于系统开销问题,此限制通常略小一点。Note Due to system overhead, this limit is usually slightly less.

最大标头大小:64 KBMaximum header size: 64 KB

属性包中的最大标头属性数:byte/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/subscription entity 实体Entity 将生成 SerializationException 异常。A SerializationException exception is generated. 每个属性的最大消息属性大小为 32 K。所有属性的累计大小不得超过 64 K。这一点适用于整个 BrokeredMessage 标头,其中既有用户属性,又有系统属性(如 SequenceNumberLabelMessageId 等)。Maximum message property size for each property is 32 K. Cumulative size of all properties cannot exceed 64 K. This applies to the entire header of the BrokeredMessage, which has both user properties as well as system properties (such as SequenceNumber, Label, MessageId, and so on).
每个主题的订阅数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. 2,0002,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/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: 1024 (1K).

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

每个规则操作的最大表达式数: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, F1). 有关每个层中每个单位的成本信息,请参阅 IoT 中心定价For information about the cost of each unit in each tier, see 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 11

备注

如果希望在 S1 或 S2 层的中心内使用超过 200 个单位,或者在 S3 层的中心内使用超过 10 个单位,请联系 Microsoft 支持部门。If you anticipate using more than 200 units with an S1 or S2 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 1010
每个 Azure 订阅的免费 IoT 中心数上限Maximum free IoT hubs per Azure subscription 11
设备 ID 的最大字符数Maximum number of characters in a Device Id 128128
设备标识的最大数目Maximum number of device identities
在单个调用中返回returned in a single call
10001000
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 256 KB256 KB
设备到云消息批中的消息数上限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
messagesmessages
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, S3)
最大消息路由规则数Maximum message routing rules 100(适用于 S1、S2、S3)100 (for S1, S2, S3)

备注

如果需要在 Azure 订阅中有 10 个以上的付费 IoT 中心,请联系 Microsoft 支持。If you need more than 10 paid IoT hubs in an Azure subscription, contact Microsoft support.

备注

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

超过以下配额时,IoT 中心服务将限制请求:The IoT Hub service throttles requests when the following quotas are exceeded:

限制Throttle 每个中心的值Per-hub value
标识注册表操作Identity registry operations
(创建、检索、列表、更新、删除),(create, retrieve, list, update, delete),
单个或批量导入/导出individual or bulk import/export
83.33/秒/单位(5000/分钟/单位)(适用于 S3)83.33/sec/unit (5000/min/unit) (for S3)
1.67/秒/单位(100/分钟/单位)(适用于 S1 和 S2)。1.67/sec/unit (100/min/unit) (for S1 and S2).
设备连接Device connections 6000/秒/单位(适用于 S3),120/秒/单位(适用于 S2),12/秒/单位(适用于 S1)。6000/sec/unit (for S3), 120/sec/unit (for S2), 12/sec/unit (for S1).
最小值为 100/秒。Minimum of 100/sec.
设备到云的发送Device-to-cloud sends 6000/秒/单位(适用于 S3),120/秒/单位(适用于 S2),12/秒/单位(适用于 S1)。6000/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/秒/单位(5000/分钟/单位)(适用于 S3),1.67/秒/单位(100/分钟/单位)(适用于 S1 和 S2)。83.33/sec/unit (5000/min/unit) (for S3), 1.67/sec/unit (100/min/unit) (for S1 and S2).
云到设备的接收Cloud-to-device receives 833.33/秒/单位(50000/分钟/单位)(适用于 S3),16.67/秒/单位(1000/分钟/单位)(适用于 S1 和 S2)。833.33/sec/unit (50000/min/unit) (for S3), 16.67/sec/unit (1000/min/unit) (for S1 and S2).
文件上传操作File upload operations 83.33 个文件上传通知/秒/单位(5000/分钟/单位)(适用于 S3),1.67 个文件上传通知/秒/单位(100/分钟/单位)(适用于 S1 和 S2)。83.33 file upload notifications/sec/unit (5000/min/unit) (for S3), 1.67 file upload notifications/sec/unit (100/min/unit) (for S1 and S2).
Azure 存储帐户一次可传出 10000 个 SAS URI。10000 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 24MB/秒/单位(适用于 S3)、480KB/秒/单位(适用于 S2)、160KB/秒/单位(适用于 S1)24MB/sec/unit (for S3), 480KB/sec/unit (for S2), 160KB/sec/unit (for S1)
基于 8KB 限制计量大小。Based on 8KB throttling meter size.
设备孪生读取Device twin reads 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 twin updates 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)
作业操作Jobs operations
(创建、更新、列表、删除)(create, update, list, delete)
83.33/秒/单位(5000/分钟/单位)(适用于 S3),1.67/秒/单位(100/分钟/单位)(适用于 S2),1.67/秒/单位(100/分钟/单位)(适用于 S1)83.33/sec/unit (5000/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)

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

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

资源Resource 限制Limit
每个 Azure 订阅的最大设备预配服务数Maximum Device Provisioning Services per Azure subscription 1010
最大登记数Maximum number of enrollments 10,00010,000
最大注册数Maximum number of registrations 10,00010,000
最大登记组数Maximum number of enrollment groups 100100
最大 CA 数Maximum number of CAs 1010

备注

可联系 Microsoft 支持部门,要求增加订阅中的实例数。You can contact Microsoft Support to increase the number of instances in your subscription.

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

限制Throttle 单服务值Per-service value
操作Operations 100/分钟100/min
设备注册数Device registrations 100/分钟100/min

数据工厂限制Data Factory limits

数据工厂是一项多租户服务,具有以下默认限制,目的是确保客户订阅不受彼此工作负荷的影响。Data factory is a multi-tenant service that has the following default limits in place to make sure customer subscriptions are protected from each other's workloads. 订阅的许多限制只需联系支持部门即可提高,最多可提高到最大限制。Many of the limits can be easily raised for your subscription up to the maximum limit by contacting support.

版本 2Version 2

资源Resource 默认限制Default Limit 最大限制Maximum Limit
Azure 订阅中的数据工厂Data factories in an Azure subscription 5050 联系支持人员Contact support
数据工厂中的管道Pipelines within a data factory 25002500 联系支持人员Contact support
数据工厂中的数据集Datasets within a data factory 25002500 联系支持人员Contact support
数据工厂中的触发器Triggers within a data factory 25002500 联系支持人员Contact support
数据工厂中的关联服务Linked services within a data factory 25002500 联系支持人员Contact support
数据工厂中的集成运行时 4Integration runtimes within a data factory 4 25002500 联系支持人员Contact support
每个管道的并行管道运行Concurrent pipeline runs per pipeline 2020 联系支持人员Contact support
每个管道的最大活动数Max activities per pipeline 2020 3030
每个管道的最大参数个数Max parameters per pipeline 2020 3030
管道对象的每个对象字节数 1Bytes per object for pipeline objects 1 200 KB200 KB 200 KB200 KB
数据集和关联服务对象的每个对象字节数 1Bytes per object for dataset and linked service objects 1 100 KB100 KB 2000 KB2000 KB
云数据移动单位 3Cloud data movement units 3 256256 联系支持人员Contact support
管道活动运行的重试次数Retry count for pipeline activity runs 1 天(超时)1 day(timeout) 1 天(超时)1 day (timeout)
编写 API 调用Write API calls 2500/小时2500/hr

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

此限制是由 Azure 资源管理器而不是 Azure 数据工厂所强加的。This limit is imposed by Azure Resource Manager, not Azure Data Factory.
联系支持人员Contact support

版本 1Version 1

资源Resource 默认限制Default Limit 最大限制Maximum Limit
Azure 订阅中的数据工厂Data factories in an Azure subscription 5050 联系支持人员Contact support
数据工厂中的管道Pipelines within a data factory 25002500 联系支持人员Contact support
数据工厂中的数据集Datasets within a data factory 50005000 联系支持人员Contact support
每个数据集的并发切片数Concurrent slices per dataset 1010 1010
管道对象的每个对象字节数 1Bytes per object for pipeline objects 1 200 KB200 KB 200 KB200 KB
数据集和关联服务对象的每个对象字节数 1Bytes per object for dataset and linked service objects 1 100 KB100 KB 2000 KB2000 KB
订阅中的 HDInsight 按需群集核心数 2HDInsight on-demand cluster cores within a subscription 2 6060 联系支持人员Contact support
云数据移动单位 3Cloud data movement units 3 3232 联系支持人员Contact support
管道活动运行的重试次数Retry count for pipeline activity runs 10001000 MaxInt(32 位)MaxInt (32 bit)

1 管道、数据集和链接服务对象代表工作负荷的逻辑组。1 Pipeline, dataset, and linked service objects represent a logical grouping of your workload. 对这些对象的限制与可以使用 Azure 数据工厂服务移动或处理的数据量无关。Limits for these objects do not relate to amount of data you can move and process with the Azure Data Factory service. 可以缩放数据工厂以处理 PB 量级的数据。Data factory is designed to scale to handle petabytes of data.

2 按需 HDInsight 核心数从包含数据工厂的订阅中分配。2 On-demand HDInsight cores are allocated out of the subscription that contains the data factory. 因此,上述限制是数据工厂针对按需 HDInsight 核心强制实施的核心限制,不同于与 Azure 订阅关联的核心限制。As a result, the above limit is the Data Factory enforced core limit for on-demand HDInsight cores and is different from the core limit associated with your Azure subscription.

3 云数据移动单位 (DMU) 用于云到云复制操作。3 Cloud data movement unit (DMU) is being used in a cloud-to-cloud copy operation. 它是一种度量单位,代表单个单位在数据工厂中的能力(包含 CPU、内存、网络资源分配)。It is a measure that represents the power (a combination of CPU, memory, and network resource allocation) of a single unit in Data Factory. 就某些方案来说,使用更多 DMU 可以提高复制吞吐量。You can achieve higher copy throughput by using more DMUs for some scenarios. 请参阅云数据移动单位 (V2)云数据移动单位 (V1)部分,了解详细信息。Refer to Cloud data movement units (V2) and Cloud data movement units (V1) section on details.

4 集成运行时 (IR) 是 Azure 数据工厂用于在不同的网络环境之间提供以下数据集成功能的计算基础结构:数据移动、调度活动来计算服务,SSIS 包的执行。4 The Integration Runtime (IR) is the compute infrastructure used by Azure Data Factory to provide the following data integration capabilities across different network environments: data movement, dispatching activities to compute services, 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

数据湖分析让管理分布式基础结构和复杂代码等复杂任务变得容易。Data Lake Analytics makes the complex task of managing distributed infrastructure and complex code easy. 它能动态地预配资源并让你以百亿亿字节为单位进行分析。It dynamically provisions resources and lets you do analytics on exabytes of data. 当作业完成时,它自动释放资源,仅需为所用的处理功能付费。When the job completes, it winds down resources automatically, and you pay only for the processing power used. 增加或减少存储数据的大小或使用的计算量时,不需要重写代码。As you increase or decrease the size of data stored or the amount of compute used, you don’t have to rewrite code. 订阅的许多默认限制只需联系支持部门即可提高。Many of the default limits can be easily raised for your subscription by contacting 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 支持以增加此限制。Contact Microsoft support to increase this limit.
提交作业时的最大脚本大小Maximum script size for job submission 3 MB3 MB
每个区域每个订阅的最大 ADLA 帐户数Maximum number of ADLA accounts per region per subscription 55 请联系 Microsoft 支持以增加此限制。Contact Microsoft support to increase this limit.

Data Lake Store 限制Data Lake Store limits

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

资源Resource 默认限制Default Limit 注释Comments
Data Lake Store 帐户的最大数量,每个订阅,每个区域Max number of Data Lake Store accounts, per subscription, per region 1010 联系支持人员以请求增加此上限Contact Support to request an increase for this limit
每个文件或文件夹的最大访问 ACL 数Max number of access ACLs, per file or folder 3232 这是硬性限制。This is a hard limit. 使用组来管理访问权限,减少条目数量Use groups to manage access with fewer entries
每个文件或文件夹的最大默认 ACL 数Max 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 数据平台的无缝迁移,并且最小化停机时间。The 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 联系支持人员以请求增加此上限Contact Support to request an increase for this limit

流分析限制Stream Analytics limits


限制标识符Limit identifier 限制Limit 注释Comments
每个区域每个订阅的最大流式处理单位数目Maximum number of Streaming Units per subscription per region 200200 增加订阅的流单元数超过 200 的请求可通过联系 Microsoft 支持部门发出。A request to increase streaming units for your subscription beyond 200 can be made by contacting Microsoft Support.
每个作业的最大输入数目Maximum number of inputs per job 6060 每个流分析作业存在 60 个输入的硬性限制。There is a hard limit of 60 inputs per Stream Analytics job.
每个作业的最大输出数目Maximum number of outputs per job 6060 每个流分析作业存在 60 个输出的硬性限制。There is a hard limit of 60 outputs per Stream Analytics job.
每个作业的最大函数数目Maximum number of functions per job 6060 每个流分析作业存在 60 个函数的硬性限制。There is a hard limit of 60 functions per Stream Analytics job.
每个作业的最大流式处理单位数Maximum number of Streaming Units per job 120120 每个流分析作业存在 120 个流式处理单位的硬性限制。There is a hard limit of 120 Streaming Units per Stream Analytics job.
每个区域的最大作业数目Maximum number of jobs per region 15001500 每个地理区域的每个订阅最多可有 1500 个作业。Each subscription may have up to 1500 jobs per geographical region.
引用数据 blob MBReference data blob MB 100100 引用数据 blob 每个不能大于 100 MB。Reference data blobs cannot be larger than 100 MB each.

Active Directory 限制Active Directory limits

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

类别Category 限制Limits
目录Directories 单个用户只能与最多 20 个 Azure Active Directory 目录相关联。A single user can only be associated with a maximum of 20 Azure Active Directory directories.
可能的组合的示例:Examples of possible combinations:
  • 单个用户创建了 20 个目录。A single user creates 20 directories.
  • 单个用户以成员身份添加到 20 个目录。A single user is added to 20 directories as a member.
  • 单个用户创建了 10 个目录,之后其他人又将该用户添加到 10 个不同的目录。A single user creates 10 directories and later is added by others to 10 different directories.
对象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.
架构扩展Schema extensions
  • String 类型扩展最多只能有 256 个字符。String type extensions can have maximum of 256 characters.
  • Binary 类型扩展限制在 256 字节以内。Binary type extensions are limited to 256 bytes.
  • 100 扩展值(在 ALL 类型和 ALL 应用程序中)可以编写到任何单一对象中。100 extension values (across ALL types and ALL applications) can be written to any single object.
  • 仅“用户”、“组”、“TenantDetail”、“设备”、“应用程序”和“ServicePrincipal” 实体可以用“String”类型或“Binary”类型单一值属性进行扩展。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 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.
  • Azure Active Directory 中的单个组可以具有任意数量的对象。Any number of objects can be members of a single group in Azure Active Directory.
  • 使用 Azure Active Directory 目录同步 (DirSync) 时,一个小组中从本地 Active Directory 同步到 Azure Active Directory 的成员数目仅限 15000。The number of members in a group you can synchronize from your on-premises Active Directory to Azure Active Directory is limited to 15K members, using Azure Active Directory Directory Synchronization (DirSync).
  • 使用 Azure AD Connect 时,一个小组中从本地 Active Directory 同步到 Azure Active Directory 的成员数目仅限 50000。The number of members in a group you can synchronize from your on-premises Active Directory to Azure Active Directory using Azure AD Connect is limited to 50K members.
访问面板Access Panel
  • 对应用程序的数量没有限制,应用程序可在每位获得 Azure AD Premium 或企业移动套件许可的最终用户的“访问面板”中查看。There is no limit to the number of applications that can be seen in the Access Panel per end user, for users assigned licenses for Azure AD Premium or the Enterprise Mobility Suite.
  • 每位获得免费版或 Azure AD 基本版 Azure Active Directory 许可的最终用户最多可在“访问面板”中查看 10 个应用磁贴(例如:Box、Salesforce 或 Dropbox)。A maximum of 10 app tiles (examples: Box, Salesforce, or Dropbox) can be seen in the Access Panel for each end user for users assigned licenses for Free or Azure AD Basic editions of Azure Active Directory. 此限制不适用于管理员帐户。This limit does not 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.

Azure 事件网格限制Azure Event Grid limits

资源Resource 限制Limit
单个区域的事件订阅数Event Subscriptions per region 10001000
单个区域的自定义主题数Custom Topics per region 2020

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 一周中每天每小时一个计划 (24*7)。A schedule for every hour, every day of the week (24*7).
物理设备上分层卷的大小上限Maximum size of a tiered volume on physical devices 64 TB(对于 8100 和 8600)64 TB for 8100 and 8600 8100 和 8600 是物理设备。8100 and 8600 are physical devices.
Azure 中虚拟设备上的分层卷的大小上限Maximum size of a tiered volume on virtual devices in Azure 30 TB(对于 8010)30 TB for 8010
64 TB(对于 8020)64 TB for 8020
8010 和 8020 是 Azure 中的虚拟设备,分别使用标准存储和高级存储。8010 and 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(对于 8100)9 TB for 8100
24 TB(对于 8600)24 TB for 8600
8100 和 8600 是物理设备。8100 and 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 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 will be processed sequentially as processing slots become available.
  • 在完成操作之前,无法为克隆或还原的分层卷创建新备份。New backups of a cloned or a restored tiered volume cannot occur until the operation is finished. 但是,对于本地卷,在卷联机后可以备份。However, 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 restore or clone operation, regardless of the volume size.
  • 卷性能一开始可能比正常情况下缓慢,因为大部分数据和元数据仍在云中。The volume performance may initially be slower than normal as most of the data and metadata still resides in the cloud. 随着数据从云流向 StorSimple 设备,性能可能会得到提升。Performance may 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 may 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 cannot 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 may initially be slower than normal as most of the data and metadata still resides in the cloud. 随着数据从云流向 StorSimple 设备,性能可能会得到提升。Performance may 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 may be affected by Internet bandwidth to the cloud.
  • 本地固定卷与分层卷不同,其卷数据也会下载到本地设备。Unlike tiered volumes, in the case of 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 may 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)* 920/720 MB/s,使用单个 10GbE 网络接口920/720 MB/s with a single 10GbE network interface 最多为 2 倍,使用 MPIO 和两个网络接口。Up to 2x with MPIO and two network interfaces.
最大客户端读取/写入吞吐量(从 HDD 层提供服务时)*Maximum client read/write throughput (when served from the HDD tier)* 120/250 MB/s120/250 MB/s
最大客户端读取/写入吞吐量(从云层提供服务时)*Maximum client read/write throughput (when served from the cloud tier)* 11/41 MB/s11/41 MB/s 读取吞吐量取决于生成和维护足够的 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 may be lower and depends on I/O mix and network conditions.

Log Analytics 限制Log Analytics limits

下列限制适用于每个订阅的 Log Analytics 资源:The following limits apply to Log Analytics resources per subscription:

资源Resource 默认限制Default Limit 注释Comments
每个订阅的免费工作区数目Number of free workspaces per subscription 1010 无法提高此限制。This limit cannot be increased.
每个订阅的付费工作区数目Number of paid workspaces per subscription 不适用N/A 受到的限制包括一个资源组中的资源数,以及一个订阅的资源组数You are limited by the number of resources within a resource group and number of resource groups per subscription

备注

截止 2018 年 4 月 2 日,新订阅中的新工作区将自动使用“每 GB”定价计划。As of April 2, 2018, new workspaces in a new subscription will automatically use the Per GB pricing plan. 对于在 4 月 2 日之前创建的现有订阅,或者是已绑定到现有 EA 注册的订阅,对于新工作区,可以继续在三个定价层之间进行选择。For existing subscriptions created before April 2, or a subscription that was tied to an existing EA enrollment, you can continue choosing between 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 month 2 1 个月21 month 2

1当客户达到其 500 MB 的每日数据传输限制时,数据分析会停止,并在下一日开始时恢复。1 When 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 天。2 The 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 MBMaximum size for a single post is 30 MB
字段值的最大大小为 32 KBMaximum 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 条记录5000 records returned for non-aggregated data
针对聚合数据返回 500000 条记录500000 records for aggregated data
聚合数据是指包含 measure 命令的搜索Aggregated data is a search that includes the measure command

备份限制Backup limits

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

限制标识符Limit Identifier 默认限制Default Limit
可针对每个保管库注册的服务器/计算机数量Number of servers/machines that can be registered against each vault 对于 Windows Server/客户端/SCDPM 为 50 个50 for Windows Server/Client/SCDPM
对于 IaaS VM 为 200 个200 for IaaS VMs
存储在 Azure 保管库存储中的数据的数据源大小Size of a data source for data stored in Azure vault storage 最大 54400 GB154400 GB max1
可在每个 Azure 订阅中创建的备份保管库的数目Number of backup vaults that can be created in each Azure subscription 每个区域 25 个恢复服务保管库25 Recovery Services vaults per region
每天计划备份的次数Number of times backup can be scheduled per day 对于 Windows Server/客户端为每天 3 个3 per day for Windows Server/Client
对于 SCDPM 为每天 2 个2 per day for SCDPM
对于 IaaS Vm 为每天 1 个Once a day for IaaS VMs
将数据磁盘附加到 Azure 虚拟机进行备份Data disks attached to an Azure virtual machine for backup 1616
附加到 Azure 虚拟机以进行备份的单个数据磁盘的大小Size of individual data disk attached to an Azure virtual machine for backup 4095 GB 24095 GB 2
  • 154400 GB 限制不适用于 IaaS VM 备份。1The 54400 GB limit does not apply to IaaS VM backup.

站点恢复限制Site Recovery limits

以下限制适用于 Azure 站点恢复:The following limits apply to Azure Site Recovery:

限制标识符LIMIT IDENTIFIER 默认限制DEFAULT LIMIT
每个订阅的保管库数Number of vaults per subscription 2525
每个 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, you can increase the limit up to 1,000 GB from the portal. 如需大于 1,000 GB 的容量,请将邮件发送到 AIDataCap@microsoft.com。For capacities greater than 1,000 GB, send mail to AIDataCap@microsoft.com.
每月免费数据量Free data per month
(基本价格计划)(Basic price plan)
1 GB1 GB 额外的数据按千兆字节收费。Additional data is charged per gigabyte.
限制Throttling 32000 个事件/秒32 k 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 K64 K
属性和指标名称长度Property and metric name length 150150 请参阅类型架构See type schemas
属性值字符串长度Property value string length 8,1928,192 请参阅类型架构See type schemas
跟踪和异常消息长度Trace and exception message length 10 k10 k 请参阅类型架构See type schemas
每个应用的可用性测试计数Availability tests count per app 100100
探查器数据保留期Profiler data retention 5 天5 days
每天发送的探查器数据量Profiler data sent per day 10GB10GB

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

API 管理限制API Management limits

资源Resource 限制Limit
缩放单位Units of scale 每个区域 10 个110 per region1
缓存Cache 每个单位 5 GB15 GB per unit1
每个 HTTP 颁发机构的并行后端连接2Concurrent backend connections2 per HTTP authority 每个单位 2048 个32048 per unit3
最大缓存响应大小Maximum cached response size 10MB10MB
最大自定义网关域Maximum custom gateway domains 每个服务实例 20 个420 per service instance4

1每个定价层的 API 管理限制不同。1API Management limits are different for each pricing tier. 若要查看定价层及其缩放限制,请转到 API 管理定价To see the pricing tiers and their scaling limits go to API Management Pricing. 2 除非后端明确关闭,否则将合并并重新使用连接。2 Connections are pooled and re-used, unless explicitly closed by the backend. 3 每个单位的基本、标准和高级级别。3 Per unit of Basic, Standard and Premium tiers. 开发人员层限制为 1024。Developer tier is limited to 1024. 4 仅高级层中可用。4 Available in Premium tier only.

Azure Redis 缓存限制Azure Redis Cache limits

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

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

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

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

密钥保管库限制Key Vault limits

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

密钥类型Key type HSM-KeyHSM-Key
CREATE 密钥CREATE Key
HSM-keyHSM-key
所有其他事务All other transactions
Software-keySoftware-key
CREATE 密钥CREATE Key
Software-keySoftware-key
所有其他事务All other transactions
RSA 2048 位RSA 2048-bit 55 10001000 1010 20002000
RSA 3072 位RSA 3072-bit 55 250250 1010 500500
RSA 4096 位RSA 4096-bit 55 125125 1010 250250
ECC P-256ECC P-256 55 10001000 1010 20002000
ECC P-384ECC P-384 55 10001000 1010 20002000
ECC P-521ECC P-521 55 10001000 1010 20002000
ECC SECP256K1ECC SECP256K1 55 10001000 1010 20002000

机密、托管存储帐户密钥,以及保管库事务:Secrets, Managed Storage Account Keys, and vault transactions:

事务类型Transactions Type 每个区域的每个保管库在 10 秒内允许的事务数上限1Max transactions allowed in 10 seconds, per vault per region1
所有事务All transactions 20002000

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

1 所有事务类型都没有订阅范围的限制,即每个密钥保管库限制的 5 倍。1 There is a subscription-wide limit for all transaction types, that is 5x per key vault limit. 例如,每个订阅的 HSM- 其他事务数限制为 10 秒内 5000 个事务。For example, HSM- other transactions per subscription are limited to 5000 transactions in 10 seconds per subscription.

多重身份验证Multi-Factor Authentication

资源Resource 默认限制Default Limit 最大限制Maximum Limit
每个订阅的最大可信 IP 地址/范围数Max number of Trusted IP addresses/ranges per subscription 00 5050
记住我的设备 - 天数Remember my devices - number of days 1414 6060
应用密码的最大数目?Max number of app passwords? 00 无限制No Limit
MFA 调用期间允许 X 次尝试Allow X attempts during MFA call 11 9999
双向短信超时秒数Two-way Text message Timeout Seconds 6060 600600
默认一次性跳过秒数Default one-time bypass seconds 300300 18001800
X 次连续 MFA 拒绝后锁定用户帐户Lock user account after X consecutive MFA denials 未设置Not Set 9999
X 分钟后重置帐户锁定计数器Reset account lockout counter after X minutes 未设置Not Set 99999999
X 分钟后解锁帐户Unlock account after X minutes 未设置Not Set 99999999

自动化限制Automation limits

资源Resource 最大限制Maximum Limit
每个自动化帐户每 30 秒可以提交的新作业的最大数量(非计划的作业)Max number of new jobs that can be submitted every 30 seconds per Automation Account (non Scheduled jobs) 100100
每个自动化帐户相同时间实例并发运行的作业的最大数量(非计划的作业)Max number of concurrent running jobs at the same instance of time per Automation Account (non Scheduled jobs) 200200
每个自动化帐户每 30 秒可以导入的模块的最大数量Max number of modules that can be imported every 30 seconds per Automation Account 55
一个模块的最大大小Max size of a Module 100 MB100 MB
作业运行时间 - 免费层Job Run Time - Free tier 每个订阅每个日历月 500 分钟500 minutes per subscription per calendar month
给定到作业的最大内存量 1Max amount of memory given to a job 1 400 MB400 MB
每个作业允许的最大网络套接字数量 1Max number of network sockets allowed per job 1 10001000
订阅中自动化帐户的最大数目Max number of Automation Accounts in a subscription 无限制No Limit

1 这些限制仅适用于 Azure 中的沙盒,对于混合辅助角色,这些仅受混合辅助角色所在的计算机的功能限制。1 These limits apply only to the sandboxes in Azure, for Hybrid workers these are only limited by the capabilities of the machine where the hybrid worker is located.

SQL 数据库限制SQL Database limits

有关 Azure SQL 数据库限制,请参阅 SQL 数据库资源限制For SQL Database limits, see SQL Database Resource Limits.

SQL 数据仓库限制SQL Data Warehouse limits

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

另请参阅See also

Understanding Azure Limits and Increases(了解 Azure 的限制和增加)Understanding Azure Limits and Increases

Azure 的虚拟机和云服务大小Virtual Machine and Cloud Service Sizes for Azure

云服务的大小Sizes for Cloud Services