Azure 訂用帳戶和服務限制、配額與限制Azure subscription and service limits, quotas, and constraints

本文件列出一些最常見的 Microsoft Azure 限制,有時也稱為配額。This document lists some of the most common Microsoft Azure limits, which are also sometimes called quotas. 本文件目前未涵蓋所有 Azure 服務。This document doesn't currently cover all Azure services. 經過一段時間, 清單就會展開並更新, 以涵蓋更多服務。Over time, the list will be expanded and updated to cover more services.

若要深入瞭解 Azure 定價, 請參閱azure 定價總覽To learn more about Azure pricing, see Azure pricing overview. 在這裡, 您可以使用定價計算機來預估成本。There, you can estimate your costs by using the pricing calculator. 您也可以移至特定服務 (例如Windows 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.

注意

如果您想要將限制或配額提升到預設限制以上, 請免費開啟線上客戶支援要求If you want to raise the limit or quota above the default limit, open an online customer support request at no charge. 限制無法高於下表所示的最大限制值。The limits can't be raised above the maximum limit value shown in the following tables. 如果沒有上限資料行, 則資源沒有可調整的限制。If there's no maximum limit column, the resource doesn't have adjustable limits.

免費試用訂用帳戶不符合限制或配額增加的資格。Free Trial subscriptions aren't eligible for limit or quota increases. 如果您有免費試用訂用帳戶,則可以升級到隨用隨付訂用帳戶。If you have a Free Trial subscription, you can upgrade to a Pay-As-You-Go subscription. 如需詳細資訊, 請參閱將Azure 免費試用訂用帳戶升級為隨用隨付訂用帳戶和免費試用訂用帳戶常見問題。For more information, see Upgrade your Azure Free Trial subscription to a Pay-As-You-Go subscription and the Free Trial subscription FAQ.

限制和 Azure Resource ManagerLimits and Azure Resource Manager

現在可以將多個 Azure 資源結合成單一 Azure 資源群組。It's now possible to combine multiple Azure resources into a single Azure resource group. 當您使用資源群組時, 限制為 [全域] 會在具有 Azure Resource Manager 的地區層級進行管理。When you use resource groups, limits that once were global become managed at a regional level with Azure Resource Manager. 如需 Azure 資源群組的詳細資訊, 請參閱Azure Resource Manager 總覽For more information about Azure resource groups, see Azure Resource Manager overview.

在下列限制清單中, 當您使用 Azure Resource Manager 時, 新的資料表會反映任何限制的差異。In the following list of limits, a new table reflects any differences in limits when you use Azure Resource Manager. 例如, 有一個訂用帳戶限制資料表和訂用帳戶限制 Azure Resource Manager資料表。For example, there's a Subscription limits table and a Subscription limits - Azure Resource Manager table. 當限制適用于這兩種情況時, 它只會顯示在第一個資料表中。When a limit applies to both scenarios, it's only shown in the first table. 除非另有說明,限制在所有區域中全域適用。Unless otherwise indicated, limits are global across all regions.

注意

Azure 資源群組中資源的配額是您的訂用帳戶可存取的每個區域, 而不是每個訂用帳戶, 因為服務管理配額為。Quotas for resources in Azure resource groups are per-region accessible by your subscription, not per-subscription as the service management quotas are. 讓我們以 vCPU 配額為例。Let's use vCPU quotas as an example. 若要要求增加對個 vcpu 支援的配額, 您必須決定要在哪些區域中使用多少個 vcpu。To request a quota increase with support for vCPUs, you must decide how many vCPUs you want to use in which regions. 然後, 針對您想要的數量和區域, 對 Azure 資源群組 vCPU 配額提出特定要求。You then make a specific request for Azure resource group vCPU quotas for the amounts and regions that you want. 如果您需要在西歐使用30個 vcpu 來執行應用程式, 您會在西歐特別要求30個 vcpu。If you need to use 30 vCPUs in West Europe to run your application there, you specifically request 30 vCPUs in West Europe. 您的 vCPU 配額不會在任何其他區域中增加, 只有西歐具有 30 vCPU 的配額。Your vCPU quota isn't increased in any other region--only West Europe has the 30-vCPU quota.

因此, 在任何一個區域中決定您的工作負載所需的 Azure 資源群組配額。As a result, decide what your Azure resource group quotas must be for your workload in any one region. 然後在您要部署的每個區域中要求該金額。Then request that amount in each region into which you want to deploy. 如需如何判斷您目前的特定區域配額的說明, 請參閱針對部署問題進行疑難排解For help in how to determine your current quotas for specific regions, see Troubleshoot deployment issues.

特定服務的限制Service-specific limits

訂用帳戶限制Subscription limits

訂用帳戶限制-Azure 服務管理 (傳統部署模型)Subscription limits - Azure Service Management (classic deployment model)

資源Resource 預設限制Default limit 上限Maximum limit
每個 Vcpu訂用帳戶1vCPUs per subscription1 2020 10,00010,000
共同管理員每訂用帳戶Coadministrators per subscription 200200 200200
每一訂用帳戶的儲存體帳戶2Storage accounts per subscription2 100100 100100
每一訂用帳戶雲端服務Cloud services per subscription 2020 200200
區域網路Local networks per subscription 1010 500500
每一訂閱的 DNS 伺服器DNS servers per subscription 99 100100
每一訂用帳戶的保留 IPReserved IPs per subscription 2020 100100
每一訂用帳戶同質群組Affinity groups per subscription 256256 256256
訂用帳戶名稱長度 (字元)Subscription name length (characters) 6464 6464

1額外小型執行個體計數為一種 vCPU,即使使用部分的 CPU 核心的 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.

訂用帳戶限制 - Azure Resource ManagerSubscription limits - Azure Resource Manager

當您使用 Azure Resource Manager 和 Azure 資源群組時, 適用下列限制。The following limits apply when you use Azure Resource Manager and Azure resource groups. 未在 Azure Resource Manager 中變更的限制不會列出。Limits that haven't changed with Azure Resource Manager aren't listed. 請參閱上表以瞭解這些限制。See the previous table for those limits.

如需 Resource Manager API 讀取和寫入限制的相關資訊,請參閱對 Resource Manager 要求進行節流For information about Resource Manager API read and write limits, see Throttling Resource Manager requests.

ResourceResource 預設限制Default limit 上限Maximum limit
每一訂用帳戶 VMVMs per subscription 每個區域 25000125,0001 per region. 25000每個區域。25,000 per region.
每一訂用帳戶的 VM 總計核心VM total cores per subscription 每個區域 201個。201 per region. 請連絡支援人員。Contact support.
每個系列的 VM, 例如 Dv2 和 F, 每個用帳戶的核心VM per series, such as Dv2 and F, cores per subscription 每個區域 201個。201 per region. 請連絡支援人員。Contact support.
每個訂用帳戶共同管理員Coadministrators per subscription 無限制。Unlimited. 無限制。Unlimited.
每一訂用帳戶每一區域的儲存體帳戶Storage accounts per region per subscription 250250 250250
每個訂用帳戶的資源群組Resource groups per subscription 980980 980980
每個訂用帳戶的可用性設定組Availability sets per subscription 2000每個區域。2,000 per region. 2000每個區域。2,000 per region.
Azure Resource Manager API 要求大小Azure Resource Manager API request size 4194304個位元組。4,194,304 bytes. 4194304個位元組。4,194,304 bytes.
每個訂用帳戶的標記2Tags per subscription2 無限制。Unlimited. 無限制。Unlimited.
每個訂用帳戶的唯一標記計算2Unique tag calculations per subscription2 10,00010,000 10,00010,000
每一訂用帳戶雲端服務Cloud services per subscription N/A3N/A3 N/A3N/A3
每一訂用帳戶同質群組Affinity groups per subscription N/A3N/A3 N/A3N/A3
每個位置的訂用帳戶層級部署Subscription-level deployments per location 80048004 800800

1預設限制會因供應專案類別類型而異, 例如免費試用版和隨用隨付, 以及依系列 (例如 Dv2、F 和 G)。例如, Enterprise 合約訂閱的預設值是350。1Default limits vary by offer category type, such as Free Trial and Pay-As-You-Go, and by series, such as Dv2, F, and G. For example, the default for Enterprise Agreement subscriptions is 350.

2您可以對每個訂用帳戶套用不限數目的標記。2You can apply an unlimited number of tags per subscription. 每個資源或資源群組的標記數目受限於 15。The number of tags per resource or resource group is limited to 15. 只有當標記數目為10000或更少時, 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. 當數位超過10000時, 您仍然可以透過標記來尋找資源。You still can find a resource by tag when the number exceeds 10,000.

3Azure 資源群組和 Resource Manager 不再需要這些功能。3These features are no longer required with Azure resource groups and Resource Manager.

4如果您達到800部署的限制, 請從已不再需要的歷程記錄中刪除部署。4If you reach the limit of 800 deployments, delete deployments from the history that are no longer needed. 若要刪除訂用帳戶層級部署, 請使用new-azdeploymentaz deployment deleteTo delete subscription level deployments, use Remove-AzDeployment or az deployment delete.

注意

虛擬機器核心具有區域總計限制。Virtual machine cores have a regional total limit. 它們也會限制每一大小的區域, 例如 Dv2 和 F。系統會分別強制執行這些限制。They also have a limit for regional per-size series, such as Dv2 and F. These limits are separately enforced. 例如,請考慮美國東部訂用帳戶的總計 VM 核心限制為 30、A 系列核心限制為 30,和 D 系列核心限制為 30。For example, consider a subscription with a US East total VM core limit of 30, an A series core limit of 30, and a D series core limit of 30. 此訂用帳戶可以部署30個 A1 Vm 或30個 D1 Vm, 或兩者的組合, 而不超過總計30個核心。This subscription can deploy 30 A1 VMs, or 30 D1 VMs, or a combination of the two not to exceed a total of 30 cores. 結合的範例為10個 A1 Vm 和20個 D1 Vm。An example of a combination is 10 A1 VMs and 20 D1 VMs.

資源群組限制Resource group limits

ResourceResource 預設限制Default limit 上限Maximum limit
每個資源群組的資源 (每個資源類型)Resources per resource group, per resource type 800800 某些資源類型可能會超過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 800800
每個部署的資源Resources per deployment 800800 800800
每個唯一範圍的管理鎖定Management locks per unique scope 2020 2020
每個資源或資源群組的標記數目Number of tags per resource or resource group 1515 1515
標記金鑰長度Tag key length 512512 512512
標記值長度Tag value length 256256 256256

1如果您達到每個資源群組的800部署限制, 請從已不再需要的歷程記錄中刪除部署。1If you reach the limit of 800 deployments per resource group, delete deployments from the history that are no longer needed. 從部署歷程記錄中刪除專案並不會影響已部署的資源。Deleting an entry from the deployment history doesn't affect the deployed resources. 您可以使用 az group deployment delete (Azure CLI) 或 Remove-AzResourceGroupDeployment (PowerShell) 以從歷程記錄中刪除項目。You can delete entries from the history with az group deployment delete for Azure CLI, or Remove-AzResourceGroupDeployment in PowerShell. 如需在持續整合和持續傳遞 (CI/CD) 案例中自動刪除部署的 PowerShell 腳本, 請參閱remove-deploymentsFor a PowerShell script that automates deleting deployments in a continuous integration and continuous delivery (CI/CD) scenario, see remove-deployments.ps1.

範本限制Template limits

Value 預設限制Default limit 上限Maximum limit
參數Parameters 256256 256256
變數Variables 256256 256256
資源 (包括複本計數)Resources (including copy count) 800800 800800
outputsOutputs 6464 6464
範本運算式Template expression 24,576 個字元24,576 chars 24,576 個字元24,576 chars
已匯出範本中的資源Resources in exported templates 200200 200200
範本大小Template size 4 MB4 MB 4 MB4 MB
參數檔案大小Parameter file size 64 KB64 KB 64 KB64 KB

使用巢狀範本,即可超出一些範本限制。You can exceed some template limits by using a nested template. 如需詳細資訊, 請參閱在部署 Azure 資源時使用連結的範本For more information, see Use linked templates when you deploy Azure resources. 若要減少參數、變數或輸出數目,您可以將數個值合併成一個物件。To reduce the number of parameters, variables, or outputs, you can combine several values into an object. 如需詳細資訊,請參閱物件作為參數For more information, see Objects as parameters.

虛擬機器限制Virtual Machines limits

虛擬機器限制Virtual Machines limits

資源Resource 預設限制Default limit 上限Maximum limit
每一個雲端服務的虛擬機器數量 1Virtual machines per cloud service1 5050 5050
每一雲端服務的輸入端點 2Input endpoints per cloud service2 150150 150150

1使用傳統部署模型而不是 Azure Resource Manager 建立的虛擬機器會自動儲存在雲端服務。1Virtual machines created by using the classic deployment model instead of Azure Resource Manager are automatically stored in a cloud service. 您可以將更多虛擬機器加入至該雲端服務以獲得負載平衡和可用性。You can add more virtual machines to that cloud service for load balancing and availability.

2 輸入端點即可從虛擬機器的雲端服務外部與某個虛擬機器進行通訊。2Input endpoints allow communications to a virtual machine from outside the virtual machine's cloud service. 在相同雲端服務或虛擬網路中的虛擬機器可自動彼此通訊。Virtual machines in the same cloud service or virtual network can automatically communicate with each other. 如需詳細資訊,請參閱如何設定虛擬機器的端點For more information, see How to set up endpoints to a virtual machine.

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

當您使用 Azure Resource Manager 和 Azure 資源群組時, 適用下列限制。The following limits apply when you use Azure Resource Manager and Azure resource groups. 未在 Azure Resource Manager 中變更的限制不會列出。Limits that haven't changed with Azure Resource Manager aren't listed. 請參閱上表以瞭解這些限制。See the previous table for those limits.

資源Resource 預設限制Default limit
每一可用性設定組的虛擬機器Virtual machines per availability set 200200
每一訂用帳戶的憑證Certificates per subscription 無限制 1Unlimited1

1使用 Azure 資源管理員時,憑證會儲存在 Azure 金鑰保存庫內。1With Azure Resource Manager, certificates are stored in the Azure Key Vault. 憑證的數目沒有限制的訂用帳戶。The number of certificates is unlimited for a subscription. 沒有憑證,每個部署,其中包含單一 VM 或可用性設定組的 1 MB 的限制。There's a 1-MB limit of certificates per deployment, which consists of either a single VM or an availability set.

使用共用映射庫部署資源時, 每個訂用帳戶都有限制:There are limits, per subscription, for deploying resources using Shared Image Galleries:

  • 100共用映射資源庫, 每個訂用帳戶, 每個區域100 shared image galleries, per subscription, per region
  • 1000每個區域每個訂用帳戶的映射定義1,000 image definitions, per subscription, per region
  • 10000映射版本, 每個訂用帳戶, 每個區域10,000 image versions, per subscription, per region

虛擬機器擴展集限制Virtual machine scale sets limits

資源Resource 預設限制Default limit 上限Maximum limit
擴展集中的 VM 數目上限Maximum number of VMs in a scale set 1,0001,000 1,0001,000
擴展集中以自訂 VM 影像為基礎的 VM 數目上限Maximum number of VMs based on a custom VM image in a scale set 600600 600600
區域中的擴展集數目上限Maximum number of scale sets in a region 2,0002,000 2,0002,000

Container Instances 限制Container Instances limits

資源Resource 預設限制Default limit
每一訂用帳戶的容器群組Container groups per subscription 10011001
每個容器群組的容器數目Number of containers per container group 6060
每個容器群組的磁碟區數目Number of volumes per container group 2020
每個 IP 的連接埠數目Ports per IP 55
容器執行個體記錄大小 - 執行中的執行個體Container instance log size - running instance 4 MB4 MB
容器執行個體記錄大小 - 已停止的執行個體Container instance log size - stopped instance 16 KB 或 1,000 行16 KB or 1,000 lines
每小時的容器建立Container creates per hour 30013001
每 5 分鐘的容器建立Container creates per 5 minutes 10011001
每小時的容器刪除Container deletes per hour 30013001
每 5 分鐘的容器刪除Container deletes per 5 minutes 10011001

1若要要求提高限制,請建立 Azure 支援要求1To request a limit increase, create an Azure Support request.

Container Registry 登入Container Registry limits

下表詳述「基本」、「標準」和「進階」服務層級的功能和限制。The following table details the features and limits of the Basic, Standard, and Premium service tiers.

ResourceResource 基本Basic 標準Standard 進階Premium
儲存體1Storage1 10 GiB10 GiB 100 GiB100 GiB 500 GiB500 GiB
影像圖層大小上限Maximum image layer size 200 GiB200 GiB 200 GiB200 GiB 200 GiB200 GiB
每分鐘的 ReadOps2, 3ReadOps per minute2, 3 1,0001,000 3,0003,000 10,00010,000
每分鐘的 WriteOps2, 4WriteOps per minute2, 4 100100 500500 2,0002,000
下載頻寬 Mbps2Download bandwidth MBps2 3030 6060 100100
上傳頻寬 Mbps2Upload bandwidth MBps2 1010 2020 5050
webhooksWebhooks 22 1010 100100
異地複寫Geo-replication N/AN/A N/AN/A 支援Supported
內容信任Content trust N/AN/A N/AN/A 支援Supported

1指定的儲存體限制是每一層的內含儲存體數量。1The specified storage limits are the amount of included storage for each tier. 對於超過這些限制的影像儲存,您需要依每 GiB 的每日費率另外支付費用。You're charged an additional daily rate per GiB for image storage above these limits. 如需費率資訊, 請參閱Azure Container Registry 定價For rate information, see Azure Container Registry pricing.

2ReadOpsWriteOps頻寬是最小的預估值。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.

Azure Kubernetes Service 限制Azure Kubernetes Service limits

資源Resource 預設限制Default limit
最大的叢集,每個訂用帳戶Maximum clusters per subscription 100100
每個叢集的節點上限Maximum nodes per cluster 100100
每個節點的最大 pod:採用 Kubenet 的基本網路功能Maximum pods per node: Basic networking with Kubenet 110110
每個節點的最大 pod:進階網路功能與 Azure 容器網路介面Maximum pods per node: Advanced networking with Azure Container Networking Interface Azure CLI 部署:301Azure CLI deployment: 301
Azure 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 Service 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

網路限制Networking limits

網路限制-Azure Resource Manager 下列限制僅適用于透過每個訂用帳戶的每個區域Azure Resource Manager管理的網路資源。Networking 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.

注意

我們最近已將所有預設限制提升至其最大限制。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

ResourceResource 預設/最大限制Default/maximum limit
虛擬網路Virtual networks 1,0001,000
每一虛擬網路的子網路Subnets per virtual network 3,0003,000
每個虛擬網路的虛擬網路對等互連Virtual network peerings per virtual network 500500
每個虛擬網路的 DNS 伺服器DNS servers per virtual network 2020
每個虛擬網路的私人 IP 位址Private IP addresses per virtual network 65,53665,536
每個網路介面的私人 IP 位址Private IP addresses per network interface 256256
每個虛擬機器的私人 IP 位址Private IP addresses per virtual machine 256256
每個網路介面的公用 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

ResourceResource 預設限制Default limit 上限Maximum limit
公用 IP 位址 - 動態Public IP addresses - dynamic 適用于 Basic 的1000。1,000 for Basic. 請連絡支援人員。Contact support.
公用 IP 位址 - 靜態Public IP addresses - static 適用于 Basic 的1000。1,000 for Basic. 請連絡支援人員。Contact support.
公用 IP 位址 - 靜態Public IP addresses - static 適用于 Standard 的200。200 for Standard. 請連絡支援人員。Contact support.
公用 IP 前置長度Public IP prefix length /28/28 請連絡支援人員。Contact support.

負載平衡器限制Load balancer limits

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

ResourceResource 預設/最大限制Default/maximum limit
負載平衡器Load balancers 1,0001,000
每個資源的規則,基本Rules per resource, Basic 250250
每個資源的規則,標準Rules per resource, Standard 1,5001,500
每個 IP 設定的規則Rules per IP configuration 299299
每個 NIC 的規則Rules per NIC 300300
前端 IP 設定, 基本Front-end IP configurations, Basic 200200
前端 IP 設定, 標準Front-end IP configurations, Standard 600600
後端集區, 基本Back-end pool, Basic 100, 單一可用性設定組100, single availability set
後端集區, 標準Back-end pool, Standard 1000, 單一虛擬網路1,000, single virtual network
每個負載平衡器的後端資源, 標準1Back-end resources per load balancer, Standard1 150150
高可用性埠, 標準High-availability ports, Standard 每個內部前端1個1 per internal front-end

1限制是最多150個資源, 任何獨立虛擬機器資源、可用性設定組資源和虛擬機器擴展集資源的組合。1The limit is up to 150 resources, in any combination of standalone virtual machine resources, availability set resources, and virtual machine scale-set resources.

下列限制僅適用于透過每個訂用帳戶的傳統部署模型所管理的網路資源。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.

ResourceResource 預設限制Default limit 上限Maximum limit
虛擬網路Virtual networks 100100 100100
區域網路網站Local network sites 2020 請連絡支援人員。Contact support.
每個虛擬網路的 DNS 伺服器DNS servers per virtual network 2020 2020
每個虛擬網路的私人 IP 位址Private IP addresses per virtual network 4,0964,096 4,0964,096
虛擬機器或角色執行個體之每個 NIC 的並行 TCP 或 UDP 流程Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 500000, 最多1000000個, 適用于兩個以上的 Nic。500,000, up to 1,000,000 for two or more NICs. 500000, 最多1000000個, 適用于兩個以上的 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 1,0001,000 1,0001,000
使用者定義的路由表User-defined route tables 200200 200200
每個路由表的使用者定義路由User-defined routes per route table 400400 400400
公用 IP 位址 (動態)Public IP addresses (dynamic) 500500 500500
保留的公用 IP 位址Reserved public IP addresses 500500 500500
每個部署的公用 VIPPublic VIP per deployment 55 連絡支援人員Contact support
每個部署的私人 VIP (內部負載平衡)Private VIP (internal load balancing) per deployment 11 11
端點存取控制清單 (Acl)Endpoint access control lists (ACLs) 5050 5050

ExpressRoute 限制ExpressRoute limits

ResourceResource 預設值/最大限制Default/maximum limit
每個訂用帳戶的 ExpressRoute 電路ExpressRoute circuits per subscription 1010
每個訂用帳戶,使用 Azure Resource Manager 區域的 ExpressRoute 線路ExpressRoute circuits per region per subscription, with Azure Resource Manager 1010
公告至 Azure 私人對等互連具有 ExpressRoute Standard 的最大路由數目Maximum number of routes advertised to Azure private peering with ExpressRoute Standard 4,0004,000
向 Azure 私人對等互連具有 ExpressRoute Premium 附加元件公告的最大路由數目Maximum number of routes advertised to Azure private peering with ExpressRoute Premium add-on 10,00010,000
從 Azure 私人對等互連的 ExpressRoute 連線的 VNet 位址空間的最大路由數目公告Maximum number of routes advertised from Azure private peering from the VNet address space for an ExpressRoute connection 200200
公告至 Microsoft 對等互連具有 ExpressRoute Standard 的最大路由數目Maximum number of routes advertised to Microsoft peering with ExpressRoute Standard 200200
向 Microsoft 對等互連具有 ExpressRoute Premium 附加元件公告的最大路由數目Maximum number of routes advertised to Microsoft peering with ExpressRoute Premium add-on 200200
ExpressRoute 線路連結至相同的虛擬網路位於相同的對等互連位置的最大數目Maximum number of ExpressRoute circuits linked to the same virtual network in the same peering location 44
ExpressRoute 線路連結至相同虛擬網路中不同對等互連位置的最大數目Maximum number of ExpressRoute circuits linked to the same virtual network in different peering locations 44
每個 ExpressRoute 電路允許的虛擬網路連結數目Number of virtual network links allowed per ExpressRoute circuit 請參閱的每個 ExpressRoute 電路的虛擬網路數目資料表。See the Number of virtual networks per ExpressRoute circuit table.

每個 ExpressRoute 電路的虛擬網路數目Number of virtual networks per ExpressRoute circuit

電路大小Circuit size 標準的虛擬網路連結數目Number of virtual network links for Standard 具有 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

應用程式閘道限制Application Gateway limits

下列表格適用於 v1、v2、「標準」及 WAF SKU (除非另外註明)。The following table applies to v1, v2, Standard, and WAF SKUs unless otherwise stated.

資源Resource 預設值/最大限制Default/maximum limit 附註Note
Azure 應用程式閘道Azure Application Gateway 訂用帳戶每 1,000 個1,000 per subscription
前端 IP 組態Front-end IP configurations 22 公用 1 個和私用 1 個1 public and 1 private
前端連接埠Front-end ports 10011001
後端位址集區Back-end address pools 10011001
每個集區的後端伺服器Back-end servers per pool 1,2001,200
HTTP 接聽程式HTTP listeners 10011001
HTTP 負載平衡規則HTTP load-balancing rules 10011001
後端 HTTP 設定Back-end HTTP settings 10011001
每個閘道的執行個體Instances per gateway 3232
SSL 憑證SSL certificates 10011001 每個 HTTP 接聽程式 11 per HTTP listeners
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 接聽程式 11 per HTTP listeners
每個接聽程式的 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
大型閘道 50 kLarge gateways 50k
URL 長度上限Maximum URL length 8,0008,000
檔案上傳大小上限標準Maximum file upload size, Standard 2 GB2 GB
WAF 檔案上傳大小上限Maximum file upload size WAF 中型 WAF 閘道、 100 MBMedium WAF gateways, 100 MB
大型的 WAF 閘道、 500 MBLarge WAF gateways, 500 MB
WAF 主體大小上限,如果沒有檔案WAF body size limit, without files 128 KB128 KB
最大的 WAF 自訂規則Maximum WAF custom rules 100100

1時已啟用 WAF 的 Sku,我們建議您限制為 40,以獲得最佳效能的資源數目。1 In case of WAF-enabled SKUs, we recommend that you limit the number of resources to 40 for optimal performance.

網路監看員限制Network Watcher limits

資源Resource 預設限制Default limit 上限Maximum limit 附註Note
Azure 網路監看員Azure Network Watcher 每個區域 1 個1 per region 每個區域 1 個1 per region 若要啟用服務的存取權,會建立網路監看員。Network Watcher is created to enable access to the service. 每個區域需要網路監看員的只有一個執行個體。Only one instance of Network Watcher is required per subscription per region.
封包擷取工作階段Packet capture sessions 每區域 100 個100 per region 10,00010,000 擷取工作階段數目,不會儲存。Number of sessions only, not saved captures.

流量管理員限制Traffic Manager limits

資源Resource 預設值/最大限制Default/maximum limit
每一訂用帳戶的設定檔Profiles per subscription 200200
每一設定檔的端點Endpoints per profile 200200

Azure DNS 限制Azure DNS limits

公用 DNS 區域Public DNS zones

ResourceResource 預設限制Default limit
每個訂用帳戶的公用 DNS 區域Public DNS Zones per subscription 250 1250 1
每個公用 DNS 區域的記錄集Record sets per public DNS zone 10,000 110,000 1
公用 DNS 區域中每個記錄集的記錄Records per record set in public DNS zone 2020
單一 Azure 資源的別名記錄數目Number of Alias records for a single Azure resource 2020
每個訂用帳戶的私人 DNS 區域Private DNS zones per subscription 10001000
每個私人 DNS 區域的記錄集Record sets per private DNS zone 2500025000
私人 DNS 區域的每個記錄集記錄Records per record set for private DNS zones 2020
每個私人 DNS 區域的虛擬網路連結Virtual Network Links per private DNS zone 10001000
已啟用自動註冊的每個私人 DNS 區域的虛擬網路連結Virtual Networks Links per private DNS zones with auto-registration enabled 100100
已啟用自動註冊的虛擬網路可連結的私人 DNS 區域數目Number of private DNS zones a virtual network can get linked to with auto-registration enabled 11
虛擬網路可以連結的私人 DNS 區域數目Number of private DNS zones a virtual network can get linked 10001000

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

Azure 防火牆限制Azure Firewall limits

ResourceResource 預設限制Default limit
資料輸送量Data throughput 30 Gbps130 Gbps1
規則Rules 10000, 結合所有規則類型。10,000, all rule types combined.
AzureFirewallSubnet 大小下限Minimum AzureFirewallSubnet size /26/26
網路和應用程式規則中的連接埠範圍Port range in network and application rules 0-64,000。0-64,000. 我們正努力放寬這項限制。Work is in progress to relax this limitation.
公用 IP 位址Public IP addresses 100 上限100 maximum
路由表Route table 根據預設, AzureFirewallSubnet 具有 0.0.0.0/0 路由, 並將 NextHopType 值設為InternetBy default, AzureFirewallSubnet has a 0.0.0.0/0 route with the NextHopType value set to Internet.

「Azure 防火牆」必須能夠直接連線到網際網路。Azure Firewall must have direct Internet connectivity. 如果您的 AzureFirewallSubnet 透過 BGP 學習到內部部署網路的預設路由, 您必須以 0.0.0.0/0 UDR 覆寫它, 並將NextHopType值設為 [網際網路], 以維持直接的網際網路連線能力。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.

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

Azure Front Door Service 限制Azure Front Door Service limits

資源Resource 預設值/最大限制Default/maximum limit
每個訂用帳戶的 azure 前端服務資源Azure Front Door Service resources per subscription 100100
前端主機,其中包含每個資源的自訂網域Front-end hosts, which includes custom domains per resource 100100
每個資源的路由規則Routing rules per resource 100100
每個資源的後端集區Back-end pools per resource 5050
每個後端集區的後端Back ends per back-end pool 100100
要符合路由規則的路徑模式Path patterns to match for a routing rule 2525
每個原則的自訂 Web 應用程式防火牆規則Custom web application firewall rules per policy 1010
每個資源的 Web 應用程式防火牆原則Web application firewall policy per resource 100100
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 to application back-end

  • 如果回應是區塊的回應,還是在收到第一個區塊時,會傳回 200。If the response is a chunked response, a 200 is returned if or when the first chunk is received.
  • 將 HTTP 要求轉送至後端之後,前端會等候 30 秒,讓來自後端的第一個封包。After the HTTP request is forwarded to the back end, Front Door waits for 30 seconds for the first packet from the back end. 然後它會傳回 「 503 錯誤給用戶端。Then it returns a 503 error to the client.
  • 從後端收到第一個封包之後,前端會等候的閒置逾時為 30 秒。After the first packet is received from the back end, Front Door waits for 30 seconds in an idle timeout. 然後它會傳回 「 503 錯誤給用戶端。Then it returns a 503 error to the client.
  • 前端到後端 TCP 工作階段逾時為 30 分鐘。Front Door to the back-end TCP session timeout is 30 minutes.

上傳和下載資料限制Upload and download data limit

使用區塊傳輸編碼 (CTE)With chunked transfer encoding (CTE) 沒有區塊處理的 HTTPWithout 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 字串)-最大的查詢字串大小為 4,096 個位元組-指定查詢字串,最大長度,以位元組為單位。Maximum URL size - 8,192 bytes - Specifies maximum length of the raw URL (scheme + hostname + port + path + query string of the URL)- Maximum Query String size - 4,096 bytes - Specifies the maximum length of the query string, in bytes.

