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

本文列出了一些最常见的 Azure 限制,有时也称为配额。This document lists some of the most common 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 定价概述To learn more about Azure pricing, see 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).

Note

如果想要提高限制或配额,使其超出默认限制,可以打开免费的联机客户支持请求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.

试用订阅Trial subscriptions.

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

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

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

Note

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

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

服务特定的限制Service-specific limits

订阅限制Subscription limits

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

资源Resource 默认限制Default Limit 最大限制Maximum Limit
每个订阅的 vCPU 数量 1vCPUs per 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 200200
每个订阅的 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特小实例作为一个 vCPU 至 vCPU 限制计数,即使使用了部分 CPU 核心。1Extra Small instances count as one vCPU towards the vCPU limit despite using a partial CPU 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 given region, make a request through Azure Support. Azure 存储团队将评审业务案例,对于特定区域最多可以批准 250 个存储帐户。The Azure Storage team will review your business case and may approve up to 250 storage accounts for a given region.

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

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

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

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

1默认限制因套餐类别类型(例如 1 元试用、提前支付)以及系列(例如 Dv2、F、G)而异。1Default limits vary by offer category type, such as 1rmb-trial, Pay In Adavance, and by series, such as Dv2, F, and G.

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

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

Note

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

资源组限制Resource group limits

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

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

模板限制Template limits

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

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

虚拟机限制Virtual Machines limits

虚拟机限制Virtual Machines limits

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

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

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

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

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

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

1使用 Azure Resource Manager 时,证书存储在 Azure 密钥保管库中。1With Azure Resource Manager, certificates are stored in the Azure Key Vault. 对于每个订阅,证书个数没有限制。The number of certificates is unlimited for a subscription. 对于每个部署(包括单一 VM 或可用性集),证书的限制为 1-MB。There's a 1-MB limit of certificates per deployment, which consists of either a single VM or an availability set.

共享映像库限制Shared Image Gallery limits

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

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

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

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

容器实例限制Container Instances limits

Resource Default limit
Container groups per subscription 1001
Number of containers per container group 60
Number of volumes per container group 20
Ports per IP 5
Container instance log size - running instance 4 MB
Container instance log size - stopped instance 16 KB or 1,000 lines
Container creates per hour 3001
Container creates per 5 minutes 1001
Container deletes per hour 3001
Container deletes per 5 minutes 1001

1To request a limit increase, create an Azure Support request.

容器注册表限制Container Registry limits

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

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

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

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

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

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

Azure Kubernetes 服务限制Azure Kubernetes Service limits

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

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

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

在“Azure 机器学习配额”页中可以找到 Azure 机器学习计算配额的最新值。The latest values for Azure Machine Learning Compute quotas can be found in the Azure Machine Learning quota page.

网络限制Networking limits

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

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

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

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

Note

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

资源Resource 默认限制Default limit
虚拟网络Virtual networks 1,0001,000
每个虚拟网络的子网数Subnets per virtual network 3,0003,000
每个虚拟网络的虚拟网络对等互连数Virtual network peerings per virtual network 500500
每个虚拟网络的 DNS 服务器数DNS servers per virtual network 2020
每个虚拟网络的专用 IP 地址数Private IP addresses per virtual network 65,53665,536
每个网络接口的专用 IP 地址数Private IP addresses per network interface 256256
每个虚拟机的专用 IP 地址数Private IP addresses per virtual machine 256256
虚拟机或角色实例的单 NIC 并发 TCP 或 UDP 流数Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 500,000500,000
网络接口卡数Network interface cards 65,53665,536
网络安全组Network Security Groups 5,0005,000
每个 NSG 的 NSG 规则数NSG rules per NSG 1,0001,000
应用程序安全组Application security groups 3,0003,000
用户定义路由表数User-defined route tables 200200
每个路由表的用户定义的路由数User-defined routes per route table 400400
每个 Azure VPN 网关的点到站点根证书数Point-to-site root certificates per Azure VPN Gateway 2020

公共 IP 地址限制Public IP address limits

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

负载均衡器限制Load balancer limits

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

