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 vm。You 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.

「 軟 限制」和「 固定限制 」通常會用非正式方式來描述目前的可調整限制， (軟限制) ，而最大限制 () 的固定限制。The terms soft limit and hard limit often are used informally to describe the current, adjustable limit (soft limit) and the maximum limit (hard limit). 如果無法調整限制，就不會有軟限制，只有硬性限制。If a limit isn't adjustable, there won't be a soft limit, only a hard limit.

免費試用版 訂用帳戶不符合限制或配額增加的資格。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.

如需 Resource Manager API 讀取和寫入限制的相關資訊，請參閱對 Resource Manager 要求進行節流。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
每個 Azure AD 租用戶的管理群組Management groups per Azure AD tenant 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. 若要刪除管理群組層級部署，請使用 Remove-AzManagementGroupDeployment 或 az deployment mg delete。To delete management group level deployments, use Remove-AzManagementGroupDeployment or az deployment mg delete.

訂用帳戶限制Subscription limits

當您使用 Azure Resource Manager 和 Azure 資源群組時，適用下列限制。The following limits apply when you use Azure Resource Manager and Azure resource groups.

資源Resource 限制Limit
每個 Azure Active Directory 租用戶的訂用帳戶Subscriptions per Azure Active Directory tenant 無限制Unlimited
每個訂用帳戶的共同管理員Coadministrators per subscription 無限制Unlimited
每個訂用帳戶的資源群組Resource groups per subscription 980980
Azure Resource Manager 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 才會傳回訂用帳戶中唯一標記名稱和值的清單。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 that are no longer needed from the history. 若要刪除訂用帳戶層級部署，請使用 Remove-AzDeployment 或 az deployment sub delete。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當記錄接近上限時，部署會自動從歷程記錄中刪除。1Deployments are automatically deleted from the history as you near the limit. 從部署歷程記錄中刪除項目時，不會影響部署的資源。Deleting an entry from the deployment history doesn't affect the deployed resources. 如需詳細資訊，請參閱 從部署歷程記錄自動刪除。For more information, see Automatic deletions from deployment history.

範本限制Template limits

值Value 限制Limit
參數Parameters 256256
變數Variables 256256
資源 (包括複本計數)Resources (including copy count) 800800
輸出Outputs 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
租用戶Tenants 單一使用者能以成員或來賓的身分，隸屬於最多 500 個 Azure AD 租用戶。A single user can belong to a maximum of 500 Azure AD tenants as a member or a guest.
單一使用者最多可以建立 200 個目錄。A single user can create a maximum of 200 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 tenant.
資源Resources
  • 根據預設，在免費版的 Azure Active Directory 中，最多可以在單一租用戶中建立 50000 個 Azure AD 資源。A maximum of 50,000 Azure AD resources can be created in a single tenant by users of the Free edition of Azure Active Directory by default. 如果您至少有一個已驗證的網域，則貴組織的預設 Azure AD 服務配額會擴充至 300000 個 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 服務配額仍會維持在 50,000 個 Azure AD 資源。Azure AD service quota for organizations created by self-service sign-up remains 50,000 Azure AD resources even after you performed an internal admin takeover and the organization is converted to a managed tenant with at least one verified domain. 此服務限制與 Azure AD 定價頁面上的定價層限制 500000 個資源無關。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.
  • 任何單一 Azure AD 資源均可寫入 100 個延伸模組值，包括所有類型和所有應用程式皆可。Only 100 extension values, across all types and all applications, can be written to any single Azure AD resource.
  • 只能使用「字串」類型或「二進位」類型單一值屬性來擴充 User、Group、TenantDetail、Device、Application 和 ServicePrincipal 實體。Only User, Group, TenantDetail, Device, Application, and ServicePrincipal entities can be extended with string-type or binary-type single-valued attributes.
  • 結構描述延伸模組僅適用於圖形 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.
  • 密碼型 SSO 應用程式的限制為 48 個使用者，這表示每個應用程式的使用者名稱/密碼配對有 48 個金鑰的限制。Password-based SSO app has a limit of 48 users, which means that there is a limit of 48 keys for username/password pairs per app. 如果您想要新增其他使用者，請參閱針對 Azure AD 中的密碼型單一登入進行疑難排解中的疑難排解指示。If you want to add additional users, see the troubleshooting instructions in Troubleshoot password-based single sign-on in Azure AD.
應用程式資訊清單Application Manifest 最多可以在應用程式資訊清單中新增 1200 個項目。A maximum of 1200 entries can be added in the Application Manifest.
群組Groups
  • 非系統管理員使用者最多可以在 Azure AD 組織中建立 250 個群組。A non-admin user can create a maximum of 250 groups in an Azure AD organization. 任何可以管理組織中群組的 Azure AD 系統管理員，也可以建立不限數目的群組 (最高可達 Azure AD 物件限制)。Any Azure AD admin who can manage groups in the organization can also create unlimited number of groups (up to the Azure AD object limit). 如果您指派角色以移除使用者的限制，請將其指派給權限較低的內建角色，例如使用者系統管理員或群組系統管理員。If you assign a role to remove the limit for a user, assign them to a less privileged built-in role such as User Administrator or Groups Administrator.
  • 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 群組中的成員數目限制為 5 萬個成員。By default, 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 Connect Sync V2 端點 API 上線。If you need to synch a group membership that's over this limit, you must onboard the Azure AD Connect Sync V2 endpoint API.
  • 在所有案例中都不支援 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 in which the signed-in user is a member are included)
  • 條件式存取 (當條件式存取原則具有群組範圍時)Conditional access (when a conditional access policy has a group scope)
  • 限制對自助式密碼重設的存取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)
  • Microsoft 365 群組。Microsoft 365 Groups.
應用程式 ProxyApplication Proxy
  • 每個應用程式 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 regardless of assigned licenses.
報表Reports 在任何報告中，最多可以檢視或下載 1000 個資料列。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.
Azure AD 角色和權限Azure AD roles and permissions
  • 可以在 Azure AD 組織中建立最多 30 個 Azure AD 自訂角色。A maximum of 30 Azure AD custom roles can be created in an Azure AD organization.
  • 無法將群組新增為群組擁有者。A group can't be added as a group owner.
  • 使用者讀取其他使用者租用戶資訊的能力，只能由 Azure AD 全組織的交換器進行限制，以停用所有租用戶資訊的所有非系統管理員使用者存取權 (不建議)。A user's ability to read other users' tenant information can be restricted only by the Azure AD organization-wide switch to disable all non-admin users' access to all tenant information (not recommended). 如需詳細資訊，請參閱限制成員使用者的預設權限。For more information, see To restrict the default permissions for member users.
  • 最多可能需要 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 每個單位 2048 個42,048 per unit4
最大快取回應大小Maximum cached response size 2 MiB2 MiB
原則文件大小上限Maximum policy document size 256 KiB5256 KiB5
每個服務執行個體的自訂閘道網域數目上限6Maximum custom gateway domains per service instance6 2020
每個服務執行個體的 CA 憑證數目上限7Maximum number of CA certificates per service instance7 1010
每個訂用帳戶的服務執行個體數目上限8Maximum number of service instances per subscription8 2020
每個服務執行個體的訂用帳戶數目上限8Maximum number of subscriptions per service instance8 500500
每個服務執行個體的用戶端憑證數目上限8Maximum number of client certificates per service instance8 5050
每個服務執行個體的 API 數目上限8Maximum number of APIs per service instance8 5050
每個服務執行個體的 API 作業數目上限8Maximum number of API operations per service instance8 1,0001,000
總要求持續時間上限8Maximum total request duration8 30 秒30 seconds
緩衝承載大小上限8Maximum buffered payload size8 2 MiB2 MiB
要求 URL 大小上限9Maximum request URL size9 4096 個位元組4096 bytes
URL 路徑區段的最大長度10Maximum length of URL path segment10 260 個字元260 characters
自我裝載閘道數目上限11Maximum number of self-hosted gateways11 2525

1調整限制取決於定價層。1Scaling limits depend on the pricing tier. 如需定價層及其調整限制的詳細資訊，請參閱 API 管理價格。For details on 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. 開發人員層的限制為 1024 個。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. 在使用層原則中，原則文件大小限制為 16 KiB。In the Consumption tier, policy document size is limited to 16 KiB.
6只有開發人員和進階層支援多個自訂網域。6Multiple custom domains are supported in the Developer and Premium tiers only.
7使用層不支援 CA 憑證。7CA certificates are not supported in the Consumption tier.
8此限制僅適用於使用層。8This limit applies to the Consumption tier only. 其他層級的這些類別沒有任何限制。There are no limits in these categories for other tiers.
9僅適用於使用層。9Applies to the Consumption tier only. 包含最多 2048 個位元組長的查詢字串。Includes an up to 2048 bytes long query string.
10若要提高此限制，請連絡支援人員。10 To raise this limit please contact support.
11只有開發人員和進階層支援自我裝載閘道。11Self-hosted gateways are supported in the Developer and Premium tiers only. 此限制適用於自我裝載閘道資源數目。The limit applies to the number of self-hosted gateway resources. 若要提高此限制，請連絡支援。To raise this limit please contact support. 請注意，在進階層中，與自我裝載閘道資源相關聯的節點 (或複本) 數目沒有限制，而在開發人員層的單一節點上具有上限。Note, that the number of nodes (or replicas) associated with a self-hosted gateway resource is unlimited in the Premium tier and capped at a single node in the Developer tier.

應用程式服務限制App Service limits

下列 App Service 限制包含 Web 應用程式、行動應用程式和 API 應用程式的限制。The following App Service limits include limits for Web Apps, Mobile Apps, and API Apps.

資源Resource 免費Free 共用Shared 基本Basic 標準Standard 進階 (v1-v3)Premium (v1-v3) 隔離Isolated
每個 Azure App Service 方案1的 Web、Mobile 或 API AppsWeb, mobile, or API apps per Azure App Service plan1 1010 100100 無限制2Unlimited2 無限制2Unlimited2 無限制2Unlimited2 無限制2Unlimited2
App Service 計劃App Service plan 每個區域 10 個10 per region 每個資源群組 10 個10 per resource group 每個資源群組 100 個100 per resource group 每個資源群組 100 個100 per resource group 每個資源群組 100 個100 per resource group 每個資源群組 100 個100 per resource group
計算執行個體類型Compute instance type 共用Shared 共用Shared 專用3Dedicated3 專用3Dedicated3 專用3Dedicated3

 專用3Dedicated3
擴充 (執行個體數目上限)Scale out (maximum instances) 1 個共用1 shared 1 個共用1 shared 3 個專用33 dedicated3 10 個專用310 dedicated3 適用於 v1 和 v2 的 20 個專用；適用於 v3 的 30 個專用。320 dedicated for v1 and v2; 30 dedicated for v3.3 100 個專用4100 dedicated4
儲存體5Storage5 1 GB51 GB5 1 GB51 GB5 10 GB510 GB5 50 GB550 GB5 250 GB5250 GB5

若超過 250 GB，請提交支援要求。For more than 250 GB, submit a support request.		 1 TB51 TB5

可用的儲存體配額是 999 GB。The available storage quota is 999 GB.
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 Minuten60 minutes 240 Minuten240 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) 每個 App Service 方案 1,024 MB1,024 MB per App Service plan 每個應用程式 1,024 MB1,024 MB per app N/AN/A N/AN/A N/AN/A N/AN/A
頻寬Bandwidth 165 MB165 MB 無限制，套用 資料傳輸費率Unlimited, data transfer rates apply 無限制，套用 資料傳輸費率Unlimited, data transfer rates apply 無限制，套用 資料傳輸費率Unlimited, data transfer rates apply 無限制，套用 資料傳輸費率Unlimited, data transfer rates apply 無限制，套用 資料傳輸費率Unlimited, data transfer rates apply
應用程式架構Application architecture 32 位元32-bit 32 位元32-bit 32 位元/64 位元32-bit/64-bit 32 位元/64 位元32-bit/64-bit 32 位元/64 位元32-bit/64-bit 32 位元/64 位元32-bit/64-bit
每個執行個體的 Web 通訊端7Web sockets per instance7 55 3535 350350 無限制Unlimited 無限制Unlimited 無限制Unlimited
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
每一訂用帳戶的 App Service 憑證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 每個方案 5 個5 per plan 每個方案 25 個25 per plan 每個應用程式 200 個200 per app 每個應用程式 200 個200 per app
虛擬網路整合Virtual Network Integration XX XX XX
私人端點Private Endpoints 每個應用程式 100 個100 per app
整合式負載平衡器Integrated load balancer XX XX XX XX X10X10
存取限制Access restrictions 每一應用程式 512 個規則512 rules per app 每一應用程式 512 個規則512 rules per app 每一應用程式 512 個規則512 rules per app 每一應用程式 512 個規則512 rules per app 每一應用程式 512 個規則512 rules per app 每一應用程式 512 個規則512 rules per app
Always OnAlways 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)
AutoscaleAutoscale XX XX XX
WebJobs11WebJobs11 XX XX XX XX XX XX
端點監視Endpoint monitoring XX XX XX XX
每個應用程式的預備位置Staging slots per app 55 2020 2020
在生產環境中測試Testing in Production XX XX XX
診斷記錄Diagnostic Logs XX XX XX XX XX XX
KuduKudu XX XX XX XX XX XX
驗證和授權Authentication and Authorization XX XX XX XX XX XX
App Service 受控憑證 (公開預覽)12App Service Managed Certificates (Public Preview)12 XX XX XX XX
SLASLA 99.95%99.95% 99.95%99.95% 99.95%99.95% 99.95%99.95%

