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

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

本文列出了一些最常见的 Microsoft Azure 限制,有时也称为配额。This document lists some of the most common Microsoft Azure limits, which are also sometimes called quotas.

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

管理限制Managing limits

备注

某些服务具有可调节的限制。Some services have adjustable limits.

当服务没有可调整的限制时,下表将使用标头限制When a service doesn't have adjustable limits, the following tables use the header Limit. 在这些情况下,默认值和最大限制相同。In those cases, the default and the maximum limits are the same.

当可以调整限制时,表包括默认限制最大限制标头。When the limit can be adjusted, the tables include Default limit and Maximum limit headers. 限制可以高于默认限制,但不能高于最大限制。The limit can be raised above the default limit but not above the maximum limit.

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

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

某些限制在区域一级管理。Some limits are managed at a regional level.

让我们以 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 Resolve errors for resource quotas.

常规限制General limits

有关资源名称的限制,请参阅Azure 资源的命名规则和限制For limits on resource names, see Naming rules and restrictions for Azure resources.

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

管理组限制Management group limits

以下限制适用于管理组The following limits apply to management groups.

资源Resource 限制Limit
每个目录的管理组Management groups per directory 10,00010,000
每个管理组的订阅Subscriptions per management group 不受限制。Unlimited.
管理组层次结构级别Levels of management group hierarchy 根级别加上 6 级1Root level plus 6 levels1
每个管理组的直接父管理组Direct parent management group per management group 一种One
每个位置的管理组级别部署Management group level deployments per location 80028002

16 个级别不包括订阅级别。1The 6 levels don't include the subscription level.

2如果达到 800 个部署的限制,请从不再需要的历史记录中删除部署。2If you reach the limit of 800 deployments, delete deployments from the history that are no longer needed. 要删除管理组级别部署,请使用删除 Az 管理组部署az 部署 mg 删除To delete management group level deployments, use Remove-AzManagementGroupDeployment or az deployment mg delete.

订阅限制Subscription limits

使用 Azure 资源管理器和 Azure 资源组时,以下限制适用。The following limits apply when you use Azure Resource Manager and Azure resource groups.

资源Resource 限制Limit
每个 Azure 活动目录租户的订阅Subscriptions per Azure Active Directory tenant 不受限制。Unlimited.
每个订阅的协管理员Coadministrators per subscription 不受限制。Unlimited.
每个订阅的资源组Resource groups per subscription 980980
Azure 资源管理器 API 请求大小Azure Resource Manager API request size 4,194,304 字节。4,194,304 bytes.
每个订阅的标记1Tags per subscription1 5050
每个订阅的唯一标记计算1Unique tag calculations per subscription1 10,00010,000
每个位置的订阅级部署数Subscription-level deployments per location 80028002

1您只能将多达 50 个标记直接应用于订阅。1You can apply up to 50 tags directly to a subscription. 但是,订阅可以包含无限数量的标记,这些标记应用于订阅中的资源组和资源。However, the subscription can contain an unlimited number of tags that are applied to resource groups and resources within the subscription. 每个资源或资源组的标记数限制为 50。The number of tags per resource or resource group is limited to 50. 当标记数少于或等于 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.

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

资源组限制Resource group limits

资源Resource 限制Limit
每个资源组的资源Resources per resource group 资源不受资源组的限制。Resources aren't limited by resource group. 相反,它们受资源组中的资源类型的限制。Instead, they're limited by resource type in a resource group. 请参阅下一行。See next row.
每个资源组的资源,每个资源类型Resources per resource group, per resource type 800 - 某些资源类型可能超过 800 限制。800 - Some resource types can exceed the 800 limit. 请参阅不限于每个资源组 800 个实例的资源See Resources not limited to 800 instances per resource group.
部署历史记录中每个资源组的部署数Deployments per resource group in the deployment history 80018001
每个部署的资源数Resources per deployment 800800
管理锁数(按唯一的作用域)Management locks per unique scope 2020
标记数(按资源或资源组)Number of tags per resource or resource group 5050
标记键长度Tag key length 512512
标记值长度Tag value length 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. 有关详细信息,请参阅解决部署计数超出 800 的错误For more information, see Resolve error when deployment count exceeds 800.

模板限制Template limits

“值”Value 限制Limit
参数Parameters 256256
变量Variables 256256
资源(包括副本计数)Resources (including copy count) 800800
OutputsOutputs 6464
模板表达式Template expression 24,576 个字符24,576 chars
已导出模板中的资源Resources in exported templates 200200
模板大小Template size 4 MB4 MB
参数文件大小Parameter file size 64 KB64 KB

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

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 限制Limit
目录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.
资源Resources
  • 默认情况下,Azure Active Directory 免费版用户最多可以在单个目录中创建 50,000 个 Azure AD 资源。A maximum of 50,000 Azure AD resources can be created in a single directory by users of the Free edition of Azure Active Directory by default. 如果至少有一个已验证的域,则组织的默认 Azure AD 服务配额将扩展到 300,000 个 Azure AD 资源。If you have at least one verified domain, the default Azure AD service quota for your organization is extended to 300,000 Azure AD resources. 此服务限制与 Azure AD 定价页上 500,000 个资源的定价层限制无关。This service limit is unrelated to the pricing tier limit of 500,000 resources on the Azure AD pricing page. 要超出默认配额,必须联系 Microsoft 支持部门。To go beyond the default quota, you must contact Microsoft Support.
  • 非管理员用户最多可以创建 250 个 Azure AD 资源。A non-admin user can create no more than 250 Azure AD resources. 活动资源和可还原的已删除资源都会计入此配额。Both active resources and deleted resources that are available to restore count toward this quota. 只能还原在不到 30 天前删除的 Azure AD 资源。Only deleted Azure AD resources that were deleted fewer than 30 days ago are available to restore. 不再可还原的已删除 Azure AD 资源在 30 天内按四分之一的值计入此配额。Deleted Azure AD resources that are no longer available to restore count toward this quota at a value of one-quarter for 30 days. 如果开发人员在其日常工作期间可能会反复超过此配额,你可以创建并分配一个自定义角色,并为此角色授予创建无限个应用注册的权限。If you have developers who are likely to repeatedly exceed this quota in the course of their regular duties, you can create and assign a custom role with permission to create a limitless number of app registrations.
架构扩展Schema extensions
  • 字符串类型扩展最多只能有 256 个字符。String-type extensions can have a maximum of 256 characters.
  • 二进制类型扩展限制在 256 字节以内。Binary-type extensions are limited to 256 bytes.
  • 只能将 100 个扩展值(包括所有类型和所有应用程序)写入任何单一 Azure AD 资源中。****Only 100 extension values, across all types and all applications, can be written to any single Azure AD resource.
  • 仅“用户”、“组”、“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.
应用程序清单Application Manifest 最多可在应用程序清单中添加 1200 个条目。A maximum of 1200 entries can be added in the Application Manifest.
Groups
  • 用户最多可在一个 Azure AD 组织中创建 250 个组。A user can create a maximum of 250 groups in an Azure AD organization.
  • Azure AD 组织最多可以有 5000 个动态组。An Azure AD organization can have a maximum of 5000 dynamic groups.
  • 最多有 100 位用户可以是单一组的所有者。A maximum of 100 users can be owners of a single group.
  • 任意数量的 Azure AD 资源都可以是单个组的成员。Any number of Azure AD resources 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.
  • 并非所有方案都支持 Azure AD 中的嵌套组Nested Groups in Azure AD are not supported within all scenarios

目前,以下是嵌套组支持的方案。At this time the following are the supported scenarios with nested groups.
  • 可以将一个组添加为另一个组的成员,并且可以实现组嵌套。One group can be added as a member of another group and you can achieve group nesting.
  • 组成员身份声明(将应用配置为接收令牌中的组成员身份声明时,会包括已登录用户所属的嵌套组)Group membership claims (when an app is configured to receive group membership claims in the token, nested groups the signed-in user is a member of are included)
  • 条件访问(将条件访问策略范围界定到组时)Conditional access (when scoping a conditional access policy to a group)
  • 限制访问自助式密码重置Restricting access to self-serve password reset
  • 限制哪些用户可以执行 Azure AD 加入和设备注册Restricting which users can do Azure AD Join and device registration

以下方案不支持嵌套组:The following scenarios DO NOT supported nested groups:
  • 应用角色分配(支持向应用分配组,但嵌套在直接分配的组中的组将没有访问权限),可用于访问和预配App role assignment (assigning groups to an app is supported, but groups nested within the directly assigned group will not have access), both for access and for provisioning
  • 基于组的许可(将许可证自动分配给组的所有成员)Group-based licensing (assigning a license automatically to all members of a group)
  • Office 365 组。Office 365 Groups.
应用程序代理Application Proxy
  • 每个应用代理应用程序每秒最多可处理 500 个事务A maximum of 500 transactions per second per App Proxy application
  • Azure AD 组织每秒最多 750 个事务A maximum of 750 transactions per second for the Azure AD organization

一个事务定义为针对唯一资源的单个 http 请求和响应。A transaction is defined as a single http request and response for a unique resource. 受到限制后,客户端将收到 429 响应(请求过多)。When throttled, clients will receive a 429 response (too many requests).
访问面板Access Panel
  • 对于可以在访问面板中按用户查看的应用程序,其数量没有限制。There's no limit to the number of applications that can be seen in the Access Panel per user. 这适用于 Azure AD Premium 或企业移动性套件的用户分配许可证。This applies to users assigned licenses for Azure AD Premium or the Enterprise Mobility Suite.
  • 每位用户最多可以在访问面板中看到 10 个应用磁贴。A maximum of 10 app tiles can be seen in the Access Panel for each user. 此限制适用于已获得 Azure AD Free 许可计划许可证的用户。This limit applies to users who are assigned licenses for Azure AD Free license plan. Box、Salesforce、Dropbox 都是应用磁贴的示例。Examples of app tiles include Box, Salesforce, or Dropbox. 此限制不适用于管理员帐户。This limit doesn't apply to administrator accounts.
报表Reports 在报告中最多可查看或下载 1,000 行。A maximum of 1,000 rows can be viewed or downloaded in any report. 系统会截断其他任何数据。Any additional data is truncated.
管理单元Administrative units Azure AD 资源可以是不超出 30 个管理单位的成员。An Azure AD resource can be a member of no more than 30 administrative units.
管理员角色和权限Admin roles and permissions
  • 不能将组添加为所有者A group cannot be added as an owner.
  • 无法将组分配给角色A group cannot be assigned to a role.
  • 用户读取其他用户目录信息的能力不能限制在 Azure AD 组织范围交换机之外,以禁用所有非管理员用户对所有目录信息的访问(不建议)。Users' ability to read other users' directory information cannot be restricted outside of the Azure AD organization-wide switch to disable all non-admin users' access to all directory information (not recommended). 有关默认权限的详细信息,请参阅此处More information on default permissions here.
  • 在管理员角色成员身份添加和撤销生效之前,最多可能需要 15 分钟或注销/登录。It may take up to 15 minutes or signing out/signing in before admin role membership additions and revocations take effect.

API 管理限制API Management limits

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

1缩放限制取决于定价层。1Scaling limits depend on the pricing tier. 要查看定价层及其缩放限制,请参阅API 管理定价To see the pricing tiers and their scaling limits, see API Management pricing.
2单位缓存大小取决于定价层。2Per unit cache size depends on the pricing tier. 要查看定价层及其缩放限制,请参阅API 管理定价To see the pricing tiers and their scaling limits, see API Management pricing.
3除非后端显式关闭,否则连接将汇集并重用。3Connections are pooled and reused unless explicitly closed by the back end.
4此限制是基本、标准和高级层的单位。4This limit is per unit of the Basic, Standard, and Premium tiers. 开发人员层限制为 1,024。The Developer tier is limited to 1,024. 此限制不适用于"消耗"层。This limit doesn't apply to the Consumption tier.
5此限制适用于基本、标准和高级层。5This limit applies to the Basic, Standard, and Premium tiers. 在"消费"层中,策略文档大小限制为 4 KiB。In the Consumption tier, policy document size is limited to 4 KiB.
6此资源仅在高级层中可用。6This resource is available in the Premium tier only.
7此资源仅适用于"消耗"层。7This resource applies to the Consumption tier only.
8仅适用于"消耗"层。8Applies to the Consumption tier only. 包括最多 2048 字节长的查询字符串。Includes an up to 2048 bytes long query string.

