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

• 06/04/2020
• • 
  • 

本文件列出一些最常見的 Microsoft Azure 限制，有時也稱為配額。This document lists some of the most common Microsoft Azure limits, which are also sometimes called quotas.

若要深入瞭解 Azure 定價，請參閱azure 定價總覽。To learn more about Azure pricing, see Azure pricing overview. 在這裡，您可以使用定價計算機來預估成本。There, you can estimate your costs by using the pricing calculator. 您也可以移至特定服務（例如Windows vm）的定價詳細資料頁面。You also can go to the pricing details page for a particular service, for example, Windows VMs. 如需協助您管理成本的祕訣，請參閱使用 Azure 計費與成本管理避免非預期的成本。For tips to help manage your costs, see Prevent unexpected costs with Azure billing and cost management.

管理限制Managing limits

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

某些限制是在區域層級管理。Some limits are managed at a regional level.

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

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

一般限制General limits

如需資源名稱的限制，請參閱Azure 資源的命名規則和限制。For limits on resource names, see Naming rules and restrictions for Azure resources.

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

管理群組限制Management group limits

下列限制適用于管理群組。The following limits apply to management groups.

¹6層級不包含訂用帳戶層級。¹The 6 levels don't include the subscription level.

²如果您達到800部署的限制，請從已不再需要的歷程記錄中刪除部署。²If you reach the limit of 800 deployments, delete deployments from the history that are no longer needed. 若要刪除管理群組層級部署，請使用AzManagementGroupDeployment或az deployment mg delete。To delete management group level deployments, use Remove-AzManagementGroupDeployment or az deployment mg delete.

訂用帳戶限制Subscription limits

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

¹您最多可以將50標記直接套用到訂用帳戶。¹You can apply up to 50 tags directly to a subscription. 不過，訂用帳戶可以包含不限數目的標記，以套用至訂用帳戶內的資源群組和資源。However, the subscription can contain an unlimited number of tags that are applied to resource groups and resources within the subscription. 每個資源或資源群組的標記數目限制為50。The number of tags per resource or resource group is limited to 50. 只有當標記數目為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.

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

資源群組限制Resource group limits

¹從2020年6月開始，部署將會在您接近限制時自動從歷程記錄中刪除。¹Starting in June 2020, deployments will be automatically deleted from the history as you near the limit. 從部署歷程記錄中刪除專案並不會影響已部署的資源。Deleting an entry from the deployment history doesn't affect the deployed resources. 如需詳細資訊，請參閱從部署歷程記錄自動刪除。For more information, see Automatic deletions from deployment history.

範本限制Template limits

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

Active Directory 限制Active Directory limits

以下是 Azure Active Directory (Azure AD) 服務的使用條件約束和其他服務限制。Here are the usage constraints and other service limits for the Azure Active Directory (Azure AD) service.

API 管理限制API Management limits

¹調整限制取決於定價層。¹Scaling limits depend on the pricing tier. 如需定價層及其調整限制的詳細資訊，請參閱API 管理價格。For details on the pricing tiers and their scaling limits, see API Management pricing.
²每個單位的快取大小取決於定價層。²Per unit cache size depends on the pricing tier. 若要查看定價層和其調整限制，請參閱API 管理價格。To see the pricing tiers and their scaling limits, see API Management pricing.
³除非後端明確關閉，否則連線會進行共用並重複使用。³Connections are pooled and reused unless explicitly closed by the back end.
⁴這項限制是基本、標準和高階層的每個單位。⁴This limit is per unit of the Basic, Standard, and Premium tiers. 開發人員層的限制為1024。The Developer tier is limited to 1,024. 此限制不適用於耗用量層。This limit doesn't apply to the Consumption tier.
⁵此限制適用于基本、標準和 Premium 層。⁵This limit applies to the Basic, Standard, and Premium tiers. 在取用量層中，原則檔案大小限制為 4 KiB。In the Consumption tier, policy document size is limited to 4 KiB.
⁶開發人員和 Premium 層僅支援多個自訂網域。⁶Multiple custom domains are supported in the Developer and Premium tiers only.
⁷消費層不支援 CA 憑證。⁷CA certificates are not supported in the Consumption tier.
⁸此資源僅適用于耗用量層。⁸This resource applies to the Consumption tier only.
⁹僅適用于耗用量層。⁹Applies to the Consumption tier only. 包含最多2048個位元組長的查詢字串。Includes an up to 2048 bytes long query string.
¹⁰只有開發人員和 Premium 層支援自我裝載閘道。¹⁰Self-hosted gateways are supported in the Developer and Premium tiers only. 此限制適用于自我裝載閘道資源的數目。The limit applies to the number of self-hosted gateway resources. 若要提高此限制，請聯絡支援人員。To raise this limit please contact support. 請注意，在進階層中，與自我裝載閘道資源相關聯的節點（或複本）數目不受限制，而且在開發人員層的單一節點上具有上限。Note, that the number of nodes (or replicas) associated with a self-hosted gateway resource is unlimited in the Premium tier and capped at a single node in the Developer tier.