1應用程式和儲存體配額是依每個 App Service 方案為準，除非另有指示。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. 如需詳細資訊，請參閱 App Service 價格。For more information, see App Service pricing.
4可應要求提高數量。4More are allowed upon request.
5儲存體限制是跨相同 App Service 方案中所有應用程式的目前總大小。5The storage limit is the total content size across all apps in the same App service plan. 單一資源群組和區域中所有 App Service 方案上的所有應用程式內容大小總計不能超過 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 15,000 個 (7,500 x 2 個核心) 和每個大型 VM 75,000 個 (18,750 x 4 個核心)。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).
8IP 連線數會以執行個體為基礎，並且取決於執行個體的大小：每個 B1/S1/P1V3 執行個體 1,920 個、每個 B2/S2/P2V3 執行個體3,968 個、每個 B3/S3/P3V3 執行個體 8,064 個。8The maximum IP connections are per instance and depend on the instance size: 1,920 per B1/S1/P1V3 instance, 3,968 per B2/S2/P2V3 instance, 8,064 per B3/S3/P3V3 instance.
9您可以透過支援要求將每個訂用帳戶的 App Service 憑證配額限制增加到最多 200 個。9The App Service Certificate quota limit per subscription can be increased via a support request to a maximum limit of 200.
10App Service 隔離式 SKU 能夠透過 Azure Load Balancer 在內部達成負載平衡 (ILB)，因此網際網路未提供公用連線。10App Service Isolated SKUs can be internally load balanced (ILB) with Azure Load Balancer, so there's no public connectivity from the internet. 因此，ILB 隔離式 App Service 的某些功能必須從具有 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在您的 App Service 執行個體中，以背景工作的方式隨選、依照排程或連續執行自訂可執行檔和/或指令碼。11Run custom executables and/or scripts on demand, on a schedule, or continuously as a background task within your App Service instance. 若要連續執行 WebJobs，「永遠開啟」是必要選項。Always On is required for continuous WebJobs execution. 可在 App Service 執行個體中執行的 WebJobs 數目沒有預先定義的限制。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.

12不支援裸網域。12Naked domains are not supported. 只發出標準憑證 (無法使用萬用字元憑證)。Only issuing standard certificates (wildcard certificates are not available). 限制為每個自訂網域只能有一個免費憑證。Limited to only one free certificate per custom domain.

自動化限制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 (約 4 百萬個作業)10 GB (approximately 4 million jobs) 達到此限制時，後續的建立作業要求會失敗。When this limit is reached, the subsequent requests to create a job fail.
最大作業串流限制Maximum job stream limit 1 MiB1 MiB 單一資料流不可大於 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 KB512 kilobytes
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 KB512 kilobytes
保留作業資料的天數上限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.

ResourceResource 限制Limit 備註Notes
檔案File 500500
登錄Registry 250250
Windows 軟體Windows software 250250 不包含軟體更新。Doesn't include software updates.
Linux 套件Linux packages 1,2501,250
服務Services 250250
精靈Daemon 250250

更新管理Update Management

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

ResourceResource 限制Limit 備註Notes
每個更新部署的電腦數目Number of machines per update deployment 10001000

Azure 應用程式組態Azure App Configuration

資源Resource 限制Limit
設定存放區-免費層Configuration stores - Free tier 1/每個訂用帳戶1 per subscription
設定存放區-標準層Configuration stores - Standard tier 每個訂用帳戶無限制unlimited per subscription
Configuration store 要求-免費層Configuration store requests - Free tier 每日1000個要求1,000 requests per day
設定存放區要求-標準層Configuration store requests - Standard tier 節流從每小時20000個要求開始Throttling starts at 20,000 requests per hour
免儲存層Storage - Free tier 10 MB10 MB
儲存體-標準層Storage - Standard tier 1 GB1 GB
索引鍵和值keys and values 單一索引鍵/值專案為 10 KB10 KB for a single key-value item

Azure Cache for Redis 限制Azure Cache for Redis limits

資源Resource 限制Limit
快取大小Cache size 1.2 TB1.2 TB
資料庫Databases 6464
連線的用戶端上限Maximum connected clients 40,00040,000
Azure Cache for Redis 複本 (供高可用性)Azure Cache for Redis replicas, for high availability 11
高級快取中包含叢集的分區Shards in a premium cache with clustering 1010

針對各個定價層，Azure Cache for Redis 限制與大小有所不同。Azure Cache for Redis limits and sizes are different for each pricing tier. 若要查看定價層和其相關聯的大小，請參閱 Azure Cache for Redis 定價。To see the pricing tiers and their associated sizes, see Azure Cache for Redis pricing.

如需 Azure Cache for Redis 組態限制的相關資訊，請參閱預設 Redis 伺服器組態。For more information on Azure Cache for Redis configuration limits, see Default Redis server configuration.

因為 Azure Cache for Redis 執行個體是由 Microsoft 設定與管理，所以 Azure Cache for 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 Cache for 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 基本Basic 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/AN/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

搜尋服務受限於磁碟空間，或者索引或索引子的數目上限，取決於何者先出現。A search service is constrained by disk space or by a hard limit on the maximum number of indexes or indexers, whichever comes first. 下表記載儲存體限制。The following table documents storage limits. 如需最大物件限制，請參閱依資源的限制。For maximum object limits, see Limits by resource.

資源Resource 免費Free 基本1Basic1 S1S1 S2S2 S3S3 S3 HDS3 HD L1L1 L2L2
服務等級協定 (SLA)2Service level agreement (SLA)2 否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/AN/A 11 1212 1212 1212 33 1212 1212
分割區大小Partition size N/AN/A 2 GB2 GB 25 GB25 GB 100 GB100 GB 200 GB200 GB 200 GB200 GB 1 TB1 TB 2 TB2 TB
複本數Replicas N/AN/A 33 1212 1212 1212 1212 1212 1212

1 [基本] 具有一個固定的磁碟分割。1 Basic has one fixed partition. 您可以使用其他搜尋單位來新增大型查詢磁碟區的複本。Additional search units can be used to add replicas for larger query volumes.

2 服務等級協定適用於專用資源上的可計費服務。2 Service level agreements are in effect 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. 美國西部 2 有 100 個電腦視覺資源和美國東部有 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 作業Operation 限制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

適用於 MySQL 的 Azure 資料庫Azure Database for MySQL

如需適用於 MySQL 的 Azure 資料庫限制詳細資訊，請參閱適用於 MySQL 的 Azure 資料庫中的限制。For Azure Database for MySQL limits, see Limitations in Azure Database for MySQL.

適用於 PostgreSQL 的 Azure 資料庫Azure Database for PostgreSQL

如需適用於 PostgreSQL 的 Azure 資料庫限制詳細資訊，請參閱適用於 PostgreSQL 的 Azure 資料庫中的限制。For Azure Database for PostgreSQL limits, see Limitations in Azure Database for PostgreSQL.

Azure Functions 限制Azure Functions limits

資源Resource 取用方案Consumption plan 進階方案Premium plan 專用方案Dedicated plan ASEASE KubernetesKubernetes
預設逾時持續時間 (分鐘)Default timeout duration (min) 55 3030 301301 3030 3030
最大逾時持續時間 (分鐘)Max timeout duration (min) 1010 無限制7unbounded7 無限制2unbounded2 無限制unbounded 無限制unbounded
連出連線上限 (每個執行個體)Max outbound connections (per instance) 600 個作用中 (總計 1200)600 active (1200 total) 無限制unbounded 無限制unbounded 無限制unbounded 無限制unbounded
要求大小上限 (MB)3Max request size (MB)3 100100 100100 100100 100100 取決於叢集Depends on cluster
查詢字串長度上限3Max query string length3 40964096 40964096 40964096 40964096 取決於叢集Depends on cluster
要求 URL 長度上限3Max request URL length3 81928192 81928192 81928192 81928192 取決於叢集Depends on cluster
每個執行個體的 ACUACU per instance 100100 210-840210-840 100-840100-840 210-2508210-2508 AKS 定價AKS pricing
記憶體上限 (每個執行個體的 GB)Max memory (GB per instance) 1.51.5 3.5-143.5-14 1.75-141.75-14 3.5 - 143.5 - 14 支援任何節點Any node is supported
每個方案的函式應用程式Function apps per plan 100100 100100 無限制4unbounded4 無限制unbounded 無限制unbounded
App Service 方案App Service plans 每個區域 100 個100 per region 每個資源群組 100 個100 per resource group 每個資源群組 100 個100 per resource group - -
儲存體5Storage5 5 TB5 TB 250 GB250 GB 50-1000 GB50-1000 GB 1 TB1 TB n/an/a
每個應用程式的自訂網域Custom domains per app 50065006 500500 500500 500500 n/an/a
自訂網域 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 包含無限制的 SNI SSL 和 1 個 IP SSL 連線unbounded SNI SSL and 1 IP SSL connections included n/an/a

1根據預設，App Service 方案中 Functions 1.x 執行階段的逾時不受限制。1 By default, the timeout for the Functions 1.x runtime in an App Service plan is unbounded.
2 需要將 App Service 方案設定為 Always On。2 Requires the App Service plan be set to Always On. 以標準費率付費。Pay at standard rates.
3 這些限制設定於主機。3 These limits are set in the host.
4 您可以裝載的實際函式應用程式數目，會視應用程式的活動、電腦執行個體的大小，及對應的資源使用率而定。4 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.
5 儲存體限制是在暫存儲存體中相同 App Service 方案中所有應用程式的內容總大小。5 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.
6 當您的函式應用程式裝載於取用方案時，僅支援 CNAME 選項。6 When your function app is hosted in a Consumption plan, only the CNAME option is supported. 對於進階方案或 App Service 方案中的函式應用程式，您可以使用 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.
7 保證最多60 分鐘。7 Guaranteed for up to 60 minutes.
8背景工作角色是裝載客戶應用程式的角色。8 Workers are roles that host customer apps. 背景工作角色可以三個固定的大小提供：一個 vCPU/3.5 GB RAM；兩個 vCPU/7 GB 的 RAM；四個 vCPU/14 GB RAM。Workers are available in three fixed sizes: One vCPU/3.5 GB RAM; Two vCPU/7 GB RAM; Four vCPU/14 GB RAM.

如需詳細資訊，請參閱 主控方案比較的函式。For more information, see Functions Hosting plans comparison.

Azure Kubernetes Service 限制Azure Kubernetes Service limits

資源Resource 限制Limit
每個訂用帳戶的叢集上限Maximum clusters per subscription 10001000
具有虛擬機器可用性設定組和基本 Load Balancer SKU 的每個叢集節點數目上限Maximum nodes per cluster with Virtual Machine Availability Sets and Basic Load Balancer SKU 100100
具有虛擬機器擴展集和 Standard Load Balancer SKU 的每個叢集節點數目上限Maximum nodes per cluster with Virtual Machine Scale Sets and Standard Load Balancer SKU 1000 (每個節點集區 100 個節點)1000 (100 nodes per node pool)
每個節點的 Pod 數目上限：採用 Kubenet 的基本網路Maximum pods per node: Basic networking with Kubenet 110110
每個節點的 Pod 數目上限：使用 Azure Container 網路介面的進階網路Maximum pods per node: Advanced networking with Azure Container Networking Interface Azure CLI 部署：301Azure CLI deployment: 301
Azure Resource Manager 範本：301Azure Resource Manager template: 301
入口網站部署：30Portal deployment: 30