应用服务限制App Service limits

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

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

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

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

1除非特别说明,否则应用和存储配额依每个应用服务计划为准。1Apps and storage quotas are per App Service plan unless noted otherwise.
2可以在这些计算机上托管的应用的实际数目取决于应用的活动、计算机实例的大小和相应的资源利用率。2The actual number of apps that you can host on these machines depends on the activity of the apps, the size of the machine instances, and the corresponding resource utilization.
3专用实例可有不同的大小。3Dedicated instances can be of different sizes. 有关详细信息,请参阅应用服务定价For more information, see App Service pricing.
4可应要求提供更多服务。4More are allowed upon request.
5存储限制是同一应用服务计划中所有应用的总内容大小。5The storage limit is the total content size across all apps in the same App service plan. 单个资源组和地区中所有应用服务计划的所有应用的总内容大小不能超过 500GB。The total content size of all apps across all App service plans in a single resource group and region cannot exceed 500GB.
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. 对于标准层及以上,Web 套接字没有理论限制,但其他因素可能会限制 Web 套接字的数量。For Standard tier and above, there are no theoretical limits to web sockets, but other factors can limit the number of web sockets. 例如,允许的最大并发请求(由maxConcurrentRequestsPerCpu定义)为:每个小型 VM 7,500 个,每个中型 VM(7,500 x 2 个内核)15,000 个,每个大型 VM(18,750 x 4 个内核)75,000 个。For example, maximum concurrent requests allowed (defined by maxConcurrentRequestsPerCpu) are: 7,500 per small VM, 15,000 per medium VM (7,500 x 2 cores), and 75,000 per large VM (18,750 x 4 cores).
8最大 IP 连接是每个实例,取决于实例大小:每个 B1/S1/P1V2 实例 1,920 个,每个 B2/S2/P2V2 实例 3,968 个,每个 B3/S3/P3V2 实例 8,064 个。8The maximum IP connections are per instance and depend on the instance size: 1,920 per B1/S1/P1V2 instance, 3,968 per B2/S2/P2V2 instance, 8,064 per B3/S3/P3V2 instance.
9每个订阅的应用服务证书配额限制可以通过支持请求增加到最大限制 200。9The App Service Certificate quota limit per subscription can be increased via a support request to a maximum limit of 200.
10应用服务隔离 SKU 可以通过 Azure 负载均衡器实现内部负载平衡 (ILB),因此没有来自 Internet 的公共连接。10App Service Isolated SKUs can be internally load balanced (ILB) with Azure Load Balancer, so there's no public connectivity from the internet. 因此,必须从能够直接访问 ILB 网络终结点的计算机使用 ILB 独立应用服务的某些功能。As a result, some features of an ILB Isolated App Service must be used from machines that have direct access to the ILB network endpoint.
11按需、按计划运行自定义可执行文件和/或脚本,或作为应用服务实例中的后台任务连续运行。11Run 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. 在应用服务实例中运行的 Web 作业数量没有预定义限制。There's no predefined limit on the number of WebJobs that can run in an App Service instance. 有一些实际的限制取决于应用程序代码正在尝试做什么。There are practical limits that depend on what the application code is trying to do.

自动化限制Automation limits

流程自动化Process automation

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

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

更改跟踪和库存Change Tracking and Inventory

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

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

更新管理Update Management

下表显示了更新管理的限制。The following table shows the limits for Update Management.

资源Resource 限制Limit 说明Notes
每个更新部署的计算机数Number of machines per update deployment 10001000

Azure Redis 缓存限制Azure Cache for Redis limits

资源Resource 限制Limit
缓存大小Cache size 1.2 TB1.2 TB
数据库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 1010

每个定价层的 Azure Redis 缓存限制和大小都不相同。Azure Cache for Redis limits and sizes are different for each pricing tier. 要查看定价层及其关联大小,请参阅Redis 定价的 Azure 缓存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.

Azure 云服务限制Azure Cloud Services limits

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

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

Azure 认知搜索限制Azure Cognitive Search limits

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

  • “免费”层**** 为多租户服务,可与其他 Azure 订阅用户共享,旨在用于评估和小型开发项目。Free multi-tenant service, shared with other Azure subscribers, 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 subscription

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

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

资源Resource 免费1Free1 BasicBasic S1S1 S2S2 S3S3 S3 HDS3 HD L1L1 L2L2
最大服务数Maximum services 11 1616 1616 88 66 66 66 66
搜索单位 (SU) 的最大规模2Maximum scale in search units (SU)2 空值N/A 3 SU3 SU 36 个 SU36 SU 36 个 SU36 SU 36 个 SU36 SU 36 个 SU36 SU 36 个 SU36 SU 36 个 SU36 SU

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

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

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

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

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

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

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

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

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

Azure 认知服务限制Azure Cognitive Services limits

以下限制适用于每个 Azure 订阅的认知服务资源数。The following limits are for the number of Cognitive Services resources per Azure subscription. 每个认知服务可能都有其他限制,有关详细信息,请参阅 Azure 认知服务Each of the Cognitive Services may have additional limitations, for more information see Azure Cognitive Services.

类型Type 限制Limit 示例Example
认知服务资源的混合A mixture of Cognitive Services resources 总共最多 200 个认知服务资源。Maximum of 200 total Cognitive Services resources. 美国西部的 100 个计算机视觉资源 2、美国西部的 50 个语音服务资源以及美国东部的 50 个文本分析资源。100 Computer Vision resources in West US 2, 50 Speech Service resources in West US, and 50 Text Analytics resources in East US.
单一类型的认知服务资源。A single type of Cognitive Services resources. 每个区域最多 100 个资源,总共最多 200 个认知服务资源。Maximum of 100 resources per region, with a maximum of 200 total Cognitive Services resources. 美国西部的 100 个计算机视觉资源 2, 和美国东部的 100 个计算机视觉资源。100 Computer Vision resources in West US 2, and 100 Computer Vision resources in East US.

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 数据资源管理器限制Azure Data Explorer limits

下表描述了 Azure 数据资源管理器群集的最大限制。The following table describes the maximum limits for Azure Data Explorer clusters.

资源Resource 限制Limit
每个订阅每个区域的群集Clusters per region per subscription 2020
每个群集的实例Instances per cluster 10001000
群集中的数据库数Number of databases in a cluster 10,00010,000
群集中附加的数据库配置数Number of attached database configurations in a cluster 7070

下表描述了对 Azure 数据资源管理器群集执行的管理操作的限制。The following table describes the limits on management operations performed on Azure Data Explorer clusters.

范围Scope OperationOperation 限制Limit
群集Cluster 读取(例如,获取群集)read (for example, get a cluster) 每5分钟500人500 per 5 minutes
群集Cluster 写入(例如,创建数据库)write (for example, create a database) 每小时1000人1000 per hour

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 Functions limits

资源Resource 消费计划Consumption plan 保费计划Premium plan 应用服务计划1App Service plan1
横向扩展Scale out 事件驱动Event driven 事件驱动Event driven 手动/自动缩放Manual/autoscale
最大实例数Max instances 200200 100100 10-2010-20
默认超时持续时间(分钟)Default timeout duration (min) 55 3030 302302
最大超时持续时间(分钟)Max timeout duration (min) 1010 无界8unbounded8 不受限制3unbounded3
最大出站连接数(每个实例)Max outbound connections (per instance) 600 个处于活动状态(总共 1200 个)600 active (1200 total) unboundedunbounded unboundedunbounded
最大请求大小 (MB)4Max request size (MB)4 100100 100100 100100
最大查询字符串长度4Max query string length4 40964096 40964096 40964096
最大请求 URL 长度4Max request URL length4 81928192 81928192 81928192
每个实例的 ACUACU per instance 100100 210-840210-840 100-840100-840
最大内存(每个实例的 GB 数)Max memory (GB per instance) 1.51.5 3.5-143.5-14 1.75-141.75-14
每个计划的函数应用数Function apps per plan 100100 100100 不受限制5unbounded5
应用服务计划App Service plans 每个区域 100100 per region 每个资源组 100 个100 per resource group 每个资源组 100 个100 per resource group
存储6Storage6 1 GB1 GB 250 GB250 GB 50-1000 GB50-1000 GB
每个应用的自定义域数Custom domains per app 50075007 500500 500500
自定义域 SSL 支持Custom domain SSL support 包含无限制的 SNI SSL 连接unbounded SNI SSL connection included 包含无限制的 SNI SSL 连接和 1 个 IP SSL 连接unbounded SNI SSL and 1 IP SSL connections included 包含无限制的 SNI SSL 连接和 1 个 IP SSL 连接unbounded SNI SSL and 1 IP SSL connections included

1 有关各种应用服务计划选项的特定限制,请参阅应用服务计划限制1 For specific limits for the various App Service plan options, see the App Service plan limits.
2 默认情况下,应用服务计划中的 Functions 1.x 运行时的超时是无限制的。2 By default, the timeout for the Functions 1.x runtime in an App Service plan is unbounded.
3 需要将应用服务计划设置为 Always On3 Requires the App Service plan be set to Always On. 按标准费率付费。Pay at standard rates.
4 这些限制在主机中设置4 These limits are set in the host.
5 可以托管的函数应用的实际数目取决于应用的活动、计算机实例的大小和相应的资源利用率。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 存储限制是同一应用服务计划中所有应用的临时存储中的总内容大小。6 The storage limit is the total content size in temporary storage across all apps in the same App Service plan. 消耗计划使用 Azure 文件存储作为临时存储。Consumption plan uses Azure Files for temporary storage.
7 当函数应用托管在消耗计划中时,仅支持 CNAME 选项。7 When your function app is hosted in a Consumption plan, only the CNAME option is supported. 对于高级计划应用服务计划中的函数应用,可以使用 CNAME 或 A 记录映射自定义域。For function apps in a Premium plan or an App Service plan, you can map a custom domain using either a CNAME or an A record.
8保证长达 60 分钟。8 Guaranteed for up to 60 minutes.

Azure Kubernetes 服务限制Azure Kubernetes Service limits