资源Resource 默认限制Default limit
负载均衡器Load balancers 1,0001,000
每个资源的规则数,基本Rules per resource, Basic 250250
前端 IP 配置,基本Front-end IP configurations, Basic 200200
后端池,基本Back-end pool, Basic 100,单个可用性集100, single availability set

ExpressRoute 限制ExpressRoute limits

ExpressRoute 限制ExpressRoute Limits

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

资源Resource 默认/最大限制Default/Max Limit
每个订阅的 ExpressRoute 线路数ExpressRoute circuits per subscription 10 个10
每个订阅每个区域的 ExpressRoute 线路数(Azure 资源管理器)ExpressRoute circuits per region per subscription (Azure Resource Manager) 10 个10
具有 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 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 线路数Maximum number of ExpressRoute circuits linked to the same virtual network in different peering locations 44
每个 ExpressRoute 线路允许的虚拟网络链接数Number of virtual network links allowed per ExpressRoute circuit 请参阅下表see table below

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

线路大小Circuit Size 针对 Standard 的 VNet 链接数Number of VNet links for standard 使用 Premium 附加设备时的 VNet 链接数Number of VNet Links with Premium add-on
50 Mbps50 Mbps 10 个10 20 个20
100 Mbps100 Mbps 10 个10 2525
200 Mbps200 Mbps 10 个10 2525
500 Mbps500 Mbps 10 个10 4040
1 Gbps1 Gbps 10 个10 5050
2 Gbps2 Gbps 10 个10 6060
5 Gbps5 Gbps 1010 7575
10 Gbps10 Gbps 10 个10 100100

应用程序网关限制Application Gateway limits

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

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

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

网络观察程序限制Network Watcher limits

资源Resource 默认限制Default limit 最大限制Maximum Limit 注意Note
网络观察程序Network Watcher 每个区域 1 个1 per region 每个区域 1 个1 per region 将创建网络观察程序资源以启用对服务的访问。Network Watcher resource is created to enable access to the service. 每个区域每个订阅只需要 1 个网络观察程序资源Only 1 Network Watcher resource is required per subscription 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.

Azure DNS 限制Azure DNS limits

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

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

Azure 防火墙限制Azure Firewall limits

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

Azure 防火墙必须具有直接的 Internet 连接。Azure Firewall must have direct Internet connectivity. 如果 AzureFirewallSubnet 知道通过 BGP 的本地网络的默认路由,则必须将其替代为 0.0.0.0/0 UDR,将 NextHopType 值设置为 Internet 以保持 Internet 直接连接 。If your AzureFirewallSubnet learns a default route to your on-premises network via BGP, you must override that with a 0.0.0.0/0 UDR with the NextHopType value set as Internet to maintain direct Internet connectivity. 默认情况下,Azure 防火墙不支持强制的安全加密链路连接到本地网络。By default, Azure Firewall doesn't support forced tunneling to an on-premises network.

但是,如果你的配置要求强制的安全加密链路连接到本地网络,Microsoft 将基于具体的情况提供支持。However, if your configuration requires forced tunneling to an on-premises network, Microsoft will support it on a case by case basis. 请联系支持人员,以便我们可以查看你的情况。Contact Support so that we can review your case. 如果接受,我们将允许你的订阅,并确保保持所需的防火墙 Internet 连接。If accepted, we'll allow your subscription and ensure the required firewall Internet connectivity is maintained.

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

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