儲存體限制Storage limits

下表說明 Azure 一般用途 v1、v2 和 Blob 儲存體帳戶的預設限制。The following table describes default limits for Azure general-purpose v1, v2, and Blob storage accounts. 輸入限制是指傳送至儲存體帳戶之要求中的所有資料。The ingress limit refers to all data from requests that are sent to a storage account. 輸出限制是指從儲存體帳戶接收的回應中的所有資料。The egress limit refers to all data from responses that are received from a storage account.

ResourceResource 預設限制Default limit
每個區域中每個訂用帳戶的儲存體帳戶數目,包括標準和進階帳戶Number of storage accounts per region per subscription, including both standard and premium accounts 250250
儲存體帳戶容量上限Maximum storage account capacity 2 PB, 適用于美國和歐洲, 而所有其他區域的 500 TB (含英國)12 PB for US and Europe, and 500 TB for all other regions (including the UK)1
每個儲存體帳戶的 blob 容器、blob、檔案共用、資料表、佇列、實體或訊息數目上限Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account 無限制No limit
每一儲存體帳戶的要求率上限1Maximum request rate1 per storage account 每秒 20,000 個要求20,000 requests per second
每一儲存體帳戶的輸入上限1 (美國、歐洲地區)Maximum ingress1 per storage account (US, Europe regions) 25 Gbps25 Gbps
每一儲存體帳戶的輸入上限1 (美國和歐洲以外的地區)Maximum ingress1 per storage account (regions other than US and Europe) 如果啟用了 RA-GRS/GRS, 則為 5 gbps, LRS/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