资源Resource 限制Limit
每个订阅的最大群集数Maximum clusters per subscription 100100
具有虚拟机可用性集和基本负载均衡器 SKU 的每个群集的最大节点Maximum nodes per cluster with Virtual Machine Availability Sets and Basic Load Balancer SKU 100100
具有虚拟机缩放集和标准负载均衡器 SKU的每个群集的最大节点Maximum nodes per cluster with Virtual Machine Scale Sets and Standard Load Balancer SKU 1000 (每个节点池 100个节点1000 (100 nodes per node pool)
每个节点的最大窗格:与 Kubenet的基本网络Maximum pods per node: Basic networking with Kubenet 110110
每个节点的最大窗格:使用 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 limits

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

Azure Maps 限制Azure Maps limits

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

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

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

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

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

Azure Monitor 限制Azure Monitor limits

警报Alerts

资源Resource 默认限制Default limit 最大限制Maximum limit
指标警报(经典)Metric alerts (classic) 每个订阅 100 个活动警报规则。100 active alert rules per subscription. 致电支持人员。Call support.
指标警报Metric alerts Azure 公共、Azure 中国 21Vianet 和 Azure 政府云中每个订阅的 2,000 个活动警报规则。2,000 active alert rules per subscription in Azure public, Azure China 21Vianet and Azure Government clouds. 致电支持人员。Call support.
活动日志警报Activity log alerts 每个订阅 100 个活动警报规则。100 active alert rules per subscription. 与默认值相同。Same as default.
日志警报Log alerts 每个订阅有 512 个活动警报规则。512 active alert rules per subscription. 每个资源有 200 个活动警报规则。200 active alert rules per resource. 致电支持人员。Call support.
操作组Action groups 每个订阅 2,000 个操作组。2,000 action groups per subscription. 致电支持人员。Call support.
自动缩放设置Autoscale settings 每个订阅每个区域 100 个。100 per region per subscription. 与默认值相同。Same as default.

操作组Action groups

资源Resource 默认限制Default limit 最大限制Maximum limit
Azure 应用推送Azure app push 每个操作组 10 个 Azure 应用操作。10 Azure app actions per action group. 致电支持人员。Call support.
电子邮件Email 一个操作组中有 1,000 个电子邮件操作。1,000 email actions in an action group.
一小时内最多 100 个电子邮件。No more than 100 emails in an hour.
另请参阅速率限制信息Also see the rate limiting information.
致电支持人员。Call support.
ITSMITSM 一个操作组中有 10 个 ITSM 操作。10 ITSM actions in an action group. 致电支持人员。Call support.
逻辑应用Logic app 一个操作组中有 10 个逻辑应用操作。10 logic app actions in an action group. 致电支持人员。Call support.
RunbookRunbook 一个操作组中有 10 个 runbook 操作。10 runbook actions in an action group. 致电支持人员。Call support.
SMSSMS 一个操作组中有 10 个短信操作。10 SMS actions in an action group.
每 5 分钟最多 1 条短信。No more than 1 SMS message every 5 minutes.
另请参阅速率限制信息Also see the rate limiting information.
致电支持人员。Call support.
语音Voice 一个操作组中有 10 个语音操作。10 voice actions in an action group.
每 5 分钟最多 1 条语音呼叫。No more than 1 voice call every 5 minutes.
另请参阅速率限制信息Also see the rate limiting information.
致电支持人员。Call support.
WebhookWebhook 一个操作组中有 10 个 Webhook 操作。10 webhook actions in an action group. 每个订阅最大 Webhook 调用次数为每分钟 1500 次。Maximum number of webhook calls is 1500 per minute per subscription. 其他限制可在特定于操作的信息中找到。Other limits are available at action-specific information. 致电支持人员。Call support.

日志查询和语言Log queries and language

限制Limit 描述Description
查询语言Query language Azure Monitor 使用与 Azure 数据资源管理器相同的 Kusto 查询语言Azure Monitor uses the same Kusto query language as Azure Data Explorer. 有关 Azure Monitor 中不支持的 KQL 语言元素,请参阅 Azure Monitor 日志查询语言差异See Azure Monitor log query language differences for KQL language elements not supported in Azure Monitor.
Azure 区域Azure regions 当数据跨多个 Azure 区域中的 Log Analytics 工作区时,日志查询可能会遇到过多的开销。Log queries can experience excessive overhead when data spans Log Analytics workspaces in multiple Azure regions. 有关详细信息,请参阅查询限制See Query limits for details.
跨资源查询Cross resource queries 单个查询中的 Application Insights 资源和 Log Analytics 工作区的最大数量限制为 100。Maximum number of Application Insights resources and Log Analytics workspaces in a single query limited to 100.
视图设计器不支持跨资源查询。Cross-resource query is not supported in View Designer.
新的 scheduledQueryRules API 支持日志警报中的跨资源查询。Cross-resource query in log alerts is supported in the new scheduledQueryRules API.
有关详细信息,请参阅跨资源查询限制See Cross-resource query limits for details.
查询限制Query throttling 用户在任何数量的工作区上每 30 秒只能有 200 个查询。A user is limited to 200 queries per 30 seconds on any number of workspaces. 此限制适用于编程查询或由可视化部分(如 Azure 仪表板和日志分析工作区摘要页)启动的查询。This limit applies to programmatic queries or to queries initiated by visualization parts such as Azure dashboards and the Log Analytics workspace summary page.

Log Analytics 工作区Log Analytics workspaces

数据收集量和保留期Data collection volume and retention

Tier 每日限制Limit per day 数据保留Data retention 注释Comment
当前每 GB 定价层Current Per GB pricing tier
(已于 2018 年 4 月推出)(introduced April 2018)
无限制No limit 30 - 730 天30 - 730 days 如果数据保留期超过 31 天,则需要收取额外的费用。Data retention beyond 31 days is available for additional charges. 详细了解 Azure Monitor 定价。Learn more about Azure Monitor pricing.
旧的免费层Legacy Free tiers
(已于 2016 年 4 月推出)(introduced April 2016)
500 MB500 MB 7 天7 days 当工作区达到 500 MB 的每日限制时,数据引入会停止,并在第二天开始时恢复。When your workspace reaches the 500 MB per day limit, data ingestion stops and resumes at the start of the next day. 日期基于 UTC。A day is based on UTC. 请注意,由 Azure 安全中心收集的数据不包含在这一 500 MB 的每日限制内,并在超出此限制后继续进行收集。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.
旧的独立(按 GB)层Legacy Standalone Per GB tier
(已于 2016 年 4 月推出)(introduced April 2016)
无限制No limit 30 至 730 天30 to 730 days 如果数据保留期超过 31 天,则需要收取额外的费用。Data retention beyond 31 days is available for additional charges. 详细了解 Azure Monitor 定价。Learn more about Azure Monitor pricing.
旧的按节点 (OMS) 定价层Legacy Per Node (OMS)
(已于 2016 年 4 月推出)(introduced April 2016)
无限制No limit 30 至 730 天30 to 730 days 如果数据保留期超过 31 天,则需要收取额外的费用。Data retention beyond 31 days is available for additional charges. 详细了解 Azure Monitor 定价。Learn more about Azure Monitor pricing.
旧的标准层Legacy Standard tier 无限制No limit 30 天30 days 不能调整保留期Retention can't be adjusted
旧的高级层Legacy Premium tier 无限制No limit 365 天365 days 不能调整保留期Retention can't be adjusted

每个订阅的工作区数。Number of workspaces per subscription.

定价层Pricing tier 工作区限制Workspace limit 注释Comments
免费层Free tier 1010 此限制不能提高。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 门户Azure portal

类别Category 限制Limit 注释Comments
日志查询返回的最大记录数Maximum records returned by a log query 10,00010,000 在查询中使用查询作用域、时间范围和筛选器来减少结果。Reduce results using query scope, time range, and filters in the query.

数据收集器 APIData Collector API

类别Category 限制Limit 注释Comments
单个发布内容的最大大小Maximum size for a single post 30 MB30 MB 将较大的卷拆分为多个发布内容。Split larger volumes into multiple posts.
字段值的最大大小Maximum size for field values 32 KB32 KB 超过 32 KB 的字段会被截断。Fields longer than 32 KB are truncated.

搜索 APISearch API

类别Category 限制Limit 注释Comments
在单个查询中返回的最大记录Maximum records returned in a single query 500,000500,000
返回的数据的最大大小Maximum size of data returned 64,000,000 字节 (~61 MiB)64,000,000 bytes (~61 MiB)
最长查询运行时间Maximum query running time 10 分钟10 minutes 有关详细信息,请参阅超时See Timeouts for details.
最大请求速率Maximum request rate 每个 AAD 用户或客户端 IP 地址每 30 秒发出 200 个请求200 requests per 30 seconds per AAD user or client IP address 有关详细信息,请参阅速率限制See Rate limits for details.

常规工作区限制General workspace limits

类别Category 限制Limit 注释Comments
表中的最大列数Maximum columns in a table 500500
列名称的最大字符数Maximum characters for column name 500500
数据导出Data export 当前不可用Not currently available 使用 Azure 函数或逻辑应用聚合和导出数据。Use Azure Function or Logic App to aggregate and export data.

数据引入容积率Data ingestion volume rate

Azure Monitor 是一种大规模数据服务,每月为成千上万的客户发送数 TB 的数据,并且此数据仍在不断增长。Azure Monitor is a high scale data service that serves thousands of customers sending terabytes of data each month at a growing pace. 使用诊断设置从 Azure 资源发送的数据的默认引入容积速率限制约为每个工作区6 GB/min。The default ingestion volume rate limit for data sent from Azure resources using diagnostic settings is approximately 6 GB/min per workspace. 这是一个近似值,因为实际大小在数据类型之间可能会有所不同,具体取决于日志长度及其压缩率。This is an approximate value since the actual size can vary between data types depending on the log length and its compression ratio. 此限制不适用于从代理或数据收集器 API 发送的数据。This limit does not apply to data that is sent from agents or Data Collector API.

如果以更高速率将数据发送到单个工作区,则某些数据将丢弃,并且在继续超过阈值的情况下,每 6 小时将向工作区中的“操作”** 表发送一个事件。If you send data at a higher rate to a single workspace, some data is dropped, and an event is sent to the Operation table in your workspace every 6 hours while the threshold continues to be exceeded. 如果引入量继续超过速率限制,或者希望很快达到该限制,则可以通过建立支持请求来请求增加工作区。If your ingestion volume continues to exceed the rate limit or you are expecting to reach it sometime soon, you can request an increase to your workspace by opening a support request.

若要在工作区中收到此类事件的通知,请根据大于零的结果数,使用以下具有警报逻辑的查询创建日志警报规则To be notified on such an event in your workspace, create a log alert rule using the following query with alert logic base on number of results grater than zero.

Operation
|where OperationCategory == "Ingestion"
|where Detail startswith "The rate of data crossed the threshold"

备注

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

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

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.

其中Where 对象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 参数Parameters 2020
计划定义Initiative definition 策略Policies 100100
计划定义Initiative definition 参数Parameters 100100
策略或计划分配Policy or initiative assignments 排除项 (notScopes)Exclusions (notScopes) 400400
策略规则Policy rule 嵌套式条件语句Nested conditionals 512512
修正任务Remediation task 资源Resources 10001000

Azure 信号R 服务限制Azure SignalR Service limits

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

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

备份限制Backup limits

有关 Azure 备份支持设置和限制的摘要,请参阅Azure 备份支持矩阵For a summary of Azure Backup support settings and limitations, see Azure Backup Support Matrices.

Batch 限制Batch limits

资源Resource 默认限制Default limit 最大限度Maximum limit
每个订阅每个区域的 Azure 批处理帐户Azure Batch accounts per region per subscription 1-31-3 5050
每个批处理帐户的专用核心数Dedicated cores per Batch account 90-90090-900 联系支持人员Contact support
每个批处理帐户的低优先级核心数Low-priority cores per Batch account 10-10010-100 联系支持人员Contact support
每个批处理帐户**的活动** 作业和作业计划(已完成的作业没有限制)Active jobs and job schedules per Batch account (completed jobs have no limit) 100-300100-300 1,00011,0001
每个 Batch 帐户的池数Pools per Batch account 20-10020-100 50015001

备注

默认限制因用于创建 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要请求超出此限制的增幅,请与 Azure 支持部门联系。1To request an increase beyond this limit, contact Azure Support.

经典部署模型限制Classic deployment model limits

如果使用经典部署模型而不是 Azure 资源管理器部署模型,则适用以下限制。If you use classic deployment model instead of the Azure Resource Manager deployment model, the following limits apply.

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

1尽管使用了部分 CPU 内核,但超小实例仍计为 vCPU 限制的一个 vCPU。1Extra small instances count as one vCPU toward the vCPU limit despite using a partial CPU core.

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

容器实例限制Container Instances limits

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

1要请求提高上限,请创建一个 Azure 支持请求1To request a limit increase, create an Azure Support request.

容器注册表限制Container Registry limits

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

资源Resource BasicBasic StandardStandard PremiumPremium
存储1Storage1 10 GiB10 GiB 100 GiB100 GiB 500 GiB500 GiB
最大映像层大小Maximum image layer size 200 GiB200 GiB 200 GiB200 GiB 200 GiB200 GiB
每分钟读取操作数2、3ReadOps per minute2, 3 1,0001,000 3,0003,000 10,00010,000
每分钟写入操作数2、4WriteOps per minute2, 4 100100 500500 2,0002,000
下载带宽 (MBps)2Download bandwidth MBps2 3030 6060 100100
上传带宽 (MBps)2Upload bandwidth MBps2 1010 2020 5050
WebhookWebhooks 22 1010 500500
异地复制Geo-replication 空值N/A 空值N/A 支持Supported
内容信任Content trust 空值N/A 空值N/A 支持Supported
虚拟网络访问Virtual network access 空值N/A 空值N/A 预览Preview
专用链路集成Private link integration 空值N/A 空值N/A 预览Preview
客户管理的密钥Customer-managed keys 空值N/A 空值N/A 预览Preview
存储库范围权限Repository-scoped permissions 空值N/A 空值N/A 预览Preview
•令 牌• Tokens 空值N/A 空值N/A 20,00020,000
•范围映射• Scope maps 空值N/A 空值N/A 20,00020,000
•每个范围映射的存储库• Repositories per scope map 空值N/A 空值N/A 500500

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.

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

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

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

数据工厂限制Data Factory limits

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

版本 2Version 2

资源Resource 默认限制Default limit 最大限制Maximum limit
Azure 订阅中的数据工厂Data factories in an Azure subscription 800800 联系支持人员Contact support.
数据工厂中的实体(例如管道、数据集、触发器、链接服务以及集成运行时)的总数Total number of entities, such as pipelines, data sets, triggers, linked services, and integration runtimes, within a data factory 5,0005,000 联系支持人员Contact support.
一个订阅中 Azure-SSIS Integration Runtime 的总 CPU 内核数Total CPU cores for Azure-SSIS Integration Runtimes under one subscription 256256 联系支持人员Contact support.
每个数据工厂的并行管道运行数(在工厂中的所有管道之间共享)Concurrent pipeline runs per data factory that's shared among all pipelines in the factory 10,00010,000 联系支持人员Contact support.
每个 Azure Integration Runtime 区域的每个订阅的并发外部活动运行数Concurrent External activity runs per subscription per Azure Integration Runtime region
外部活动在集成运行时进行管理,但在链接的服务上执行,包括数据砖块、存储过程、HDInsights、Web 等。External activities are managed on integration runtime but execute on linked services, including Databricks, stored procedure, HDInsights, Web, and others.
30003000 联系支持人员Contact support.
每个 Azure Integration Runtime 区域的每个订阅的并发管道活动运行数Concurrent Pipeline activity runs per subscription per Azure Integration Runtime region
管道活动在集成运行时上执行,包括 Lookup、GetMetadata 和 Delete。Pipeline activities execute on integration runtime, including Lookup, GetMetadata, and Delete.
10001000 联系支持人员Contact support.
每个 Azure Integration Runtime 区域的每个订阅的并发创作操作数Concurrent authoring operations per subscription per Azure Integration Runtime region
包括测试连接、浏览器文件夹列表和表列表、预览数据。Including test connection, browse folder list and table list, preview data.
200200 联系支持人员Contact support.
每个Azure 集成运行时区域每个订阅的并发数据集成单元1消耗Concurrent Data Integration Units1 consumption per subscription per Azure Integration Runtime region 区域组 12:6000Region group 12: 6000
区域组 22:3000Region group 22: 3000
区域组 32: 1500Region group 32: 1500
联系支持人员Contact support.
每个管道的最大活动数,包括容器的内部活动Maximum activities per pipeline, which includes inner activities for containers 4040 4040
可以针对单个自承载集成运行时创建的最大链接集成运行时数Maximum number of linked integration runtimes that can be created against a single self-hosted integration runtime 100100 联系支持人员Contact support.
每个管道的最大参数个数Maximum parameters per pipeline 5050 5050
ForEach 项ForEach items 100,000100,000 100,000100,000
ForEach 并行度ForEach parallelism 2020 5050
每个管道的最大排队运行Maximum queued runs per pipeline 100100 100100
每个表达式的字符数Characters per expression 8,1928,192 8,1928,192
最小翻转窗口触发间隔Minimum tumbling window trigger interval 15 分钟15 min 15 分钟15 min
管道活动运行的最大超时时间Maximum timeout for pipeline activity runs 7 天7 days 7 天7 days
管道对象的每个对象的字节数3Bytes per object for pipeline objects3 200 KB200 KB 200 KB200 KB
数据集和链接服务对象的每个对象的字节数3Bytes per object for dataset and linked service objects3 100 KB100 KB 2,000 KB2,000 KB
每个复制活动运行的数据集成单元数1Data Integration Units1 per copy activity run 256256 联系支持人员Contact support.
编写 API 调用Write API calls 1,200/小时1,200/h

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

此限制是由 Azure 资源管理器而不是 Azure 数据工厂所强加的。This limit is imposed by Azure Resource Manager, not Azure Data Factory.
联系支持人员Contact support.
每分钟监视的查询数Monitoring queries per minute 1,0001,000 联系支持人员Contact support.
每分钟的实体 CRUD 操作数Entity CRUD operations per minute 5050 联系支持人员Contact support.
数据流调试会话的最大时间Maximum time of data flow debug session 8 小时8 hrs 8 小时8 hrs
每个工厂的并发数据流数Concurrent number of data flows per factory 5050 联系支持人员Contact support.
每个工厂每个用户的数据流调试会话的并发数量Concurrent number of data flow debug sessions per user per factory 33 33
数据流 Azure IR TTL 限制Data Flow Azure IR TTL limit 4 小时4 hrs 联系支持人员Contact support.

1 数据集成单元 (DIU) 用于云到云复制操作,详见数据集成单元(版本 2)1 The data integration unit (DIU) is used in a cloud-to-cloud copy operation, learn more from Data integration units (version 2). 有关计费的信息,请参阅 Azure 数据工厂定价For information on billing, see Azure Data Factory pricing.

2 Azure 集成运行时可在全球范围内使用,以确保数据合规性、效率和降低网络出口成本。2 Azure Integration Runtime is globally available to ensure data compliance, efficiency, and reduced network egress costs.

区域组Region group 区域Regions
区域组 1Region group 1 美国中部、美国东部、美国东部、北欧、西欧、美国西部、美国西部 2Central US, East US, East US2, North Europe, West Europe, West US, West US 2
区域组 2Region group 2 澳大利亚东部、澳大利亚东南部、巴西南部、印度中部、日本东部、美国中北部、美国中南部、东南亚、美国中西部Australia East, Australia Southeast, Brazil South, Central India, Japan East, Northcentral US, Southcentral US, Southeast Asia, West Central US
区域组 3Region group 3 加拿大 中部、 东亚、 法国 中部、 韩国 中部、 英国南部Canada Central, East Asia, France Central, Korea Central, UK South

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

版本 1Version 1

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

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

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

3版本 1 的云数据移动单元 (DMU) 用于云到云复制操作,从云数据移动单元(版本 1)中了解更多信息。3 The cloud data movement unit (DMU) for version 1 is used in a cloud-to-cloud copy operation, learn more from Cloud data movement units (version 1). 有关计费的信息,请参阅 Azure 数据工厂定价For information on billing, see Azure Data Factory pricing.

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

Web 服务调用限制Web service call limits

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

Data Lake Analytics 限制Data Lake Analytics limits

Azure 数据湖分析使管理分布式基础结构和复杂代码的复杂任务变得简单。Azure Data Lake Analytics makes the complex task of managing distributed infrastructure and complex code easy. 它动态地提供资源,您可以使用它对 PB 的数据进行分析。It dynamically provisions resources, and you can use it to do analytics on exabytes of data. 作业完成后,它会自动关闭资源。When the job completes, it winds down resources automatically. 您只为所使用的处理能力付费。You pay only for the processing power that was used. 随着存储的数据大小或使用的计算量的增加或减小,您不必重写代码。As you increase or decrease the size of data stored or the amount of compute used, you don't have to rewrite code. 要提高订阅的默认限制,请与支持人员联系。To raise the default limits for your subscription, contact support.

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

Data Lake Store 限制Data Lake Store limits

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

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

数据共享限制Data Share limits

Azure 数据共享使组织能够简单安全地与其客户和合作伙伴共享数据。Azure Data Share enables organizations to simply and securely share data with their customers and partners.

资源Resource 限制Limit
每个 Azure 订阅的最大数据共享资源数Maximum number of Data Share resources per Azure subscription 5050
每个数据共享资源的最大发送共享数Maximum number of sent shares per Data Share resource 100100
每个数据共享资源接收的最大共享数Maximum number of received shares per Data Share resource 100100
每个发送共享的最大邀请数Maximum number of invitations per sent share 100100
每个发送共享的最大共享订阅数Maximum number of share subscriptions per sent share 100100
每股最大数据集数Maximum number of datasets per share 100100
每股快照计划的最大数量Maximum number of snapshot schedules per share 11

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

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

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

事件网格限制Event Grid limits

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

资源Resource 限制Limit
每个 Azure 订阅的自定义主题数Custom topics per Azure subscription 100100
每个主题的事件订阅数Event subscriptions per topic 500500
自定义主题的发布速率(入口)Publish rate for a custom topic (ingress) 每个主题每秒 5,000 个事件5,000 events per second per topic
发布请求数Publish requests 每秒 250 个250 per second
事件大小Event size 1 MB(以多个 64 KB 事件为单位充电)1 MB (charged in as multiple 64-KB events)

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

资源Resource 限制Limit
每个事件域的主题数Topics per event domain 100,000100,000
域中每个主题的事件订阅数Event subscriptions per topic within a domain 500500
域范围事件订阅数Domain scope event subscriptions 5050
事件域(入口)的发布速率Publish rate for an event domain (ingress) 每秒 5,000 个事件5,000 events per second
发布请求数Publish requests 每秒 250 个250 per second
每个 Azure 订阅的事件域Event Domains per Azure Subscription 100100

事件中心限制Event Hubs limits

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

以下限制是基本层、标准层和专用层之间的通用限制。The following limits are common across basic, standard, and dedicated tiers.

限制Limit 范围Scope 说明Notes “值”Value
每个订阅的事件中心命名空间数Number of Event Hubs namespaces per subscription 订阅Subscription - 100100
每个命名空间的事件中心数Number of event hubs per namespace 命名空间Namespace 创建新事件中心的后续请求会被拒绝。Subsequent requests for creation of a new event hub are rejected. 1010
每个事件中心的分区数Number of partitions per event hub 实体Entity - 3232
事件中心名称的最大大小Maximum size of an event hub name 实体Entity - 50 个字符50 characters
每个使用者组的非 epoch 接收者数Number of non-epoch receivers per consumer group 实体Entity - 55
最大吞吐量单位Maximum throughput units 命名空间Namespace 超出吞吐量单位限制会导致数据受到限制,并生成服务器忙异常Exceeding the throughput unit limit causes your data to be throttled and generates a server busy exception. 若要为标准层请求更大数量的吞吐量单位,请提交支持请求To request a larger number of throughput units for a Standard tier, file a support request. 额外的吞吐量单位将基于承诺的购买以大小为 20 个单位的块的形式提供。Additional throughput units are available in blocks of 20 on a committed purchase basis. 2020
每个命名空间的授权规则数量Number of authorization rules per namespace 命名空间Namespace 将拒绝后续的授权规则创建请求。Subsequent requests for authorization rule creation are rejected. 1212
对 GetRuntimeInformation 方法的调用次数Number of calls to the GetRuntimeInformation method 实体Entity - 每秒 50 次50 per second
虚拟网络 (VNet) 和 IP 配置规则的数量Number of virtual network (VNet) and IP Config rules 实体Entity - 128128

事件中心基本层和标准层 - 配额和限制Event Hubs Basic and Standard - quotas and limits

限制Limit 范围Scope 说明Notes BasicBasic StandardStandard
事件中心事件的最大大小Maximum size of Event Hubs event 实体Entity   256 KB256 KB 1 MB1 MB
每个事件中心的使用者组数Number of consumer groups per event hub 实体Entity   11 2020
每个命名空间的 AMQP 连接数Number of AMQP connections per namespace 命名空间Namespace 系统会拒绝后续的附加连接请求,且调用代码会收到异常。Subsequent requests for additional connections are rejected, and an exception is received by the calling code. 100100 5,0005,000
事件数据的最长保留期限Maximum retention period of event data 实体Entity   1 天1 day 1-7 天1-7 days
启用 Apache Kafka 的命名空间Apache Kafka enabled namespace 命名空间Namespace 使用 Kafka 协议的事件中心命名空间流应用程序Event Hubs namespace streams applications using Kafka protocol No Yes
捕获Capture 实体Entity 启用后,同一流上的微批处理When enabled, micro-batches on the same stream No Yes

事件中心专用层 - 配额和限制Event Hubs Dedicated - quotas and limits

事件中心专用层产品/服务按固定的月度价格计费,至少使用 4 个小时。The Event Hubs Dedicated offering is billed at a fixed monthly price, with a minimum of 4 hours of usage. 专用层提供标准计划的所有功能,但具有企业规模容量和限制,以满足客户的工作负荷需求。The Dedicated tier offers all the features of the Standard plan, but with enterprise scale capacity and limits for customers with demanding workloads.

FeatureFeature 限制Limits
带宽Bandwidth 20 CU20 CUs
命名空间Namespaces 每个 CU 5050 per CU
事件中心Event Hubs 每个命名空间 10001000 per namespace
入口事件Ingress events 附送Included
消息大小Message Size 1 MB1 MB
“度量值组”Partitions 每个 CU 20002000 per CU
使用者组Consumer groups 每个 CU 无限制,每个事件中心 1000No limit per CU, 1000 per event hub
中转连接Brokered connections 包括 100 K100 K included
消息保留Message Retention 90 天,每个 CU 包含 10 TB90 days, 10 TB included per CU
捕获Capture 附送Included

Identity Manager 限制Identity Manager limits

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

IoT 中心限制IoT Central limits

IoT 中心将可在订阅中部署的应用程序数限制为 10。IoT Central limits the number of applications you can deploy in a subscription to 10. 如果需要增加此限制,请联系 Microsoft 支持If you need to increase this limit, contact Microsoft support.

IoT 中心限制IoT Hub limits

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

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

备注

如果希望在 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 100100
每个 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
messagesmessages
100100
每台设备的最大云到设备队列深度Maximum cloud-to-device queue depth per device 5050
反馈消息的最大传送计数Maximum delivery count for feedback messages
(响应云到设备消息时)in response to a cloud-to-device message
100100
反馈消息的最大 TTLMaximum TTL for feedback messages in
(响应云到设备消息时)response to a cloud-to-device message
2 天2 days
设备孪生的最大大小Maximum size of device twin 有 8 KB 用于标记部分,并且各有 32 KB 分别用于所需的属性部分和报告的属性部分8 KB for tags section, and 32 KB for desired and reported properties sections each
设备孪生字符串键的最大大小Maximum length of device twin string key 1 KB1 KB
设备孪生字符串值的最大大小Maximum length of device twin string value 4 KB4 KB
设备孪生中对象的最大深度Maximum depth of object in device twin 1010
直接方法有效负载的最大大小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)

