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
|[Core Tools deployment](./functions-run-local.md#deploy-containers)|[`func azurecontainerapps`](./functions-core-tools-reference.md#func-azurecontainerapps-deploy)| No | No | No |[`func kubernetes`](./functions-core-tools-reference.md#func-kubernetes-deploy)|
|[Core Tools deployment](./functions-run-local.md#deploy-containers)|No| No | No | No |[`func kubernetes`](./functions-core-tools-reference.md#func-kubernetes-deploy)|
| Diagnostics |Not currently available<sup>4</sup>|[Yes](../container-apps/troubleshooting.md#use-the-diagnose-and-solve-problems-tool)|[Yes](./functions-diagnostics.md)|[Yes](./functions-diagnostics.md)| No |
49
+
|[App Service authentication](../app-service/overview-authentication-authorization.md)|[Yes](../container-apps/authentication.md)| Yes | Yes | Yes | No |
| Diagnostics |[Yes](../container-apps/troubleshooting.md#use-the-diagnose-and-solve-problems-tool)|[Yes](../container-apps/troubleshooting.md#use-the-diagnose-and-solve-problems-tool)|[Yes](./functions-diagnostics.md)|[Yes](./functions-diagnostics.md)| No |
| Dedicated GPUs | Yes ([workload profiles](../container-apps/workload-profiles-overview.md)) | Yes ([workload profiles](../container-apps/workload-profiles-overview.md)) | No | No | Yes |
57
57
|[Configurable memory/CPU count](../container-apps/workload-profiles-overview.md)| Yes | Yes | No | No | Yes |
@@ -62,7 +62,6 @@ The degree to which various features and behaviors of Azure Functions are suppor
62
62
1. On Container Apps, the default is 10 instances, but you can set the [maximum number of replicas](../container-apps/scale-app.md#scale-definition), which has an overall maximum of 1000. This setting is honored as long as there's enough cores quota available. When you create your function app from the Azure portal, you're limited to 300 instances.
63
63
2. In some regions, Linux apps on a Premium plan can scale to 100 instances. For more information, see the [Premium plan article](functions-premium-plan.md#region-max-scale-out). <br/>
64
64
3. For specific limits for the various App Service plan options, see the [App Service plan limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-app-service-limits).
65
-
4. Feature parity is a goal of integrated hosting on Azure Container Apps.
66
65
5. Requires [KEDA](./functions-kubernetes-keda.md); supported by most triggers. To learn which triggers support event-driven scaling, see [Considerations for Container Apps hosting](functions-container-apps-hosting.md#considerations-for-container-apps-hosting).
67
66
6. When the [minimum number of replicas](../container-apps/scale-app.md#scale-definition) is set to zero, the default timeout depends on the specific triggers used in the app.
68
67
7. There's no maximum execution timeout duration enforced. However, the grace period given to a function execution is 60 minutes [during scale in](event-driven-scaling.md#scale-in-behaviors), and a grace period of 10 minutes is given during platform updates.
0 commit comments