應用程式服務限制App Service limits

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

¹應用程式和儲存體配額是依每個 App Service 方案為準，除非另有指示。¹Apps and storage quotas are per App Service plan unless noted otherwise.
²您可以在這些電腦上裝載的實際應用程式數目，會視應用程式的活動、電腦執行個體的大小，及對應的資源使用率而定。²The 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.
³專用的執行個體可有不同的大小。³Dedicated instances can be of different sizes. 如需詳細資訊，請參閱 App Service 價格。For more information, see App Service pricing.
⁴可應要求提高數量。⁴More are allowed upon request.
⁵儲存體限制是跨相同 App Service 方案中所有應用程式的目前總大小。⁵The storage limit is the total content size across all apps in the same App service plan. 單一資源群組和區域中所有 App Service 方案上的所有應用程式內容大小總計不能超過 500GB。The total content size of all apps across all App service plans in a single resource group and region cannot exceed 500GB.
⁶這些資源都會受到專用執行個體 (執行個體大小和執行個體數目) 上的實體資源限制。⁶These resources are constrained by physical resources on the dedicated instances (the instance size and the number of instances).
⁷如果您將基本層的一個應用程式調整為兩個執行個體，則其中每個執行個體有 350 個並行連線。⁷If you scale an app in the Basic tier to two instances, you have 350 concurrent connections for each of the two instances. 針對標準層和其以上版本，Web 通訊端沒有理論上的限制，但其他因素可能會限制 Web 通訊端的數目。For Standard tier and above, there are no theoretical limits to web sockets, but other factors can limit the number of web sockets. 例如，允許的並行要求數上限 (由 maxConcurrentRequestsPerCpu所定義) 是：每個小型 VM 7,500 個、每個中型 VM 15,000 個 (7,500 x 2 個核心) 和每個大型 VM 75,000 個 (18,750 x 4 個核心)。For example, maximum concurrent requests allowed (defined by maxConcurrentRequestsPerCpu) are: 7,500 per small VM, 15,000 per medium VM (7,500 x 2 cores), and 75,000 per large VM (18,750 x 4 cores).
⁸IP 連線數會以執行個體為基礎，並且取決於執行個體的大小：每個 B1/S1/P1V2 執行個體 1,920 個、每個 B2/S2/P2V2 執行個體3,968 個、每個 B3/S3/P3V2 執行個體 8,064 個。⁸The maximum IP connections are per instance and depend on the instance size: 1,920 per B1/S1/P1V2 instance, 3,968 per B2/S2/P2V2 instance, 8,064 per B3/S3/P3V2 instance.
⁹您可以透過支援要求將每個訂用帳戶的 App Service 憑證配額限制增加到最多 200 個。⁹The App Service Certificate quota limit per subscription can be increased via a support request to a maximum limit of 200.
¹⁰App Service 隔離式 SKU 能夠透過 Azure Load Balancer 在內部達成負載平衡 (ILB)，因此網際網路未提供公用連線。¹⁰App 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.
¹¹在您的 App Service 執行個體中，以背景工作的方式隨選、依照排程或連續執行自訂可執行檔和/或指令碼。¹¹Run custom executables and/or scripts on demand, on a schedule, or continuously as a background task within your App Service instance. 若要連續執行 WebJobs，「永遠開啟」是必要選項。Always On is required for continuous WebJobs execution. 可在 App Service 執行個體中執行的 WebJobs 數目沒有預先定義的限制。There's no predefined limit on the number of WebJobs that can run in an App Service instance. 但根據應用程式程式碼嘗試執行的動作，會有一些實際限制。There are practical limits that depend on what the application code is trying to do.

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