备注

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

备注

目前,可注册到单个 IoT 中心的设备和模块的总数上限为 1,000,000。Currently, the total number of devices plus modules that can be registered to a single IoT hub is capped at 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 initiations/sec/unit (5,000/min/unit) (for S3), 1.67 file upload initiations/sec/unit (100/min/unit) (for S1 and S2).
Azure 存储帐户一次可传出 10,000 个 SAS URI。10,000 SAS URIs can be out for an Azure Storage account at one time.
一次可传出 10 个 SAS URI/设备。10 SAS URIs/device can be out at one time.
直接方法Direct methods 24 MB/秒/单位(适用于 S3),480 KB/秒/单位(适用于 S2),160 KB/秒/单位(适用于 S1)。24 MB/sec/unit (for S3), 480 KB/sec/unit (for S2), 160 KB/sec/unit (for S1).
基于 8-KB 限制计量大小。Based on 8-KB throttling meter size.
设备孪生读取Device twin reads 500/秒/单位(适用于 S3),最大为 100/秒或 10/秒/单位(适用于 S2),100/秒(适用于 S1)500/sec/unit (for S3), Maximum of 100/sec or 10/sec/unit (for S2), 100/sec (for S1)
设备孪生更新Device twin updates 250/秒/单位(适用于 S3),最大为 50/秒或 5/秒/单位(适用于 S2),50/秒(适用于 S1)250/sec/unit (for S3), Maximum of 50/sec or 5/sec/unit (for S2), 50/sec (for S1)
作业操作Jobs operations
(创建、更新、列表、删除)(create, update, list, and delete)
83.33/秒/单位(5,000/分钟/单位)(适用于 S3),1.67/秒/单位(100/分钟/单位)(适用于 S2),1.67/秒/单位(100/分钟/单位)(适用于 S1)。83.33/sec/unit (5,000/min/unit) (for S3), 1.67/sec/unit (100/min/unit) (for S2), 1.67/sec/unit (100/min/unit) (for S1).
作业每设备操作吞吐量Jobs per-device operation throughput 50/秒/单位(适用于 S3),最大为 10/秒或 1/秒/单位(适用于 S2),10/秒(适用于 S1)。50/sec/unit (for S3), maximum of 10/sec or 1/sec/unit (for S2), 10/sec (for S1).
设备流启动率Device stream initiation rate 5 个新流/秒(仅适用于 S1、S2、S3 和 F1)。5 new streams/sec (for S1, S2, S3, and F1 only).

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

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