ResourceResource 默认/最大限制Default/maximum limit
每个订阅的 Azure Front Door 服务资源数Azure Front Door Service resources per subscription 100100
每个资源的前端主机数(包括自定义域)Front-end hosts, which includes custom domains per resource 100100
每个资源的路由规则数Routing rules per resource 100100
每个资源的后端池数Back-end pools per resource 5050
每个后端池的后端数Back ends per back-end pool 100100
要匹配路由规则的路径模式数Path patterns to match for a routing rule 2525
每个策略的自定义 Web 应用程序防火墙规则数Custom web application firewall rules per policy 10 个10
每个资源的 Web 应用程序防火墙策略数Web application firewall policy per resource 100100
Web 应用程序防火墙根据每个自定义规则匹配条件数Web application firewall match conditions per custom rule 10 个10
每个匹配条件的 Web 应用防火墙 IP 地址范围数Web application firewall IP address ranges per match condition 600600
每个匹配条件的 Web 应用程序防火墙字符串匹配值数Web application firewall string match values per match condition 10 个10
Web 应用程序防火墙字符串匹配值长度Web application firewall string match value length 256256
Web 应用程序防火墙 POST 正文参数名称长度Web application firewall POST body parameter name length 256256
Web 应用程序防火墙 HTTP 标头名称长度Web application firewall HTTP header name length 256256
Web 应用程序防火墙 Cookie 名称长度Web application firewall cookie name length 256256
已检查的 Web 应用程序防火墙 HTTP 请求正文大小Web application firewall HTTP request body size inspected 128 KB128 KB
Web 应用程序防火墙自定义响应正文长度Web application firewall custom response body length 2 KB2 KB

超时值Timeout values

客户端到 Front DoorClient to Front Door

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

Front Door 到应用程序后端Front Door to application back-end

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

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

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

其他限制Other limits

  • 最大 URL 大小(8,192 字节)指定原始 URL(URL 的方案 + 主机名 + 端口 + 路径 + 查询字符串)的最大长度;最大查询字符串大小(4,096 字节)指定查询字符串的最大长度(以字节为单位)。Maximum URL size - 8,192 bytes - Specifies maximum length of the raw URL (scheme + hostname + port + path + query string of the URL)- Maximum Query String size - 4,096 bytes - Specifies the maximum length of the query string, in bytes.

存储限制Storage limits

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

ResourceResource 默认限制Default limit
每个订阅每个区域的存储帐户数,包括标准帐户和高级帐户Number of storage accounts per region per subscription, including both standard and premium accounts 250250
最大存储帐户容量Maximum storage account capacity 500 TB500 TB
每个存储帐户的 Blob 容器、Blob、文件共享、表、队列、实体或消息数上限Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account 无限制No limit
每个存储帐户的最大请求速率1Maximum request rate1 per storage account 每秒 20,000 个请求20,000 requests per second
每个存储帐户的最大入口1Maximum ingress1 per storage account 如果已启用 RA-GRS/GRS,则为 5 Gbps;对于 LRS,为 10 Gbps25 Gbps if RA-GRS/GRS is enabled, 10 Gbps for LRS2
常规用途 v2 存储帐户和 Blob 存储帐户的最大出口Maximum egress for general-purpose v2 and Blob storage accounts 50 Gbps50 Gbps
常规用途 v1 存储帐户的最大出口Max egress for general-purpose v1 storage accounts 如果已启用 RA-GRS/GRS,则为 10 Gbps;对于 LRS,为 15 Gbps210 Gbps if RA-GRS/GRS is enabled, 15 Gbps for LRS 2

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

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

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

Note

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

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

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

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

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

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

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

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

Azure Blob 存储限制Azure Blob storage limits

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

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

Azure 文件限制Azure Files limits

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

资源Resource 标准文件共享Standard file shares
文件共享的最小大小Minimum size of a file share 没有最小值;提前支付No minimum; pay in advance
文件共享的最大大小Maximum size of a file share 5 TiB5 TiB
文件共享中文件的最大大小Maximum size of a file in a file share 1 TiB1 TiB
文件共享中的文件数上限Maximum number of files in a file share 无限制No limit
每个共享的最大 IOPSMaximum IOPS per share 1000 IOPS1000 IOPS
每个文件共享的存储的访问策略的最大数目Maximum number of stored access policies per file share 55
单个文件共享的目标吞吐量Target throughput for a single file share 最多 60 MiB/秒Up to 60 MiB/sec
每个文件打开图柄的最大数目Maximum open handles per file 2,000 个打开句柄2,000 open handles
共享快照的最大数目Maximum number of share snapshots 200 个共享快照200 share snapshots
最大对象(目录和文件)名称长度Maximum object (directories and files) name length 2,048 个字符2,048 characters
最大路径名组成部分(在路径 \A\B\C\D 中,每个字母是一个组成部分)Maximum pathname component (in the path \A\B\C\D, each letter is a component) 255 个字符255 characters