1Azure 標準儲存體帳戶支援更高的容量限制, 以及依要求輸入的更高限制。1Azure Standard Storage accounts support higher capacity limits and higher limits for ingress by request. 若要要求提高帳戶的輸入限制,請連絡 Azure 支援To request an increase in account limits for ingress, contact Azure Support. 如需詳細資訊, 請參閱宣佈較大型、較大規模的儲存體帳戶For more information, see Announcing larger, higher scale storage accounts.

2 Azure 儲存體複寫選項包括:2 Azure Storage replication options include:

  • RA-GRS:讀取權限異地備援儲存體。RA-GRS: Read-access geo-redundant storage. 如果已啟用 RA-GRS,次要位置的輸出目標會與主要位置的輸出目標完全相同。If RA-GRS is enabled, egress targets for the secondary location are identical to those for the primary location.
  • GRS:異地備援儲存體。GRS: Geo-redundant storage.
  • ZRS:區域備援儲存體。ZRS: Zone-redundant storage.
  • LRS:本地備援儲存體。LRS: Locally redundant storage.

注意

我們建議您在大部分情況下使用一般用途 v2 儲存體帳戶。We recommend that you use a general-purpose v2 storage account for most scenarios. 您可以輕鬆地將一般用途 v1 或 Azure Blob 儲存體帳戶升級至一般用途 v2 帳戶, 而不需停機, 也不需要複製資料。You can easily upgrade a general-purpose v1 or an Azure Blob storage account to a general-purpose v2 account with no downtime and without the need to copy data.

如需 Azure 儲存體帳戶的詳細資訊, 請參閱儲存體帳戶總覽For more information on Azure Storage accounts, see Storage account overview.

如果您應用程式的需求超過單一儲存體帳戶的延展性目標,您可以將應用程式建置為使用多個儲存體帳戶。If the needs of your application exceed the scalability targets of a single storage account, you can build your application to use multiple storage accounts. 接著您可以在這些儲存體帳戶之間分割資料物件。You can then partition your data objects across those storage accounts. 如需有關大量價格的資訊, 請參閱Azure 儲存體定價For information on volume pricing, see Azure Storage pricing.

所有儲存體帳戶都能在一般網路拓撲上執行,並支援本文中說明的延展性和效能目標,無論它們在何時建立。All storage accounts run on a flat network topology and support the scalability and performance targets outlined in this article, regardless of when they were created. 如需 Azure 儲存體平面網路架構及延展性的詳細資訊,請參閱 Microsoft Azure 儲存體:具有高度一致性的高可用性雲端儲存體服務 (英文)。For more information on the Azure Storage flat network architecture and on scalability, see Microsoft Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency.

如需有關儲存體帳戶限制的詳細資訊, 請參閱Azure 儲存體擴充性和效能目標For more information on storage account limits, see Azure Storage scalability and performance targets.

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

只有在您使用 Azure 儲存體使用 Azure Resource Manager 執行管理作業時,才會適用下列限制。The following limits apply only when you perform management operations by using Azure Resource Manager with Azure Storage.

資源Resource 預設限制Default limit
儲存體帳戶的管理作業 (讀取)Storage account management operations (read) 每 5 分鐘 800800 per 5 minutes
儲存體帳戶管理作業 (寫入)Storage account management operations (write) 每小時 200200 per hour
儲存體帳戶的管理作業 (清單)Storage account management operations (list) 每 5 分鐘 100100 per 5 minutes

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

資源Resource 目標Target
單一 blob 容器的大小上限Maximum size of single blob container 儲存體帳戶容量上限相同Same as maximum storage account capacity
最大數目的區塊中的區塊 blob 或附加 blobMaximum number of blocks in a block blob or append blob 50,000 個區塊50,000 blocks
中的區塊 blob 的區塊大小上限Maximum size of a block in a block blob 100 MiB100 MiB
區塊 blob 的大小上限Maximum size of a block blob 50,000 x 100 MiB (約為 4.75 TiB)50,000 X 100 MiB (approximately 4.75 TiB)
附加 blob 中的區塊大小上限Maximum size of a block in an append blob 4 MiB4 MiB
附加 blob 的大小上限Maximum size of an append blob 50,000 x 4 MiB (約為 195 GiB)50,000 x 4 MiB (approximately 195 GiB)
分頁 blob 的大小上限Maximum size of a page blob 8 TiB8 TiB
每個 blob 容器的預存的存取原則的最大數目Maximum number of stored access policies per blob container 55
單一 Blob 的目標輸送量Target throughput for single blob 儲存體帳戶輸入/輸出限制到1Up to storage account ingress/egress limits1

1單一物件輸送量取決於許多因素,包括但不是限於: 並行存取、 要求大小、 效能層級、 上傳來源和目的地,以下載的速度。1 Single object throughput depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. 若要善用高輸送量的區塊 blob效能增強功能,使用 Put Blob 或 Put Block 要求的大小 > 4 MiB (> 256 KiB premium 效能區塊 blob 儲存體或 Data Lake 儲存體 Gen2)。To take advantage of high-throughput block blob performance enhancements, use a Put Blob or Put Block request size of > 4 MiB (> 256 KiB for premium-performance block blob storage or for Data Lake Storage Gen2).

Azure 檔案的限制Azure Files limits

如需 Azure 檔案儲存體限制的詳細資訊, 請參閱Azure 檔案儲存體擴充性和效能目標For more information on Azure Files limits, see Azure Files scalability and performance targets.

資源Resource 標準檔案共用Standard file shares 進階檔案共用Premium file shares
檔案共用大小上限Minimum size of a file share 沒有最小值;預付No minimum; pay as you go 100 giB;佈建100 GiB; provisioned
檔案共用的大小上限Maximum size of a file share 5 TiB (GA)、 100 TiB (預覽)5 TiB (GA), 100 TiB (preview) 100 TiB100 TiB
檔案共用中的檔案大小上限Maximum size of a file in a file share 1 TiB1 TiB 1 TiB1 TiB
檔案共用中檔案的最大數目Maximum number of files in a file share 沒有限制No limit 沒有限制No limit
每個共用最大 IOPSMaximum IOPS per share 1000 IOPS (GA),10,000 IOPS (預覽)1,000 IOPS (GA), 10,000 IOPS (preview) 100,000 IOPS100,000 IOPS
每個檔案的預存的存取原則的最大數目的共用Maximum number of stored access policies per file share 55 55
單一檔案共用的目標輸送量Target throughput for a single file share 最多 60 MiB/秒 (GA),最多 300 MiB/秒 (預覽)Up to 60 MiB/sec (GA), up to 300 MiB/sec (preview) 請參閱進階檔案共用的輸入和輸出值See premium file share ingress and egress values
單一檔案共用的最大輸出Maximum egress for a single file share 請參閱標準檔案共用的目標輸送量See standard file share target throughput 最多 6,204 MiB/秒Up to 6,204 MiB/s
單一檔案共用的最大輸入Maximum ingress for a single file share 請參閱標準檔案共用的目標輸送量See standard file share target throughput 最多 4,136 MiB/秒Up to 4,136 MiB/s
每個檔案的開啟控制代碼數目上限Maximum open handles per file 2,000 個開啟控制代碼2,000 open handles 2,000 個開啟控制代碼2,000 open handles
共用快照集的數目上限Maximum number of share snapshots 200 個共用快照集200 share snapshots 200 個共用快照集200 share snapshots
物件 (目錄和檔案) 名稱長度上限Maximum object (directories and files) name length 2048 個字元2,048 characters 2048 個字元2,048 characters
最大路徑名稱元件 (在路徑 \A\B\C\D 中,每個字母都是元件)Maximum pathname component (in the path \A\B\C\D, each letter is a component) 255 個字元255 characters 255 個字元255 characters

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

ResourceResource 目標Target 固定限制Hard limit
每個區域的儲存體同步服務數目Storage Sync Services per region 20個儲存體同步服務20 Storage Sync Services Yes
每個儲存體同步服務的同步群組Sync groups per Storage Sync Service 100 個同步群組100 sync groups Yes
每個儲存體同步服務的已註冊伺服器Registered servers per Storage Sync Service 99 部伺服器99 servers Yes
每個同步群組的雲端端點Cloud endpoints per sync group 1 個雲端端點1 cloud endpoint Yes
每個同步群組的伺服器端點Server endpoints per sync group 50 個伺服器端點50 server endpoints No
每部伺服器的伺服器端點Server endpoints per server 30 個伺服器端點30 server endpoints Yes
每個同步群組的檔案系統物件 (目錄和檔案)File system objects (directories and files) per sync group 50000000物件50 million objects No
目錄中的檔案系統物件 (目錄和檔案) 數目上限Maximum number of file system objects (directories and files) in a directory 5000000物件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 64 KiB64 KiB Yes
並行同步處理工作階段Concurrent sync sessions V4 代理程式和更新版本:限制會根據可用的系統資源而有所不同。V4 agent and later: The limit varies based on available system resources.
V3 代理程式:每個處理器有兩個作用中的同步會話, 或每個伺服器最多八個作用中的同步會話。V3 agent: Two active sync sessions per processor or a maximum of eight active sync sessions per server.
Yes

注意

Azure 檔案同步端點可以相應增加至 Azure 檔案共用的大小。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 每秒,會假設 1 KiB 訊息大小 20,000 則訊息20,000 messages per second, which assumes a 1-KiB message size
單一佇列 (1 KiB 訊息) 的目標輸送量Target throughput for a single queue (1-KiB messages) 每秒最多 2,000 個訊息Up to 2,000 messages per second

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

資源Resource 目標Target
單一資料表的大小上限Maximum size of a single table 500 TiB500 TiB
資料表實體的大小上限Maximum size of a table entity 1 MiB1 MiB
資料表實體中屬性的最大數目Maximum number of properties in a table entity 255,其中包含三個系統屬性:PartitionKey、 RowKey 和 Timestamp255, which includes three system properties: PartitionKey, RowKey, and Timestamp
中實體的屬性值的總大小上限Maximum total size of property values in an entity 1 MiB1 MiB
實體中的個別屬性的總大小上限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.
每個資料表的預存的存取原則的最大數目Maximum number of stored access policies per table 55
每一儲存體帳戶的要求率上限Maximum request rate per storage account 20,000 每秒交易數,其中假設 1 KiB 實體大小20,000 transactions per second, which assumes a 1-KiB entity size
單一資料表分割區 (1 KiB 實體) 的目標輸送量Target throughput for a single table partition (1 KiB-entities) 每秒最多 2,000 個實體Up to 2,000 entities per second

虛擬機器磁碟限制Virtual machine disk limits

您可以將數個數據磁片連接到 Azure 虛擬機器。You can attach a number of data disks to an Azure virtual machine. 根據 VM 資料磁片的擴充性和效能目標, 您可以決定您需要的磁片數目和類型, 以符合您的效能和容量需求。Based on the scalability and performance targets for a VM's data disks, you can determine the number and type of disk that you need to meet your performance and capacity requirements.

重要

為達最佳效能,限制連結至虛擬機器的高度使用磁碟數目,以避免可能的節流。For optimal performance, limit the number of highly utilized disks attached to the virtual machine to avoid possible throttling. 如果所有連接的磁片不會同時高度使用, 則虛擬機器可以支援更多的磁片。If all attached disks aren't highly utilized at the same time, the virtual machine can support a larger number of disks.

針對 Azure 受控磁片:For Azure managed disks:

下表說明每個訂用帳戶每個區域的預設和最大資源數限制。The following table illustrates the default and maximum limits of the number of resources per region per subscription. 每個資源群組的受控磁碟、快照集和映射數目沒有限制。There is no limit for the number of Managed Disks, snapshots and images per resource group.

ResourceResource 預設限制Default limit 上限Maximum limit
標準受控磁碟Standard managed disks 50,00050,000 50,00050,000
標準 SSD 受控磁碟Standard SSD managed disks 50,00050,000 50,00050,000
進階受控磁碟Premium managed disks 50,00050,000 50,00050,000
Standard_LRS 快照集Standard_LRS snapshots 50,00050,000 50,00050,000
Standard_ZRS 快照集Standard_ZRS snapshots 50,00050,000 50,00050,000
受控映射Managed image 50,00050,000 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, 也就是每一磁片 20000/300 IOPS。For example, for a Basic tier VM, the maximum number of highly utilized disks is about 66, which is 20,000/300 IOPS per disk. 標準層 VM 的高度使用磁片數目上限大約是 40, 也就是每一磁片 20000/500 IOPS。The maximum number of highly utilized disks for a Standard tier VM is about 40, which is 20,000/500 IOPS per disk.

  • Premium 儲存體帳戶: Premium 儲存體帳戶的總輸送量速率上限為 50 Gbps。For Premium storage accounts: A Premium storage account has a maximum total throughput rate of 50 Gbps. 所有 VM 磁碟的總輸送量不應該超過此限。The total throughput across all of your VM disks should not exceed this limit.

如需詳細資訊, 請參閱虛擬機器大小For more information, see Virtual machine sizes.

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

標準的 HDD 受控磁碟

標準磁碟類型Standard Disk Type S4S4 S6S6 S10S10 S15S15 S20S20 S30S30 S40S40 S50S50 S60S60 S70S70 S80S80
磁碟大小 (以 GiB 為單位)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0964,096 8,1928,192 16,38416,384 32,76732,767
每一磁碟的 IOPSIOPS per disk 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最高 1,300Up to 1,300 最高 2,000Up to 2,000 最高 2,000Up to 2,000
每一磁碟的輸送量Throughput per disk 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 300 MiB/秒Up to 300 MiB/sec 最高 500 MiB/秒Up to 500 MiB/sec 最高 500 MiB/秒Up to 500 MiB/sec
Standard HDD managed disks
標準磁碟類型Standard Disk Type S4S4 S6S6 S10S10 S15S15 S20S20 S30S30 S40S40 S50S50 S60S60 S70S70 S80S80
磁碟大小 (以 GiB 為單位)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0964,096 8,1928,192 16,38416,384 32,76732,767
每一磁碟的 IOPSIOPS per disk 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最高 1,300Up to 1,300 最高 2,000Up to 2,000 最高 2,000Up to 2,000
每一磁碟的輸送量Throughput per disk 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 300 MiB/秒Up to 300 MiB/sec 最高 500 MiB/秒Up to 500 MiB/sec 最高 500 MiB/秒Up to 500 MiB/sec

SSD 標準受控磁碟

標準 SSD 的大小Standard SSD sizes E4E4 E6E6 E10E10 E15E15 E20E20 E30E30 E40E40 E50E50 E60E60 E70E70 E80E80
磁碟大小 (以 GiB 為單位)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0964,096 8,1928,192 16,38416,384 32,76732,767
每一磁碟的 IOPSIOPS per disk 最高 120Up to 120 最高 240Up to 240 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最高 2,000Up to 2,000 最多 4,000 個Up to 4,000 最多 6000Up to 6,000
每一磁碟的輸送量Throughput per disk 最高 25 MiB/秒Up to 25 MiB/sec 最高 50 MiB/秒Up to 50 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最多 400 個 MiB/秒Up to 400 MiB/sec 最多 600 MiB/秒Up to 600 MiB/sec 最高 750 MiB/秒Up to 750 MiB/sec
Standard SSD managed disks
標準 SSD 的大小Standard SSD sizes E4E4 E6E6 E10E10 E15E15 E20E20 E30E30 E40E40 E50E50 E60E60 E70E70 E80E80
磁碟大小 (以 GiB 為單位)Disk size in GiB 3232 6464 128128 256256 512512 1,0241,024 2,0482,048 4,0964,096 8,1928,192 16,38416,384 32,76732,767
每一磁碟的 IOPSIOPS per disk 最高 120Up to 120 最高 240Up to 240 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最多 500Up to 500 最高 2,000Up to 2,000 最多 4,000 個Up to 4,000 最多 6000Up to 6,000
每一磁碟的輸送量Throughput per disk 最高 25 MiB/秒Up to 25 MiB/sec 最高 50 MiB/秒Up to 50 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最高 60 MiB/秒Up to 60 MiB/sec 最多 400 個 MiB/秒Up to 400 MiB/sec 最多 600 MiB/秒Up to 600 MiB/sec 最高 750 MiB/秒Up to 750 MiB/sec