资源Resource 限制Limit
每个 Azure 订阅的最大设备预配服务数Maximum device provisioning services per Azure subscription 1010
最大登记数Maximum number of enrollments 1,000,0001,000,000
最大注册数Maximum number of registrations 1,000,0001,000,000
最大登记组数Maximum number of enrollment groups 100100
最大 CA 数Maximum number of CAs 2525
链接的 IoT 中心的最大数量Maximum number of linked IoT hubs 5050
消息的最大大小Maximum size of message 96 KB96 KB

备注

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

备注

增加 CA 的最大数目不受支持。Increasing the maximum number of CAs is not supported.

超过以下配额时,设备预配服务将限制请求。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

密钥保管库限制Key Vault limits

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

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

备注

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

限制阈值是加权的,并且是针对其总和施加的。The throttling thresholds are weighted, and enforcement is on their sum. 例如,如上表所示,当您对 RSA HSM 键执行 GET 操作时,使用 4,096 位密钥的成本是 2,048 位密钥的八倍。For example, as shown in the previous table, when you perform GET operations on RSA HSM-keys, it's eight times more expensive to use 4,096-bit keys compared to 2,048-bit keys. 这是因为 1,000/125 = 8。That's because 1,000/125 = 8.

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

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

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

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

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

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

媒体服务限制Media Services limits

备注

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

帐户限制Account limits

资源Resource 默认限制Default Limit
单个订阅中的媒体服务帐户数Media Services accounts in a single subscription 25(固定)25 (fixed)

资产限额Asset limits

资源Resource 默认限制Default Limit
每个媒体服务帐户的资产Assets per Media Services account 1,000,0001,000,000

存储限制Storage limits

资源Resource 默认限制Default Limit
文件大小File size 在某些情况下,支持在媒体服务中处理的最大文件大小存在限制。In some scenarios, there is a limit on the maximum file size supported for processing in Media Services. (1)(1)
存储帐户Storage accounts 100(2) (固定)100(2) (fixed)

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

下表显示了媒体保留单位(S1、S2 和 S3)的限制。The following table shows the limits on the media reserved units S1, S2, and S3. 如果源文件大于表中定义的限制,则编码作业将失败。If your source file is larger than the limits defined in the table, your encoding job fails. 编码持续时间较长的 4K 分辨率源时,需要使用 S3 媒体保留单位才能达到所需的性能。If you encode 4K resolution sources of long duration, you're required to use S3 media reserved units to achieve the performance needed. 如果 S3 媒体保留单位上的 4K 内容大于 260-GB 限制,请开具支持票证。If you have 4K content that's larger than the 260-GB limit on the S3 media reserved units, open a support ticket.

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

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

作业(编码&分析)限制Jobs (encoding & analyzing) limits

资源Resource 默认限制Default Limit
每个媒体服务帐户的作业数Jobs per Media Services account 500,000 (3) (固定)500,000 (3) (fixed)
每个作业的作业输入Job inputs per Job 50(固定)50 (fixed)
每个作业的作业输出Job outputs per Job 20(固定)20 (fixed)
每个媒体服务帐户的转换数Transforms per Media Services account 100(固定)100 (fixed)
变换转换中的输出Transform outputs in a Transform 20(固定)20 (fixed)
每个作业输入的文件Files per job input 10(固定)10 (fixed)

3此数字包括排队、已完成、处于活动状态和取消的作业。3 This number includes queued, finished, active, and canceled Jobs. 不包括已删除的作业。It does not include deleted Jobs.

即使记录总数低于最大配额,也会自动删除帐户中所有超过 90 天的作业记录。Any Job record in your account older than 90 days will be automatically deleted, even if the total number of records is below the maximum quota.

实时流限制Live streaming limits

资源Resource 默认限制Default Limit
每个媒体服务帐户的实时事件(4)Live Events (4) per Media Services account 55
每个直播活动的实时输出Live Outputs per Live Event 3 (5)3 (5)
最长实时输出持续时间Max Live Output duration 25 小时25 hours

4有关实时事件限制的详细信息,请参阅实时事件类型比较和限制4 For detailed information about Live Event limitations, see Live Event types comparison and limitations.

5实时输出从创建开始,删除时停止。5 Live Outputs start on creation and stop when deleted.

包装&交货限制Packaging & delivery limits

资源Resource 默认限制Default Limit
每个媒体服务帐户的流式处理端点(已停止或正在运行)Streaming Endpoints (stopped or running) per Media Services account 2(固定)2 (fixed)
动态清单筛选器Dynamic Manifest Filters 100100
流式处理策略Streaming Policies 100 (6)100 (6)
一次与一个资产关联的唯一流式处理定位符Unique Streaming Locators associated with an Asset at one time 100(7) (固定)100(7) (fixed)

6使用自定义流式处理策略时,应为媒体服务帐户设计一组有限的此类策略,并在需要相同的加密选项和协议时将其重新用于流式处理器。6 When using a custom Streaming Policy, you should design a limited set of such policies for your Media Service account, and re-use them for your StreamingLocators whenever the same encryption options and protocols are needed. 不应为每个流式处理定位符创建新的流式处理策略。You should not be creating a new Streaming Policy for each Streaming Locator.

7流式处理器不是用于管理每个用户的访问控制。7 Streaming 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.

保护限制Protection limits

资源Resource 默认限制Default Limit
每个内容密钥策略的选项Options per Content Key Policy 3030
每个帐户的媒体服务密钥交付服务上每种 DRM 类型的每月许可证数Licenses per month for each of the DRM types on Media Services key delivery service per account 1,000,0001,000,000

支持票证Support ticket

对于未固定的资源,您可以通过打开支持票证请求提高配额。For resources that are not fixed, you may ask for the quotas to be raised, by opening a support ticket. 请在请求中包含有关所需的配额更改、用例方案和所需区域的详细信息。Include detailed information in the request on the desired quota changes, use-case scenarios, and regions required.
不要创建更多的 Azure 媒体服务帐户以求获取更高的限制。Do not create additional Azure Media Services accounts in an attempt to obtain higher limits.

媒体服务 v2(旧版)Media Services v2 (legacy)

有关特定于媒体服务 v2(旧版)的限制,请参阅媒体服务 v2(旧版)For limits specific to Media Services v2 (legacy), see Media Services v2 (legacy)

移动服务限制Mobile Services limits

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

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

多重身份验证限制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

网络限制Networking limits

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

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

备注

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

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

公共 IP 地址限制Public IP address limits

资源Resource 默认限制Default limit 最大限制Maximum limit
公共 IP 地址1Public IP addresses1 10 表示基本。10 for Basic. 联系支持人员。Contact support.
静态公共 IP 地址1Static Public IP addresses1 10 表示基本。10 for Basic. 联系支持人员。Contact support.
标准公共 IP 地址1Standard Public IP addresses1 1010 联系支持人员。Contact support.
公共 IP 前缀Public IP Prefixes 受订阅中标准公共 IP 数量的限制limited by number of Standard Public IPs in a subscription 联系支持人员。Contact support.
公共 IP 前缀长度Public IP prefix length /28/28 联系支持人员。Contact support.