1 當您使用 Azure CLI 或 Resource Manager 範本部署 Azure Kubernetes Service (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 Machine Learning 限制Azure Machine Learning limits

您可以在 [Azure Machine Learning 配額] 頁面中找到 Azure Machine Learning 計算配額的最新值The latest values for Azure Machine Learning Compute quotas can be found in the Azure Machine Learning quota page

Azure 地圖服務限制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 訂用帳戶中 Azure 地圖服務帳戶的累計資料大小限制。The following table shows the cumulative data size limit for Azure Maps accounts in an Azure subscription. Azure 地圖服務資料服務僅適用於 S1 定價層。The Azure Maps Data service is available only at the S1 pricing tier.

資源Resource 限制Limit
每個 Azure 訂用帳戶的儲存體上限Maximum storage per Azure subscription 1 GB1 GB
每個檔案上傳的大小上限Maximum size per file upload 100 MB100 MB

如需 Azure 地圖服務定價層的詳細資訊，請參閱 Azure 地圖服務定價。For more information on the Azure Maps pricing tiers, see Azure Maps pricing.

Azure 監視器限制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 China 21Vianet 和 Azure Government 雲端中每個訂用帳戶 5,000 個使用中警示規則。5,000 active alert rules per subscription in Azure public, Azure China 21Vianet and Azure Government clouds. 如果達到此限制，請探索是否可以使用相同類型的多資源警示。If you are hitting this limit, explore if you can use same type multi-resource alerts.
每個警示規則 5,000 個計量時間序列。5,000 metric time-series per alert rule.		 請致電支援部門。Call support.
活動記錄警示Activity log alerts 每個訂用帳戶有 100 個使用中警示規則 (無法增加)。100 active alert rules per subscription (cannot be increased). 與預設值相同Same as default
記錄警示Log alerts 每個訂用帳戶 512 個使用中警示規則。512 active alert rules per subscription. 每個訂用帳戶 200 個使用中警示規則。200 active alert rules per resource. 請致電支援部門Call support
警示規則和動作規則描述長度Alert rules and Action rules description length 記錄搜尋警示為 4096 個字元Log search alerts 4096 characters
所有其他警示為 2048 個字元All other 2048 characters		 與預設值相同Same as default

動作群組Action groups

資源Resource 預設限制Default limit 上限Maximum limit
Azure 應用程式推送Azure app push 每個動作群組有 10 個 Azure 應用程式動作。10 Azure app actions per action group. 與預設值相同Same as Default
電子郵件Email 一個動作群組中有 1000 個電子郵件動作。1,000 email actions in an action group.
一小時內不超過 100 個電子郵件。No more than 100 emails in an hour.
另請參閱速率限制資訊。Also see the rate limiting information.		 與預設值相同Same as Default
ITSMITSM 一個動作群組中有 10 個 ITSM 動作。10 ITSM actions in an action group. 與預設值相同Same as Default
邏輯應用程式Logic app 一個動作群組中有 10 個邏輯應用程式動作。10 logic app actions in an action group. 與預設值相同Same as Default
RunbookRunbook 一個動作群組中有 10 個 Runbook 動作。10 runbook actions in an action group. 與預設值相同Same as Default
SMSSMS 一個動作群組中有 10 個 SMS 動作。10 SMS actions in an action group.
每 5 分鐘不超過 1 個 SMS 訊息。No more than 1 SMS message every 5 minutes.
另請參閱速率限制資訊。Also see the rate limiting information.		 與預設值相同Same as Default
語音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.		 與預設值相同Same as Default
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. 與預設值相同Same as Default

AutoscaleAutoscale

資源Resource 預設限制Default limit 上限Maximum limit
自動調整設定Autoscale settings 每個區域中每個訂用帳戶 100 個。100 per region per subscription. 與預設值相同Same as default
自動調整規模設定檔Autoscale profiles 每個自動調整規模設定為 20 個設定檔。20 profiles per autoscale setting. 與預設值相同Same as default

記錄查詢和語言Log queries and language

一般查詢限制General query limits

限制Limit 描述Description
查詢語言Query language Azure 監視器使用與 Azure 資料總管相同的 Kusto 查詢語言。Azure Monitor uses the same Kusto query language as Azure Data Explorer. 如需 Azure 監視器中不支援的 KQL 語言元素，請參閱 Azure 監視器記錄查詢語言差異。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.
View Designer 不支援跨資源查詢。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.

使用者查詢節流User query throttling

Azure 監視器有數個節流限制，可防止使用者傳送過多的查詢。Azure Monitor has several throttling limits to protect against users sending an excessive number of queries. 這類行為可能會導致系統後端資源多載，並損害服務回應能力。Such behavior can potentially overload the system backend resources and jeopardize service responsiveness. 下列限制旨在保護客戶避免遇到業務中斷，並確保一致的服務層級。The following limits are designed to protect customers from interruptions and ensure consistent service level. 使用者節流和限制旨在影響極端使用案例，並且與一般使用方式無關。The user throttling and limits are designed to impact only extreme usage scenario and should not be relevant for typical usage.

MeasureMeasure 每位使用者限制Limit per user 描述Description
並行查詢Concurrent queries 55 如果該使用者已有 5 個查詢正在執行，則會將所有新查詢放在每個使用者的並行佇列中。If there are already 5 queries running for the user, any new queries are placed in a per-user concurrency queue. 當其中一個正在執行的查詢結束時，會從佇列中提取下一個查詢並啟動。When one of the running queries ends, the next query will be pulled from the queue and started. 這不包含來自警示規則的查詢。This does not include queries from alert rules.
並行佇列中的時間Time in concurrency queue 3 分鐘3 minutes 如果查詢停留在佇列中的時間超過3分鐘而未啟動，則會以錯誤碼 429 的 HTTP 錯誤回應終止。If a query sits in the queue for more than 3 minutes without being started, it will be terminated with an HTTP error response with code 429.
並行佇列中的查詢總數Total queries in concurrency queue 200200 一旦佇列中的查詢數目達到 200，任何其他查詢都會以 HTTP 錯誤碼 429 拒絕。Once the number of queries in the queue reaches 200, any additional queries will by rejected with an HTTP error code 429. 此數目是除了可同時執行的 5 個查詢以外的數目。This number is in addition to the 5 queries that can be running simultaneously.
查詢速率Query rate 每 30 秒 200 個查詢200 queries per 30 seconds 這是單一使用者可以向所有工作區提交查詢的整體速率。This is the overall rate that queries can be submitted by a single user to all workspaces. 這項限制適用於程式設計查詢或由視覺效果組件 (例如 Azure 儀表板和 Log Analytics 工作區摘要頁面) 所起始的查詢。This limit applies to programmatic queries or queries initiated by visualization parts such as Azure dashboards and the Log Analytics workspace summary page.
  • 如在 Azure 監視器中最佳化記錄查詢中所述，將查詢最佳化。Optimize your queries as described in Optimize log queries in Azure Monitor.
  • 儀表板和活頁簿可以在單一檢視中包含多個查詢，其會在每次載入或重新整理時產生高載查詢。Dashboards and workbooks can contain multiple queries in a single view that generate a burst of queries every time they load or refresh. 請考慮將這些查詢拆分為視需要載入的多個檢視。Consider breaking them up into multiple views that load on demand.
  • 在 Power BI 中，請考慮僅擷取匯總的結果，而不是原始記錄。In Power BI, consider extracting only aggregated results rather than raw logs.

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 監視器價格。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. 請注意，每天 500 MB 的限制不包含 Azure 資訊安全中心所收集的資料，而且將繼續收集高於此限制的資料。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 監視器價格。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 監視器價格。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 每個 Azure AD 使用者或用戶端 IP 位址每 30 秒 200 個要求200 requests per 30 seconds per Azure AD 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 監視器是一種大規模的資料服務，服務對象為每月需傳送數 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 監視器客戶隔離，避免其受到多租用戶環境中突然激增的尖峰所影響。The volume rate limit intends to isolate Azure Monitor customers from sudden ingestion spikes in multitenancy environment. 定義於工作區的預設擷取磁碟區速率閾值為 500 MB (已壓縮)，解壓縮大約 6 GB/分鐘 -- 根據記錄長度和其壓縮率的不同，實際大小在資料類型之間可能會有所不同。A default ingestion volume rate threshold of 500 MB (compressed) is defined in workspaces, this is translated to approximately 6 GB/min uncompressed -- the actual size can vary between data types depending on the log length and its compression ratio. 磁碟區速率限制適用於透過 診斷設定 從 Azure 資源內嵌的資料。The volume rate limit applies to data ingested from Azure resources via Diagnostic settings. 達到磁碟區速率限制時，重試機制會嘗試在 30 分鐘內內嵌資料 4 次，並在作業失敗後將其卸載。When volume rate limit is reached, a retry mechanism attempts to ingest the data 4 times in a period of 30 minutes and drop it if operation fails. 其不適用於從 代理程式 或 資料收集器 API 中內嵌的資料。It doesn't apply to data ingested from agents or Data Collector API.

如果以高於工作區中所設定閾值的 80% 速率將資料傳送至您的工作區時，則每隔 6 小時會將事件傳送至工作區中的 [作業] 資料表，同時會持續超過閾值。When data sent to your workspace is at a volume rate higher than 80% of the threshold configured in your workspace, an event is sent to the Operation table in your workspace every 6 hours while the threshold continues to be exceeded. 當內嵌的磁碟區速率高於閾值時，則系統會卸除某些資料，且每隔 6 小時會將事件傳送至工作區中的 [作業] 資料表，同時會持續超過閾值。When ingested volume rate is higher than threshold, 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 rate continues to exceed the threshold or you are expecting to reach it sometime soon, you can request to increase it in by opening a support request.

請參閱在 Azure 監視器中監視 Log Analytics 工作區的健康情況，以建立要在您達到任何擷取限制時主動發出通知的警示規則。See Monitor health of Log Analytics workspace in Azure Monitor to create alert rules to be proactively notified when you reach any ingestion limits.

注意

視使用 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. 若容量大於 1000 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 原則限制Azure Policy limits

Azure 原則的每個物件類型都有最大計數。There's a maximum count for each object type for Azure Policy. 對於定義，_範圍_項目表示管理群組或訂用帳戶。For definitions, an entry of Scope means the management group or subscription. 針對指派和豁免，_範圍_項目表示管理群組、訂用帳戶、資源群組或個別資源。For assignments and exemptions, an entry of Scope means the management group, subscription, resource group, or individual resource.

WhereWhere 何事What 最大計數Maximum count
影響範圍Scope 原則定義Policy definitions 500500
影響範圍Scope 計畫定義Initiative definitions 200200
租用戶Tenant 計畫定義Initiative definitions 2,5002,500
影響範圍Scope 原則或方案指派Policy or initiative assignments 200200
影響範圍Scope 豁免Exemptions 10001000
原則定義Policy definition 參數Parameters 2020
計畫定義Initiative definition 原則Policies 10001000
計畫定義Initiative definition 參數Parameters 100100
原則或方案指派Policy or initiative assignments 排除項目 (notScopes)Exclusions (notScopes) 400400
原則規則Policy rule 巢狀的條件Nested conditionals 512512
補救工作Remediation task 資源Resources 500500

Azure 角色型存取控制限制Azure 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 自訂角色Azure custom roles per tenant 5,0005,000
每一租用戶的 Azure 自訂角色Azure custom roles per tenant
(適用於 Azure 德國和 Azure China 21Vianet)(for Azure Germany and Azure China 21Vianet)		 2,0002,000

Azure SignalR Service 限制Azure SignalR Service limits

資源Resource 預設限制Default limit 上限Maximum limit
免費層中每個執行個體的 Azure SignalR Service 單位數Azure SignalR Service units per instance for Free tier 11 11
標準層中每個執行個體的 Azure SignalR Service 單位數Azure SignalR Service units per instance for Standard tier 100100 100100
免費層中每個區域中每個訂用帳戶的 Azure SignalR Service 單位數Azure SignalR Service units per subscription per region for Free tier 55 55
每個區域中每個訂用帳戶的 Azure SignalR Service 單位總數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
免費層中每天每個單位的額外訊息數Additional messages per unit per day for Free tier 00 00
標準層中每天每個單位的內含訊息數Included messages per unit per day for Standard tier 1,000,0001,000,000 1,000,0001,000,000
標準層中每天每個單位的額外訊息數Additional messages per unit per day for Standard tier 無限制Unlimited 無限制Unlimited

若要要求更新訂用帳戶的預設限制，請開啟支援票證。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

ResourceResource 預設限制Default limit 上限Maximum limit
Azure Batch 帳戶 (每一區域的每一訂用帳戶)Azure Batch accounts per region per subscription 1-31-3 5050
每一 Batch 帳戶的專用核心Dedicated cores per Batch account 90-90090-900 請連絡支援人員Contact support
每一 Batch 帳戶的低優先順序核心Low-priority cores per Batch account 10-10010-100 請連絡支援人員Contact support
作用中的 工作和每一 Batch 帳戶的作業排程 (已完成 作業沒有限制)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

1 若想要要求增加到超過此限制，請連絡 Azure 支援。1To request an increase beyond this limit, contact Azure Support.

注意

預設限制會根據您用來建立 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.

重要

為了協助我們更有效地管理全球流感期間的產能，某些區域中新 Batch 帳戶的預設核心配額，以及某些類型的訂用帳戶，在某些情況下會從上述值範圍中縮減為零個核心。To help us better manage capacity during the global health pandemic, the default core quotas for new Batch accounts in some regions and for some types of subscription have been reduced from the above range of values, in some cases to zero cores. 當您建立新的 Batch 帳戶時，檢查您的核心配額 並視需要要求增加的核心配額。When you create a new Batch account, check your core quota and request a core quota increase, if required. 或者，考慮重新使用已具有足夠配額的 Batch 帳戶。Alternatively, consider reusing Batch accounts that already have sufficient quota.

傳統部署模型限制Classic deployment model limits

如果您使用傳統部署模型，而不是 Azure Resource Manager 部署模型，則適用下列限制。If you use classic deployment model instead of the Azure Resource Manager deployment model, the following limits apply.

資源Resource 預設限制Default limit 上限Maximum limit
每一訂用帳戶的 vCPU1vCPUs 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 限制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
每個訂用帳戶每個區域的標準 sku 核心 (CPU)Standard sku cores (CPUs) per region per subscription 101,2101,2
每個訂用帳戶每個區域 K80 GPU 的標準 sku 核心 (CPU)Standard sku cores (CPUs) for K80 GPU per region per subscription 181,2181,2
每個訂用帳戶每個區域 P100 或 V100 GPU 的標準 sku 核心 (CPU)Standard sku cores (CPUs) for P100 or V100 GPU per region per subscription 01,201,2
每個 IP 的連接埠數目Ports per IP 55
容器執行個體記錄大小 - 執行中的執行個體Container instance log size - running instance 4 MB4 MB
容器執行個體記錄大小 - 已停止的執行個體Container instance log size - stopped instance 16 KB 或 1,000 行16 KB or 1,000 lines
每小時的容器建立Container creates per hour 30013001
每 5 分鐘的容器建立Container creates per 5 minutes 10011001
每小時的容器刪除Container deletes per hour 30013001
每 5 分鐘的容器刪除Container deletes per 5 minutes 10011001

1若要要求提高限制，請建立 Azure 支援要求。1To request a limit increase, create an Azure Support request. 包括 Azure 免費帳戶和 Azure 學生版在內的免費訂用帳戶沒有資格增加限制或配額。Free subscriptions including Azure Free Account and Azure for Students aren't eligible for limit or quota increases. 如果您有免費訂用帳戶，則可以升級到隨用隨付訂用帳戶。If you have a free subscription, you can upgrade to a Pay-As-You-Go subscription.
2隨用隨付訂用帳戶的預設限制。2Default limit for Pay-As-You-Go subscription. 其他類別類型的限制可能有所不同。Limit may differ for other category types.

Container Registry 登入Container Registry limits

下表詳細說明 Basic、Standard 和 Premium 服務層的功能和限制。The following table details the features and limits of the Basic, Standard, and Premium service tiers.

資源Resource 基本Basic 標準Standard PremiumPremium
包含的儲存體1 (GiB)Included storage1 (GiB) 1010 100100 500500
儲存體限制 (TiB)Storage limit (TiB) 2020 2020 2020
映像層大小上限 (GiB)Maximum image layer size (GiB) 200200 200200 200200
每分鐘的 ReadOps2, 3ReadOps per minute2, 3 1,0001,000 3,0003,000 10,00010,000
每分鐘的 WriteOps2, 4WriteOps per minute2, 4 100100 500500 2,0002,000
下載頻寬 2 (Mbps)Download bandwidth2 (Mbps) 3030 6060 100100
上傳頻寬 2 (Mbps)Upload bandwidth 2 (Mbps) 1010 2020 5050
WebhookWebhooks 22 1010 500500
異地複寫Geo-replication N/AN/A N/AN/A 支援Supported
可用性區域Availability zones N/AN/A N/AN/A 預覽Preview
內容信任Content trust N/AN/A N/AN/A 支援Supported
具有私人端點的私人連結Private link with private endpoints N/AN/A N/AN/A 支援Supported
• 私人端點• Private endpoints N/AN/A N/AN/A 1010
服務端點 VNet 存取Service endpoint VNet access N/AN/A N/AN/A 預覽Preview
客戶管理的金鑰Customer-managed keys N/AN/A N/AN/A 支援Supported
存放庫範圍的權限Repository-scoped permissions N/AN/A N/AN/A 預覽Preview
• 權杖• Tokens N/AN/A N/AN/A 20,00020,000
• 範圍對應• Scope maps N/AN/A N/AN/A 20,00020,000
• 每個範圍對應的存放庫• Repositories per scope map N/AN/A N/AN/A 500500

1 每一層的每日費率包含的儲存體。1 Storage included in the daily rate for each tier. 可以使用額外的儲存體，每個 GiB 需要額外的每日費率，以登錄儲存體限制為上限。Additional storage may be used, up to the registry storage limit, at an additional daily rate per GiB. 如需費率資訊，請參閱 Azure Container Registry 定價。For rate information, see Azure Container Registry pricing. 如果您需要的儲存體超過登錄儲存體上限，請連絡 Azure 支援。If you need storage beyond the registry storage limit, please contact Azure Support.

2ReadOps、WriteOps 和「頻寬」是最小預估值。2ReadOps, WriteOps, and Bandwidth are minimum estimates. Azure Container Registry 致力於改善需要使用時的效能。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. 您可能想要使用多個設定檔，依網際網路網域、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 限制Data Factory limits

Azure Data Factory 是一種多租用戶服務，並具有以下的預設限制以確保客戶訂用帳戶不會受到彼此工作負載的影響。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.

第 2 版Version 2

資源Resource 預設限制Default limit 上限Maximum limit
Azure 訂用帳戶中的資料處理站Data factories in an Azure subscription 800800 800800
資料處理站中的實體總數，例如管線、資料集、觸發程序、連結的服務、私人端點和整合執行階段Total number of entities, such as pipelines, data sets, triggers, linked services, Private Endpoints, 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 10,00010,000
每訂用帳戶每個 Azure Integration Runtime 區域的並行外部活動執行Concurrent External activity runs per subscription per Azure Integration Runtime region
外部活動是在整合執行階段上管理，但在連結的服務上執行；包括 Databricks、預存程序、HDInsight、網頁和其他。此限制不適用於自我裝載 IR。External activities are managed on integration runtime but execute on linked services, including Databricks, stored procedure, HDInsights, Web, and others. This limit does not apply to Self-hosted IR.		 3,0003,000 3,0003,000
每訂用帳戶每個 Azure Integration Runtime 區域的並行管線活動執行Concurrent Pipeline activity runs per subscription per Azure Integration Runtime region
管線活動會在整合執行階段上執行，包括 Lookup、GetMetadata 和 Delete。此限制不適用於自我裝載 IR。Pipeline activities execute on integration runtime, including Lookup, GetMetadata, and Delete. This limit does not apply to Self-hosted IR.		 1,0001,000 1,0001,000
每訂用帳戶每個 Azure Integration Runtime 區域的製作作業Concurrent authoring operations per subscription per Azure Integration Runtime region
包括測試連線、瀏覽資料夾清單和資料表清單、預覽資料。此限制不適用於自我裝載 IR。Including test connection, browse folder list and table list, preview data. This limit does not apply to Self-hosted IR.		 200200 200200
每訂用帳戶每個 Azure Integration Runtime 區域的並行資料整合單位1耗用量Concurrent Data Integration Units1 consumption per subscription per Azure Integration Runtime region 區域群組 12：6,000Region group 12: 6,000
區域群組 22：3,000Region group 22: 3,000
區域群組 32：1,500Region group 32: 1,500		 區域群組 12：6,000Region group 12: 6,000
區域群組 22：3,000Region group 22: 3,000
區域群組 32：1,500Region group 32: 1,500
每個管線的活動數目上限，包含容器的內部活動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
每個活動執行的每個承載位元組數4Bytes per payload for each activity run4 896 KB896 KB 896 KB896 KB
每次複製活動執行的資料整合單位1Data Integration Units1 per copy activity run 256256 256256
寫入 API 呼叫Write API calls 1,200/小時1,200/h 1,200/小時1,200/h

這是由 Azure Resource Manager 所加諸的限制，而不是 Azure Data Factory。This limit is imposed by Azure Resource Manager, not Azure Data Factory.
讀取 API 呼叫Read API calls 12,500/小時12,500/h 12,500/小時12,500/h

這是由 Azure Resource Manager 所加諸的限制，而不是 Azure Data Factory。This limit is imposed by Azure Resource Manager, not Azure Data Factory.
監視每分鐘查詢次數Monitoring queries per minute 1,0001,000 1,0001,000
資料流程偵錯工作階段上限Maximum time of data flow debug session 8 小時8 hrs 8 小時8 hrs
每個整合執行階段的並行資料流程數Concurrent number of data flows per integration runtime 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 4 小時4 hrs

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 Data Factory 定價。For information on billing, see Azure Data Factory pricing.

2 Azure Integration Runtime 為全域可用，以確保資料合規性、效率，並降低網路輸出成本。2 Azure Integration Runtime is globally available to ensure data compliance, efficiency, and reduced network egress costs.

區域群組Region group 區域Regions
區域群組 1Region group 1 美國中部、美國東部、美國東部 2、歐洲北部、歐洲西部、美國西部、美國西部 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 Data Factory 移動和處理的資料量無關。Limits for these objects don't relate to the amount of data you can move and process with Azure Data Factory. Data Factory 可視需要調整以處理數 PB 的資料。Data Factory is designed to scale to handle petabytes of data.

4 每個活動執行的承載包含活動設定、相關聯的資料集和已連結的服務設定 (如果有的話)，以及每個活動類型所產生的一小部分系統屬性。4 The payload for each activity run includes the activity configuration, the associated dataset(s) and linked service(s) configurations if any, and a small portion of system properties generated per activity type. 此承載大小的限制與您可使用 Azure Data Factory 移動和處理的資料量無關。Limit for this payload size doesn't relate to the amount of data you can move and process with Azure Data Factory. 如果您達到此限制，請參閱徵兆和建議。Learn about the symptoms and recommendation if you hit this limit.

第 1 版Version 1

ResourceResource 預設限制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
管線物件的每個物件位元組大小1Bytes per object for pipeline objects1 200 KB200 KB 200 KB200 KB
資料集和已連結服務的每個物件位元組大小1Bytes per object for data set and linked service objects1 100 KB100 KB 2,000 KB2,000 KB
訂用帳戶中的 Azure HDInsight 隨選叢集核心2Azure HDInsight on-demand cluster cores within a subscription2 6060 連絡客戶支援。Contact support.
每次複製活動執行的雲端資料移動單位3Cloud data movement units per copy activity run3 3232 3232
管線活動執行的重試計數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 Data Factory 移動和處理的資料量無關。Limits for these objects don't relate to the amount of data you can move and process with Azure Data Factory. 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 核心的 Data Factory 強制核心限制，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 Data Factory 定價。For information on billing, see Azure Data Factory pricing.

ResourceResource 預設下限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 Resource Manager 有 API 呼叫限制。Azure Resource Manager has limits for API calls. 您可使用 Azure 資源管理員 API 限制內的速率進行 API 呼叫。You can make API calls at a rate within the Azure Resource Manager API limits.

Data Lake Analytics 限制Data Lake Analytics limits

Azure Data Lake Analytics 簡化了管理分散式基礎結構與複雜程式碼這項複雜工作。Azure Data Lake Analytics makes the complex task of managing distributed infrastructure and complex code easy. 其會動態佈建資源，而您可將其用於分析數 EB 的資料。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.

ResourceResource 限制Limit 註解Comments
並行作業數上限Maximum number of concurrent jobs 2020
每個帳戶的分析單位 (AU) 數目上限Maximum number of analytics units (AUs) per account 250250 使用最多結合跨越 20 個作業之 250 個 AU 的任意組合。Use any combination of up to a maximum of 250 AUs across 20 jobs. 若要提高此限制，請連絡 Microsoft 支援服務。To increase this limit, contact Microsoft Support.
用於提交作業的指令碼大小上限Maximum script size for job submission 3 MB3 MB
每個訂用帳戶在每個區域中的 Data Lake Analytics 帳戶數目上限Maximum number of Data Lake Analytics accounts per region per subscription 55 若要提高此限制，請連絡 Microsoft 支援服務。To increase this limit, contact Microsoft Support.

Data Lake Storage 限制Data Lake Storage limits

Azure Data Lake Storage Gen2 不是專用的服務或儲存體帳戶類型。Azure Data Lake Storage Gen2 is not a dedicated service or storage account type. 這是最新版本的功能，專門用於巨量資料分析。It is the latest release of capabilities that are dedicated to big data analytics. 這些功能適用於一般用途 v2 或 BlockBlobStorage 儲存體帳戶，您可藉由啟用帳戶的 階層命名空間 功能來加以取得。These capabilities are available in a general-purpose v2 or BlockBlobStorage storage account, and you can obtain them by enabling the Hierarchical namespace feature of the account. 如需調整目標，請參閱下列文章。For scale targets, see these articles.

Azure Data Lake Storage Gen1 是專用的服務。Azure Data Lake Storage Gen1 is a dedicated service. 這是容納巨量資料分析工作負載的企業級超大規模存放庫。It's an enterprise-wide hyper-scale repository for big data analytic workloads. 您可以使用 Data Lake Storage 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 Storage Gen1 帳戶中儲存的資料量並無任何限制。There's no limit to the amount of data you can store in a Data Lake Storage Gen1 account.

ResourceResource 限制Limit 註解Comments
每個區域中每個訂用帳戶的 Data Lake Storage Gen1 帳戶數目上限Maximum number of Data Lake Storage Gen1 accounts, per subscription, per region 1010 若要要求提高此限制，請連絡支援人員。To request an increase for this limit, contact support.
每個檔案或資料夾的存取 ACL 數目上限Maximum number of access ACLs, per file or folder 3232 這是一種硬性限制。This is a hard limit. 使用群組以較少的項目來管理存取。Use groups to manage access with fewer entries.
每個檔案或資料夾的預設 ACL 數目上限Maximum number of default ACLs, per file or folder 3232 這是一種硬性限制。This is a hard limit. 使用群組以較少的項目來管理存取。Use groups to manage access with fewer entries.

Data Share 限制Data Share limits

Azure Data Share 可讓組織輕鬆安全地與其客戶和合作夥伴共用資料。Azure Data Share enables organizations to simply and securely share data with their customers and partners.

ResourceResource 限制Limit
每個 Azure 訂用帳戶的資料共用資源數目上限Maximum number of Data Share resources per Azure subscription 100100
每個資料共用資源的已傳送共用數上限Maximum number of sent shares per Data Share resource 200200
每個資料共用資源的已接收共用數上限Maximum number of received shares per Data Share resource 100100
每個已傳送共用的邀請數目上限Maximum number of invitations per sent share 200200
每個已傳送共用的共用訂用帳戶數目上限Maximum number of share subscriptions per sent share 200200
每個共用的資料集數目上限Maximum number of datasets per share 200200
每個共用的快照集排程數目上限Maximum number of snapshot schedules per share 11

Database Migration Service 限制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.

ResourceResource 限制Limit 註解Comments
每個區域的每個訂用帳戶服務數目上限Maximum number of services per subscription, per region 1010 若要要求提高此限制，請連絡支援人員。To request an increase for this limit, contact support.

數位 Twins 限制Digital Twins limits

注意

這項服務的某些區域具有可調整的限制，其他則否。Some areas of this service have adjustable limits, and others do not. 這會在下表中以可 調整的？ 資料行表示。This is represented in the tables below with the Adjustable? column. 當限制可以調整時，可 調整 的值是 [是]。When the limit can be adjusted, the Adjustable? value is Yes.

功能限制Functional limits

下表列出 Azure 數位 Twins 的功能限制。The table below lists the functional limits of Azure Digital Twins.

區域Area 功能Capability 預設限制Default limit 調？Adjustable?
Azure 資源Azure resource 每個訂用帳戶的區域中的 Azure 數位 Twins 實例數目Number of Azure Digital Twins instances in a region, per subscription 1010 是Yes
Digital TwinsDigital twins Azure 數位 Twins 實例中的 twins 數目Number of twins in an Azure Digital Twins instance 200,000200,000 是Yes
Digital TwinsDigital twins 單一對應項的連入關聯性數目Number of incoming relationships to a single twin 5,0005,000 否No
Digital TwinsDigital twins 來自單一對應項的傳出關聯性數目Number of outgoing relationships from a single twin 5,0005,000 否No
Digital TwinsDigital twins 單一對應項的大小上限Maximum size of a single twin 32 KB32 KB 否No
Digital TwinsDigital twins 要求承載大小上限Maximum request payload size 32 KB32 KB 否No
路由Routing 單一 Azure 數位 Twins 實例的端點數目Number of endpoints for a single Azure Digital Twins instance 66 否No
路由Routing 單一 Azure 數位 Twins 實例的路由數目Number of routes for a single Azure Digital Twins instance 66 是Yes
模型Models 單一 Azure 數位 Twins 實例內的模型數目Number of models within a single Azure Digital Twins instance 10,00010,000 是Yes
模型Models 可在單一 API 呼叫中上傳的模型數目Number of models that can be uploaded in a single API call 250250 否No
模型Models 在單一頁面中傳回的專案數Number of items returned in a single page 100100 否No
查詢Query 在單一頁面中傳回的專案數Number of items returned in a single page 100100 是Yes
查詢Query AND / OR 查詢中的運算式數目Number of AND / OR expressions in a query 5050 是Yes
查詢Query 子句中的陣列專案數目 IN / NOT INNumber of array items in an IN / NOT IN clause 5050 是Yes
查詢Query 查詢中的字元數Number of characters in a query 8,0008,000 是Yes
查詢Query JOINS查詢中的數目Number of JOINS in a query 55 是Yes

速率限制Rate limits

下表反映不同 Api 的速率限制。The following table reflects the rate limits of different APIs.

APIAPI 功能Capability 預設限制Default limit 調？Adjustable?
模型 APIModels API 每秒要求數Number of requests per second 100100 是Yes
數位 Twins APIDigital Twins API 每秒要求數Number of requests per second 2,0002,000 是Yes
數位 Twins APIDigital Twins API 每秒在 所有 twins 和關聯 性中的建立/刪除作業數目Number of create/delete operations per second across all twins and relationships 5050 是Yes
數位 Twins APIDigital Twins API 單一 對應項或其關聯性每秒的建立/更新/刪除作業數目Number of create/update/delete operations per second on a single twin or its relationships 1010 否No
查詢 APIQuery API 每秒要求數Number of requests per second 500500 是Yes
查詢 APIQuery API 每秒查詢單位數Query Units per second 4,0004,000 是Yes
事件路由 APIEvent Routes API 每秒要求數Number of requests per second 100100 是Yes

其他限制Other limits

您可以在 GitHub： 數位 Twins 定義語言 (DTDL) -第2版中，找到 Azure 數位 TWINS 模型 DTDL 檔中的資料類型和欄位限制。Limits on data types and fields within DTDL documents for Azure Digital Twins models can be found within its spec documentation in GitHub: Digital Twins Definition Language (DTDL) - version 2.

查詢延遲詳細資料和其他查詢限制可在 how to：查詢對應項圖形中找到。Query latency details and other query limitations can be found in How-to: Query the twin graph.

事件方格限制Event Grid limits

下列限制適用於 Azure 事件方格主題 (系統、自訂和合作夥伴主題)。The following limits apply to Azure Event Grid topics (system, custom, and partner topics).

資源Resource 限制Limit
每個 Azure 訂用帳戶的自訂主題Custom topics per Azure subscription 100100
每個主題的事件訂用帳戶Event subscriptions per topic 500500
自訂或合作夥伴主題 (輸入) 的發佈速率Publish rate for a custom or a partner topic (ingress) 5000 個事件/秒或 1 MB/秒 (以先達到者為準)5,000 events/sec or 1 MB/sec (whichever is met first)
事件大小Event size 1 MB1 MB
每個主題的私人端點連線數Private endpoint connections per topic 6464
每個主題的 IP 防火牆規則數IP Firewall rules per topic 1616

下列限制適用於 Azure 事件方格網域。The following limits apply to Azure Event Grid domains.

資源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) 5000 個事件/秒或 1 MB/秒 (以先達到者為準)5,000 events/sec or 1 MB/sec (whichever is met first)
每個 Azure 訂用帳戶的事件網域數Event Domains per Azure Subscription 100100
每個網域的私人端點連線數Private endpoint connections per domain 6464
每個網域的 IP 防火牆規則數IP Firewall rules per domain 1616