Azure 文件同步限制Azure File Sync limits

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

Note

Azure 文件同步终结点可以纵向扩展到 Azure 文件共享的大小。An Azure File Sync endpoint can scale up to the size of an Azure file share. 如果达到 Azure 文件共享大小限制,同步将无法运行。If the Azure file share size limit is reached, sync will not be able to operate.

Azure 队列存储限制Azure Queue storage limits

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

Azure 表存储限制Azure Table storage limits

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

虚拟机磁盘限制Virtual machine disk limits

Azure 虚拟机支持附加许多的数据磁盘。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.

Important

为了获得最佳性能,需要限制附加到虚拟机的、重度使用的磁盘数,以避免可能的性能限制。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:
资源Resource 默认限制Default Limit 最大限制Maximum Limit
标准托管磁盘Standard Managed Disks 10,00010,000 50,00050,000
标准 SSD 托管磁盘Standard SSD Managed Disks 10,00010,000 50,00050,000
高级托管磁盘Premium Managed Disks 10,00010,000 50,00050,000
标准 LRS 快照Standard_LRS Snapshots 10,00010,000 50,00050,000
标准 ZRS 快照Standard_ZRS Snapshots 10,00010,000 50,00050,000
托管映像Managed Image 10,00010,000 50,00050,000
  • 对于标准存储帐户: 标准存储帐户的总请求率上限为 20,000 IOPS。For standard storage accounts: A standard storage account has a maximum total request rate of 20,000 IOPS. 在标准存储帐户中,所有虚拟机磁盘的 IOPS 总数不应超过此限制。The total IOPS across all of your virtual machine disks in a standard storage account should not exceed this limit.

    可以根据请求率的限制,大致计算单个标准存储帐户可支持的重度使用磁盘数。You can roughly calculate the number of highly utilized disks supported by a single standard storage account based on the request rate limit. 例如,对于基本层 VM,重度使用的磁盘数上限约为 66(每个磁盘 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.

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

托管虚拟机磁盘Managed virtual machine disks

标准 HDD 托管磁盘Standard HDD Managed Disks

标准磁盘类型Standard Disk Type  S4S4               S6S6               S10S10              S15S15 S20S20              S30S30              S40S40              S50S50             
磁盘大小 (GiB)Disk size in GiB          3232             6464             128128            256256 512512            1,0241,024    2,0482,048     4,0954,095   
每个磁盘的 IOPSIOPS per disk       最大 500Up to 500              最大 500Up to 500              最大 500Up to 500              最大 500Up to 500 最大 500Up to 500              最大 500Up to 500              最大 500Up to 500             最大 500Up to 500             
每个磁盘的吞吐量Throughput per disk 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec 最多 60 MiB/秒Up to 60 MiB/sec

标准 SSD 托管磁盘Standard SSD Managed Disks

标准 SSD 磁盘类型Standard SSD Disk Type E4E4 E6E6 E10E10 E15E15 E20E20 E30E30 E40E40 E50E50
磁盘大小 (GiB)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0954,095
每个磁盘的 IOPSIOPS per disk 最多 120Up to 120 最多 240Up to 240 最大 500Up to 500 最大 500Up to 500 最大 500Up to 500 最大 500Up to 500 最大 500Up to 500 最大 500Up to 500
每个磁盘的吞吐量Throughput per disk 最多 25 MB/秒Up to 25 MB/sec 最多 50 MB/秒Up to 50 MB/sec 最多 60 MB/秒Up to 60 MB/sec 最多 60 MB/秒Up to 60 MB/sec 最多 60 MB/秒Up to 60 MB/sec 最多 60 MB/秒Up to 60 MB/sec 最多 60 MB/秒Up to 60 MB/sec 最多 60 MB/秒Up to 60 MB/sec

高级 SSD 托管磁盘:每个磁盘的限制Premium SSD Managed Disks: per disk limits

高级磁盘类型Premium Disk Type  P4P4               P6P6               P10P10              P15P15 P20P20              P30P30              P40P40              P50P50             
磁盘大小 (GiB)Disk size in GiB           3232             6464             128128            256256 512512            1,0241,024    2,0482,048     4,0954,095   
每个磁盘的 IOPSIOPS per disk       最多 120Up to 120 最多 240Up to 240              最大 500Up to 500              最多 1,100Up to 1,100 最多 2,300Up to 2,300              最多 5,000Up to 5,000              最多 7,500Up to 7,500             最多 7,500Up to 7,500             
每个磁盘的吞吐量Throughput per disk 最多 25 MiB/秒Up to 25 MiB/sec 最多 50 MiB/秒Up to 50 MiB/sec 最多 100 MiB/秒Up to 100 MiB/sec 最多 125 MiB/秒Up to 125 MiB/sec 最多 150 MiB/秒Up to 150 MiB/sec 最多 200 MiB/秒Up to 200 MiB/sec 最多 250 MiB/秒Up to 250 MiB/sec 最多 250 MiB/秒Up to 250 MiB/sec

非托管虚拟机磁盘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

Azure 云服务限制Azure 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, and API Apps.

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

Functions 限制Functions limits

Resource Consumption plan Premium plan App Service plan1
Scale out Event driven Event driven Manual/autoscale
Max instances 200 20 10-20
Default time out duration (min) 5 30 302
Max time out duration (min) 10 unbounded unbounded3
Max outbound connections (per instance) 600 active (1200 total) unbounded unbounded
Max request size (MB)4 100 100 100
Max query string length4 4096 4096 4096
Max request URL length4 8192 8192 8192
ACU per instance 100 210-840 100-840
Max memory (GB per instance) 1.5 3.5-14 1.75-14
Function apps per plan 100 100 unbounded5
App Service plans 100 per region 100 per resource group 100 per resource group
Storage6 1 GB 250 GB 50-1000 GB
Custom domains per app 5007 500 500
Custom domain SSL support unbounded SNI SSL connection included unbounded SNI SSL and 1 IP SSL connections included unbounded SNI SSL and 1 IP SSL connections included

1 For specific limits for the various App Service plan options, see the App Service plan limits.
2 By default, the timeout for the Functions 1.x runtime in an App Service plan is unbounded.
3 Requires the App Service plan be set to Always On. Pay at standard rates.
4 These limits are set in the host.
5 The actual number of function apps that you can host depends on the activity of the apps, the size of the machine instances, and the corresponding resource utilization. 6 The storage limit is the total content size in temporary storage across all apps in the same App Service plan. Consumption plan uses Azure Files for temporary storage.
7 When your function app is hosted in a Consumption plan, only the CNAME option is supported. For function apps in an App Service plan, you can map a custom domain using either a CNAME or an A record.

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

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

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

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

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

Batch 限制Batch limits

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

Note

默认限制因用于创建 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.

Azure Cosmos DB 限制Azure Cosmos DB limits

有关 Azure Cosmos DB 的限制,请参阅 Azure Cosmos DB 中的限制For Azure Cosmos DB limits, see Limits in Azure Cosmos DB.

Azure Database for MySQLAzure Database for MySQL

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

Azure Database for PostgreSQLAzure Database for PostgreSQL

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

Azure 搜索限制Azure Search limits

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

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

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

存储受磁盘空间限制,或者受索引或文档的最大数目的硬性限制,具体取决于先达到哪一项限制。Storage is constrained by disk space or by a hard limit on the maximum number of indexes or documents, whichever comes first.

资源Resource 免费Free 基本Basic S1S1 S2S2 S3S3 S3 HDS3 HD
服务级别协议 (SLA)Service Level Agreement (SLA) 1No 1 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 3 23 2
分区大小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
最大索引数Maximum indexes 33 55 5050 200200 200200 每个分区 1000,或者每个服务 30001000 per partition or 3000 per service
最大索引器数Maximum indexers 33 55 5050 200200 200200 无索引器支持No indexer support
最大数据源数Maximum datasources 33 55 5050 200200 200200 无索引器支持No indexer support
最大文档数Maximum documents 10,00010,000 1 百万1 million 每个分区 1500 万,或者每个服务 1 亿 8 千万15 million per partition or 180 million per service 每个分区 6 千万,或者每个服务 7 亿 2 千万60 million per partition or 720 million per service 每个分区 1 亿 2 千万,或者每个服务 14 亿120 million per partition or 1.4 billion per service 每个索引 1 百万,或者每个分区 2 亿1 million per index or 200 million per partition
每秒估计的查询数 (QPS)Estimated queries per second (QPS) 不适用N/A 每个副本大约 3 个~3 per replica 每个副本大约 15 个~15 per replica 每个副本大约 60 个~60 per replica 每个副本大约 60 个~60 per replica 每个副本大于 60 个>60 per replica

1 免费层和预览功能不带服务级别协议 (SLA)。1 Free tier and preview features do not come with service level agreements (SLAs). 对于所有可计费的层,SLA 将在用户为服务提供足够冗余时生效。For all billable tiers, 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.

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.

媒体服务限制Media Services limits

Note

对于不固定的资源,可以通过开具支持票证的方式请求提高配额。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 10 个10
存储帐户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).