自動化限制Automation limits

程序自動化Process automation

¹沙箱是可供多個作業使用的共用環境。¹A 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.

更新管理Update Management

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

Azure Cache for Redis 限制Azure Cache for Redis limits

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

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

因為 Azure Cache for Redis 執行個體是由 Microsoft 設定與管理，所以 Azure Cache for Redis 並未支援所有的 Redis 命令。Because configuration and management of Azure Cache for Redis instances is done by Microsoft, not all Redis commands are supported in Azure Cache for Redis. 如需詳細資訊，請參閱 Azure Cache for Redis 中不支援的 Redis 命令。For more information, see Redis commands not supported in Azure Cache for Redis.

Azure 雲端服務限制Azure Cloud Services limits

¹具有 web 或背景工作角色的每個 Azure 雲端服務可以有兩個部署，一個用於生產，另一個用於預備環境。¹Each Azure Cloud Service with web or worker roles can have two deployments, one for production and one for staging. 這項限制是指不同角色的數目，也就是設定。This limit refers to the number of distinct roles, that is, configuration. 這項限制不會參考每個角色的實例數目，也就是調整規模。This limit doesn't refer to the number of instances per role, that is, scaling.

Azure 認知搜尋限制Azure Cognitive Search limits

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

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

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

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

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

¹ 免費服務是根據共用而非專用的資源。¹ Free is based on shared, not dedicated, resources. 共用資源上不支援相應增加。Scale-up is not supported on shared resources.

²搜尋單位是計費單位，配置為複本或資料分割。² Search units are billing units, allocated as either a replica or a partition. 您需要這兩種資源才能進行儲存、編製索引及查詢作業。You need both resources for storage, indexing, and query operations. 若要深入了解 SU 計算，請參閱針對查詢和索引工作負載調整資源層級。To learn more about SU computations, see Scale resource levels for query and index workloads.

每個搜尋服務的限制Limits per search service

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

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

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

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

Azure 認知服務限制Azure Cognitive Services limits

下列限制適用于每個 Azure 訂用帳戶的認知服務資源數目。The following limits are for the number of Cognitive Services resources per Azure subscription. 每個認知服務可能會有額外的限制，如需詳細資訊，請參閱Azure 認知服務。Each of the Cognitive Services may have additional limitations, for more information see Azure Cognitive Services.

Azure Cosmos DB 限制Azure Cosmos DB limits

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

Azure 資料總管限制Azure Data Explorer limits

下表描述 Azure 資料總管叢集的最大限制。The following table describes the maximum limits for Azure Data Explorer clusters.

下表描述在 Azure 資料總管叢集上執行之管理作業的限制。The following table describes the limits on management operations performed on Azure Data Explorer clusters.

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

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

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

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

Azure Functions 限制Azure Functions limits

¹根據預設，App Service 計畫中的函式1.x 執行時間的超時不受限制。¹ By default, the timeout for the Functions 1.x runtime in an App Service plan is unbounded.
²要求 App Service 計畫必須設定為Always On。² Requires the App Service plan be set to Always On. 以標準費率付費。Pay at standard rates.
³ 主機中設定了這些限制。³ These limits are set in the host.
⁴您可以裝載的函式應用程式實際數目，取決於應用程式的活動、電腦實例的大小，以及對應的資源使用率。⁴ 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.
⁵儲存體限制是相同 App Service 方案中所有應用程式的暫存儲存體中的總內容大小。⁵ 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.
⁶當您的函數應用程式裝載于取用方案時，只支援 CNAME 選項。⁶ 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.
⁷保證最多60分鐘。⁷ Guaranteed for up to 60 minutes.
^{8 個}背景工作角色是裝載客戶應用程式的角色。⁸ Workers are roles that host customer apps. 背景工作角色提供三種固定大小：一個 vCPU/3.5 GB RAM;兩個 vCPU/7 GB 的 RAM;四個 vCPU/14 GB RAM。Workers are available in three fixed sizes: One vCPU/3.5 GB RAM; Two vCPU/7 GB RAM; Four vCPU/14 GB RAM.

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

Azure Kubernetes Service 限制Azure Kubernetes Service limits