事件中樞限制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.

所有階層的通用限制Common limits for all tiers

下列限制在所有階層之間是共通的。The following limits are common across all tiers.

限制Limit 注意Notes 值Value
每一訂用帳戶的「事件中樞」命名空間數目Number of Event Hubs namespaces per subscription - 100100
每個命名空間的事件中樞數目Number of event hubs per namespace 建立新的事件中樞的後續要求將遭到拒絕。Subsequent requests for creation of a new event hub are rejected. 1010
事件中樞內的資料分割數目Number of partitions per event hub - 3232
事件中樞名稱的大小Size of an event hub name - 256 個字元256 characters
取用者群組名稱的大小Size of a consumer group name - 256 個字元256 characters
每個取用者群組的非 epoch 接收者數目Number of non-epoch receivers per consumer group - 55
每個命名空間的授權規則數目Number of authorization rules per namespace 建立授權規則的後續要求將遭到拒絕。Subsequent requests for authorization rule creation are rejected. 1212
對 GetRuntimeInformation 方法的呼叫次數Number of calls to the GetRuntimeInformation method - 每秒 50 個50 per second
虛擬網路 (VNet)和 IP 設定規則的數目Number of virtual network (VNet) and IP Config rules - 128128

基本層和標準層Basic vs. standard tiers