Note

如果经常使用相同的天数/访问权限等,则应使用相同的策略 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

内容分发网络限制Content Delivery Network limits

资源Resource 软性限制Soft limit
CDN 配置文件CDN profiles 88
每个配置文件的 CDN 终结点数CDN endpoints per profile 1010
每个终结点的自定义域数Custom domains per endpoint 1010

通过打开支持票证请求更新订阅的软限制。Request an update to your subscription's soft limits by opening 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.

Azure Monitor 限制Azure Monitor limits

警报Alerts

Resource Default limit Maximum limit
Metric alerts (classic) 100 active alert rules per subscription. Call support.
Metric alerts 1000 active alert rules per subscription (in public clouds) and 100 active alert rules per subscription in Azure China 21Vianet and Azure Government. Call support.
Activity log alerts 100 active alert rules per subscription. Same as default.
Log alerts 512 Call support.
Action groups 2,000 action groups per subscription. Call support.
Autoscale settings 100 per region per subscription. Same as default.

操作组Action groups

Resource Default limit Maximum limit
Azure app push 10 Azure app actions per action group. Call support.
Email 1,000 email actions in an action group.
No more than 100 emails in an hour.
Also see the rate limiting information.
Call support.
ITSM 10 ITSM actions in an action group. Call support.
Logic app 10 logic app actions in an action group. Call support.
Runbook 10 runbook actions in an action group. Call support.
SMS 10 SMS actions in an action group.
No more than 1 SMS message every 5 minutes.
Also see the rate limiting information.
Call support.
Voice 10 voice actions in an action group.
No more than 1 voice call every 5 minutes.
Also see the rate limiting information.
Call support.
Webhook 10 webhook actions in an action group. Maximum number of webhook calls is 1500 per minute per subscription. Other limits are available at action-specific information. Call support.

