You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Max memory (GB per instance) | 1.5 | 4<sup>14</sup> | 3.5-14 | 1.75-14/3.5-14 |[varies](/azure/container-apps/billing)|
20
+
| Max instance count (Windows/Linux) | 200/100 | 1000 <sup>15</sup> | 100/20 | varies by SKU/100<sup>10</sup> | 10-300<sup>19</sup> |
21
+
| Function apps per plan<sup>12</sup> | 100 | 100 | 100 | unbounded<sup>4</sup> | unbounded<sup>4</sup> |
22
22
|[App Service plans](/azure/app-service/overview-hosting-plans)| 100 per [region](https://azure.microsoft.com/global-infrastructure/regions/)| n/a | 100 per resource group |100 per resource group | n/a |
23
-
|[Deployment slots](/azure/azure-functions/functions-deployment-slots) per app<sup>10</sup> | 2 | n/a | 3 | 1-20<sup>9</sup> | not supported |
| Custom domains per app</a> |500<sup>7</sup> | 500 | 500 | 500 | not supported |
26
27
| Custom domain [SSL support](/azure/app-service/configure-ssl-bindings)|unbounded SNI SSL connection included | unbounded SNI SSL and 1 IP SSL connections included | unbounded SNI SSL and 1 IP SSL connections included |unbounded SNI SSL and 1 IP SSL connections included | not supported |
27
28
28
29
Notes on service limits:
@@ -31,17 +32,18 @@ Notes on service limits:
31
32
2. Requires the App Service plan be set to [Always On](/azure/azure-functions/dedicated-plan#always-on). Pay at standard [rates](https://azure.microsoft.com/pricing/details/app-service/).
32
33
3. These limits are [set in the host](https://github.com/Azure/azure-functions-host/blob/dev/src/WebJobs.Script.WebHost/web.config).
33
34
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.
34
-
5. The storage limit is the total content size in temporary storage across all apps in the same App Service plan. Consumption plan uses Azure Files for temporary storage.
35
-
6. When your function app is hosted in a [Consumption plan](/azure/azure-functions/consumption-plan), only the CNAME option is supported. For function apps in a [Premium plan](/azure/azure-functions/functions-premium-plan) or an [App Service plan](/azure/azure-functions/dedicated-plan), you can map a custom domain using either a CNAME or an A record.
36
-
7. Guaranteed for up to 60 minutes.
37
-
8. 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.
38
-
9. See [App Service limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits) for details.
39
-
10. Including the production slot.
40
-
11. There's currently a limit of 5000 function apps in a given subscription.
41
-
12. The Flex Consumption plan is currently in preview.
42
-
13. Flex Consumption plan instance sizes are currently defined as either 2,048 MB or 4,096 MB. For more information, see [Instance memory](/azure/azure-functions/flex-consumption-plan#instance-memory).
43
-
14. Flex Consumption plan during preview has a regional subscription quota that limits the total memory usage of all instances across a given region. For more information, see [Instance memory](/azure/azure-functions/flex-consumption-plan#instance-memory).
44
-
15. In a Flex Consumption plan, the host doesn't enforce an execution time limit. However, there are currently no guarantees because the platform might need to terminate your instances during scale-in, deployments, or to apply updates.
45
-
16. When the [minimum number of replicas](/azure/container-apps/scale-app#scale-definition) is set to zero, the default timeout depends on the specific triggers used in the app.
46
-
17. When the [minimum number of replicas](../articles/container-apps/scale-app.md#scale-definition) is set to one or more.
47
-
18. On Container Apps, you can set the [maximum number of replicas](/azure/container-apps/scale-app#scale-definition), which is honored as long as there's enough cores quota available.
35
+
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 guaranteed to be at least 500MB.
36
+
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](/azure-functions/functions-app-settings#website_contentazurefileconnectionstring). On Linux Consumption, you must provide your own Azure Files share.
37
+
7. When your function app is hosted in a [Consumption plan](/azure/azure-functions/consumption-plan), only the CNAME option is supported. For function apps in a [Premium plan](/azure/azure-functions/functions-premium-plan) or an [App Service plan](/azure/azure-functions/dedicated-plan), you can map a custom domain using either a CNAME or an A record.
38
+
8. Guaranteed for up to 60 minutes.
39
+
9. 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.
40
+
10. See [App Service limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits) for details.
41
+
11. Including the production slot.
42
+
12. There's currently a limit of 5000 function apps in a given subscription.
43
+
13. The Flex Consumption plan is currently in preview.
44
+
14. Flex Consumption plan instance sizes are currently defined as either 2,048 MB or 4,096 MB. For more information, see [Instance memory](/azure/azure-functions/flex-consumption-plan#instance-memory).
45
+
15. Flex Consumption plan during preview has a regional subscription quota that limits the total memory usage of all instances across a given region. For more information, see [Instance memory](/azure/azure-functions/flex-consumption-plan#instance-memory).
46
+
16. In a Flex Consumption plan, the host doesn't enforce an execution time limit. However, there are currently no guarantees because the platform might need to terminate your instances during scale-in, deployments, or to apply updates.
47
+
17. When the [minimum number of replicas](/azure/container-apps/scale-app#scale-definition) is set to zero, the default timeout depends on the specific triggers used in the app.
48
+
18. When the [minimum number of replicas](../articles/container-apps/scale-app.md#scale-definition) is set to one or more.
49
+
19. On Container Apps, you can set the [maximum number of replicas](/azure/container-apps/scale-app#scale-definition), which is honored as long as there's enough cores quota available.
0 commit comments