下表顯示基本和標準層可能有所不同的限制。The following table shows limits that may be different for basic and standard tiers.

限制Limit 注意Notes 基本Basic 標準Standard
事件中樞事件的大小上限Maximum size of Event Hubs event   256 KB256 KB 1 MB1 MB
每一個事件中樞取用者群組數目Number of consumer groups per event hub   11 2020
每個命名空間的 AMQP 連線數目Number of AMQP connections per 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   1 日1 day 1-7 天1-7 days
最大輸送量單位Maximum throughput units 超過此限制會導致您的資料受到節流，並產生伺服器忙碌例外狀況。Exceeding this 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 2020

專用層和標準層Dedicated tier vs. standard tier

事件中樞專用供應項目以每月固定價格計費，最低為 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.

請參閱此文件，以了解如何使用 Azure 入口網站建立專用的事件中樞叢集。Refer to this document on how to create dedicated Event Hubs cluster using Azure portal.

功能Feature 標準Standard 專用Dedicated
頻寬Bandwidth 20 TU (最多 40 TU)20 TUs (up to 40 TUs) 20 個 CU20 CUs
命名空間Namespaces 11 每個 CU 50 個50 per CU
事件中樞Event Hubs 每一命名空間 10 個10 per namespace 每一命名空間 1000 個1000 per namespace
輸入事件Ingress events 按百萬個事件付費Pay per million events 已包括Included
訊息大小Message Size 100 萬個位元組1 Million Bytes 100 萬個位元組1 Million Bytes
資料分割Partitions 每個事件中樞 32 個32 per Event Hub 每個事件中樞 1024 個1024 per event hub
每個 CU 2000 個2000 per CU
用戶群組Consumer groups 每個事件中樞 20 個20 per Event Hub 沒有每個 CU 的限制，每個事件中樞 1000 個No limit per CU, 1000 per event hub
代理連線Brokered connections 含 1000 個，上限為 5000 個1,000 included, 5,000 max 含 10 萬個和上限100 K included and max
訊息保留期Message Retention 7 天，每個 CU 包含 84 GB7 days, 84 GB included per TU 90 天，每個 CU 包含 10 TB90 days, 10 TB included per CU
擷取Capture 按小時付費Pay per hour 已包括Included