Log Analytics 工作区Log Analytics workspaces

Data collection volume and retention

Tier Limit per day Data retention Comment
Current Per GB pricing tier
(introduced April 2018)
No limit 30 - 730 days Data retention beyond 31 days is available for additional charges. Learn more about Azure Monitor pricing.
Legacy Free tiers
(introduced April 2016)
500 MB 7 days When your workspace reaches the 500 MB per day limit, data ingestion stops and resumes at the start of the next day. A day is based on UTC. Note that data collected by Azure Security Center is not included in this 500 MB per day limit and will continue to be collected above this limit.
Legacy Standalone Per GB tier
(introduced April 2016)
No limit 30 to 730 days Data retention beyond 31 days is available for additional charges. Learn more about Azure Monitor pricing.
Legacy Per Node (OMS)
(introduced April 2016)
No limit 30 to 730 days Data retention beyond 31 days is available for additional charges. Learn more about Azure Monitor pricing.
Legacy Standard tier No limit 30 days Retention can't be adjusted
Legacy Premium tier No limit 365 days Retention can't be adjusted

Number of workspaces per subscription.

Pricing tier Workspace limit Comments
Free tier 10 This limit can't be increased.
All other tiers No limit You're limited by the number of resources within a resource group and the number of resource groups per subscription.