1公共 IP 地址的默认限制因产品/服务类别类型而异,例如免费试用、即用即付、CSP。1Default limits for Public IP addresses vary by offer category type, such as Free Trial, Pay-As-You-Go, CSP. 例如,企业协议订阅的默认值为 1000。For example, the default for Enterprise Agreement subscriptions is 1000.

负载均衡器限制Load balancer limits

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

标准负载均衡器Standard Load Balancer

资源Resource 限制Limit
负载均衡器Load balancers 1,0001,000
每个资源的规则Rules per resource 1,5001,500
每个 NIC 的规则(跨 NIC 上的所有 IP)Rules per NIC (across all IPs on a NIC) 300300
前端 IP 配置Frontend IP configurations 600600
后端池大小Backend pool size 1,000 个 IP 配置,单个虚拟网络1,000 IP configurations, single virtual network
每个负载平衡器的后端资源 1Backend resources per Load Balancer 1 150150
高可用性端口High-availability ports 每个内部前端 1 个1 per internal frontend
每个负载均衡器的出站规则Outbound rules per Load Balancer 2020
TCP 空闲超时TCP idle timeout 4 分钟/30 分钟4 minutes/30 minutes

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

基本负载平衡器Basic Load Balancer

资源Resource 限制Limit
负载均衡器Load balancers 1,0001,000
每个资源的规则Rules per resource 250250
每个 NIC 的规则(跨 NIC 上的所有 IP)Rules per NIC (across all IPs on a NIC) 300300
前端 IP 配置Frontend IP configurations 200200
后端池大小Backend pool size 300 个 IP 配置,单一可用性集300 IP configurations, single availability set
每个负载均衡器的可用性集Availability sets per Load Balancer 150150

以下限制仅适用于通过每个订阅的经典部署模型管理的网络资源。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 100100 100100
本地网络站点Local network sites 2020 5050
每个虚拟网络的 DNS 服务器数DNS servers per virtual network 2020 2020
每个虚拟网络的专用 IP 地址数Private IP addresses per virtual network 4,0964,096 4,0964,096
虚拟机或角色实例的单 NIC 并发 TCP 或 UDP 流数Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 如果 NIC 至少有两个,则为 500,000(至多 1,000,000)。500,000, up to 1,000,000 for two or more NICs. 如果 NIC 至少有两个,则为 500,000(至多 1,000,000)。500,000, up to 1,000,000 for two or more NICs.
网络安全组 (NSG)Network Security Groups (NSGs) 200200 200200
每个 NSG 的 NSG 规则数NSG rules per NSG 1,0001,000 1,0001,000
用户定义路由表数User-defined route tables 200200 200200
每个路由表的用户定义的路由数User-defined routes per route table 400400 400400
公共 IP 地址 (动态)Public IP addresses (dynamic) 500500 500500
保留的公共 IP 地址Reserved public IP addresses 500500 500500
每个部署的公共 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

ExpressRoute 限制ExpressRoute limits

资源Resource 限制Limit
每个订阅的 ExpressRoute 线路数ExpressRoute circuits per subscription 1010
每个订阅的 ExpressRoute 电路,使用 Azure 资源管理器ExpressRoute circuits per region per subscription, with Azure Resource Manager 1010
使用 ExpressRoute 标准通告到 Azure 专用对等互连的最大路由数Maximum number of routes advertised to Azure private peering with ExpressRoute Standard 4,0004,000
使用 ExpressRoute 高级加载项通告到 Azure 专用对等互连的最大路由数Maximum number of routes advertised to Azure private peering with ExpressRoute Premium add-on 10,00010,000
从 ExpressRoute 连接的 VNet 地址空间从 Azure 专用对等互连通告的最大路由数Maximum number of routes advertised from Azure private peering from the VNet address space for an ExpressRoute connection 200200
使用 ExpressRoute 标准向 Microsoft 对等互连通告的最大路由数Maximum number of routes advertised to Microsoft peering with ExpressRoute Standard 200200
使用 ExpressRoute 高级加载项向 Microsoft 通告对等路由的最大路由数Maximum number of routes advertised to Microsoft peering with ExpressRoute Premium add-on 200200
在同一对等位置连接到同一虚拟网络的最大 ExpressRoute 电路数Maximum number of ExpressRoute circuits linked to the same virtual network in the same peering location 44
链接到不同对等互连位置中相同虚拟网络的最大 ExpressRoute 线路数Maximum number of ExpressRoute circuits linked to the same virtual network in different peering locations 44
每个 ExpressRoute 线路允许的虚拟网络链接数Number of virtual network links allowed per ExpressRoute circuit 请参阅每个 ExpressRoute 电路表的虚拟网络数See the Number of virtual networks per ExpressRoute circuit table.

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

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

*仅限 100 Gbps 快速路由*100 Gbps ExpressRoute Direct Only

备注

全局覆盖连接计入每个 ExpressRoute 电路的虚拟网络连接限制。Global Reach connections count against the limit of virtual network connections per ExpressRoute Circuit. 例如,10 Gbps 高级电路将允许 5 个全局到达连接和 95 个到 ExpressRoute 网关的连接或 95 个全局到达连接,以及 5 个到 ExpressRoute 网关的连接,或到 100 个连接限制的任何其他组合电路。For example, a 10 Gbps Premium Circuit would allow for 5 Global Reach connections and 95 connections to the ExpressRoute Gateways or 95 Global Reach connections and 5 connections to the ExpressRoute Gateways or any other combination up to the limit of 100 connections for the circuit.

虚拟 WAN 限制Virtual WAN limits

资源Resource 限制Limit
每个区域的虚拟 WAN 中心数Virtual WAN hubs per region 11
每个虚拟 WAN 的虚拟 WAN 中心数Virtual WAN hubs per virtual wan Azure 区域Azure regions
每个中心的 VPN(分支)连接数VPN (branch) connections per hub 1,0001,000
每个中心的 VNet 连接数VNet connections per hub 500500
每个中心的点到站点用户数Point-to-Site users per hub 10,00010,000
每个虚拟 WAN VPN 网关的聚合吞吐量Aggregate throughput per Virtual WAN VPN gateway 20 Gbps20 Gbps
每个虚拟 WAN VPN 连接的吞吐量(2 个隧道)Throughput per Virtual WAN VPN connection (2 tunnels) 2 Gbps 和 1 Gbps/IPsec 隧道2 Gbps with 1 Gbps/IPsec tunnel
每个虚拟 WAN ExpressRoute 网关的聚合吞吐量Aggregate throughput per Virtual WAN ExpressRoute gateway 20 Gbps20 Gbps

应用程序网关限制Application Gateway limits

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

资源Resource 限制Limit 注意Note
Azure 应用程序网关Azure Application Gateway 每个订阅 1,000 个1,000 per subscription
前端 IP 配置Front-end IP configurations 22 1 个公共,1 个专用1 public and 1 private
前端端口Front-end ports 10011001
后端地址池Back-end address pools 10011001
每个池的后端服务器数Back-end servers per pool 1,2001,200
HTTP 侦听器HTTP listeners 20012001 限制为路由流量的 100 个活动侦听器。Limited to 100 active listeners that are routing traffic. 活动侦听器 = 侦听器总数 - 未活动的侦听器。Active listeners = total number of listeners - listeners not active.
如果路由规则中的默认配置设置为路由流量(例如,它有一个侦听器、后端池和 HTTP 设置),则该配置也算作侦听器。If a default configuration inside a routing rule is set to route traffic (for example, it has a listener, a backend pool, and HTTP settings) then that also counts as a listener.
HTTP 负载均衡规则HTTP load-balancing rules 10011001
后端 HTTP 设置Back-end HTTP settings 10011001
每个网关的实例数Instances per gateway V1 SKU - 32V1 SKU - 32
V2 SKU - 125V2 SKU - 125
SSL 证书数SSL certificates 10011001 每个 HTTP 侦听器 1 个1 per HTTP listener
最大 SSL 证书大小Maximum SSL certificate size V1 SKU - 10 KBV1 SKU - 10 KB
V2 SKU - 16 KBV2 SKU - 16 KB
身份验证证书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 listener
每个侦听器的 URL 映射数URL maps per listener 11
每个 URL 映射基于路径的最大规则数Maximum path-based rules per URL map 100100
重定向配置数Redirect configurations 10011001
并发的 WebSocket 连接数Concurrent WebSocket connections 中型网关 20kMedium gateways 20k
大型网关 50kLarge gateways 50k
最大 URL 长度Maximum URL length 32KB32KB
HTTP/2 的最大标头大小Maximum header size for HTTP/2 4KB4KB
最大文件上传大小:标准Maximum file upload size, Standard 2 GB2 GB
最大文件上传大小 WAFMaximum file upload size WAF V1 中型 WAF 网关,100 MBV1 Medium WAF gateways, 100 MB
V1 大型 WAF 网关,500 MBV1 Large WAF gateways, 500 MB
V2 WAF,750 MBV2 WAF, 750 MB
WAF 正文大小限制,不带文件WAF body size limit, without files 128 KB128 KB
最大 WAF 自定义规则Maximum WAF custom rules 100100
最大 WAF 排除项数Maximum WAF exclusions 100100

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 限制Limit 注意Note
Azure 网络观察程序Azure Network Watcher 每个区域 1 个1 per region 创建网络观察程序是为了启用对服务的访问。Network Watcher is created to enable access to the service. 每个区域的每个订阅只需要一个网络观察程序实例。Only one instance of Network Watcher is required per subscription per region.
数据包捕获会话Packet capture sessions 每个区域 10,00010,000 per region 仅会话数,未保存捕获。Number of sessions only, not saved captures.

以下限制适用于 Azure 专用链接:The following limits apply to Azure private link:

资源Resource 限制Limit
每个虚拟网络的专用终结点数Number of private endpoints per virtual network 10001000
每个订阅的专用终结点数Number of private endpoints per subscription      6400064000
每个订阅的专用链接服务数Number of private link service per subscription       800800
专用链路服务上的 IP 配置数量Number of IP Configurations on a private link service    8 (此号码适用于每个 PLS 使用的 NAT IP 地址)8 (This number is for the NAT IP addresses used per PLS)
同一专用链接服务上的专用终结点数Number of private endpoints on the same private link service 10001000

流量管理器限制Traffic Manager limits

资源Resource 限制Limit
每个订阅的配置文件数Profiles per subscription 200200
每个配置文件的终结点数Endpoints per profile 200200

Azure 堡垒限制Azure Bastion limits

资源Resource 限制Limit
并发 RDP 连接数Concurrent RDP connections 25*25*
并发 SSH 连接数Concurrent SSH connections 50**50**

*可能因其他正在进行的 RDP 会话或其他正在进行的 SSH 会话而有所不同。*May vary due to other on-going RDP sessions or other on-going SSH sessions.
**如果存在现有的 RDP 连接或通过其他正在进行的 SSH 会话使用,则可能会有所不同。**May vary if there are existing RDP connections or usage from other on-going SSH sessions.

Azure DNS 限制Azure DNS limits

公共 DNS 区域Public DNS zones

资源Resource 限制Limit
每个订阅的公共 DNS 区域数Public DNS Zones per subscription 250 1250 1
每个公共 DNS 区域的记录集数Record sets per public DNS zone 10,000 110,000 1
公共 DNS 区域中每个记录集的记录数Records per record set in public DNS zone 2020
单个 Azure 资源的别名记录数Number of Alias records for a single Azure resource 2020
每个订阅的专用 DNS 区域Private DNS zones per subscription 10001000
每个专用 DNS 区域的记录集Record sets per private DNS zone 2500025000
为专用 DNS 区域设置的记录Records per record set for private DNS zones 2020
每个专用 DNS 区域的虚拟网络链接Virtual Network Links per private DNS zone 10001000
启用自动注册的专用 DNS 区域的虚拟网络链接Virtual Networks Links per private DNS zones with auto-registration enabled 100100
虚拟网络可以通过启用自动注册连接到的专用 DNS 区域数Number of private DNS zones a virtual network can get linked to with auto-registration enabled 11
虚拟网络可以链接的专用 DNS 区域数Number of private DNS zones a virtual network can get linked 10001000
虚拟机每秒可以发送到 Azure DNS 解析器的 DNS 查询数Number of DNS queries a virtual machine can send to Azure DNS resolver, per second 500 2500 2
每个虚拟机排队(挂起响应)的最大 DNS 查询数Maximum number of DNS queries queued (pending response) per virtual machine 200 2200 2

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

