Skip to content

Latest commit

 

History

History
48 lines (46 loc) · 5.84 KB

functions-limits.md

File metadata and controls

48 lines (46 loc) · 5.84 KB
author ms.service ms.custom ms.topic ms.date ms.author
ggailey777
azure-functions
build-2024
include
02/02/2025
glenga
Resource Flex Consumption plan Premium plan Dedicated plan/ASE Container Apps Consumption plan
Default time-out duration (min) 30 30 301 3016 5
Max time-out duration (min) unbounded9 unbounded9 unbounded2 unbounded17 10
Max outbound connections (per instance) unbounded unbounded unbounded unbounded 600 active (1200 total)
Max request size (MB)3 210 210 210 210 210
Max query string length3 4096 4096 4096 4096 4096
Max request URL length3 8192 8192 8192 8192 8192
ACU per instance 210-840 100-840/210-25010 varies 100 varies
Max memory (GB per instance) 414 3.5-14 1.75-256/8-256 varies 1.5
Max instance count (Windows | Linux) n/a | 100015 varies by S KU | 10011 10-30018 200 | 100 1000
Function apps per plan13 1 100 unbounded4 unbounded4 100
App Service plans n/a 100 per resource group 100 per resource group n/a 100 per region
Deployment slots per app12 n/a 3 1-2011 not supported 2
Storage (temporary)5 0.8 GB 21-140 GB 11-140 GB n/a 0.5 GB
Storage (persisted) 0 GB7 250 GB 10-1000 GB11 n/a 1 GB6,7
Custom domains per app 500 500 500 not supported 5007
Custom domain TSL/SSL support unbounded SNI SSL and one IP SSL connection included unbounded SNI SSL and one IP SSL connection included unbounded SNI SSL and one IP SSL connection included not supported unbounded SNI SSL connection included

Notes on service limits:

  1. By default, the time-out for the Functions 1.x runtime in an App Service plan is unbounded.
  2. Requires the App Service plan be set to Always On. Pay at standard rates. A grace period of 10 minutes is given during platform updates.
  3. These limits are set in the host.
  4. The actual number of function apps that you can host depends on the activity of the apps, the size of the machine instances, and the corresponding resource utilization.
  5. The storage limit is the total content size in temporary storage across all apps in the same App Service plan. For Consumption plans on Linux, the storage is currently 1.5 GB.
  6. Consumption plan uses an Azure Files share for persisted storage. When you provide your own Azure Files share, the specific share size limits depend on the storage account you set for WEBSITE_CONTENTAZUREFILECONNECTIONSTRING.
  7. On Linux, you must explicitly mount your own Azure Files share.
  8. When your function app is hosted in a Consumption plan, only the CNAME option is supported. 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.
  9. There's no maximum execution time-out duration enforced. However, the grace period given to a function execution is 60 minutes during scale in and 10 minutes during platform updates.
  10. Workers are roles that host customer apps. Workers are available in three fixed sizes: One vCPU/3.5 GB RAM; Two vCPU/7 GB RAM; Four vCPU/14 GB RAM.
  11. See App Service limits for details.
  12. Including the production slot.
  13. There's currently a limit of 5,000 function apps in a given subscription.
  14. Flex Consumption plan instance sizes are currently defined as either 2,048 MB or 4,096 MB. For more information, see Instance memory.
  15. Flex Consumption plan has a regional subscription quota that limits the total memory usage of all instances across a given region. For more information, see Instance memory.
  16. When the minimum number of replicas is set to zero, the default time-out depends on the specific triggers used in the app.
  17. When the minimum number of replicas is set to one or more.
  18. On Container Apps, you can set the maximum number of replicas, which is honored as long as there's enough cores quota available.