Azure portal

Category Limits Comments
Maximum records returned by a log query 10,000 Reduce results using query scope, time range, and filters in the query.

Data Collector API

Category Limits Comments
Maximum size for a single post 30 MB Split larger volumes into multiple posts.
Maximum size for field values 32 KB Fields longer than 32 KB are truncated.

Search API

Category Limits Comments
Maximum records returned for non-aggregated data 5,000
Maximum records for aggregated data 500,000 Aggregated data is a search that includes the summarize command.
Maximum size of data returned 64,000,000 bytes (~61 MiB)
Maximum query running time 10 minutes See Timeouts for details.
Maximum request rate 200 requests per 30 seconds per AAD user or client IP address See Rate limits for details.

General workspace limits

Category Limits Comments
Maximum columns in a table 500
Maximum characters for column name 500
Regions at capacity West Central US You cannot currently create a new workspace in this region since it is at temporary capacity limit. This limit is planned to be addressed by end of September, 2019.
Data export Not currently available Use Azure Function or Logic App to aggregate and export data.

Note

Depending on how long you've been using Log Analytics, you might have access to legacy pricing tiers. Learn more about Log Analytics legacy pricing tiers.

Application InsightsApplication Insights

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 GB You can reduce data by setting a cap. If you need more data, you can increase the limit in the portal, up to 1,000 GB. For capacities greater than 1,000 GB, send email to AIDataCap@microsoft.com.
Throttling 32,000 events/second The limit is measured over a minute.
Data retention 90 days This resource is for Search, Analytics, and Metrics Explorer.
Availability multi-step test detailed results retention 90 days This resource provides detailed results of each step.
Maximum event size 64,000
Property and metric name length 150 See type schemas.
Property value string length 8,192 See type schemas.
Trace and exception message length 32,768 See type schemas.
Availability tests count per app 100
Profiler data retention 5 days
Profiler data sent per day 10 GB

For more information, see About pricing and quotas in Application Insights.

通知中心限制Notification Hubs limits

层:TIER: 免费FREE 基本BASIC 标准STANDARD
包括的推送数Included Pushes 100 万1 Million 1000 万10 Million 1000 万10 Million
活动设备数Active Devices 500500 200,000200,000 1000 万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 namespaces per subscription 订阅Subscription - 100100
每个命名空间的事件中心数Number of event hubs per namespace 命名空间Namespace 创建新事件中心的后续请求会被拒绝。Subsequent requests for creation of a new event hub are rejected. 10 个10
每个事件中心的分区数Number of partitions per event hub 实体Entity - 3232
每个事件中心的使用者组数Number of consumer groups per event hub 实体Entity - 20 个20
每个命名空间的 AMQP 连接数Number of AMQP connections per namespace 命名空间Namespace 系统会拒绝后续的附加连接请求,且调用代码会收到异常。Subsequent requests for additional connections are rejected, and an exception is received by the calling code. 5,0005,000
事件中心事件的最大大小Maximum size of Event Hubs event 实体Entity - 1 MB1 MB
事件中心名称的最大大小Maximum size of an event hub name 实体Entity - 50 个字符50 characters
每个使用者组的非 epoch 接收者数Number of non-epoch receivers per consumer group 实体Entity - 55
事件数据的最长保留期限Maximum retention period of event data 实体Entity - 1-7 天1-7 days
最大吞吐量单位Maximum throughput units 命名空间Namespace 超出吞吐量单位限制会导致数据受到限制,并生成 ServerBusyExceptionExceeding the throughput unit limit causes your data to be throttled and generates a ServerBusyException. 额外的吞吐量单位将基于承诺的购买以大小为 20 个单位的块的形式提供。Additional throughput units are available in blocks of 20 on a committed purchase basis. 20 个20

