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
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-container-apps-hosting.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ Keep in mind the following considerations when deploying your function app conta
107
107
+ You can use managed identities for these connections:
108
108
+[Deployment from an Azure Container Registry](functions-deploy-container-apps.md?tabs=acr#create-and-configure-a-function-app-on-azure-with-the-image)
109
109
+[Triggers and bindings](functions-reference.md#configure-an-identity-based-connection)
+ When either your function app and Azure Container Registry-based deployment use managed identity-based connections, you can't modify the CPU and memory allocation settings in the portal. You must instead [use the Azure CLI](functions-how-to-custom-container.md?tabs=acr%2Cazure-cli2%2Cazure-cli&pivots=container-apps#container-apps-workload-profiles).
112
112
+ You currently can't move a Container Apps hosted function app deployment between resource groups or between subscriptions. Instead, you would have to recreate the existing containerized app deployment in a new resource group, subscription, or region.
113
113
+ When using Container Apps, you don't have direct access to the lower-level Kubernetes APIs.
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-infrastructure-as-code.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,7 +169,7 @@ You need to set the connection string of this storage account as the `AzureWebJo
169
169
170
170
Deployments to an app running in the Flex Consumption plan require a container in Azure Blob Storage as the deployment source. You can use either the default storage account or you can specify a separate storage account. For more information, see [Configure deployment settings](flex-consumption-how-to.md#configure-deployment-settings).
171
171
172
-
This deployment account must already be configured when you create your app, including the specific container used for deployments. To learn more about configuring deployments, see [Deployment sources](#deployment-sources-2).
172
+
This deployment account must already be configured when you create your app, including the specific container used for deployments. To learn more about configuring deployments, see [Deployment sources](#deployment-sources).
173
173
174
174
This example shows how to create a container in the storage account:
175
175
@@ -187,7 +187,7 @@ For the snippet in context, see [this deployment example](https://github.com/Azu
187
187
188
188
---
189
189
190
-
Other deployment settings are [configured with the app itself](#deployment-sources-2).
190
+
Other deployment settings are [configured with the app itself](#deployment-sources).
191
191
192
192
::: zone-end
193
193
### Enable storage logs
@@ -1243,8 +1243,6 @@ For a complete reference example, see [this ARM template](https://github.com/Azu
1243
1243
When using a connection string instead of managed identities, you need to instead set the `authentication.type` to `StorageAccountConnectionString` and set `authentication.storageAccountConnectionStringName` to the name of the application setting that contains the deployment storage account connection string.
1244
1244
::: zone-end
1245
1245
::: zone pivot="consumption-plan"
1246
-
## Deployment sources
1247
-
1248
1246
Your Bicep file or ARM template can optionally also define a deployment for your function code using a [zip deployment package](./deployment-zip-push.md).
1249
1247
::: zone-end
1250
1248
::: zone pivot="dedicated-plan,premium-plan,consumption-plan"
@@ -1752,12 +1750,11 @@ These site settings are required on the `siteConfig` property:
0 commit comments