結構描述登錄限制Schema registry limitations

標準和專用層的限制相同Limits that are the same for standard and dedicated tiers

功能Feature 限制Limit
結構描述群組名稱的長度上限Maximum length of a schema group name 5050
結構描述名稱的長度上限Maximum length of a schema name 100100
每個結構描述的大小 (位元組)Size in bytes per schema 1 MB1 MB
每個結構描述群組的屬性數目Number of properties per schema group 10241024
每個群組屬性金鑰的大小 (位元組)Size in bytes per group property key 256256
每個群組屬性值的大小 (位元組)Size in bytes per group property value 10241024

標準和專用層的限制不同Limits that are different for standard and dedicated tiers

限制Limit 標準Standard 專用Dedicated
結構描述登錄 (命名空間) 的大小 (MB)Size of the schema registry (namespace) in mega bytes 2525 10241024
結構描述登錄或命名空間中的結構描述群組數目Number of schema groups in a schema registry or namespace 1 - 排除預設群組1 - excluding the default group 10001000
跨所有結構描述群組的架構版本數目Number of schema versions across all schema groups 2525 1000010000

IoT Central 限制IoT Central limits

IoT Central 會將您可在訂用帳戶中部署的應用程式數目限制為 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 5050
每個 Azure 訂用帳戶的免費 IoT 中樞上限Maximum free IoT hubs per Azure subscription 11
裝置識別碼中的字元數目上限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
雲端到裝置訊息的 TTL 上限Maximum 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
回應雲端到裝置訊息之反應訊息的 Maximum TTL for feedback messages in
TTL 上限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 訂用帳戶中需要超過 50 個付費的 IoT 中樞，請連絡 Microsoft 支援服務。If you need more than 50 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).
10,000 個 SAS URI 可以讓 Azure 儲存體帳戶一次用盡。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 適用於所有交易類型的全訂用帳戶限制，是每個金鑰保存庫限制的五倍。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.

注意

每個訂閱所啟用私人端點的金鑰保存庫數目屬於可調整的限制。The number of key vaults with private endpoints enabled per subscription is an adjustable limit. 以下顯示的限制為預設限制。The limit shown below is the default limit. 如果您想要求增加服務的限制，請傳送電子郵件至 akv-privatelink@microsoft.com。If you would like to request a limit increase for your service, please send an email to akv-privatelink@microsoft.com. 我們會根據個案核准這些要求。We will approve these requests on a case by case basis.

資源Resource 限制Limit
每個金鑰保存庫的私人端點Private endpoints per key vault 6464
每個訂用帳戶具有私人端點的金鑰保存庫Key vaults with private endpoints per subscription 400400

受控識別限制Managed identity limits

  • 每個受控識別都會計入 Azure AD 租用戶中的物件配額限制，如 Azure AD 服務限制中所述。Each managed identity counts towards the object quota limit in an Azure AD tenant as described in Azure AD service limits and restrictions.

  • 可建立受控識別的速率有下列限制：The rate at which managed identities can be created have the following limits:

    1. 每個 Azure 區域的每個 Azure AD 租用戶：每 20 秒 200 個建立作業。Per Azure AD Tenant per Azure region: 200 create operations per 20 seconds.
    2. 每個 Azure 區域的每個 Azure 訂用帳戶：每 20 秒 40 個建立作業。Per Azure Subscription per Azure region : 40 create operations per 20 seconds.

  • 在您建立使用者指派的受控身分識別時，僅支援使用英數字元 (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.

媒體服務限制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 100 (固定)100 (fixed)

資產限制Asset limits

資源Resource 預設限制Default Limit
每個媒體服務帳戶的資產Assets per Media Services account 1,000,0001,000,000

儲存體 (媒體) 限制Storage (media) 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 單一 blob 支援的大小上限目前在 Azure Blob 儲存體是最多 5 TB。1 The maximum size supported for a single blob is currently up to 5 TB in Azure Blob Storage. 其他限制會根據服務所使用的 VM 大小，套用在 Azure 媒體服務中。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. 如果您的4K 內容大於 S3 媒體保留單元的 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 DVR 視窗的大小Size of the DVR window

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 22
動態資訊清單篩選條件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 使用自訂的串流原則時，您應該為媒體服務帳戶設計一組受限的這類原則，並且在需要相同的加密選項和通訊協定時，對 StreamingLocators 重新使用這些原則。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 基本Basic 標準Standard
API 呼叫API calls 500,000500,000 每一單位 150 萬個1.5 million per unit 每一單位 1500 萬個15 million per unit
使用中裝置Active devices 500500 無限制Unlimited 無限制Unlimited
調整Scale N/AN/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 jobsScheduled jobs 限制Limited 已包括Included 已包括Included
Azure SQL Database (必要)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 限制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 Resource ManagerNetworking limits - Azure Resource Manager

下列限制僅適用於透過每個訂用帳戶每一區域的 Azure Resource Manager 所管理的網路資源。The following limits apply only for networking resources managed through Azure Resource Manager per region per subscription. 深入了解如何根據您的訂用帳戶限制檢視目前資源使用量。Learn how to view your current resource usage against your subscription limits.

注意

我們最近已將所有預設限制提升至其最大限制。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
每個虛擬網路的虛擬網路閘道 (ExpressRoute 閘道)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
每個 NIC、每個 IP 組態的應用程式安全性群組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 addresses per Resource Group 800800 請連絡支援人員。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. 例如，Enterprise 合約訂用帳戶的預設值是 1000。For example, the default for Enterprise Agreement subscriptions is 1000.

負載平衡器限制Load balancer limits

下列限制僅適用於透過每個訂用帳戶每一區域的 Azure Resource Manager 所管理的網路資源。The following limits apply only for networking resources managed through Azure Resource Manager per region per subscription. 深入了解如何根據您的訂用帳戶限制檢視目前資源使用量。Learn how to view your current resource usage against your subscription limits.

Standard Load BalancerStandard 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 1000 個 IP 組態，單一虛擬網路1,000 IP configurations, single virtual network
每個 Load Balancer 的後端資源1Backend resources per Load Balancer 1 250250
高可用性連接埠High-availability ports 每個內部前端 1 個1 per internal frontend
每個 Load Balancer 的輸出規則Outbound rules per Load Balancer 600600
每個 VM 的負載平衡器Load Balancers per VM 2 個 (1 個公用和 1 個內部)2 (1 Public and 1 internal)

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 placement groups.

基本負載平衡器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
每個 Load Balancer 的可用性設定組Availability sets per Load Balancer 11
每個 VM 的負載平衡器Load Balancers per VM 2 個 (1 個公用和 1 個內部)2 (1 Public and 1 internal)

下列限制僅適用於透過每個訂用帳戶的 傳統 部署模型所管理的網路資源。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 500,000 個，最多 1,000,000 個 (適用於 2 個以上的 NIC)。500,000, up to 1,000,000 for two or more NICs. 500,000 個，最多 1,000,000 個 (適用於 2 個以上的 NIC)。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 200200 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
每個部署的公用 IPPublic IP per deployment 55 請連絡支援人員Contact support
每個部署的私人 IP (內部負載平衡)Private IP (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 Resource Manager)ExpressRoute circuits per region per subscription, with Azure Resource Manager 1010
具有 ExpressRoute Standard 的 Azure 私人對等互連的公告路由數目上限Maximum number of routes advertised to Azure private peering with ExpressRoute Standard 4,0004,000
具有 ExpressRoute Premium 附加元件的 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 Standard 的 Microsoft 對等互連的公告路由數目上限Maximum number of routes advertised to Microsoft peering with ExpressRoute Standard 200200
具有 ExpressRoute Premium 附加元件的 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 Standard 的虛擬網路連結數目Number of virtual network links for Standard 具有 Premium 附加元件的虛擬網路連結數目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 ExpressRoute Direct*100 Gbps ExpressRoute Direct Only

注意

Global Reach 連線數計入每個 ExpressRoute 線路的虛擬網路連線數限制。Global Reach connections count against the limit of virtual network connections per ExpressRoute Circuit. 例如，10 Gbps Premium 線路可允許 5 個 Global Reach 連線和連線至 ExpressRoute 閘道的 95 個連線，或 95 個 Global Reach 連線和連線至 ExpressRoute 閘道的 5 個連線，或任何其他組合，直到線路的 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.

虛擬網路閘道限制Virtual Network Gateway limits

資源Resource 限制Limit
VNet 位址首碼VNet Address Prefixes 每個 VPN 閘道600600 per VPN gateway
匯總 BGP 路由Aggregate BGP routes 每個 VPN 閘道40004,000 per VPN gateway
局域網路閘道位址首碼Local Network Gateway address prefixes 每個局域網路閘道10001000 per local network gateway
S2S 連線S2S connections 取決於閘道 SKUDepends on the gateway SKU
P2S 連線P2S connections 取決於閘道 SKUDepends on the gateway SKU
P2S 路由限制-IKEv2P2S route limit - IKEv2 適用于 Windows 的非 Windows 25 的 256 /256 for non-Windows / 25 for Windows
P2S 路由限制-OpenVPNP2S route limit - OpenVPN 10001000
最大Max. flowsflows 適用于 / VpnGw2-4/az 的 VpnGw1/az 512K 10 萬100K for VpnGw1/AZ / 512K for VpnGw2-4/AZ

NAT 閘道限制NAT Gateway limits

資源Resource 限制Limit
公用 IP 位址Public IP addresses 每個 NAT 閘道16個16 per NAT gateway

虛擬 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
彙總每個虛擬 WAN 站對站 VPN 閘道的輸送量Aggregate throughput per Virtual WAN Site-to-site 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
每個中樞的點對站使用者Point-to-Site users per hub 10,00010,000
彙總每個虛擬 WAN 使用者 VPN (點對站) 閘道的輸送量Aggregate throughput per Virtual WAN User VPN (Point-to-site) gateway 20 Gbps20 Gbps
彙總每個虛擬 WAN ExpressRoute 閘道的輸送量Aggregate throughput per Virtual WAN ExpressRoute gateway 20 Gbps20 Gbps
每個中樞的 ExpressRoute 線路連線ExpressRoute Circuit connections per hub 44
每個中樞的 VNet 連線VNet connections per hub 500 減去虛擬 WAN 中的中樞總數500 minus total number of hubs in Virtual WAN
彙總每個虛擬 WAN 中樞路由器的輸送量Aggregate throughput per Virtual WAN Hub Router 50 Gbps 適用於 VNet 對 VNet 傳輸50 Gbps for VNet to VNet transit
連線至單一虛擬 WAN 中樞的所有 VNet 上的 VM 工作負載VM workload across all VNets connected to a single Virtual WAN hub 20002000

應用程式閘道限制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
WAF 檔案上傳大小上限Maximum 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 per Application Gateway 4040

1 若 SKU 啟用了 WAF，您必須將資源數限制為 40。1 In case of WAF-enabled SKUs, you must limit the number of resources to 40.

網路監看員限制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,000 個10,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 services 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
每個金鑰保存庫的私人端點數目Number of private endpoints per key vault 6464
每個訂用帳戶具有私人端點的金鑰保存庫數目Number of key vaults with private endpoints per subscription 400400
可連結至私人端點的私人 DNS 區域群組數目Number of private DNS zone groups that can be linked to a private endpoint 11
每個群組中的 DNS 區域數目Number of DNS zones in each group 55

範疇限制Purview limits

您可以在 [Azure 範疇配額] 頁面中找到 azure 範疇配額的最新值The latest values for Azure Purview quotas can be found in the Azure Purview quota page

流量管理員限制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

1 如果需要增加這些限制，請連絡 Azure 支援。1If you need to increase these limits, contact Azure Support.

私人 DNS 區域Private DNS zones

資源Resource 限制Limit
每一訂用帳戶的公用 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 1000 11000 1
每個虛擬機器的已排入佇列 (回應待決) DNS 查詢數目上限Maximum number of DNS queries queued (pending response) per virtual machine 200 1200 1

1這些限制會套用至每個個別虛擬機器，而不會套用於虛擬網路層級。1These 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 單一公用 IP 位址可有 298 個。298 for a single public IP address.
任何其他公用 IP 位址都會貢獻可用的 SNAT 連接埠，但會減少可用的 DNAT 規則數目。Any additional public IP addresses contribute to the available SNAT ports, but reduce the number of the available DNAT rules. 例如，兩個公用 IP 位址能容納 297 個 DNAT 規則。For example, two public IP addresses allow for 297 DNAT rules. 如果同時針對 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 1 - 655351 - 65535
公用 IP 位址Public IP addresses 最大值 250。250 maximum. 所有公用 IP 位址都可以在 DNAT 規則中使用，而且這些公用 IP 位址全都會提供給可用的 SNAT 埠。All public IP addresses can be used in DNAT rules and they all contribute to available SNAT ports.
IP 群組中的 IP 位址IP addresses in IP Groups 每個防火牆最多 100 個 IP 群組。Maximum of 100 IP Groups per firewall.
每個 IP 群組最多 5000 個個別 IP 位址或 IP 首碼。Maximum 5000 individual IP addresses or IP prefixes per each IP Group.
路由表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 防火牆」必須能夠直接連線到網際網路。Azure Firewall must have direct Internet connectivity. 如果您的 AzureFirewallSubnet 學習到透過 BGP 連至您內部部署網路的預設路由，您必須將其覆寫為 0.0.0.0/0 UDR，且 NextHopType 值必須設為 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. 受理後，我們會允許您的訂用帳戶，並確實維持必要的防火牆網際網路連線。If accepted, we'll allow your subscription and ensure the required firewall Internet connectivity is maintained.
網路規則中的 FQDNFQDNs in network rules 為達到良好效能，每個防火牆的所有網路規則不超過 1000 個 FQDN。For good performance, do not exceed more than 1000 FQDNs across all network rules per firewall.

1 如果需要增加這些限制，請連絡 Azure 支援。1If you need to increase these limits, contact Azure Support.

Azure Front Door Service 限制Azure Front Door Service limits

資源Resource 限制Limit
每個訂用帳戶的 Azure Front Door 資源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 中的 sendRecvTimeoutSeconds 欄位來設定。This value is configurable via the field sendRecvTimeoutSeconds in the API.
    • 針對快取案例，此逾時無法設定，因此如果快取要求，而且來自 Front Door 或後端的第一個封包耗時超過 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.
  • Front Door 至後端 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 大小上限 - 8192 個位元組 - 指定原始 URL 的長度上限 (配置 + 主機名稱 + 連接埠 + 路徑 + URL 的查詢字串)Maximum URL size - 8,192 bytes - Specifies maximum length of the raw URL (scheme + hostname + port + path + query string of the URL)
  • 查詢字串大小上限 - 4096 個位元組 - 指定查詢字串的長度上限 (以位元組為單位)。Maximum Query String size - 4,096 bytes - Specifies the maximum length of the query string, in bytes.
  • 來自健全狀態探查 URL 的 HTTP 回應標頭大小上限 - 4096 個位元組 - 指定健全狀態探查所有回應標頭的長度上限。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 基本Basic 標準Standard
包含的推送Included pushes 100 萬1 million 1000 萬10 million 1000 萬10 million
使用中裝置Active devices 500500 200,000200,000 1000 萬10 million
每一安裝或註冊的標籤配額Tag quota per installation or registration 6060 6060 6060

如需限制和定價的詳細資訊，請參閱通知中樞定價。For more information on limits and pricing, see Notification Hubs pricing.

服務匯流排限制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. 網路傳訊：1000 則。Net Messaging: 1,000.

AMQP：5000 則。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. 針對基本或標準層為 10000 個。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) 1000 個。For the Premium tier, 1,000 per messaging unit (MU). 上限為 4000 個。Maximum limit is 4,000.
每個命名空間的分割主題或佇列數目Number of partitioned topics or queues per namespace 命名空間Namespace 後續要求在命名空間上建立新分割主題或佇列會遭到拒絕。Subsequent requests for creation of a new partitioned topic or queue on the namespace are rejected. 因此，如果透過 Azure 入口網站設定，則會產生錯誤訊息。As a result, if configured through the Azure portal, an error message is generated. 如果從管理 API 進行呼叫，則呼叫端程式碼會收到 QuotaExceededException 例外狀況。If called from the management API, the exception QuotaExceededException is received by the calling code. 基本和標準層：100 個。Basic and Standard tiers: 100.