| 每个命名空间的授权规则数量 |命名空间|将拒绝后续的授权规则创建请求。|12 || Number of authorization rules per namespace |Namespace|Subsequent requests for authorization rule creation are rejected.|12 |

服务总线限制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 GB 或 5 GB。1, 2, 3, 4 GB or 5 GB.

在高级 SKU 以及启用了分区的标准 SKU 中,最大队列/主题大小是 80 GB。In the Premium SKU, as well as Standard with partitioning 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 namespace 命名空间Namespace 系统将拒绝后续的在命名空间中创建新主题或队列的请求。Subsequent requests for creation of a new topic or queue on the namespace are rejected. 因此,如果是通过 Azure 门户配置的,将生成错误消息。As a result, if configured through the Azure portal, an error message is generated. 如果是通过管理 API 调用的,调用代码将收到异常。If called from the management API, an exception is received by the calling code. 10,000(基本/标准层)。10,000(Basic/Standard tier). 命名空间中主题和队列的数目之和必须小于或等于 10,000。The total number of topics and queues in a namespace must be less than or equal to 10,000.
每个命名空间的分区主题/队列Number of partitioned topics/queues per namespace 命名空间Namespace 系统将拒绝后续的在命名空间中创建新分区主题或队列的请求。Subsequent requests for creation of a new partitioned topic or queue on the namespace are rejected. 因此,如果是通过 Azure 门户配置的,将生成错误消息。As a result, if configured through the Azure portal, an error message is generated. 如果是通过管理 API 调用的,调用代码将收到 QuotaExceededException 异常。If called from the management API, a QuotaExceededException exception is received by the calling code. 基本和标准层 - 100Basic and Standard Tiers - 100

高级层中不支持分区实体。Partitioned entities are not supported in the Premium tier.

在每个命名空间中,每个分区队列或主题的实体配额不会超过 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
消息 SessionID 的最大大小Maximum size of a message SessionID 实体Entity - 128128
队列/主题/订阅实体的消息大小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).

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

最大标头大小: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 limit 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 (1 K)。Maximum length of filter condition string: 1024 (1K).

规则操作字符串的最大长度:1024 (1 K)。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 10 个10 11

Note

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

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

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

Note

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

Note

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

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

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

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

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

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

Note

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

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

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

流分析限制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 (Azure AD) 服务的使用限制和其他服务限制。Here are the usage constraints and other service limits for the Azure Active Directory (Azure AD) service.

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

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

    WhereWhere 对象What 最大计数Maximum count
    作用域Scope 策略定义Policy definitions 500500
    作用域Scope 计划定义Initiative definitions 100100
    租户Tenant 计划定义Initiative definitions 1,0001,000
    作用域Scope 策略或计划分配Policy or initiative assignments 100100
    策略定义Policy definition parametersParameters 20 个20
    计划定义Initiative definition 策略Policies 100100
    计划定义Initiative definition parametersParameters 100100
    策略或计划分配Policy or initiative assignments 排除项(不在范围内的项)Exclusions (notScopes) 400400
    策略规则Policy rule 嵌套式条件语句Nested conditionals 512512

    备份限制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 为 1000 个1000 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 每个区域 500 个恢复服务保管库500 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 GB4095 GB
    • 154400 GB 限制不适用于 IaaS VM 备份。1The 54400 GB limit does not apply to IaaS VM backup.

    Site Recovery 限制Site Recovery limits

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

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

    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 2MB2MB
    最大策略文档大小Maximum policy document size 256KB256KB
    最大自定义网关域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 Cache for Redis limits

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

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

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

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

    Key Vault 限制Key Vault limits

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

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

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

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

    有关超出这些限制时如何处理限制的信息,请参阅 Azure Key Vault 限制指南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.

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

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

    自动化限制Automation limits

    流程自动化Process automation

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

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

    Identity Manager 限制Identity Manager limits

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

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

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

    SQL 数据库限制SQL Database limits

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

    SQL 数据仓库限制SQL Data Warehouse limits

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

    另请参阅See also