進階 SSD 受控磁碟:每個磁碟限制

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

進階 SSD 受控磁碟:每個 VM 限制Premium SSD managed disks: Per-VM limits

資源Resource 預設限制Default limit
每個 VM 的最大 IOPSMaximum IOPS Per VM 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
每個永續性磁碟的最大 8KB IOPSMaximum 8-KB IOPS per persistent disk 300300 500500
執行的最大 IOPS 的磁碟數目上限Maximum number of disks that perform the maximum IOPS 6666 4040

進階非受控的虛擬機器磁碟:每個帳戶限制Premium unmanaged virtual machine disks: Per-account limits

資源Resource 預設限制Default limit
每一帳戶的磁碟容量總計Total disk capacity per account 35 TB35 TB
每一帳戶的快照集容量總計Total snapshot capacity per account 10 TB10 TB
每個帳戶 (輸入 + 輸出) 的最大頻寬1Maximum bandwidth per account (ingress + egress)1 <=50 Gbps<=50 Gbps

1輸入是指傳送至儲存體帳戶的要求中的所有資料。1Ingress refers to all data from requests that are sent to a storage account. 輸出是指從儲存體帳戶中所收到的回應的所有資料。Egress refers to all data from responses that are received from a storage account.

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

進階儲存體磁碟類型Premium storage disk type P10P10 P20P20 P30P30 P40P40 P50P50
磁碟大小Disk size 128 GB128 GiB 512 GB512 GiB 1,024 giB (1 TB)1,024 GiB (1 TB) 2,048 giB (2 TB)2,048 GiB (2 TB) 4095 giB (4 TB)4,095 GiB (4 TB)
每個磁碟的最大 IOPSMaximum IOPS per disk 500500 2,3002,300 5,0005,000 7,5007,500 7,5007,500
每個磁碟的最大輸送量Maximum throughput per disk 100 MB/秒100 MB/sec 150 MB/秒150 MB/sec 200 MB/秒200 MB/sec 250 MB/秒250 MB/sec 250 MB/秒250 MB/sec
每個儲存體帳戶的磁碟數目上限Maximum number of disks per storage account 280280 7070 3535 1717 88

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

資源Resource 預設限制Default limit
每個 VM 的最大 IOPSMaximum IOPS per VM 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

Azure 雲端服務限制Azure Cloud Services limits

資源Resource 預設限制Default limit 上限Maximum limit
每個部署的 web 或背景工作角色1Web or worker roles per deployment1 2525 2525
執行個體輸入端點每個部署Instance input endpoints per deployment 2525 2525
輸入端點每個部署Input endpoints per deployment 2525 2525
內部端點每個部署Internal endpoints per deployment 2525 2525
每個部署的託管服務憑證Hosted service certificates per deployment 199199 199199

1與 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 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.

TypeType 限制Limit 範例Example
認知服務資源的混合A mixture of Cognitive Services resources 最多200認知服務資源總計。Maximum of 200 total Cognitive Services resources. 100電腦視覺美國西部的美國西部2、50語音服務資源中的資源, 以及50美國東部的文字分析資源。100 Computer Vision resources in West US 2, 50 Speech Service resources in West US, and 50 Text Analytics resources in East US.
單一類型的認知服務資源。A single type of Cognitive Services resources. 每個區域最多100個資源, 最大值為200認知服務資源總計。Maximum of 100 resources per region, with a maximum of 200 total Cognitive Services resources. 100電腦視覺在美國東部的美國西部2和100電腦視覺資源中的資源。100 Computer Vision resources in West US 2, and 100 Computer Vision resources in East US.

應用程式服務限制App Service limits

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

ResourceResource 免費Free 共用Shared 基本Basic 標準Standard 進階 (v2)Premium (v2) 隔離式方案Isolated
每個Azure App Service 方案1Web、行動或 API 應用程式Web, 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 20 個專用320 dedicated3 100 個專用4100 dedicated4
儲存體5Storage5 1 GB51 GB5 1 GB51 GB5 10 GB510 GB5 50 GB550 GB5 250 GB5250 GB5

1 TB51 TB5
CPU 時間 (5 分鐘)6CPU time (5 minutes)6 3 分鐘3 minutes 3 分鐘3 minutes 無限制,以標準費率付費Unlimited, pay at standard rates 無限制,以標準費率付費Unlimited, pay at standard rates 無限制,以標準費率付費Unlimited, pay at standard rates 無限制,以標準費率付費Unlimited, pay at standard rates
CPU 時間 (天)6CPU time (day)6 60 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) 1024 MB/App Service 方案1,024 MB per App Service plan 每個應用程式 1024 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
並行 偵錯工具連接數 (每個應用程式)Concurrent debugger connections per application 11 11 11 55 55 55
App Service 每個訂用帳戶的憑證10App Service Certificates per subscription10 不支援Not supported 不支援Not supported 1010 1010 1010 1010
每個應用程式的自訂網域Custom domains per app 0 (僅限 azurewebsites.net 子網域)0 (azurewebsites.net subdomain only) 500500 500500 500500 500500 500500
自訂網域 SSL 支援Custom domain SSL support 不支援, 預設會提供 *. azurewebsites.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
整合式負載平衡器Integrated load balancer XX XX XX XX X9X9
永遠開啟Always On XX XX XX XX
排定的備份Scheduled backups 排定的備份每隔2小時, 最多每日12次備份 (手動 + 排程)Scheduled backups every 2 hours, a maximum of 12 backups per day (manual + scheduled) 排定的備份每小時, 最多每天50備份 (手動 + 排程)Scheduled backups every hour, a maximum of 50 backups per day (manual + scheduled) 排定的備份每小時, 最多每天50備份 (手動 + 排程)Scheduled backups every hour, a maximum of 50 backups per day (manual + scheduled)
AutoscaleAutoscale XX XX XX
WebJobs8WebJobs8 XX XX XX XX XX XX
Azure 排程器 支援Azure Scheduler support XX XX XX XX XX
端點監視Endpoint monitoring XX XX XX XX
預備位置Staging slots 55 2020 2020
SLASLA 99.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.
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 7500、每中型 VM 15000 (7500 x 2 核心) 和每個大型 VM 75000 (18750 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).
8在您的 App Service 執行個體中,以背景工作的方式隨選、依照排程或連續執行自訂可執行檔和/或指令碼。8Run 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. 若是排程 WebJobs,則 Azure 排程器免費或標準版本是必要項目。Azure Scheduler Free or Standard is required for scheduled WebJobs. 在 App Service 實例中可執行檔 Webjob 數目沒有預先定義的限制。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.
9App Service 隔離式方案 Sku 可以透過 Azure Load Balancer 進行內部負載平衡 (ILB), 因此沒有網際網路的公用連線能力。9App 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.
10每個訂用帳戶的 App Service 憑證配額限制可以透過支援要求增加為200的最大限制。10The App Service Certificate quota limit per subscription can be increased via a support request to a maximum limit of 200.

函數限制Functions limits

ResourceResource 耗用量方案Consumption plan Premium 方案Premium plan App Service 計畫1App Service plan1
相應放大Scale out 事件驅動Event driven 事件驅動Event driven 手動/自動調整Manual/autoscale
執行個體數上限Max instances 200200 2020 10-2010-20
預設超時時間 (分鐘)Default time out duration (min) 55 3030 302302
最大時間輸出持續時間(分鐘)Max time out duration (min) 1010 無限制unbounded 無界限3unbounded3
最大輸出連線數 (每個實例)Max outbound connections (per instance) 600作用中 (1200 總計)600 active (1200 total) 無限制unbounded 無限制unbounded
要求大小上限 (MB)4Max request size (MB)4 100100 100100 100100
最大查詢字串長度4Max query string length4 40964096 40964096 40964096
要求 URL 長度上限4Max request URL length4 81928192 81928192 81928192
每個實例的ACUACU per instance 100100 210-840210-840 100-840100-840
最大記憶體 (每個實例 GB)Max memory (GB per instance) 1.51.5 3.5-143.5-14 1.75-141.75-14
每個方案的函數應用程式Function apps per plan 100100 100100 無界限5unbounded5
App Service 方案App Service plans 每個區域100100 per region 每個資源群組 100 個100 per resource group 每個資源群組 100 個100 per resource group
儲存體6Storage6 1 GB1 GB 250 GB250 GB 50-1000 GB50-1000 GB
每個應用程式的自訂網域Custom domains per app 50075007 500500 500500
自訂網域 SSL 支援Custom domain SSL support 包含未系結的 SNI SSL 連線unbounded SNI SSL connection included 包含未系結的 SNI SSL 和1個 IP SSL 連線unbounded SNI SSL and 1 IP SSL connections included 包含未系結的 SNI SSL 和1個 IP SSL 連線unbounded SNI SSL and 1 IP SSL connections included

1如需各種 App Service 計畫選項的特定限制, 請參閱App Service 方案限制1 For specific limits for the various App Service plan options, see the App Service plan limits.
2根據預設, App Service 計畫中的函式1.x 執行時間的超時不受限制。2 By default, the timeout for the Functions 1.x runtime in an App Service plan is unbounded.
3要求 App Service 計畫必須設定為Always On3 Requires the App Service plan be set to Always On. 以標準費率付費。Pay at standard rates.
4 主機中設定了這些限制。4 These limits are set in the host.
5您可以裝載的函式應用程式實際數目, 取決於應用程式的活動、電腦實例的大小, 以及對應的資源使用率。5 The actual number of function apps that you can host depends on the activity of the apps, the size of the machine instances, and the corresponding resource utilization.
6儲存限制是相同 App Service 方案中所有應用程式的暫存儲存體中的總內容大小。6 The storage limit is the total content size in temporary storage across all apps in the same App Service plan. 取用方案會使用 Azure 檔案儲存體暫存儲存體。Consumption plan uses Azure Files for temporary storage.
7當您的函數應用程式裝載于取用方案時, 只支援 CNAME 選項。7 When your function app is hosted in a Consumption plan, only the CNAME option is supported. 針對高階方案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.

排程器限制Scheduler limits

下表描述 Azure 排程器中的每一個主要配額、限制、預設值和節流。The following table describes each of the major quotas, limits, defaults, and throttles in Azure Scheduler.

資源Resource 限制說明Limit description
工作大小Job size 工作大小上限是 16,000。The maximum job size is 16,000. 如果 PUT 或 PATCH 作業導致大於此限制的作業大小,則會傳回「400 不正確的要求」狀態碼。If a PUT or a PATCH operation results in a job size larger than this limit, a 400 Bad Request status code is returned.
作業集合Job collections 每一 Azure 訂用帳戶的作業集合數目上限是 200,000 個。The maximum number of job collections per Azure subscription is 200,000.
每個集合的工作數Jobs per collection 根據預設,免費作業集合中的作業數目上限是 5 個,而標準作業集合中是 50 個作業。By default, the maximum number of jobs is five jobs in a free job collection and 50 jobs in a standard job collection.

您可以變更作業集合上的作業數目上限。You can change the maximum number of jobs on a job collection. 作業集合中的所有作業都限制為作業集合上設定的值。All jobs in a job collection are limited to the value set on the job collection. 如果您嘗試建立的作業數超過最大作業配額,則要求會失敗,並顯示「409 衝突」狀態碼。If you attempt to create more jobs than the maximum jobs quota, the request fails with a 409 Conflict status code.

開始時間Time to start time 「開始時間」上限為 18 個月。The maximum "time to start time" is 18 months.
週期範圍Recurrence span 週期範圍上限為 18 個月。The maximum recurrence span is 18 months.
頻率Frequency 根據預設,免費作業集合中的最大週期配額是一小時,而標準作業集合中是一分鐘。By default, the maximum frequency quota is one hour in a free job collection and one minute in a standard job collection.

您可以將作業集合上的最大頻率設定成低於該上限。You can make the maximum frequency on a job collection lower than the maximum. 作業集合中的所有作業都限制為作業集合上設定的值。All jobs in the job collection are limited to the value set on the job collection. 如果您嘗試在作業集合上建立頻率高於最大頻率的作業,則要求會失敗,並顯示「409 衝突」狀態碼。If you attempt to create a job with a higher frequency than the maximum frequency on the job collection, the request fails with a 409 Conflict status code.

內文大小Body size 要求的最大的主體大小會為 8192 個字元。The maximum body size for a request is 8,192 chars.
要求 URL 大小Request URL size 要求 URL 最大大小為 2048 個字元。The maximum size for a request URL is 2,048 chars.
標頭計數Header count 標頭計數上限為 50 個標頭。The maximum header count is 50 headers.
彙總標頭大小Aggregate header size 最大的彙總標頭大小為 4096 個字元。The maximum aggregate header size is 4,096 chars.
逾時Timeout 要求逾時是靜態的也就是無法設定。The request timeout is static, that is, not configurable. 而是 HTTP 動作的 60 秒。and is 60 seconds for HTTP actions. 對於執行時間較長的作業,請依照 HTTP 非同步通訊協定來操作。For longer running operations, follow the HTTP asynchronous protocols. 例如,立即傳回 202 但是在背景繼續工作。For example, return a 202 immediately but continue working in the background.
工作歷程記錄Job history 工作歷程記錄中儲存的最大的回應主體是 2,048 個位元組。The maximum response body stored in job history is 2,048 bytes.
保留工作歷程記錄Job history retention 保留最多兩個月或高達最後 1,000 個執行的作業歷程記錄。Job history is kept for up to two months or up to the last 1,000 executions.
保留已完成和發生錯誤的工作Completed and faulted job retention 已完成與發生錯誤的作業會保留 60 天。Completed and faulted jobs are kept for 60 days.

Batch 限制Batch limits

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
Active 作業和作業排程,每個 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

注意

預設限制會根據您用來建立 Batch 帳戶的訂用帳戶類型而有所不同。Default limits vary depending on the type of subscription you use to create a Batch account. 所顯示的核心配額是針對 Batch 服務模式中的 Batch 帳戶。Cores quotas shown are for Batch accounts in Batch service mode. 檢視您 Batch 帳戶中的配額View the quotas in your Batch account.

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

BizTalk 服務限制BizTalk Services limits

下表顯示 Azure BizTalk 服務的限制。The following table shows the limits for Azure BizTalk Services.

資源Resource 免費 (預覽)Free (Preview) 開發人員Developer 基本Basic 標準Standard 進階Premium
相應放大Scale out N/AN/A N/AN/A 是,增加 1 個基本單位Yes, in increments of 1 Basic unit 是,增加 1 個標準單位Yes, in increments of 1 Standard unit 是,增加 1 個高級單位Yes, in increments of 1 Premium unit
調整限制Scale limit N/AN/A N/AN/A 最多 8 個單位Up to 8 units 最多 8 個單位Up to 8 units 最多 8 個單位Up to 8 units
每個單位的 EAI 橋接器EAI bridges per unit N/AN/A 2525 2525 125125 500500
每一單位 EDI 合約EDI agreements per unit N/AN/A 1010 5050 250250 1,0001,000
每個單位的混合式連線Hybrid connections per unit 55 55 1010 5050 100100
混合式連接資料傳輸 (Gb) 每個單位Hybrid connection data transfer (GBs) per unit 55 55 5050 250250 500500
每個單位使用 BizTalk Adapter 服務的連線數目Number of connections that use BizTalk Adapter Service per unit N/AN/A 11 22 55 2525
封存Archiving N/AN/A 可用Available N/AN/A N/AN/A 可用Available
高可用性High availability N/AN/A N/AN/A 可用Available 可用Available 可用Available

Azure Cosmos DB 限制Azure Cosmos DB limits

如 Azure Cosmos DB 限制, 請參閱Azure Cosmos DB 的限制For Azure Cosmos DB limits, see Limits in Azure Cosmos DB.

適用於 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 搜尋服務限制Azure Search limits