¹當您使用 Azure CLI 或 Resource Manager 範本部署 Azure Kubernetes Service （AKS）叢集時，此值最多可設定為每個節點250個 pod。¹When you deploy an Azure Kubernetes Service (AKS) cluster with the Azure CLI or a Resource Manager template, this value is configurable up to 250 pods per node. 您無法在已部署 AKS 叢集之後，或使用 Azure 入口網站部署叢集時，設定每個節點的最大 pod 數。You can't configure maximum pods per node after you've already deployed an AKS cluster, or if you deploy a cluster by using the Azure portal.

Azure Machine Learning 限制Azure Machine Learning limits

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

Azure 地圖服務限制Azure Maps limits

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

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

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

Azure 監視器限制Azure Monitor limits

警示Alerts

動作群組Action groups

記錄查詢和語言Log queries and language

一般查詢限制General query limits

使用者查詢節流User query throttling

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

• 如Azure 監視器中優化記錄查詢中所述，將您的查詢優化。Optimize your queries as described in Optimize log queries in Azure Monitor.
• 儀表板和活頁簿可以在單一視圖中包含多個查詢，以在每次載入或重新整理時產生高載的查詢。Dashboards and workbooks can contain multiple queries in a single view that generate a burst of queries every time they load or refresh. 請考慮將它們分解成多個視需要載入的視圖。Consider breaking them up into multiple views that load on demand.
• 在 Power BI 中，請考慮只解壓縮匯總的結果，而不是原始記錄。In Power BI, consider extracting only aggregated results rather than raw logs.

Log Analytics 工作區Log Analytics workspaces

資料收集磁片區與保留期Data collection volume and retention

每個訂用帳戶的工作區數目。Number of workspaces per subscription.

Azure 入口網站Azure portal

資料收集器 APIData Collector API

搜尋 APISearch API

一般工作區限制General workspace limits

資料內嵌磁片區速率Data ingestion volume rate

Azure 監視器是一種大規模的資料服務，服務對象為每月需傳送數 TB 資料 (且不斷成長) 的上千名客戶。Azure Monitor is a high scale data service that serves thousands of customers sending terabytes of data each month at a growing pace. 使用診斷設定從 Azure 資源傳送之資料的預設內嵌磁片區速率限制約為每個工作區6 GB/分鐘。The default ingestion volume rate limit for data sent from Azure resources using diagnostic settings is approximately 6 GB/min per workspace. 這是估計值，因為根據記錄長度和其壓縮比率，實際大小可能會在資料類型之間有所不同。This is an approximate value since the actual size can vary between data types depending on the log length and its compression ratio. 此限制不適用於從代理程式或資料收集器 API傳送的資料。This limit does not apply to data that is sent from agents or Data Collector API.

如果您以較高的速率將資料傳送至單一工作區，則會卸載某些資料，並每隔6小時將事件傳送至工作區中的作業資料表， 而臨界值會繼續超過閾值。If you send data at a higher rate to a single workspace, some data is dropped, and an event is sent to the Operation table in your workspace every 6 hours while the threshold continues to be exceeded. 如果您的內嵌磁片區持續超過速率限制，或您希望很快就會到達，您可以傳送電子郵件至 LAIngestionRate@microsoft.com 或開啟支援要求，以要求增加您的工作區。If your ingestion volume continues to exceed the rate limit or you are expecting to reach it sometime soon, you can request an increase to your workspace by sending an email to LAIngestionRate@microsoft.com or opening a support request.

若要在您的工作區中收到這類事件的通知，請使用下列查詢建立記錄警示規則，並以大於的結果數目為零的警示邏輯基底。To be notified on such an event in your workspace, create a log alert rule using the following query with alert logic base on number of results grater than zero.

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

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.

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

Azure 原則限制Azure Policy limits

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

Azure SignalR Service 限制Azure SignalR Service limits

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

備份限制Backup limits

如需 Azure 備份支援設定和限制的摘要，請參閱Azure 備份支援矩陣。For a summary of Azure Backup support settings and limitations, see Azure Backup Support Matrices.

Batch 限制Batch limits

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

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

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

¹雖然只使用部分 CPU 核心，在計算 vCPU 限制時，仍會將超小型執行個體視為一個 vCPU。¹Extra small instances count as one vCPU toward the vCPU limit despite using a partial CPU core.