進階層不支援分割的實體。Partitioned entities aren't supported in the Premium tier.

每個分割佇列或主題的配額計數為每個命名空間 1000 個實體。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
工作階段識別碼訊息的大小上限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.

屬性包中的標頭屬性數目上限︰byte/int.MaxValue。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 產生 SerializationException 例外狀況。The exception SerializationException is generated. 每個屬性的訊息屬性大小上限為 32000。Maximum message property size for each property is 32,000. 所有屬性的累計大小不得超過 64000。Cumulative size of all properties can't exceed 64,000. 此限制適用於 BrokeredMessage 的整個標頭，其中同時包含使用者屬性和系統屬性，例如 Sequence Number、Label 和 Message ID。This limit applies to the entire header of the Brokered Message, which has both user properties and system properties, such as Sequence Number, Label, and Message ID.
每個主題的訂用帳戶數目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. 針對標準層和進階層每個主題 2000 個。2,000 per-topic for the Standard tier and Premium 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. 篩選條件字串的長度上限︰1024 (1 K)。Maximum length of filter condition string: 1,024 (1 K).

規則動作字串的長度上限︰1024 (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 限制Site Recovery limits

下列限制適用於 Azure Site Recovery。The following limits apply to Azure Site Recovery.

限制識別碼Limit identifier 限制Limit
每個訂用帳戶的保存庫數目Number of vaults per subscription 500500
每個復原服務保存庫的伺服器數目Number of servers per Recovery Services vault 250250
每個復原服務保存庫的保護群組數目Number of protection groups per Recovery Services vault 沒有限制No limit
每個復原服務保存庫的復原計畫數目Number of recovery plans per Recovery Services vault 沒有限制No limit
每個保護群組的伺服器數目Number of servers per protection group 沒有限制No limit
每個復原計畫的伺服器數目Number of servers per recovery plan 100100

SQL Database 限制SQL Database limits

如 SQL Database 限制，請參閱 SQL Database 單一資料庫的資源限制、彈性集區和集區 資料庫 SQL Database 資源限制，以及 SQL 受控執行個體的 SQL Database 資源限制。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 SQL Managed Instance.

Azure Synapse Analytics 限制Azure Synapse Analytics limits

如 Azure Synapse Analytics 限制，請參閱 Azure Synapse 資源限制。For Azure Synapse Analytics limits, see Azure Synapse resource limits.

儲存體限制Storage limits

下表說明 Azure 一般用途 v1、v2、Blob 儲存體及區塊 Blob 儲存體帳戶的預設限制。The following table describes default limits for Azure general-purpose v1, v2, Blob storage, and block blob 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.

注意

您可以要求更高的容量和輸入限制。You can request higher capacity and ingress limits. 若要要求提高，請連絡 Azure 支援。To request an increase, contact Azure Support.

資源Resource 限制Limit
每個區域中每個訂用帳戶的儲存體帳戶數目，包括標準和進階儲存體帳戶。Number of storage accounts per region per subscription, including standard, and premium storage accounts. 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) 10 Gbps10 Gbps
每一儲存體帳戶的輸入上限1 (美國和歐洲以外的區域)Maximum ingress1 per storage account (regions other than US and Europe) 如果啟用 RA-GRS/GRS，則為 5 Gbps，LRS/ZRS 為 10 Gbps25 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/ZRS 為 30 Gbps220 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/ZRS 為 15 Gbps210 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 儲存體複寫。For more information, see Azure Storage replication.

注意

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.

所有儲存體帳戶都會在平面網路拓撲上執行，不論其建立時間為何。All storage accounts run on a flat network topology regardless of when they were created. 如需 Azure 儲存體平面網路架構及延展性的詳細資訊，請參閱 Microsoft Azure 儲存體：具有高度一致性的高可用性雲端儲存體服務 (英文)。For more information on the Azure Storage flat network architecture and on scalability, see Microsoft Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency.

如需標準儲存體帳戶限制的詳細資訊，請參閱 標準儲存體帳戶的擴充性目標。For more information on limits for standard storage accounts, see Scalability targets for standard storage accounts.

儲存體資源提供者限制Storage resource provider limits

只有在使用 Azure Resource Manager 搭配 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 分鐘 800800 per 5 minutes
儲存體帳戶管理作業 (寫入)Storage account management operations (write) 每秒 10 次/每小時 1200 次10 per second / 1200 per hour
儲存體帳戶的管理作業 (清單)Storage account management operations (list) 每 5 分鐘 100100 per 5 minutes

Azure Blob 儲存體的限制Azure Blob storage limits

資源Resource 目標Target 目標 (預覽)Target (Preview)
單一 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 4000 MiB (預覽)4000 MiB (preview)
區塊 Blob 的大小上限Maximum size of a block blob 50,000 X 100 MiB (大約 4.75 TiB)50,000 X 100 MiB (approximately 4.75 TiB) 50,000 X 4000 MiB (大約 190.7 TiB) (預覽)50,000 X 4000 MiB (approximately 190.7 TiB) (preview)
附加 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 TiB28 TiB2
每個 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 MiB2Up to 60 MiB per second2
單一區塊 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. 具體而言，請針對標準儲存體帳戶，呼叫 Put Blob 或 Put Block 作業，其 Blob 或區塊大小大於 4 MiB。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 Storage 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.

2 具有階層命名空間設定的帳戶尚未支援分頁 Blob。2 Page blobs are not yet supported in accounts that have the Hierarchical namespace setting on them.

下表描述服務版本所允許的最大區塊和 Blob 大小。The following table describes the maximum block and blob sizes permitted by service version.

服務版本Service version 區塊大小上限 (透過 Put Block)Maximum block size (via Put Block) Blob 大小上限 (透過 Put Block List)Maximum blob size (via Put Block List) 透過單一寫入作業的 Blob 大小上限 (透過 Put Blob)Maximum blob size via single write operation (via Put Blob)
2019-12-12 版和更新版本Version 2019-12-12 and later 4000 MiB (預覽)4000 MiB (preview) 大約 190.7 TiB (4000 MiB X 50,000 個區塊) (預覽)Approximately 190.7 TiB (4000 MiB X 50,000 blocks) (preview) 5000 MiB (預覽)5000 MiB (preview)
2016-05-31 版至 2019-07-07 版Version 2016-05-31 through version 2019-07-07 100 MiB100 MiB 大約 4.75 TiB (100 MiB X 50,000 個區塊)Approximately 4.75 TiB (100 MiB X 50,000 blocks) 256 MiB256 MiB
2016-05-31 之前的版本Versions prior to 2016-05-31 4 MiB4 MiB 大約 195 GiB (4 MiB X 50,000 個區塊)Approximately 195 GiB (4 MiB X 50,000 blocks) 64 MiB64 MiB

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 4 TiB4 TiB
檔案共用中的檔案數目上限Maximum number of files in a file share 沒有限制No limit 沒有限制No limit
每個共用的最大 IOPSMaximum IOPS per share 10,000 IOPS**、1,000 IOPS 或 100 毫秒內 100 個要求10,000 IOPS**, 1,000 IOPS or 100 requests in 100ms 100,000 IOPS100,000 IOPS
每個檔案共用的預存存取原則的最大數目Maximum number of stored access policies per file share 55 55
單一檔案共用的目標輸送量Target throughput for a single file share 最高 300 MiB/秒**、最高 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 or directory 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
固定連結限制 (僅限 NFS)Hard link limit (NFS only) N/AN/A 178178
SMB 多重通道的通道數目上限Maximum number of SMB Multichannel channels N/AN/A 44