2这些限制应用于每个单独的虚拟机,而不是在虚拟网络级别。2These limits are applied to every individual virtual machine and not at the virtual network level. 将删除超出这些限制的 DNS 查询。DNS queries exceeding these limits are dropped.

Azure 防火墙限制Azure Firewall limits

资源Resource 限制Limit
数据吞吐量Data throughput 30 Gbps130 Gbps1
规则Rules 10,000.10,000. 所有规则类型合并。All rule types combined.
最大 DNAT 规则Maximum DNAT rules 298298
如果为 TCP 和 UDP 配置了规则的协议,则它计为两个规则。If a rule's protocol is configured for both TCP and UDP, it counts as two rules.
最小 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 最大值为 100 个(目前,仅为前五个公共 IP 地址添加 SNAT 端口。100 maximum (Currently, SNAT ports are added only for the first five public IP addresses.)
路由表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

资源Resource 限制Limit
每个订阅的 Azure 前门资源Azure Front Door resources per subscription 100100
每个资源的前端主机数(包括自定义域)Front-end hosts, which includes custom domains per resource 500500
每个资源的路由规则数Routing rules per resource 500500
每个资源的后端池数Back-end pools per resource 5050
每个后端池的后端数Back ends per back-end pool 100100
要匹配路由规则的路径模式数Path patterns to match for a routing rule 2525
单个缓存清除调用中的 URLURLs in a single cache purge call 100100
每个策略的自定义 Web 应用程序防火墙规则数Custom web application firewall rules per policy 100100
每个订阅的 Web 应用程序防火墙策略Web application firewall policy per subscription 100100
Web 应用程序防火墙根据每个自定义规则匹配条件数Web application firewall match conditions per custom rule 1010
每个匹配条件的 Web 应用防火墙 IP 地址范围数Web application firewall IP address ranges per match condition 600600
每个匹配条件的 Web 应用程序防火墙字符串匹配值数Web application firewall string match values per match condition 1010
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. 此值可通过 API 中的字段"发送 RecvTimeout 秒"进行配置。This value is configurable via the field sendRecvTimeoutSeconds in the API.
    • 对于缓存方案,此超时是不可配置的,因此,如果缓存了请求,并且从前门或后端的第一个数据包需要 30 多秒的时间,则将 504 错误返回到客户端。For caching scenarios, this timeout is not configurable and so, if a request is cached and it takes more than 30 seconds for the first packet from Front Door or from the backend, then a 504 error is returned 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. 此超时值不可配置。This timeout value is not configurable.
  • 前端 TCP 会话超时为 90 秒。Front Door to the back-end TCP session timeout is 90 seconds.

上传和下载数据限制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 的查询字符串)Maximum URL size - 8,192 bytes - Specifies maximum length of the raw URL (scheme + hostname + port + path + query string of the URL)
  • 最大查询字符串大小 - 4,096 字节 - 指定查询字符串的最大长度(以字节为单位)。Maximum Query String size - 4,096 bytes - Specifies the maximum length of the query string, in bytes.
  • 来自运行状况探测 URL 的最大 HTTP 响应标头大小 - 4,096 字节 - 指定运行状况探测的所有响应标头的最大长度。Maximum HTTP response header size from health probe URL - 4,096 bytes - Specified the maximum length of all the response headers of health probes.

通知中心限制Notification Hubs limits

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

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

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

资源Resource 限制Limit
每个 Azure 订阅的 Azure 资源角色分配数Role assignments for Azure resources per Azure subscription 2,0002,000
每个管理组的 Azure 资源角色分配数Role assignments for Azure resources per management group 500500
每个租户的 Azure 资源自定义角色数Custom roles for Azure resources per tenant 5,0005,000
每个租户的 Azure 资源自定义角色数Custom roles for Azure resources per tenant
(适用于 Azure 德国和 Azure 中国 21Vianet)(for Azure Germany and Azure China 21Vianet)
2,0002,000

服务总线限制Service Bus limits

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

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

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

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

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

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

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

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

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

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

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

属性包中属性的最大大小:没有明确的限制。Maximum size of property in property bag: No explicit limit. 受最大标头大小限制。Limited by maximum header size.
队列、主题或订阅实体的消息属性大小Message property size for a queue, topic, or subscription entity 实体Entity 生成异常序列化异常The exception SerializationException is generated. 每个属性的最大消息属性大小为 32,000。Maximum message property size for each property is 32,000. 所有属性的累积大小不能超过 64,000。Cumulative size of all properties can't exceed 64,000. 此限制适用于BrokeredMessage的整个标头 ,它同时具有用户属性和系统属性,如序列号标签MessageIdThis limit applies to the entire header of the BrokeredMessage, which has both user properties and system properties, such as SequenceNumber, Label, and MessageId.
每个主题的订阅数Number of subscriptions per topic 实体Entity 系统将拒绝后续的为主题创建更多订阅的请求。Subsequent requests for creating additional subscriptions for the topic are rejected. 因此,如果是通过门户配置的,会显示错误消息。As a result, if configured through the portal, an error message is shown. 如果是通过管理 API 调用的,调用代码将收到异常。If called from the management API, an exception is received by the calling code. 标准层每个主题 2,000 个主题。2,000 per-topic for the Standard tier.
每个主题的 SQL 筛选器数Number of SQL filters per topic 实体Entity 后续关于创建主题上其他筛选器的请求将被拒绝,并且调用代码会收到异常。Subsequent requests for creation of additional filters on the topic are rejected, and an exception is received by the calling code. 2,0002,000
每个主题的相关性筛选器数Number of correlation filters per topic 实体Entity 后续关于创建主题上其他筛选器的请求将被拒绝,并且调用代码会收到异常。Subsequent requests for creation of additional filters on the topic are rejected, and an exception is received by the calling code. 100,000100,000
SQL 筛选器或操作的大小Size of SQL filters or actions 命名空间Namespace 后续创建其他筛选器的请求将被拒绝,并且调用代码会收到异常。Subsequent requests for creation of additional filters are rejected, and an exception is received by the calling code. 筛选条件字符串的最大长度:1,024 (1 K)。Maximum length of filter condition string: 1,024 (1 K).

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

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

在服务总线命名空间上配置的规则适用于所有类型的:队列、主题。Rules that are configured on a Service Bus namespace apply to all types: queues, topics.
每个事务的消息数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.
虚拟网络和 IP 筛选器规则的数量Number of virtual network and IP filter rules 命名空间Namespace   128128

站点恢复限制Site Recovery limits

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

限制标识符Limit identifier 限制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

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.

存储限制Storage limits

下表描述了 Azure 通用 v1、v2、Blob 存储、块 Blob 存储和启用数据存储库的存储帐户的默认限制。The following table describes default limits for Azure general-purpose v1, v2, Blob storage, block blob storage, and Data Lake Storage Gen2 enabled storage accounts. 入口限制是指发送到存储帐户的所有数据。The ingress limit refers to all data that is sent to a storage account. 出口限制是指从存储帐户接收的所有数据。The egress limit refers to all data that is received from a storage account.

资源Resource 限制Limit
每个订阅每个区域的存储帐户数,包括启用标准存储 Gen2 的标准存储帐户和数据存储库帐户。3Number of storage accounts per region per subscription, including standard, premium, and Data Lake Storage Gen2 enabled storage accounts.3 250250
最大存储帐户容量Maximum storage account capacity 5 PiB 15 PiB 1
每个存储帐户的 Blob 容器、Blob、文件共享、表、队列、实体或消息数上限Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account 无限制No limit
每个存储帐户的最大请求速率1Maximum request rate1 per storage account 每秒 20,000 个请求20,000 requests per second
每个存储帐户的最大入口1(美国、欧洲区域)Maximum ingress1 per storage account (US, Europe regions) 25 Gbps25 Gbps
每个存储帐户的最大入口1(美国和欧洲以外的区域)Maximum ingress1 per storage account (regions other than US and Europe) 启用 RA-GRS/GRS 时为 5 Gbps,LRS/ZRS2为 10 Gbps5 Gbps if RA-GRS/GRS is enabled, 10 Gbps for LRS/ZRS2
常规用途 v2 存储帐户和 Blob 存储帐户的最大出口(所有区域)Maximum egress for general-purpose v2 and Blob storage accounts (all regions) 50 Gbps50 Gbps
通用 v1 存储帐户的最大出口(美国区域)Maximum egress for general-purpose v1 storage accounts (US regions) 如果启用 RA-GRS/GRS,则为 20 Gbps,LRS/ZRS2的 30 Gbps20 Gbps if RA-GRS/GRS is enabled, 30 Gbps for LRS/ZRS2
常规用途 v1 存储帐户的最大出口(非美国区域)Maximum egress for general-purpose v1 storage accounts (non-US regions) 如果启用 RA-GRS/GRS,则为 10 Gbps,LRS/ZRS2的 15 Gbps10 Gbps if RA-GRS/GRS is enabled, 15 Gbps for LRS/ZRS2
每个存储帐户的最大虚拟网络规则数Maximum number of virtual network rules per storage account 200200
每个存储帐户的最大 IP 地址规则数Maximum number of IP address rules per storage account 200200

1 Azure 存储标准帐户支持更高的容量限制和更高的请求进入限制。1 Azure Storage standard accounts support higher capacity limits and higher limits for ingress by request. 若要请求增加帐户限制,请与 Azure 支持联系。To request an increase in account limits, contact Azure Support.

2如果您的存储帐户启用了具有异地冗余存储 (RA-GRS) 或地理区域冗余存储 (RA-GZRS) 的读取访问,则辅助位置的传出目标与主位置的传出目标相同。2 If your storage account has read-access enabled with geo-redundant storage (RA-GRS) or geo-zone-redundant storage (RA-GZRS), then the egress targets for the secondary location are identical to those of the primary location. Azure 存储复制选项包括:Azure Storage replication options include:

3 Azure 数据湖存储 Gen2是一组专用于 Azure Blob 存储的大型数据分析功能。3 Azure Data Lake Storage Gen2 is a set of capabilities dedicated to big data analytics, built on Azure Blob storage. Azure 存储和 Blob 存储限制适用于数据湖存储第 2 代。Azure Storage and blob storage limitations apply to Data Lake Storage Gen2.

备注

Microsoft 建议您在大多数方案中使用通用 v2 存储帐户。Microsoft recommends 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. 有关详细信息,请参阅升级到常规用途 v2 存储帐户For more information, see Upgrade to a general-purpose v2 storage account.

如果应用程序的需求超过单个存储帐户的伸缩性目标,则可以构建使用多个存储帐户的应用程序。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 regardless of when they were created. 有关 Azure 存储的扁平网络体系结构和可伸缩性的详细信息,请参阅 Windows Azure 存储:具有高度一致性的高可用云存储服务For more information on the Azure Storage flat network architecture and on scalability, see Microsoft Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency.

有关标准存储帐户限制的详细信息,请参阅标准存储帐户的可伸缩性目标For more information on limits for standard storage accounts, see Scalability targets for standard storage accounts.

存储资源提供程序限制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 限制Limit
存储帐户管理操作数(读取)Storage account management operations (read) 每 5 分钟 800 次800 per 5 minutes
存储帐户管理操作数(写入)Storage account management operations (write) 每小时 1200 次1200 per hour
存储帐户管理操作数(列出)Storage account management operations (list) 每 5 分钟 100 次100 per 5 minutes