定價層會決定搜尋服務的容量和限制。Pricing tiers determine the capacity and limits of your search service. 層級包括:Tiers include:

  • 免費的多租使用者服務, 與其他 Azure 訂閱者共用, 適用于評估和小型開發專案。Free multitenant service, shared with other Azure subscribers, is intended for evaluation and small development projects.
  • 可針對規模較小的生產工作負載提供專用的計算資源,以及針對高可用性的查詢工作負載提供最多 3 個複本。Basic provides dedicated computing resources for production workloads at a smaller scale, with up to three replicas for highly available query workloads.
  • 標準(包括 S1、S2、S3 及 s3 高密度) 適用于較大型的生產工作負載。Standard, which includes S1, S2, S3, and S3 High Density, is for larger production workloads. 標準層中有多個層級, 因此您可以選擇最符合您工作負載設定檔的資源設定。Multiple levels exist within the Standard tier so that you can choose a resource configuration that best matches your workload profile.

每一訂用帳戶的限制Limits per subscription

您可以建立多個訂用帳戶內的服務。You can create multiple services within a subscription. 每一個可以佈建於特定層。Each one can be provisioned at a specific tier. 您受限於只允許每一層的服務數目。You're limited only by the number of services allowed at each tier. 例如,您最多可在基本層建立 12 個服務,並在同一個訂用帳戶內的 S1 層另外建立 12 個服務。For example, you could create up to 12 services at the Basic tier and another 12 services at the S1 tier within the same subscription. 如需各層的詳細資訊,請參閱選擇 Azure 搜尋服務的 SKU 或階層For more information about tiers, see Choose an SKU or tier for Azure Search.

最大服務限制可以視要求引發。Maximum service limits can be raised upon request. 如果您需要更多服務相同的訂用帳戶,請連絡 Azure 支援。If you need more services within the same subscription, contact Azure Support.

資源Resource 免費1Free1 基本Basic S1S1 S2S2 S3S3 S3 HDS3 HD L1L1 L2L2
服務數目上限Maximum services 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

儲存體受限於磁碟空間,或者索引、文件或其他高層級資源的「數目上限」 ,取決於何者較早出現。Storage is constrained by disk space or by a hard limit on the maximum number of indexes, document, or other high-level resources, whichever comes first. 下表記載儲存體限制。The following table documents storage limits. 如需索引、 文件和其他物件的最大限制,請參閱資源限制For maximum limits on indexes, documents, and other objects, see Limits by resource.

資源Resource 免費Free 基本1Basic1 S1S1 S2S2 S3S3 S3 HD2S3 HD2 L1L1 L2L2
服務等級協定 (SLA)3Service level agreement (SLA)3 No yesYes 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. 在這一層,額外搜尋單位可增加的查詢工作負載配置更多複本。At this tier, additional search units are used for allocating more replicas for increased query workloads.

2 S3 HD 上有固定限制的三個資料分割,低於 S3 的分割區限制。2 S3 HD has a hard limit of three partitions, which is lower than the partition limit for S3. 較低的分割區限制是因為 S3 HD 的索引計數較高。The lower partition limit is imposed because the index count for S3 HD is substantially higher. 假設計算資源 (儲存體和處理) 和內容 (索引和文件) 的服務限制都存在,會先達到內容限制。Given that service limits exist for both computing resources (storage and processing) and content (indexes and documents), the content limit is reached first.

3服務等級協定會提供專用資源上的可計費服務。3 Service level agreements are offered for billable services on dedicated resources. 免費服務和預覽功能不提供 SLA。Free services and preview features have no SLA. 對於可計費服務,SLA 會在您為您的服務佈建足夠的備援性時生效。For billable services, SLAs take effect when you provision sufficient redundancy for your service. 兩個或多個複本所需查詢 (讀取) Sla。Two or more replicas are required for query (read) SLAs. 三個或多個複本所需查詢和檢索 (讀 / 寫) Sla。Three or more replicas are required for query and indexing (read-write) SLAs. 資料分割數目並不是 SLA 考量。The number of partitions isn't an SLA consideration.

若要深入了解更細微的限制,例如文件大小、每秒的查詢數、金鑰、要求和回應,請參閱 Azure 搜尋服務的服務限制To learn more about limits on a more granular level, such as document size, queries per second, keys, requests, and responses, see Service limits in Azure Search.

媒體服務限制Media Services limits

注意

如需不固定的資源,開啟支援票證以要求增加配額。For resources that aren't fixed, open a support ticket to ask for an increase in the quotas. 請勿建立其他的 Azure 媒體服務帳戶在嘗試取得較高的限制。Don't create additional Azure Media Services accounts in an attempt to obtain higher limits.

資源Resource 預設限制Default limit
單一訂用帳戶中的 azure 媒體服務帳戶Azure Media Services accounts in a single subscription 25 (固定)25 (fixed)
媒體保留單元,每個媒體服務帳戶Media reserved units per Media Services account 25 (S1)25 (S1)
10 (S2, S3)110 (S2, S3)1
每個媒體服務帳戶的工作Jobs per Media Services account 50,000250,0002
每個作業的鏈結工作Chained tasks per job 30 (固定)30 (fixed)
每個媒體服務帳戶的資產Assets per Media Services account 1,000,0001,000,000
每個工作的資產Assets per task 5050
每個作業的資產Assets per job 100100
一次與資產相關聯的唯一定位器Unique locators associated with an asset at one time 5454
每個媒體服務帳戶的直播頻道Live channels per Media Services account 55
每個通道中已停止狀態的程式Programs in stopped state per channel 5050
每個通道中執行中的程式Programs in running state per channel 33
串流端點已停止,或執行每個媒體服務帳戶Streaming endpoints that are stopped or running per Media Services account 22
每個串流端點的資料流單位Streaming units per streaming endpoint 1010
儲存體帳戶Storage accounts 1,0005 (fixed)1,0005 (fixed)
policiesPolicies 1,000,00061,000,0006
檔案大小File size 在某些情況下,沒有限制對於媒體服務中支援處理的最大檔案大小。7In some scenarios, there's a limit on the maximum file size supported for processing in Media Services.7

1如果您變更類型,例如從 S2 到 S1,保留的單元最大值限制會重設。1If you change the type, for example, from S2 to S1, the maximum reserved unit limits are reset.

2這個數目包括佇列、 完成、 作用中和已取消的作業。2This number includes queued, finished, active, and canceled jobs. 它不包含已刪除的工作。It doesn't include deleted jobs. 您可以使用,以刪除舊工作IJob.Delete刪除HTTP 要求。You can delete old jobs by using IJob.Delete or the DELETE HTTP request.

截至 2017 年 4 月 1 日起,任何超過 90 天您帳戶中的作業記錄會自動刪除,以及其相關聯的工作記錄。As of April 1, 2017, any job record in your account older than 90 days is automatically deleted, along with its associated task records. 即使記錄總數低於配額上限,就會發生自動刪除。Automatic deletion occurs even if the total number of records is below the maximum quota. 若要封存的作業和工作的資訊,請使用 程式碼中所述使用媒體服務.NET SDK 管理資產To archive the job and task information, use the code described in Manage assets with the Media Services .NET SDK.

3要求清單作業實體時,最多 1000 個作業會傳回每個要求。3When you make a request to list job entities, a maximum of 1,000 jobs is returned per request. 要追蹤的所有提交的作業,使用 top 或略過查詢中所述OData 系統查詢選項To keep track of all submitted jobs, use the top or skip queries as described in OData system query options.

4定位器不設計來管理每位使用者存取控制。4Locators aren't designed for managing per-user access control. 若要給予個別使用者不同的存取權限,請使用數位版權管理 (DRM) 解決方案。To give different access rights to individual users, use digital rights management (DRM) solutions. 如需詳細資訊,請參閱 < 使用 Azure Media Services 保護內容For more information, see Protect your content with Azure Media Services.

5的儲存體帳戶必須是相同的 Azure 訂用帳戶。5The storage accounts must be from the same Azure subscription.

6對於不同的媒體服務原則的 1,000,000 個原則的限制。6There's a limit of 1,000,000 policies for different Media Services policies. 範例是針對 Locator 原則或 ContentKeyAuthorizationPolicy。An example is for the Locator policy or ContentKeyAuthorizationPolicy.

注意

如果您一律使用相同的天數和存取權限,使用相同的原則識別碼。If you always use the same days and access permissions, use the same policy ID. 資訊和範例,請參閱使用媒體服務.NET SDK 管理資產For information and an example, see Manage assets with the Media Services .NET SDK.

7支援單一 blob 目前是 Azure Blob 儲存體最多 5 TB 的大小上限。7The maximum size supported for a single blob is currently up to 5 TB in Azure Blob Storage. 其他的限制適用於服務所使用的 VM 大小所根據的媒體服務中。Additional limits apply in Media Services based on the VM sizes that are used by the service. 大小限制適用於您上傳的檔案,也因為媒體服務處理 (編碼或分析) 而產生的檔案。The size limit applies to the files that you upload and also the files that get generated as a result of Media Services processing (encoding or analyzing). 如果原始程式檔超過 260 GB,您的工作可能會失敗。If your source file is larger than 260-GB, your Job will likely fail.

下表會顯示上媒體保留單位 S1、 S2 和 S3 的限制。The following table shows the limits on the media reserved units S1, S2, and S3. 如果您的來源檔案大於資料表中定義的限制,編碼作業將會失敗。If your source file is larger than the limits defined in the table, your encoding job fails. 如果編碼的持續時間較長的 4k 解析來源,您會需要使用 S3 媒體保留單元,以達到所需的效能。If you encode 4K resolution sources of long duration, you're required to use S3 media reserved units to achieve the performance needed. 如果您有 4k 內容超過 S3 媒體保留單元的 260 GB 限制,與我們連絡amshelp@microsoft.com取得潛在防護功能,以支援您的案例。If you have 4K content that's larger than the 260-GB limit on the S3 media reserved units, contact us at amshelp@microsoft.com for potential mitigations to support your scenario.

媒體保留單元類型Media reserved unit type 輸入的大小的上限 (GB)Maximum input size (GB)
S1S1 2626
S2S2 6060
S3S3 260260

內容傳遞網路限制Content Delivery Network limits

資源Resource 預設限制Default limit
Azure 內容傳遞網路設定檔Azure Content Delivery Network profiles 2525
每個設定檔的內容傳遞網路端點Content Delivery Network endpoints per profile 2525
每個端點的自訂網域Custom domains per endpoint 2525

內容傳遞網路的訂用帳戶可以包含一或多個內容傳遞網路設定檔。A Content Delivery Network subscription can contain one or more Content Delivery Network profiles. 內容傳遞網路設定檔可以包含一或多個內容傳遞網路端點。A Content Delivery Network profile can contain one or more Content Delivery Network endpoints. 您可能想要使用多個設定檔來組織您的內容傳遞網路端點依網際網路網域、 web 應用程式或其他準則。You might want to use multiple profiles to organize your Content Delivery Network endpoints by internet domain, web application, or some other criteria.

行動服務限制Mobile Services limits

Tier 免費Free 基本Basic 標準Standard
API 呼叫API calls 500,000500,000 1.5 億,每個單位1.5 million per unit 每個單位的 15 萬15 million per unit
作用中裝置Active devices 500500 無限Unlimited 無限Unlimited
調整Scale N/AN/A 最多 6 個單位Up to 6 units 無單位限制Unlimited units
推播通知Push notifications Azure 通知中樞免費層包含,最多 1 百萬次推播Azure Notification Hubs Free tier included, up to 1 million pushes 包含通知中樞基本層,最多 10 萬個推播Notification Hubs Basic tier included, up to 10 million pushes 包含通知中樞標準層,最多 10 萬個推播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 MB165 MB per day (daily rollover) 已包括Included 已包括Included

如需有關限制和定價的詳細資訊,請參閱 < Azure 行動服務定價For more information on limits and pricing, see Azure Mobile Services 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 1000 使用中的警示規則每個訂用帳戶 (在公用雲端中) 和每個訂用帳戶中 Azure 中國 21Vianet 和 Azure Government 的 100 個作用中警示規則。1000 active alert rules per subscription (in public clouds) and 100 active alert rules per subscription in Azure China 21Vianet and Azure Government. 請連絡支援人員。Call support.
活動記錄警示Activity log alerts 100 個作用中警示規則每訂用帳戶。100 active alert rules per subscription. 預設值相同。Same as default.
記錄警示Log alerts 512512 請連絡支援人員。Call support.
動作群組Action groups 2,000 動作群組,每個訂用帳戶。2,000 action groups per subscription. 請連絡支援人員。Call support.
自動調整設定Autoscale settings 訂用帳戶每區域每 100 個。100 per region per subscription. 預設值相同。Same as default.

動作群組Action groups

資源Resource 預設限制Default limit 上限Maximum limit
Azure 應用程式推送Azure app push 每個動作群組的 10 個 azure 應用程式動作。10 Azure app actions per action group. 請連絡支援人員。Call support.
EmailEmail 在 動作群組的電子郵件動作 1,000。1,000 email actions in an action group.
一小時內不超過 100 個電子郵件。No more than 100 emails in an hour.
另請參閱速率限制資訊Also see the rate limiting information.
請連絡支援人員。Call support.
ITSMITSM 在 動作群組中的 10 個 ITSM 動作。10 ITSM actions in an action group. 請連絡支援人員。Call support.
邏輯應用程式Logic app 在 動作群組中的 10 個邏輯應用程式動作。10 logic app actions in an action group. 請連絡支援人員。Call support.
RunbookRunbook 在 動作群組中的 10 個 runbook 動作。10 runbook actions in an action group. 請連絡支援人員。Call support.
smsSMS 在 動作群組中的 10 個簡訊動作。10 SMS actions in an action group.
不超過 1 的 SMS 訊息每隔 5 分鐘。No more than 1 SMS message every 5 minutes.
另請參閱速率限制資訊Also see the rate limiting information.
請連絡支援人員。Call support.
語音Voice 在 動作群組中的 10 個語音動作。10 voice actions in an action group.
不超過 1 的語音通話每隔 5 分鐘。No more than 1 voice call every 5 minutes.
另請參閱速率限制資訊Also see the rate limiting information.
請連絡支援人員。Call support.
WebhookWebhook 在 動作群組中的 10 個 webhook 動作。10 webhook actions in an action group. Webhook 呼叫的數目上限是 1500 每分鐘每個訂用帳戶。Maximum number of webhook calls is 1500 per minute per subscription. 其他限制位於動作特有的資訊Other limits are available at action-specific information. 請連絡支援人員。Call support.

記錄查詢和語言Log queries and language

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

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. 請注意,Azure 資訊安全中心所收集的資料不包含在每一天的限制此 500 MB,而且將會繼續收集超過此限制。Note that data collected by Azure Security Center is not included in this 500 MB per day limit and will continue to be collected above this limit.
舊版的 「 獨立每 GB 」 層Legacy Standalone Per GB tier
(引進 2016 年 4 月)(introduced April 2016)
沒有限制No limit 30 至 730 天30 to 730 days 超過 31 天的資料保留期可供其他費用。Data retention beyond 31 days is available for additional charges. 深入了解 Azure 監視器定價。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

CategoryCategory 限制Limits 註解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

CategoryCategory 限制Limits 註解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

CategoryCategory 限制Limits 註解Comments
傳回非彙總資料的最大記錄Maximum records returned for non-aggregated data 5,0005,000
彙總資料的最大資料錄Maximum records for aggregated data 500,000500,000 彙總的資料是包含搜尋summarize命令。Aggregated data is a search that includes the summarize command.
傳回的資料大小上限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 每 30 秒,每個 AAD 使用者或用戶端 IP 位址的 200 個要求200 requests per 30 seconds per AAD user or client IP address 請參閱速率限制如需詳細資訊。See Rate limits for details.

一般的工作區限制General workspace limits

CategoryCategory 限制Limits 註解Comments
在資料表中的最大資料行Maximum columns in a table 500500
資料行名稱的字元數上限Maximum characters for column name 500500
在容量的區域Regions at capacity 美國中西部West Central US 您目前無法建立這個區域中新的工作區,因為它是暫存的容量限制。You cannot currently create a new workspace in this region since it is at temporary capacity limit. 這項限制已規劃於 2019 年 9 月日結束處理。This limit is planned to be addressed by end of September, 2019.
匯出資料Data export 目前無法使用Not currently available 彙總,並將資料匯出至使用 Azure 函式或邏輯應用程式。Use Azure Function or Logic App to aggregate and export data.

注意