* 標準檔案共用的限制適用於標準檔案共用可用的三個層級：交易最佳化、經常性存取和非經常性存取。* The limits for standard file shares apply to all three of the tiers available for standard file shares: transaction optimized, hot, and cool.

** 標準檔案共用的預設值為 5 TiB，請參閱啟用和建立大型檔案共用，以取得如何增加標準檔案共用規模 (最高可達 100 TiB) 的詳細資料。** Default on standard file shares is 5 TiB, see Enable and create large file shares for the details on how to increase the standard file shares scale up to 100 TiB.

Azure 檔案同步的限制Azure File Sync limits

資源Resource 目標Target 固定限制Hard limit
每個區域的儲存體同步服務數目Storage Sync Services per region 100 個儲存體同步服務100 Storage Sync Services 是Yes
每個儲存體同步服務的同步群組Sync groups per Storage Sync Service 200 個同步群組200 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 100 個伺服器端點100 server endpoints 是Yes
每部伺服器的伺服器端點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 and newer: Based on file system cluster size (double file system cluster size). 例如，若檔案系統叢集大小為 4 KB，則最小檔案大小會是 8 KB。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 KiB 訊息大小)20,000 messages per second, which assumes a 1-KiB message size
單一佇列的目標輸送量 (1 KiB 訊息)Target throughput for a single queue (1-KiB messages) 每秒最多 2,000 個訊息Up to 2,000 messages per second

Azure 資料表儲存體的限制Azure Table storage limits

下表描述資料表儲存體的容量、延展性和效能目標。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 (包括 3 個系統屬性：PartitionKey、RowKey 和 Timestamp)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.
PartitionKeySize of the PartitionKey 大小最多 1 KiB 的字串A string up to 1 KiB in size
RowKeySize 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. 無論磁碟以平台代控金鑰還是客戶自控金鑰進行加密，限制都會維持不變。The limits remain the same irrespective of disks encrypted with either platform-managed keys or customer-managed keys. 每個資源群組的受控磁碟、快照集和映像數目沒有限制。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

若為標準儲存體帳戶： 標準儲存體帳戶的總要求率上限為 20000 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.

磁片加密集Disk encryption sets

每個訂用帳戶的每個區域都有50磁片加密集的限制。There's a limitation of 50 disk encryption sets per region, per subscription. 如需詳細資訊，請參閱適用于 Linux 或 Windows 虛擬機器的加密檔。For more information, see the encryption documentation for Linux or Windows virtual machines. 如果您需要增加配額，請聯絡 Azure 支援。If you need to increase the quota, contact Azure support.

受控虛擬機器磁碟Managed virtual machine disks

標準 HDD 受控磁碟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 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 300 MB/秒Up to 300 MB/sec 最高 500 MB/秒Up to 500 MB/sec 最高 500 MB/秒Up to 500 MB/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 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 60 MB/秒Up to 60 MB/sec 最高 400 MB/秒Up to 400 MB/sec 最高 600 MB/秒Up to 600 MB/sec 最高 750 MB/秒Up to 750 MB/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 MB/秒25 MB/sec 25 MB/秒25 MB/sec 25 MB/秒25 MB/sec 25 MB/秒25 MB/sec 50 MB/秒50 MB/sec 100 MB/秒100 MB/sec 125 MB/秒125 MB/sec 150 MB/秒150 MB/sec 200 MB/秒200 MB/sec 250 MB/秒250 MB/sec 250 MB/秒250 MB/sec 500 MB/秒500 MB/sec 750 MB/秒750 MB/sec 900 MB/秒900 MB/sec
每一磁碟的 IOPS 高載上限Max 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 MB/秒170 MB/sec 170 MB/秒170 MB/sec 170 MB/秒170 MB/sec 170 MB/秒170 MB/sec 170 MB/秒170 MB/sec 170 MB/秒170 MB/sec 170 MB/秒170 MB/sec 170 MB/秒170 MB/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 80,000 IOPS (使用 GS5 虛擬機器)80,000 IOPS with GS5 VM
每一 VM 的輸送量上限Maximum throughput per VM 2,000 MB/秒 (使用 GS5 虛擬機器)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 GiB (1 TB)1,024 GiB (1 TB) 2,048 GiB (2 TB)2,048 GiB (2 TB) 4,095 GiB (4 TB)4,095 GiB (4 TB)
每一磁碟的最大 IOPSMaximum IOPS per disk 500500 2,3002,300 5,0005,000 7,5007,500 7,5007,500
每一磁碟的輸送量上限Maximum throughput per disk 100 MB/秒100 MB/sec 150 MB/秒150 MB/sec 200 MB/秒200 MB/sec 250 MB/秒250 MB/sec 250 MB/秒250 MB/sec
每個儲存體帳戶的磁碟數目上限Maximum number of disks per storage account 280280 7070 3535 1717 88

進階非受控虛擬機器磁碟：每一 VM 的限制Premium unmanaged virtual machine disks: Per-VM limits

資源Resource 限制Limit
每一 VM 的最大 IOPSMaximum IOPS per VM 80,000 IOPS (使用 GS5 虛擬機器)80,000 IOPS with GS5 VM
每一 VM 的輸送量上限Maximum throughput per VM 2,000 MB/秒 (使用 GS5 虛擬機器)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 適用於 StorSimple 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 適用於 StorSimple 801030 TB for StorSimple 8010

64 TB 適用於 StorSimple 802064 TB for StorSimple 8020		 StorSimple 8010 和 StorSimple 8020 為 Azure 中的虛擬裝置，分別使用了「標準儲存體」和「進階儲存體」。StorSimple 8010 and StorSimple 8020 are virtual devices in Azure that use Standard storage and Premium storage, respectively.
實體裝置上之固定在本機的磁碟區的大小上限Maximum size of a locally pinned volume on physical devices 9 TB 適用於 StorSimple 81009 TB for StorSimple 8100

24 TB 適用於 StorSimple 860024 TB for StorSimple 8600		 StorSimple 8100 和 StorSimple 8600 都是實體裝置。StorSimple 8100 and StorSimple 8600 are physical devices.
iSCSI 連線的數目上限Maximum number of iSCSI connections 512512
從起始端之 iSCSI 連線的數目上限Maximum number of iSCSI connections from initiators 512512
每個裝置的存取控制記錄的數目上限Maximum number of access control records per device 6464
每個備份原則的磁碟區數目上限Maximum number of volumes per backup policy 2424
每個備份原則保留的備份數目上限Maximum number of backups retained per backup policy 6464
每個備份原則的排程數目上限Maximum number of schedules per backup policy 1010
每個磁碟區可以保留之任何類型快照集的數目上限Maximum number of snapshots of any type that can be retained per volume 256256 此數量包括本機快照和雲端快照。This amount includes local snapshots and cloud snapshots.
可以在任何裝置中呈現的快照集數目上限Maximum number of snapshots that can be present in any device 10,00010,000
可以針對備份、還原或複製進行平行處理的磁碟區數目上限Maximum number of volumes that can be processed in parallel for backup, restore, or clone 1616
  • 如果有 16 個以上的磁碟區，當有可用的處理插槽時會依序處理它們。If there are more than 16 volumes, they're processed sequentially as processing slots become available.
  • 作業完成前，無法對於備份或還原的分層式磁碟區進行新的備份。New backups of a cloned or a restored tiered volume can't occur until the operation is finished. 對於本機磁碟區，在磁碟區上線後允許備份。For a local volume, backups are allowed after the volume is online.
分層磁碟區的還原和複製復原時間Restore and clone recover time for tiered volumes <2 分鐘<2 minutes
  • 無論磁碟區大小為何，磁碟區均可在 2 分鐘內用於還原或複製作業。The volume is made available within 2 minutes of a restore or clone operation, regardless of the volume size.
  • 磁碟區效能一開始可能會比正常情況慢，因為大部分資料和中繼資料仍然位於雲端。The volume performance might initially be slower than normal as most of the data and metadata still resides in the cloud. 資料從雲端流向 StorSimple 裝置時，效能會提升。Performance might increase as data flows from the cloud to the StorSimple device.
  • 下載中繼資料的總時間取決於配置的磁碟區大小。The total time to download metadata depends on the allocated volume size. 中繼資料會於背景自動帶入裝置，速率為每 TB 的配置磁碟區資料 5 分鐘。Metadata is automatically brought into the device in the background at the rate of 5 minutes per TB of allocated volume data. 此速率可能會受到雲端的網際網路頻寬影響。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. 中繼資料會於背景自動帶入裝置，速率為每 TB 的配置磁碟區資料 5 分鐘。Metadata is automatically brought into the device in the background at the rate of 5 minutes per TB of allocated volume data. 此速率可能會受到雲端的網際網路頻寬影響。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.
  • 還原作業的時間可能會很久，且完成還原的總時間將取決於所佈建的本機磁碟區大小、網際網路頻寬及裝置上現有的資料。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 GB 乙太網路介面920/720 MB/sec with a single 10-gigabit Ethernet network interface 最多 2 倍，使用 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.
查詢中的字元數目上限Maximum number of characters in a query 512000512000 Azure 串流分析作業查詢的固定限制為 512k 個字元。There's a hard limit of 512k characters in an Azure Stream Analytics job query.

虛擬機器限制Virtual Machines limits

虛擬機器限制Virtual Machines limits

資源Resource 限制Limit
每一雲端服務的虛擬機器 1Virtual machines per cloud service 1 5050
每一雲端服務的輸入端點 2Input endpoints per cloud service 2 150150

1 使用傳統部署模型 (而非 Azure Resource Manager) 所建立的虛擬機器都會自動儲存在雲端服務中。1 Virtual 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 輸入端點即可從虛擬機器的雲端服務外部與某個虛擬機器進行通訊。2 Input 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.

虛擬機器限制 - Azure 資源管理員Virtual Machines limits - Azure Resource Manager

當您使用 Azure Resource Manager 和 Azure 資源群組時，適用下列限制。The following limits apply when you use Azure Resource Manager and Azure resource groups.

資源Resource 限制Limit
每一訂用帳戶 VMVMs per subscription 每個區域 25,000 個1。25,0001 per region.
每一訂用帳戶的 VM 總計核心VM total cores per subscription 每個區域 20 個1。201 per region. 請連絡支援人員以提高限制。Contact support to increase limit.
每一訂用帳戶的 Azure 現成 VM 總核心Azure Spot VM total cores per subscription 每個區域 20 個1。201 per region. 請連絡支援人員以提高限制。Contact support to increase limit.
每一訂用帳戶的每個系列 (例如 Dv2 和 F) VM 核心VM per series, such as Dv2 and F, cores per subscription 每個區域 20 個1。201 per region. 請連絡支援人員以提高限制。Contact support to increase limit.
每一訂用帳戶的可用性設定組Availability sets per subscription 每個區域 2,500 個。2,500 per region.
每一可用性設定組的虛擬機器Virtual machines per availability set 200200
依資源群組的鄰近放置群組Proximity placement groups per resource group 800800
每一可用性設定組的虛擬機器Certificates per availability set 19921992
每一訂用帳戶的憑證Certificates per subscription 無限制3Unlimited3

1預設限制會因供應項目類別類型 (例如免費試用版和隨用隨付) 以及因系列 (例如 Dv2、F 和 G) 而有所不同。例如，Enterprise 合約訂用帳戶的預設值為 350。1 Default 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屬性 (例如 SSH 公開金鑰) 也會推送為憑證，並計入此限制。2 Properties such as SSH public keys are also pushed as certificates and count towards this limit. 若要略過此限制，請使用適用於 Windows 的 Azure Key Vault 延伸模組，或適用於 Linux 的 Azure Key Vault 延伸模組以安裝憑證。To bypass this limit, use the Azure Key Vault extension for Windows or the Azure Key Vault extension for Linux to install certificates.

3使用 Azure 資源管理員時，憑證會儲存在 Azure 金鑰保存庫內。3 With Azure Resource Manager, certificates are stored in the Azure Key Vault. 訂用帳戶的憑證數目不受限制。The number of certificates is unlimited for a subscription. 每一部署都有 1 MB 的憑證限制，這是由單一 VM 或可用性設定組所組成。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
  • 每個區域中每個訂用帳戶 1000 個映像定義1,000 image definitions, per subscription, per region
  • 每個區域中每個訂用帳戶 10000 個映像版本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,5002,500

請參閱See also