Azure Blob 存储限制Azure Blob storage limits

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

1 单个 blob 的吞吐量取决于多个因素,包括但不限于:并发性、请求大小、性能层、源上传速度和目标下载速度。1 Throughput for a single blob depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. 要利用高通量块 blob的性能增强,请上载较大的 blob 或块。To take advantage of the performance enhancements of high-throughput block blobs, upload larger blobs or blocks. 具体地说,对于标准存储帐户,请使用大于 4 MiB 的 Blob 或块大小调用 Put BlobPut Block 操作。Specifically, call the Put Blob or Put Block operation with a blob or block size that is greater than 4 MiB for standard storage accounts. 对于高级块 Blob 或 Data Lake 存储 Gen2 存储帐户,请使用大于 256 KiB 的块或 blob 大小。For premium block blob or for Data Lake Storage Gen2 storage accounts, use a block or blob size that is greater than 256 KiB.

Azure 文件限制Azure Files limits

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

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

*在大多数区域中可用,请参阅区域可用性,了解可用区域的详细信息。* Available in most regions, see Regional availability for the details on available regions.

Azure 文件同步限制Azure File Sync limits

资源Resource 目标Target 硬限制Hard limit
每个区域的存储同步服务数Storage Sync Services per region 20 个存储同步服务20 Storage Sync Services Yes
每个存储同步服务的同步组数Sync groups per Storage Sync Service 100 个同步组100 sync groups Yes
每个存储同步服务的已注册服务器Registered servers per Storage Sync Service 99 台服务器99 servers Yes
每个同步组的云终结点数Cloud endpoints per sync group 1 个云终结点1 cloud endpoint Yes
每个同步组的服务器终结点数Server endpoints per sync group 50 个服务器终结点50 server endpoints No
每个服务器的服务器终结点数Server endpoints per server 30 个服务器终结点30 server endpoints Yes
每个同步组的文件系统对象数(目录和文件)File system objects (directories and files) per sync group 1 亿个对象100 million objects No
目录中的最大文件系统对象(目录和文件)数Maximum number of file system objects (directories and files) in a directory 500 万个对象5 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 V9:基于文件系统群集大小(双文件系统群集大小)。V9: Based on file system cluster size (double file system cluster size). 例如,如果文件系统群集大小为 4kb,则最小文件大小将为 8kb。For example, if the file system cluster size is 4kb, the minimum file size will be 8kb.
V8 及更旧: 64 KiBV8 and older: 64 KiB
Yes

备注

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

下表描述了表存储的容量、可扩展性和性能目标。The following table describes capacity, scalability, and performance targets for Table storage.

资源Resource 目标Target
Azure 存储帐户中表的个数Number of tables in an Azure storage account 仅受存储帐户的容量限制Limited only by the capacity of the storage account
表中的分区个数Number of partitions in a table 仅受存储帐户的容量限制Limited only by the capacity of the storage account
分区中实体的个数Number of entities in a partition 仅受存储帐户的容量限制Limited only by the capacity of the storage account
单个表的最大大小Maximum size of a single table 500 TiB500 TiB
单个实体的最大大小,包括所有属性值Maximum size of a single entity, including all property values 1 MiB1 MiB
表实体中属性的最大数目Maximum number of properties in a table entity 255 (包括三个系统属性,分区键行键, 和时间戳255 (including the three system properties, PartitionKey, RowKey, and Timestamp)
实体中单个属性的最大总大小Maximum total size of an individual property in an entity 因属性类型而异。Varies by property type. 有关详细信息,请参阅了解表服务数据模型中的属性类型For more information, see Property Types in Understanding the Table Service Data Model.
PartitionKey 的大小Size of the PartitionKey 大小高达 1 KiB 的字符串A string up to 1 KiB in size
RowKey 的大小Size of the RowKey 大小高达 1 KiB 的字符串A string up to 1 KiB in size
实体组事务的大小Size of an entity group transaction 事务最多只能包含 100 个实体,有效负载的大小必须小于 4 MiB。A transaction can include at most 100 entities and the payload must be less than 4 MiB in size. 实体组事务只能包含对实体的更新一次。An entity group transaction can include an update to an entity only once.
每个表存储的访问策略的最大数目Maximum number of stored access policies per table 55
每个存储帐户的最大请求速率Maximum request rate per storage account 20,000 事务/秒,假定实体大小为 1-KiB20,000 transactions per second, which assumes a 1-KiB entity size
单个表分区的目标吞吐量(1 KiB 实体)Target throughput for a single table partition (1 KiB-entities) 每秒最多 2,000 个实体Up to 2,000 entities per second

虚拟机磁盘限制Virtual machine disk limits

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

重要

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

对于 Azure 托管磁盘:For Azure managed disks:

下表说明了每个订阅每个区域的资源数的默认和最大限制。The following table illustrates the default and maximum limits of the number of resources per region per subscription. 每个资源组的托管磁盘、快照和映像数没有限制。There is no limit for the number of Managed Disks, snapshots and images per resource group.

资源Resource 限制Limit
标准托管磁盘Standard managed disks 50,00050,000
标准 SSD 托管磁盘Standard SSD managed disks 50,00050,000
高级托管磁盘Premium managed disks 50,00050,000
Standard_LRS快照Standard_LRS snapshots 50,00050,000
Standard_ZRS快照Standard_ZRS snapshots 50,00050,000
托管映像Managed image 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。For example, for a Basic tier VM, the maximum number of highly utilized disks is about 66, which is 20,000/300 IOPS per disk. 标准层 VM 的最大高度使用磁盘数约为 40,即每个磁盘 20,000/500 IOPS。The maximum number of highly utilized disks for a Standard tier VM is about 40, which is 20,000/500 IOPS per disk.

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

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

托管虚拟机磁盘Managed virtual machine disks

标准硬盘托管磁盘Standard HDD managed disks

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

标准 SSD 托管磁盘Standard SSD managed disks

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

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

高级 SSD 大小Premium SSD sizes  P1P1 P2P2 P3P3 P4P4 P6P6 P10P10 P15P15 P20P20 P30P30 P40P40 P50P50 P60P60 P70P70 P80P80
磁盘大小 (GiB)Disk size in GiB 44 88 1616 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0964,096 8,1928,192 16,38416,384 32,76732,767
每个磁盘预配的 IOPSProvisioned IOPS per disk 120120 120120 120120 120120 240240 500500 1,1001,100 2,3002,300 5,0005,000 7,5007,500 7,5007,500 16,00016,000 18,00018,000 20,00020,000
每个磁盘预配的吞吐量Provisioned Throughput per disk 25 MiB/秒25 MiB/sec 25 MiB/秒25 MiB/sec 25 MiB/秒25 MiB/sec 25 MiB/秒25 MiB/sec 50 MiB/秒50 MiB/sec 100 MiB/秒100 MiB/sec 125 MiB/秒125 MiB/sec 150 MiB/秒150 MiB/sec 200 MiB/秒200 MiB/sec 250 MiB/秒250 MiB/sec 250 MiB/秒250 MiB/sec 500 MiB/秒500 MiB/sec 750 MiB/秒750 MiB/sec 900 MiB/秒900 MiB/sec
每个磁盘最大的突发 IOPSMax burst IOPS per disk 3,5003,500 3,5003,500 3,5003,500 3,5003,500 3,5003,500 3,5003,500 3,5003,500 3,5003,500
每个磁盘最大的突发吞吐量Max burst throughput per disk 170 MiB/秒170 MiB/sec 170 MiB/秒170 MiB/sec 170 MiB/秒170 MiB/sec 170 MiB/秒170 MiB/sec 170 MiB/秒170 MiB/sec 170 MiB/秒170 MiB/sec 170 MiB/秒170 MiB/sec 170 MiB/秒170 MiB/sec
最大突发持续时间Max burst duration 30 分钟30 min 30 分钟30 min 30 分钟30 min 30 分钟30 min 30 分钟30 min 30 分钟30 min 30 分钟30 min 30 分钟30 min
符合预留条件Eligible for reservation No No No No No No No No 是,最多一年Yes, up to one year 是,最多一年Yes, up to one year 是,最多一年Yes, up to one year 是,最多一年Yes, up to one year 是,最多一年Yes, up to one year 是,最多一年Yes, up to one year

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

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

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

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

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

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

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

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

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

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

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

资源Resource 限制Limit
每个 VM 的最大 IOPSMaximum IOPS per VM GS5 VM 为 80,000 IOPS80,000 IOPS with GS5 VM
每个 VM 的最大吞吐量Maximum throughput per VM 使用 GS5 VM 时,2,000 MB/秒2,000 MB/sec with GS5 VM

StorSimple 系统限制StorSimple System limits

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

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

流分析限制Stream Analytics limits


限制标识符Limit identifier 限制Limit 注释Comments
每个区域每个订阅的最大流式处理单元数Maximum number of streaming units per subscription per region 500500 要请求将订阅的流式处理单元增加到 500 之后,请与Microsoft 支持To request an increase in streaming units for your subscription beyond 500, contact Microsoft Support.
每个作业的最大输入数目Maximum number of inputs per job 6060 每个 Azure 流分析作业有 60 个输入的硬限制。There's a hard limit of 60 inputs per Azure Stream Analytics job.
每个作业的最大输出数目Maximum number of outputs per job 6060 每个流分析作业有 60 个输出的硬限制。There's a hard limit of 60 outputs per Stream Analytics job.
每个作业的最大函数数目Maximum number of functions per job 6060 每个流分析作业有 60 个函数的硬限制。There's a hard limit of 60 functions per Stream Analytics job.
每个作业的最大流式处理单元数Maximum number of streaming units per job 192192 每个流分析作业的流单元限制为 192 个硬限制。There's a hard limit of 192 streaming units per Stream Analytics job.
每个区域的最大作业数目Maximum number of jobs per region 1,5001,500 每个订阅每个地理区域最多可以有 1,500 个作业。Each subscription can have up to 1,500 jobs per geographical region.
引用数据 blob MBReference data blob MB 300300 参考数据 blob 不能大于每个 300 MB。Reference data blobs can't be larger than 300 MB each.

虚拟机限制Virtual Machines limits

虚拟机限制Virtual Machines limits

资源Resource 限制Limit
每个云服务的虚拟机数1Virtual machines per cloud service1 5050
每个云服务的输入终结点数2Input endpoints per cloud service2 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.

资源Resource 限制Limit
每个订阅的 VM 数VMs per subscription 每个区域 25,000 个125,0001 per region.
每个订阅的 VM 核心总数VM total cores per subscription 每个区域 201。201 per region. 联系支持以增加限制。Contact support to increase limit.
Azure Spot VM 每个订阅的总内核数Azure Spot VM total cores per subscription 每个区域 201。201 per region. 联系支持以增加限制。Contact support to increase limit.
VM 系列(例如 Dv2 和 F)、每个订阅的核心数VM per series, such as Dv2 and F, cores per subscription 每个区域 201。201 per region. 联系支持以增加限制。Contact support to increase limit.
每个订阅的可用性集Availability sets per subscription 每个区域 2,000 个。2,000 per region.
每个可用性集的虚拟机数Virtual machines per availability set 200200
每个订阅的证书数Certificates per subscription 无限制2Unlimited2

1默认限制因产品/服务类别类型而异,例如免费试用和即用即付,以及按系列(如 Dv2、F 和 G)更改。例如,企业协议订阅的默认值为 350。1Default limits vary by offer category type, such as Free Trial and Pay-As-You-Go, and by series, such as Dv2, F, and G. For example, the default for Enterprise Agreement subscriptions is 350.

2使用 Azure 资源管理器,证书存储在 Azure 密钥保管库中。2With 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.

备注

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

使用共享映像库部署资源时,每个订阅存在限制: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 限制Limit
规模集中的 VM 的最大数目Maximum number of VMs in a scale set 1,0001,000
最大 VM 数,具体取决于规模集中的自定义 VM 映像Maximum number of VMs based on a custom VM image in a scale set 600600
区域中规模集的最大数目Maximum number of scale sets in a region 2,0002,000

请参阅See also