根據多久您已使用 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 預設限制Default limit 附註Note
每日資料總量Total data per day 100 GB100 GB 您可以設定上限來減少資料。You can reduce data by setting a cap. 如果您需要更多資料,可以從入口網站將限制增加到最多 1,000 GB。If you need more data, you can increase the limit in the portal, up to 1,000 GB. 容量大於 1,000 GB,傳送電子郵件至AIDataCap@microsoft.com。For capacities greater than 1,000 GB, send email to AIDataCap@microsoft.com.
節流Throttling 32,000 個事件/秒32,000 events/second 此限制會測量超過一分鐘。The limit is measured over a minute.
資料保留Data retention 90 天90 days 此資源適用於搜尋分析計量瀏覽器This resource is for Search, Analytics, and Metrics Explorer.
可用性多步驟測試詳述的結果保留期Availability multi-step test detailed results retention 90 天90 days 此資源會提供每個步驟的詳細結果。This resource provides detailed results of each step.
事件大小上限Maximum event size 64,00064,000
屬性和度量名稱長度Property and metric name length 150150 請參閱類型結構描述See type schemas.
屬性值字串長度Property value string length 8,1928,192 請參閱類型結構描述See type schemas.
追蹤和例外狀況訊息長度Trace and exception message length 32,76832,768 請參閱類型結構描述See type schemas.
每個應用程式的可用性測試計數Availability tests count per app 100100
分析工具資料保留期Profiler data retention 5 天5 days
每天傳送的分析工具資料Profiler data sent per day 10 GB10 GB

如需詳細資訊,請參閱關於 Application Insights 中的價格和配額For more information, see About pricing and quotas in Application Insights.

通知中樞限制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.

事件中樞限制Event Hubs limits

下表列出 Azure 事件中樞的特定配額與限制。The following table lists quotas and limits specific to Azure Event Hubs. 如需事件中樞價格的相關資訊,請參閱事件中樞價格For information about Event Hubs pricing, see Event Hubs pricing.

限制Limit ScopeScope 注意Notes Value
每一訂用帳戶的「事件中樞」命名空間數目Number of Event Hubs namespaces per subscription 訂閱Subscription - 100100
每個命名空間的事件中樞數目Number of event hubs per namespace 命名空間Namespace 建立新事件中樞的後續要求會遭到拒絕。Subsequent requests for creation of a new event hub are rejected. 1010
事件中樞內的資料分割數目Number of partitions per event hub 實體Entity - 3232
事件中樞事件的大小上限Maximum size of Event Hubs event 實體Entity - 1 MB1 MB
事件中樞名稱的大小上限Maximum size of an event hub name 實體Entity - 50 個字元50 characters
每個取用者群組的非 epoch 接收者數目Number of non-epoch receivers per consumer group 實體Entity - 55
最大輸送量單位Maximum throughput units 命名空間Namespace 超過輸送量單位限制會導致您的資料受到節流, 並產生伺服器忙碌的例外狀況。Exceeding the throughput unit limit causes your data to be throttled and generates a server busy exception. 若要為標準層要求大量的輸送量單位, 請提出支援要求To request a larger number of throughput units for a Standard tier, file a support request. 更多輸送量單位依承諾購買方式,以 20 個為一組來取得。Additional throughput units are available in blocks of 20 on a committed purchase basis. 2020
每個命名空間的授權規則數目Number of authorization rules per namespace 命名空間Namespace 授權規則建立的後續要求會遭到拒絕。Subsequent requests for authorization rule creation are rejected. 1212
GetRuntimeInformation 方法的呼叫次數Number of calls to the GetRuntimeInformation method 實體Entity - 每秒5050 per second
虛擬網路 (VNet) 和 IP 設定規則的數目Number of virtual network (VNet) and IP Config rules 實體Entity - 128128

事件中樞基本和標準-配額和限制Event Hubs Basic and Standard - quotas and limits

限制Limit ScopeScope 注意Notes 基本Basic 標準Standard
每一個事件中樞取用者群組數目Number of consumer groups per event hub 實體Entity - 11 2020
每個命名空間的 AMQP 連線數目Number of AMQP connections per namespace 命名空間Namespace 後續的其他連接要求會遭到拒絕, 而且呼叫程式碼會收到例外狀況。Subsequent requests for additional connections are rejected, and an exception is received by the calling code. 100100 5,0005,000
事件資料的最大保留期間Maximum retention period of event data 實體Entity - 1 天1 day 1-7 天1-7 days
已啟用 Apache Kafka 的命名空間Apache Kafka enabled namespace 命名空間Namespace 使用 Kafka 通訊協定事件中樞命名空間串流應用程式Event Hubs namespace streams applications using Kafka protocol No Yes
擷取Capture 實體Entity 啟用時, 相同資料流程上的微批次When enabled, micro-batches on the same stream No Yes

事件中樞專用-配額和限制Event Hubs Dedicated - quotas and limits

事件中樞專用供應專案以固定的每月價格計費, 最低使用量為4小時。The Event Hubs Dedicated offering is billed at a fixed monthly price, with a minimum of 4 hours of usage. 專用層提供標準方案的所有功能, 但具備企業級的容量和限制, 可滿足具有工作負載需求的客戶。The Dedicated tier offers all the features of the Standard plan, but with enterprise scale capacity and limits for customers with demanding workloads.

功能Feature 限制Limits
頻寬Bandwidth 20 Cu20 CUs
命名空間Namespaces 50/CU50 per CU
事件中樞Event Hubs 1000每個命名空間1000 per namespace
輸入事件Ingress events 內含Included
訊息大小Message Size 1000000個位元組1 Million Bytes
分割區Partitions 2000/CU2000 per CU
取用者群組Consumer groups 每個事件中樞不會有每個 CU 的限制 (1000)No limit per CU, 1000 per event hub
代理連線Brokered connections 包含 10 萬個100 K included
訊息保留期Message Retention 最多7天 (即將推出90天保留期), 每個 CU 包含 10 TBUp to 7 days (90 day retention coming soon), 10 TB included per CU
擷取Capture 內含Included

服務匯流排限制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 ScopeScope 注意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 訂用帳戶的 Premium 命名空間數目上限Maximum number of Premium namespaces per Azure subscription 命名空間Namespace 入口網站會拒絕後續對其他 Premium 命名空間的要求。Subsequent requests for additional Premium namespaces are rejected by the portal. 5050
佇列或主題大小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.

在 Premium SKU 和啟用分割的標準 SKU 中, 佇列或主題大小上限為 80 GB。In the Premium SKU, and the Standard SKU with partitioning enabled, the maximum queue or topic size is 80 GB.
命名空間上的並行連線數目Number of concurrent connections on a namespace 命名空間Namespace 後續的其他連接要求會遭到拒絕, 而且呼叫程式碼會收到例外狀況。Subsequent requests for additional connections are rejected, and an exception is received by the calling code. REST 作業不會計入並行 TCP 連線。REST operations don't count toward concurrent TCP connections. NetMessaging:1000。NetMessaging: 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 進行呼叫, 則呼叫程式碼會收到例外狀況QuotaExceededExceptionIf 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。 Int32.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 會產生例外狀況SerializationExceptionThe 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的整個標頭, 其中同時包含使用者屬性和系統屬性, 例如SequenceNumberLabelMessageIdThis limit applies to the entire header of the BrokeredMessage, which has both user properties and system properties, such as SequenceNumber, Label, and MessageId.
每個主題的訂用帳戶數目Number of subscriptions per topic 實體Entity 後續要求建立主題的其他訂用帳戶會遭到拒絕。Subsequent requests for creating additional subscriptions for the topic are rejected. 因此,如果透過入口網站設定,則會顯示錯誤訊息。As a result, if configured through the portal, an error message is shown. 如果從管理 API 進行呼叫,則呼叫端程式碼會收到例外狀況。If called from the management API, an exception is received by the calling code. 適用于基本或標準層的每個主題2000。2,000 per-topic for the Basic or Standard tier.
每個主題的 SQL 篩選器數目Number of SQL filters per topic 實體Entity 後續要求在主題上建立其他篩選器會遭到拒絕, 而且呼叫程式碼會收到例外狀況。Subsequent requests for creation of additional filters on the topic are rejected, and an exception is received by the calling code. 2,0002,000
每個主題的相互關聯篩選器數目Number of correlation filters per topic 實體Entity 後續要求在主題上建立其他篩選器會遭到拒絕, 而且呼叫程式碼會收到例外狀況。Subsequent requests for creation of additional filters on the topic are rejected, and an exception is received by the calling code. 100,000100,000
SQL 篩選器或動作的大小Size of SQL filters or actions 命名空間Namespace 後續要求建立其他篩選器都會遭到拒絕, 而且呼叫程式碼會收到例外狀況。Subsequent requests for creation of additional filters are rejected, and an exception is received by the calling code. 篩選條件字串的長度上限︰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: 12.

在服務匯流排命名空間上設定的規則可套用到該命名空間中的所有佇列和主題。Rules that are configured on a Service Bus namespace apply to all queues and topics in that namespace.
每個交易的訊息數目Number of messages per transaction TransactionTransaction 其他內送訊息會遭到拒絕, 而呼叫程式碼會收到例外狀況, 指出「無法在單一交易中傳送超過100個訊息」。Additional incoming messages are rejected, and an exception stating "Cannot send more than 100 messages in a single transaction" is received by the calling code. 100100

適用於 Send()SendAsync() 作業。For both Send() and SendAsync() operations.

IoT 中樞限制IoT Hub limits

下表列出不同服務層 S1、 S2、 S3 及 F1 相關聯的限制。The following table lists the limits associated with the different service tiers S1, S2, S3, and F1. 如需每個成本單元在每個層中,請參閱Azure IoT 中樞價格For information about the cost of each unit in each tier, see Azure IoT Hub pricing.

資源Resource S1 標準S1 Standard S2 標準S2 Standard S3 標準S3 Standard F1 免費F1 Free
訊息/天Messages/day 400,000400,000 6,000,0006,000,000 300,000,000300,000,000 8,0008,000
單位上限Maximum units 200200 200200 1010 11

注意

如果您預計使用超過 200 個單位的 S1 或 S2 層中樞或 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
上限messages
100100
回應雲端到裝置訊息之反應訊息的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
(標記、報告的屬性,以及所需的屬性)(tags, reported properties, and desired properties)
8 KB8 KB
裝置對應項字串值的大小上限Maximum size of device twin string value 4 KB4 KB
裝置對應項中的物件的最大深度Maximum depth of object in device twin 55
直接方法承載的大小上限Maximum size of direct method payload 128 KB128 KB
作業歷程記錄的保留期上限Job history maximum retention 30 天30 days
並行作業數上限Maximum concurrent jobs 10 (適用於 S3)、5 (適用於 S2)、1 (適用於 S1)10 (for S3), 5 for (S2), 1 (for S1)
額外端點上限Maximum additional endpoints 10 (適用於 S1、 S2 與 S3)10 (for S1, S2, and S3)
訊息路由規則數上限Maximum message routing rules 100 (適用於 S1、 S2 與 S3)100 (for S1, S2, and S3)
同時連線之裝置串流的數目上限Maximum number of concurrently connected device streams 50 (僅適用於 S1、S2、S3 和 F1)50 (for S1, S2, S3, and F1 only)
裝置串流資料傳輸上限Maximum device stream data transfer 每日 300 MB (僅適用於 S1、S2、S3 和 F1)300 MB per day (for S1, S2, S3, and F1 only)

注意

如果您需要超過 50 個 Azure 訂用帳戶付費的 IoT 中樞,請連絡 Microsoft 支援服務。If you need more than 50 paid IoT hubs in an Azure subscription, contact Microsoft Support.

注意

您目前可以連線到單一 IoT 中樞的裝置數目上限為 1,000,000 個。Currently, the maximum number of devices you can connect to a single IoT hub is 1,000,000. 如果您想要上調此限制,請連絡 Microsoft 支援服務If you want to increase this limit, contact Microsoft Support.

超過下列配額時,IoT 中樞節流處理要求。IoT Hub throttles requests when the following quotas are exceeded.