²儲存體帳戶限制包括標準和進階儲存體帳戶。²The storage account limit includes both Standard and Premium storage accounts.

Container Instances 限制Container Instances limits

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

Container Registry 登入Container Registry limits

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

每一層的每日費率包含¹個儲存體。¹ Storage included in the daily rate for each tier. 針對其他儲存體，您需支付每個 GiB 的額外每日費率，最高可達儲存體限制。For additional storage, you're charged an additional daily rate per GiB, up to the storage limit. 如需費率資訊，請參閱 Azure Container Registry 定價。For rate information, see Azure Container Registry pricing.

²ReadOps、WriteOps 和「頻寬」是最小預估值。²ReadOps, WriteOps, and Bandwidth are minimum estimates. Azure Container Registry 致力於改善需要使用時的效能。Azure Container Registry strives to improve performance as usage requires.

³docker pull 會根據映像中的圖層數目以及資訊清單擷取，來轉譯為多個讀取作業。³A docker pull translates to multiple read operations based on the number of layers in the image, plus the manifest retrieval.

⁴docker push 會根據必須推送的圖層數目，來轉譯為多個寫入作業。⁴A docker push translates to multiple write operations, based on the number of layers that must be pushed. docker push 包含 ReadOps，以擷取現有映像的資訊清單。A docker push includes ReadOps to retrieve a manifest for an existing image.

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

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

Data Factory 限制Data Factory limits

Azure Data Factory 是一種多租用戶服務，並具有以下的預設限制以確保客戶訂用帳戶不會受到彼此工作負載的影響。Azure Data Factory is a multitenant service that has the following default limits in place to make sure customer subscriptions are protected from each other's workloads. 若要提高訂用帳戶的上限，請連絡支援人員。To raise the limits up to the maximum for your subscription, contact support.

第 2 版Version 2

¹資料整合單位 (DIU) 用於雲端到雲端複製作業，請參閱資料整合單位 (第2版) 以深入了解。¹ 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.

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

³管線、資料集和連結的服務物件代表您工作負載的邏輯群組。³ 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

¹管線、資料集和連結的服務物件代表您工作負載的邏輯群組。¹ 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.

² 隨選 HDInsight 核心並非配置在包含資料處理站的訂用帳戶之中。² 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.

³第 1 版的雲端資料移動單位 (DMU) 用於雲端到雲端複製作業，請參閱雲端資料移動單位 (第 1 版) 深入了解。³ 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.

Web 服務呼叫限制Web service call limits

Azure Resource Manager 有 API 呼叫限制。Azure Resource Manager has limits for API calls. 您可使用 Azure 資源管理員 API 限制內的速率進行 API 呼叫。You can make API calls at a rate within the Azure Resource Manager API limits.

Data Lake Analytics 限制Data Lake Analytics limits

Azure Data Lake Analytics 讓管理分散式基礎結構和複雜程式碼的複雜工作變得簡單。Azure Data Lake Analytics makes the complex task of managing distributed infrastructure and complex code easy. 它會以動態方式布建資源，而您可以使用它來執行資料的 eb 分析。It dynamically provisions resources, and you can use it to do analytics on exabytes of data. 當作業完成時，它會自動股資源。When the job completes, it winds down resources automatically. 您只需支付所使用的處理能力。You pay only for the processing power that was used. 當您增加或減少儲存的資料大小或使用的計算數量時，就不需要重寫程式碼。As you increase or decrease the size of data stored or the amount of compute used, you don't have to rewrite code. 若要提高訂用帳戶的預設限制，請聯絡支援人員。To raise the default limits for your subscription, contact support.

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 Storage Gen1，在單一位置針對作業和探索性分析，捕捉任何大小、類型和內嵌速度的資料。You can use Data Lake Storage Gen1 to capture data of any size, type, and ingestion speed in one single place for operational and exploratory analytics. 您可以在 Data Lake Storage Gen1 帳戶中儲存的資料量沒有限制。There's no limit to the amount of data you can store in a Data Lake Storage Gen1 account.

資料共用限制Data Share limits

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

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.

數位 Twins 限制Digital Twins limits

功能限制Functional limits

下表列出 Azure 數位 Twins 在目前預覽中的功能限制。The table below lists the functional limits of Azure Digital Twins in the current preview.

速率限制Rate limits