節流Throttle 每個中心的值Per-hub value
身分識別登錄作業Identity registry operations
(建立、 擷取、 列出、 更新和刪除),(create, retrieve, list, update, and delete),
個別或大量匯入/匯出individual or bulk import/export
(適用於 S3) 83.33/sec/unit (5000/分鐘/單位)。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 6000/秒/單位 (適用於 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 6000/秒/單位 (適用於 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/sec/unit (5000/分鐘/單位) (適用於 S3)、 1.67/sec/unit (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/sec/unit (50000/分鐘/單位) (適用於 S3)、 16.67/sec/unit (1000/分鐘/單位) (適用於 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 檔案上傳通知/秒/單位 (5000/分鐘/單位) (適用於 S3),1.67 檔案上傳通知/秒/單位 (100/分鐘/單位),(適用於 S1 和 S2)。83.33 file upload notifications/sec/unit (5,000/min/unit) (for S3), 1.67 file upload notifications/sec/unit (100/min/unit) (for S1 and S2).
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/sec/unit (5000/分鐘/單位) (適用於 S3)、 1.67/sec/unit (100/分鐘/單位) (適用於 S2)、 1.67/sec/unit (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 個新資料流/sec (適用於 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 1010
訊息大小上限Maximum size of message 96 KB96 KB

注意

若要提高您訂用帳戶中的執行個體數目,請連絡 Microsoft 支援服務To increase the number of instances in your subscription, contact Microsoft Support.

注意

若要提高佈建服務的註冊和登錄數目,請連絡 Microsoft 支援服務To increase the number of enrollments and registrations on your provisioning service, contact Microsoft Support.

裝置佈建服務會在超過下列配額時開始對要求進行節流。The Device Provisioning Service throttles requests when the following quotas are exceeded.

節流Throttle 每個單位值Per-unit value
作業Operations 200/分鐘/服務200/min/service
裝置登錄Device registrations 200/分鐘/服務200/min/service
裝置輪詢作業Device polling operation 5/10 秒/裝置5/10 sec/device

Data Factory 限制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

ResourceResource 預設限制Default limit 上限Maximum limit
Azure 訂用帳戶中的資料處理站Data factories in an Azure subscription 5050 連絡客戶支援Contact support.
資料處理站內的實體 (例如管線、資料集、觸發程式、連結的服務和整合執行時間) 總數Total number of entities, such as pipelines, data sets, triggers, linked services, and integration runtimes, within a data factory 5,0005,000 連絡客戶支援Contact support.
一個訂用帳戶下的 Azure SSIS 整合執行時間的總 CPU 核心數Total CPU cores for Azure-SSIS Integration Runtimes under one subscription 256256 連絡客戶支援Contact support.
每個資料處理站的並行管線執行會在 factory 中的所有管線之間共用Concurrent pipeline runs per data factory that's shared among all pipelines in the factory 10,00010,000 連絡客戶支援Contact support.
每個訂用帳戶每個Azure Integration Runtime 區域的並行外部活動執行Concurrent External activity runs per subscription per Azure Integration Runtime region
外部活動是在整合執行時間上管理, 但在連結的服務上執行, 包括 Databricks、預存程式、HDInsights 和其他。External activities are managed on integration runtime but execute on linked services, including Databricks, stored procedure, HDInsights, and others.
30003000 連絡客戶支援Contact support.
每個訂用帳戶每個Azure Integration Runtime 區域的並行管線活動執行Concurrent Pipeline activity runs per subscription per Azure Integration Runtime region
管線活動會在整合執行時間上執行, 包括 Lookup、GetMetadata 和 Delete。Pipeline activities execute on integration runtime, including Lookup, GetMetadata, and Delete.
10001000 連絡客戶支援Contact support.
每個訂用帳戶每個Azure Integration Runtime 區域的並行撰寫作業Concurrent authoring operations per subscription per Azure Integration Runtime region
包括 [測試連接]、[流覽資料夾清單] 和 [資料表清單]、[預覽資料]。Including test connection, browse folder list and table list, preview data.
200200 連絡客戶支援Contact support.
並行資料整合單位1每個訂用帳戶每個Azure Integration Runtime 區域的耗用量Concurrent Data Integration Units1 consumption per subscription per Azure Integration Runtime region 區域群組 12:6000Region group 12: 6000
區域群組 22:3000Region group 22: 3000
區域群組 32:1500Region group 32: 1500
連絡客戶支援Contact support.
每個管線的活動上限, 包括容器的內部活動Maximum activities per pipeline, which includes inner activities for containers 4040 4040
可以針對單一自我裝載整合執行時間建立之連結整合執行時間的最大數目Maximum number of linked integration runtimes that can be created against a single self-hosted integration runtime 100100 連絡客戶支援Contact support.
每個管線的參數上限Maximum parameters per pipeline 5050 5050
ForEach 項目ForEach items 100,000100,000 100,000100,000
ForEach 平行處理原則ForEach parallelism 2020 5050
每個運算式的字元數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 2000 KB2,000 KB
每次複製活動執行的資料整合單位1Data Integration Units1 per copy activity run 256256 連絡客戶支援Contact support.
寫入 API 呼叫Write API calls 1200/h1,200/h

這是由 Azure Resource Manager 所加諸的限制,而不是 Azure Data Factory。This limit is imposed by Azure Resource Manager, not Azure Data Factory.
連絡客戶支援Contact support.
讀取 API 呼叫Read API calls 12500/h12,500/h

這是由 Azure Resource Manager 所加諸的限制,而不是 Azure Data Factory。This limit is imposed by Azure Resource Manager, not Azure Data Factory.
連絡客戶支援Contact support.
監視每分鐘查詢次數Monitoring queries per minute 1,0001,000 連絡客戶支援Contact support.
每分鐘的實體 CRUD 作業Entity CRUD operations per minute 5050 連絡客戶支援Contact support.

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 RegionsRegions
區域群組1Region group 1 美國中部、美國東部、東部美國2、北歐、西歐、美國西部、美國西部2Central US, East US, East US2, North Europe, West Europe, West US, West US 2
區域群組2Region group 2 澳大利亞東部、澳大利亞東南部、巴西南部、印度中部、日本東部、Northcentral US、中南部 US、東南亞、美國中西部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.

第 1 版Version 1

ResourceResource 預設限制Default limit 上限Maximum limit
Azure 訂用帳戶中的資料處理站Data factories in an Azure subscription 5050 連絡客戶支援Contact support.
資料處理站內的管線Pipelines within a data factory 2,5002,500 連絡客戶支援Contact support.
Data factory 內的資料集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 2000 KB2,000 KB
Azure HDInsight 訂用帳戶中的隨選叢集核心2Azure HDInsight on-demand cluster cores within a subscription2 6060 連絡客戶支援Contact support.
每次複製活動執行的雲端資料移動單位3Cloud data movement units per copy activity run3 3232 連絡客戶支援Contact support.
管線活動執行的重試計數Retry count for pipeline activity runs 1,0001,000 MaxInt (32 位元)MaxInt (32 bit)

1管線、資料集和連結的服務物件代表您工作負載的邏輯群組。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 資料湖分析簡化了管理分散式基礎結構與複雜程式碼的複雜工作。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 預設限制Default 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 Store 限制Data Lake Store limits

Azure Data Lake Storage Gen1 是容納巨量資料分析工作負載的企業級超大規模存放庫。Azure Data Lake Storage Gen1 is an enterprise-wide hyper-scale repository for big data analytic workloads. 您可以使用 Data Lake 儲存體 Gen1 來擷取在進行運作和探究分析的單一位置擷取任何大小、 類型和擷取速度的資料。You can use Data Lake Storage Gen1 to capture data of any size, type, and ingestion speed in one single place for operational and exploratory analytics. 您可以儲存在 Data Lake 儲存體 Gen1 帳戶中的資料量沒有限制。There's no limit to the amount of data you can store in a Data Lake Storage Gen1 account.

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

Database Migration Service 限制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 預設限制Default limit 註解Comments
每個區域的每個訂用帳戶服務數目上限Maximum number of services per subscription, per region 22 若要要求增加此限制,請連絡支援。To request an increase for this limit, contact support.

串流分析限制Stream Analytics limits


限制識別碼Limit identifier 限制Limit 註解Comments
每個區域的串流處理單位的最大數目Maximum number of streaming units per subscription per region 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 沒有固定限制 60 個輸入每個 Azure Stream Analytics 作業。There's a hard limit of 60 inputs per Azure Stream Analytics job.
每個工作的輸出數目上限Maximum number of outputs per job 6060 沒有固定限制 60 個輸出每個 Stream Analytics 作業。There's a hard limit of 60 outputs per Stream Analytics job.
每個工作的函式數目上限Maximum number of functions per job 6060 沒有固定限制 60 個函式每一個 Stream Analytics 作業。There's a hard limit of 60 functions per Stream Analytics job.
每個工作的串流單位的最大數目Maximum number of streaming units per job 192192 沒有固定的每一個 Stream Analytics 作業的 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.

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.

CategoryCategory 限制Limits
目錄Directories 單一使用者能以成員或來賓的身分,隸屬於最多 500 個 Azure AD 目錄。A single user can belong to a maximum of 500 Azure AD directories as a member or a guest.
單一使用者最多可以建立 20 個目錄。A single user can create a maximum of 20 directories.
網域Domains 您可以新增 900 個以內的受控網域名稱。You can add no more than 900 managed domain names. 如果您要設定所有網域與內部部署 Active Directory 建立同盟,則可以在每個目錄中新增 450 個以內的網域名稱。If you set up all of your domains for federation with on-premises Active Directory, you can add no more than 450 domain names in each directory.
物件Objects
  • 依照預設,在免費版的 Azure Active Directory 中,最多可以在單一目錄中建立 50,000 個物件。A maximum of 50,000 objects can be created in a single directory by users of the Free edition of Azure Active Directory by default. 如果您有至少一個已驗證的網域,則 Azure AD 中的預設目錄服務配額會擴充至 300,000 個物件。If you have at least one verified domain, the default directory service quota in Azure AD is extended to 300,000 objects.
  • 非系統管理員的使用者最多可以建立 250 個物件。A non-admin user can create no more than 250 objects. 此配額可還原的計數包括作用中的物件和已刪除的物件。Both active objects and deleted objects that are available to restore count toward this quota. 只可還原 30 天內刪除的已刪除物件。Only deleted objects that were deleted fewer than 30 days ago are available to restore. 此配額無法還原的已刪除物件計數值為 30 天的四分之一。Deleted objects that are no longer available to restore count toward this quota at a value of one-quarter for 30 days. 您可以將系統管理員角色指派給非系統管理員使用者,他們會因為需要進行的日常工作而重覆超過此配額。Perhaps assign an administrator role to non-admin users who are likely to repeatedly exceed this quota in the course of their regular duties.
結構描述延伸模組Schema extensions
  • 字串類型延伸模組最多可以包含 256 個字元。String-type extensions can have a maximum of 256 characters.
  • 二進位類型延伸模組受限於 256 個位元組。Binary-type extensions are limited to 256 bytes.
  • 任何單一物件均可寫入 100 個延伸模組值,包括所有 類型和所有 應用程式皆可。Only 100 extension values, across all types and all applications, can be written to any single object.
  • 只能使用「字串」類型或「二進位」類型單一值屬性來擴充 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.
群組Groups
  • 最多 100 個使用者可以成為單一群組的擁有者。A maximum of 100 users can be owners of a single group.
  • 任何數目的物件都可以是單一群組的成員。Any number of objects can be members of a single group.
  • 使用者可以是任意數目群組的成員。A user can be a member of any number of groups.
  • 可以使用 Azure AD Connect 從您的內部部署 Active Directory 同步至 Azure Active Directory 群組中的成員數目限制為 5 萬個成員。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.
應用程式 ProxyApplication Proxy
  • 最多 500 筆的交易,每個應用程式 Proxy 應用程式每秒A maximum of 500 transactions per second per App Proxy application
  • 最多 750 每秒交易數個租用戶A maximum of 750 transactions per second for the tenant

交易被定義為單一 http 要求和回應唯一的資源。A transaction is defined as a single http request and response for a unique resource. 節流時,用戶端會收到 429 的回應 (太多要求)。When throttled, clients will receive a 429 response (too many requests).
存取面板Access Panel
  • 每位使用者在存取面板中可以看到的應用程式數目沒有限制。There's no limit to the number of applications that can be seen in the Access Panel per user. 這適用於已指派 Azure AD Premium 或 Enterprise Mobility Suite 授權的使用者。This applies to users assigned licenses for Azure AD Premium or the Enterprise Mobility Suite.
  • 每位使用者可在存取面板中看到最多 10 個應用程式圖格。A maximum of 10 app tiles can be seen in the Access Panel for each user. 這項限制適用於已指派「免費」或 Azure Active Directory 的 Azure AD Basic 版本授權的使用者。This limit applies to users who are assigned licenses for Free or Azure AD Basic editions of Azure Active Directory. 應用程式圖格範例包括 Box、Salesforce 或 Dropbox。Examples of app tiles include Box, Salesforce, or Dropbox. 此限制不適用於系統管理員帳戶。This limit doesn't apply to administrator accounts.
報告Reports 在任何報告中,最多可以檢視或下載 1000 個資料列。A maximum of 1,000 rows can be viewed or downloaded in any report. 任何其他資料會遭到截斷。Any additional data is truncated.
管理單位Administrative units 物件可以是有不超過 30 個管理單位的成員。An object can be a member of no more than 30 administrative units.
系統管理員角色與權限Admin roles and permissions
  • 群組無法加入成為擁有者A group cannot be added as an owner.
  • 無法將群組指派給角色A group cannot be assigned to a role.
  • 使用者的能力讀取其他使用者的目錄資訊無法限制之外的整個租用戶的切換,以停用所有非系統管理員使用者的存取 (不建議使用) 的所有目錄資訊。Users’ ability to read other users’ directory information cannot be restricted outside of the tenant-wide switch to disable all non-admin users’ access to all directory information (not recommended). 預設權限的更多有關此處More information on default permissions here.
  • 可能需要 15 分鐘,或簽署外/登入之前系統管理員角色成員資格新增項目和撤銷才會生效。It may take up to 15 minutes or signing out/signing in before admin role membership additions and revocations take effect.

事件方格限制Event Grid limits

Azure Event Grid 系統主題和自訂主題,會適用下列限制事件網域。The following limits apply to Azure Event Grid system topics and custom topics, not event domains.

ResourceResource 限制Limit
每個 Azure 訂用帳戶的自訂主題Custom topics per Azure subscription 100100
每個主題的事件訂用帳戶Event subscriptions per topic 500500
自訂主題 (輸入) 的發佈速率Publish rate for a custom topic (ingress) 每個主題每秒 5,000 個事件5,000 events per second per topic
發佈要求Publish requests 每秒 250250 per second
事件大小Event size 支援的 64 KB 一般情況下運作 (GA)。Support for 64 KB in General Availability (GA). 1 MB 的支援目前為預覽狀態。Support for 1 MB is currently in preview.

下列限制適用於僅限事件的網域。The following limits apply to event domains only.

ResourceResource 限制Limit
每個事件網域的主題Topics per event domain 公開預覽期間 1,000 個1,000 during public preview
事件訂用帳戶每個網域中的主題Event subscriptions per topic within a domain 公開預覽期間 50 個50 during public preview
網域範圍事件訂用帳戶Domain scope event subscriptions 公開預覽期間 50 個50 during public preview
發行事件網域 (輸入) 的速率Publish rate for an event domain (ingress) 公開預覽期間每秒 5,000 個事件5,000 events per second during public preview
發佈要求Publish requests 每秒 250250 per second

Azure 地圖服務限制Azure Maps limits

下表顯示 Azure Maps S0 定價層的使用量限制。The following table shows the usage limit for the Azure Maps S0 pricing tier. 使用量限制取決於定價層。Usage limit depends on the pricing tier.

資源Resource S0 定價層限制S0 pricing tier limit
每一訂用帳戶的要求率上限Maximum request rate per subscription 每秒 50 個要求50 requests per second

下表顯示 Azure 地圖服務的資料大小限制。The following table shows the data size limit for Azure Maps. Azure 地圖服務的資料服務是只能在 S1 定價層。The Azure Maps data service is available only at the S1 pricing tier.

資源Resource 限制Limit
資料大小上限Maximum size of data 50 MB50 MB

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

Azure 原則限制Azure Policy limits

Azure 原則的每個物件類型都有最大計數。There's a maximum count for each object type for Azure Policy. _範圍_的項目表示訂用帳戶或管理群組An entry of Scope means either the subscription or the management group.

WhereWhere 何事What 最大計數Maximum count
影響範圍Scope 原則定義Policy definitions 500500
影響範圍Scope 計畫定義Initiative definitions 100100
租用戶Tenant 計畫定義Initiative definitions 1,0001,000
影響範圍Scope 原則或方案指派Policy or initiative assignments 100100
原則定義Policy definition 參數Parameters 2020
計畫定義Initiative definition 原則Policies 100100
計畫定義Initiative definition 參數Parameters 100100
原則或方案指派Policy or initiative assignments 排除項目 (notScopes)Exclusions (notScopes) 400400
原則規則Policy rule 巢狀的條件Nested conditionals 512512

StorSimple 系統限制StorSimple System limits

限制識別碼Limit identifier 限制Limit 註解Comments
儲存體帳戶認證的數目上限Maximum number of storage account credentials 6464
磁碟區容器的數目上限Maximum number of volume containers 6464
磁碟區的數目上限Maximum number of volumes 255255
每個頻寬範本之排程的數目上限Maximum number of schedules per bandwidth template 168168 每小時、 一週的每日排程。A schedule for every hour, every day of the week.
實體裝置上之分層磁碟區的大小上限Maximum size of a tiered volume on physical devices StorSimple 8100 和 StorSimple 8600 的 64 TB64 TB for StorSimple 8100 and StorSimple 8600 StorSimple 8100 和 StorSimple 8600 為實體裝置。StorSimple 8100 and StorSimple 8600 are physical devices.
Azure 中的虛擬裝置上之分層磁碟區的大小上限Maximum size of a tiered volume on virtual devices in Azure 30 TB for StorSimple 801030 TB for StorSimple 8010
64 TB for StorSimple 802064 TB for StorSimple 8020
StorSimple 8010 和 StorSimple 8020 會在 Azure 中分別使用標準儲存體和進階儲存體的虛擬裝置。StorSimple 8010 and StorSimple 8020 are virtual devices in Azure that use Standard storage and Premium storage, respectively.
實體裝置上之固定在本機的磁碟區的大小上限Maximum size of a locally pinned volume on physical devices 9 TB for StorSimple 81009 TB for StorSimple 8100
24 TB for StorSimple 860024 TB for StorSimple 8600
StorSimple 8100 和 StorSimple 8600 為實體裝置。StorSimple 8100 and StorSimple 8600 are physical devices.
iSCSI 連線的數目上限Maximum number of iSCSI connections 512512
從起始端之 iSCSI 連線的數目上限Maximum number of iSCSI connections from initiators 512512
每個裝置的存取控制記錄的數目上限Maximum number of access control records per device 6464
每個備份原則的磁碟區數目上限Maximum number of volumes per backup policy 2424
每個備份原則保留的備份數目上限Maximum number of backups retained per backup policy 6464
每個備份原則的排程數目上限Maximum number of schedules per backup policy 1010
每個磁碟區可以保留之任何類型快照集的數目上限Maximum number of snapshots of any type that can be retained per volume 256256 此數量包含本機快照和雲端快照集。This amount includes local snapshots and cloud snapshots.
可以在任何裝置中呈現的快照集數目上限Maximum number of snapshots that can be present in any device 10,00010,000
可以針對備份、還原或複製進行平行處理的磁碟區數目上限Maximum number of volumes that can be processed in parallel for backup, restore, or clone 1616
  • 如果有 16 個以上的磁碟區,它們會循序處理可用的處理插槽時會。If there are more than 16 volumes, they're processed sequentially as processing slots become available.
  • 等到作業完成後,就不會發生新的複製的備份或還原的分層式磁碟區。New backups of a cloned or a restored tiered volume can't occur until the operation is finished. 對於本機的磁碟區,磁碟區上線後允許備份。For a local volume, backups are allowed after the volume is online.
分層磁碟區的還原和複製復原時間Restore and clone recover time for tiered volumes < 2 分鐘<2 minutes
  • 磁碟區均可在還原或複製作業,無論磁碟區大小的 2 分鐘內。The volume is made available within 2 minutes of a restore or clone operation, regardless of the volume size.
  • 磁碟區效能一開始可能會低於正常現象,因為大部分的資料和中繼資料仍然位於雲端。The volume performance might initially be slower than normal as most of the data and metadata still resides in the cloud. 為資料流,從雲端至 StorSimple 裝置可能會提升效能。Performance might increase as data flows from the cloud to the StorSimple device.
  • 下載中繼資料的總時間取決於配置的磁碟區大小。The total time to download metadata depends on the allocated volume size. 中繼資料會於背景自動帶入裝置,速率為每 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 gigabit Ethernet 網路介面920/720 MB/sec with a single 10-gigabit Ethernet network interface 使用 MPIO 和兩個網路介面的最多兩次。Up to two times with MPIO and two network interfaces.
最大用戶端讀取/寫入輸送量,當由 HDD 層 *Maximum client read/write throughput, when served from the HDD tier* 120/250 MB/秒120/250 MB/sec
最大用戶端讀取/寫入輸送量,從雲端層 * 提供服務時Maximum client read/write throughput, when served from the cloud tier* 11/41 MB/秒11/41 MB/sec 讀取輸送量取決於用戶端產生和維護足夠的 I/O 佇列深度。Read throughput depends on clients generating and maintaining sufficient I/O queue depth.

*每種 I/O 類型的最大輸送量是 100%讀取和 100%寫入案例測量。*Maximum throughput per I/O type was measured with 100 percent read and 100 percent write scenarios. 實際輸送量可能較低,取決於 I/O 混合和網路狀況。Actual throughput might be lower and depends on I/O mix and network conditions.

備份限制Backup limits

下列限制適用於 Azure 備份。The following limits apply to Azure Backup.

限制Limit 預設值Default
伺服器或機器可在保存庫註冊。Servers or machines that can be registered in a vault. Windows Server/Windows 用戶端/System Center Data Protection Manager:50.Windows Server/Windows Client/System Center Data Protection Manager: 50.

IaaS VM:1,000.IaaS VMs: 1,000.
保存庫儲存體中的資料來源的大小。Size of a data source in vault storage. 54,400 GB 最大值。54,400-GB maximum. 此限制不適用於 IaaS VM 備份。The limit doesn't apply to IaaS VM backup.
Azure 訂用帳戶中的備份保存庫。Backup vaults in an Azure subscription. 每個區域 500 個保存庫。500 vaults per region.
排程每日備份。Schedule daily backups. Windows Server/用戶端:一天安排三。Windows Server/Client: Three a day.
System Center DPM:兩個一天。System Center DPM: Two a day.
IaaS VM:一天一次。IaaS VMs: Once a day.
連接到 Azure VM 備份的資料磁碟。Data disks attached to an Azure VM for backup. 1616
連接到 Azure VM 備份的個別資料磁碟。Individual data disk attached to Azure VM for backup. 4,095 GB4,095 GB

Azure SignalR Service 限制Azure SignalR Service limits

資源Resource 預設限制Default limit 上限Maximum limit
免費層的每個執行個體的 azure SignalR 服務單位Azure SignalR Service units per instance for Free tier 11 11
Azure SignalR 服務單位,每個標準層的執行個體Azure SignalR Service units per instance for Standard tier 100100 100100
Azure SignalR 服務單位,每個區域免費層Azure SignalR Service units per subscription per region for Free tier 55 55
計算每個區域的總 Azure SignalR 服務單位Total Azure SignalR Service unit counts per subscription per region 150150 無限Unlimited
免費層中每天每個單位的連線數Connections per unit per day for Free tier 2020 2020
標準層中每天每個單位的連線數Connections per unit per day for Standard tier 1,0001,000 1,0001,000
免費層中每天每個單位的內含訊息數Included messages per unit per day for Free tier 20,00020,000 20,00020,000
標準層中每天每個單位的內含訊息數Included messages per unit per day for Standard tier 1,000,0001,000,000 1,000,0001,000,000

若要要求更新訂用帳戶的預設限制,請開啟支援票證。To request an update to your subscription's default limits, open a support ticket.

Site Recovery 限制Site Recovery limits

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

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

API 管理限制API Management limits

資源Resource 限制Limit
縮放單位數上限Maximum number of scale units 每個區域 10 個110 per region1
快取大小Cache size 每個單位 5 GB25 GB per unit2
並行的後端連線3每個 HTTP 授權單位Concurrent back-end connections3 per HTTP authority 每個單位 204842,048 per unit4
最大快取回應大小Maximum cached response size 2 MB2 MB
原則文件大小上限Maximum policy document size 256 KB5256 KB5
每個服務執行個體的自訂閘道網域數目上限6Maximum custom gateway domains per service instance6 2020
每個服務執行個體的 CA 憑證的最大數目Maximum number of CA certificates per service instance 1010
每個訂用帳戶的服務執行個體數目上限7Maximum number of service instances per subscription7 2020
每個服務執行個體的訂用帳戶數目上限7Maximum number of subscriptions per service instance7 500500
每個服務執行個體的用戶端憑證數目上限7Maximum number of client certificates per service instance7 5050
每個服務執行個體的 API 數目上限7Maximum number of APIs per service instance7 5050
每個服務執行個體的 API 作業數目上限7Maximum number of API operations per service instance7 1,0001,000
最大值的總要求持續時間7Maximum total request duration7 30 秒30 seconds
緩衝承載大小上限7Maximum buffered payload size7 2 MB2 MB

1調整限制取決於定價層。1Scaling limits depend on the pricing tier. 若要查看定價層和調整限制,請參閱API 管理價格To see the pricing tiers and their scaling limits, see API Management pricing.
2每單位快取大小取決於定價層。2Per unit cache size depends on the pricing tier. 若要查看定價層和調整限制,請參閱API 管理價格To see the pricing tiers and their scaling limits, see API Management pricing.
3連線集區,而且除非明確關閉由後端重複使用。3Connections are pooled and reused unless explicitly closed by the back end.
4這項限制是每個 Basic、 Standard 和 Premium 層單位。4This limit is per unit of the Basic, Standard, and Premium tiers. 開發人員層次是限制為 1,024。The Developer tier is limited to 1,024. 這項限制不適用於使用情況層。This limit doesn't apply to the Consumption tier.
5這個限制適用於 Basic、 Standard 和 Premium 層。 5This limit applies to the Basic, Standard, and Premium tiers. 在耗用量層中,原則文件大小會限制為 4 KB。In the Consumption tier, policy document size is limited to 4 KB.
6此資源是只在進階層中可用。6This resource is available in the Premium tier only.
7耗用量層僅適用於此資源。7This resource applies to the Consumption tier only.

Azure Cache for Redis 限制Azure Cache for Redis limits

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

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

如需 Azure 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.

金鑰保存庫限制Key Vault limits

金鑰交易 (每個區域的每個在 10 秒,允許的最大交易保存庫1):Key transactions (maximum transactions allowed in 10 seconds, per vault per region1):

金鑰類型Key type HSM 金鑰HSM key
建立金鑰CREATE key
HSM 金鑰HSM key
所有其他交易All other transactions
軟體金鑰Software key
建立金鑰CREATE key
軟體金鑰Software key
所有其他交易All other transactions
RSA 2,048 位元RSA 2,048-bit 55 1,0001,000 1010 2,0002,000
RSA 3072 位元RSA 3,072-bit 55 250250 1010 500500
RSA 4096 位元RSA 4,096-bit 55 125125 1010 250250
ECC P-256ECC P-256 55 1,0001,000 1010 2,0002,000
ECC P-384ECC P-384 55 1,0001,000 1010 2,0002,000
ECC P-521ECC P-521 55 1,0001,000 1010 2,0002,000
ECC SECP256K1ECC SECP256K1 55 1,0001,000 1010 2,0002,000

注意

在上表中,我們可以看到,RSA 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 取得交易。For RSA 2,048-bit HSM-keys, 1,000 GET transactions per 10 seconds are allowed.

節流臨界值進行加權,並強制執行位於其總和。The throttling thresholds are weighted, and enforcement is on their sum. 比方說,如下表所示,您執行 GET 作業 RSA HSM 金鑰時,八倍昂貴使用 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 金鑰保存庫用戶端只能有一個的下列作業遇到之前,先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 金鑰取得交易1,000 RSA 2,048-bit HSM-key GET transactions
  • 125 RSA 4096 位元 HSM 金鑰取得交易125 RSA 4,096-bit HSM-key GET transactions
  • 124 的 RSA 4096 位元的 HSM 金鑰取得交易和 8 的 RSA 2,048 位元 HSM 金鑰取得交易124 RSA 4,096-bit HSM-key GET transactions and 8 RSA 2,048-bit HSM-key GET transactions

祕密、 受管理的儲存體帳戶金鑰及保存庫交易:Secrets, managed storage account keys, and vault transactions:

交易類型Transactions type 每個區域的每個在 10 秒,允許的最大交易保存庫1Maximum transactions allowed in 10 seconds, per vault per region1
所有交易All transactions 2,0002,000

如需如何處理節流時超過這些限制的資訊,請參閱Azure Key Vault 節流指導方針For information on how to handle throttling when these limits are exceeded, see Azure Key Vault throttling guidance.

1全訂用帳戶限制的所有交易類型是五次,每個金鑰保存庫的限制。1 A subscription-wide limit for all transaction types is five times per key vault limit. 比方說,每個訂用帳戶的 HSM-其他交易在 10 秒後,每個訂用帳戶僅限於 5,000 筆交易筆。For example, HSM-other transactions per subscription are limited to 5,000 transactions in 10 seconds per subscription.

多重要素驗證限制Multi-Factor Authentication limits

資源Resource 預設限制Default limit 上限Maximum limit
受信任的 IP 位址或範圍的最大數目每訂用帳戶Maximum number of trusted IP addresses or ranges per subscription 00 5050
記住我的裝置的天數Remember my devices, number of days 1414 6060
應用程式密碼的最大數目Maximum number of app passwords 00 沒有限制No limit
MFA 呼叫期間允許 X 次嘗試Allow X attempts during MFA call 11 9999
雙向簡訊逾時秒數Two-way text message timeout seconds 6060 600600
預設一次性略過秒數Default one-time bypass seconds 300300 1,8001,800
X 次連續 MFA 被拒後鎖定使用者帳戶Lock user account after X consecutive MFA denials 未設定Not set 9999
X 分鐘後重設帳戶鎖定計數器Reset account lockout counter after X minutes 未設定Not set 9,9999,999
X 分鐘後解除鎖定帳戶Unlock account after X minutes 未設定Not set 9,9999,999

自動化限制Automation limits

程序自動化Process automation

資源Resource 上限Maximum limit 注意Notes
新的作業可以提交每個 Azure 自動化帳戶 (未排程的作業) 每隔 30 秒的最大數目Maximum number of new jobs that can be submitted every 30 seconds per Azure Automation account (nonscheduled jobs) 100100 當到達這個限制時,建立作業,後續要求將會失敗。When this limit is reached, the subsequent requests to create a job fail. 用戶端會收到錯誤回應。The client receives an error response.
並行執行的作業,在相同的執行個體的每個自動化帳戶 (未排程的作業) 的時間的最大數目Maximum number of concurrent running jobs at the same instance of time per Automation account (nonscheduled jobs) 200200 當到達這個限制時,建立作業,後續要求將會失敗。When this limit is reached, the subsequent requests to create a job fail. 用戶端會收到錯誤回應。The client receives an error response.
儲存體大小上限的 30 天的循環內的作業中繼資料Maximum storage size of job metadata for a 30-day rolling period 10 GB (約 4 百萬個作業)10 GB (approximately 4 million jobs) 當到達這個限制時,建立作業,後續要求將會失敗。When this limit is reached, the subsequent requests to create a job fail.
最大的工作資料流限制Maximum job stream limit 1MB1MB 單一資料流不能大於 1 MB。A single stream cannot be larger than 1 MB.
模組可匯入每個自動化帳戶每隔 30 秒的最大數目Maximum number of modules that can be imported every 30 seconds per Automation account 55
模組的最大大小Maximum size of a module 100 MB100 MB
作業執行時間,免費層Job run time, Free tier 每個訂用帳戶每行事曆月份 500 分鐘500 minutes per subscription per calendar month
每個沙箱所允許的磁碟空間的最大數量1Maximum amount of disk space allowed per sandbox1 1 GB1 GB 適用於 Azure 的沙箱。Applies to Azure sandboxes only.
提供給沙箱的記憶體數量上限1Maximum amount of memory given to a sandbox1 400 MB400 MB 適用於 Azure 的沙箱。Applies to Azure sandboxes only.
每個沙箱所允許的網路通訊端數目上限1Maximum number of network sockets allowed per sandbox1 1,0001,000 適用於 Azure 的沙箱。Applies to Azure sandboxes only.
每個 runbook 所允許的最大執行階段1Maximum runtime allowed per runbook1 3 小時3 hours 適用於 Azure 的沙箱。Applies to Azure sandboxes only.
訂用帳戶中的自動化帳戶的最大數目Maximum number of Automation accounts in a subscription 沒有限制No limit
混合式背景工作角色群組,每個自動化帳戶的最大數目Maximum number of Hybrid Worker Groups per Automation Account 4,0004,000
可以在單一的混合式 Runbook 背景工作角色執行的並行作業數目上限Maximum number of concurrent jobs that can be run on a single Hybrid Runbook Worker 5050
最大的 runbook 作業參數的大小Maximum runbook job parameter size 512 kb512 kilobits
最大的 runbook 參數Maximum runbook parameters 5050 如果達到 50 參數限制,您可以將 JSON 或 XML 字串傳遞至參數,並剖析與 runbook。If you reach the 50-parameter limit, you can pass a JSON or XML string to a parameter and parse it with the runbook.
最大的 webhook 承載大小Maximum webhook payload size 512 kb512 kilobits
作業資料會保留的天數上限Maximum days that job data is retained 30 天30 days
PowerShell 工作流程狀態大小上限Maximum PowerShell workflow state size 5 MB5 MB 適用於 PowerShell 工作流程 runbook 時檢查點檢查工作流程。Applies to PowerShell workflow runbooks when checkpointing workflow.

1沙箱是一種共用的環境,可供多個工作。1A sandbox is a shared environment that can be used by multiple jobs. 使用相同的沙箱的工作都受限於沙箱的資源限制。Jobs that use the same sandbox are bound by the resource limitations of the sandbox.

變更追蹤與詳細目錄Change Tracking and Inventory

下表顯示每一機器的變更追蹤的追蹤項目限制。The following table shows the tracked item limits per machine for change tracking.

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

Identity Manager 限制Identity Manager limits

CategoryCategory 限制Limit
指派使用者給受控身分識別User-assigned managed identities
  • 當您建立使用者指派給受控身分識別、 只有英數字元 (0-9、a-z 和 A-Z) 和連字號 (-) 支援。When you create user-assigned managed identities, only alphanumeric characters (0-9, a-z, and A-Z) and the hyphen (-) are supported. 指派給虛擬機器或虛擬機器擴展集才能正常運作中,名稱是限制為 24 個字元。For the assignment to a virtual machine or virtual machine scale set to work properly, the name is limited to 24 characters.
  • 如果您使用受控身分識別虛擬機器擴充功能,支援的限制為 32 的使用者指派給受控身分識別。If you use the managed identity virtual machine extension, the supported limit is 32 user-assigned managed identities. 受控身分識別虛擬機器擴充功能,不支援的限制是 512 的使用者指派身分識別。Without the managed identity virtual machine extension, the supported limit is 512 user-assigned identities.

角色型存取控制限制Role-based access control limits

資源Resource 限制Limit
Azure 資源每個 Azure 訂用帳戶的角色指派Role assignments for Azure resources per Azure subscription 2,0002,000
自訂每個租用戶的 Azure 資源角色Custom roles for Azure resources per tenant 5,0005,000
自訂每個租用戶的 Azure 資源角色Custom roles for Azure resources per tenant
(特定的雲端,例如 Azure Government、 Azure 德國和 Azure 中國 21Vianet)(specialized clouds, such as Azure Government, Azure Germany, and Azure China 21Vianet)
2,0002,000

SQL Database 限制SQL Database limits

如 SQL Database 限制, 請參閱單一資料庫的 SQL Database 資源限制、彈性集區和集區資料庫的 SQL Database 資源限制, 以及受控實例的 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 managed instances.

SQL 資料倉儲限制SQL Data Warehouse limits

如 SQL 資料倉儲限制, 請參閱SQL 資料倉儲資源限制For SQL Data Warehouse limits, see SQL Data Warehouse resource limits.

另請參閱See also