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/durable/durable-functions-mssql-container-apps-hosting.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ ms.topic: how-to
5
5
ms.date: 05/06/2025
6
6
---
7
7
8
-
# Host a Durable Functions app in Azure Container Apps
8
+
# Host a Durable Functions app in Azure Container Apps (.NET isolated)
9
9
10
10
Azure Functions provides integrated support for developing, deploying, and managing containerized Function Apps on Azure Container Apps. Use Azure Container Apps for your Functions apps when you need to run in the same environment as other microservices, APIs, websites, workflows, or any container hosted programs. Learn more about [running Azure Functions in Container Apps](../../container-apps/functions-overview.md).
11
11
@@ -163,7 +163,6 @@ A [workload profile](../functions-container-apps-hosting.md#hosting-and-workload
163
163
--resource-group $resourceGroup \
164
164
--name $containerAppEnv \
165
165
--location $location \
166
-
--infrastructure-subnet-resource-id $subnetId
167
166
```
168
167
169
168
1. Create a container app based on the Durable Functions image.
@@ -178,7 +177,7 @@ A [workload profile](../functions-container-apps-hosting.md#hosting-and-workload
178
177
--query properties.outputs.fqdn
179
178
```
180
179
181
-
1. Make note of the app URL, which should look similar to `https://<APP_NAME>.victoriouswave-3866c33e.<REGION>.azurecontainerapps.io`.
180
+
1. Make note of the app URL, which should look similar to `https://<APP_NAME>.<ENVIRONMENT_IDENTIFIER>.<REGION>.azurecontainerapps.io`.
182
181
183
182
### Create databases
184
183
@@ -235,22 +234,22 @@ In this section, you set up **user-assigned managed identity** for Azure Storage
1. Assign the role `Storage Blob Data Owner` role for access to the storage account.
237
+
1. Assign the role **Storage Blob Data Owner** role for access to the storage account.
239
238
240
239
```azurecli
241
240
echo "Assign Storage Blob Data Owner role to identity"
242
241
az role assignment create --assignee "$clientId" --role "Storage Blob Data Owner" --scope "$scope"
243
242
```
244
243
245
244
### Set up app settings
246
-
247
-
Authenticating to the MSSQL database using managed identity isn't supported when hosting a Durable Functions app in Azure Container Apps. For now, this guide authenticates using connection strings.
245
+
> [!NOTE]
246
+
> Authenticating to the MSSQL database using managed identity isn't supported when hosting a Durable Functions app in Azure Container Apps. For now, this guide authenticates using connection strings.
248
247
249
248
1. From the SQL database resource in the Azure portal, navigate to **Settings** > **Connection strings** to find the connection string.
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/quickstart-mssql.md
+7-12Lines changed: 7 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,11 +76,6 @@ Another file, *HelloOrchestration.cs*, contains the basic building blocks of a D
76
76
77
77
For more information about these functions, see [Durable Functions types and features](./durable-functions-types-features-overview.md).
78
78
79
-
#### Check for latest extension version
80
-
For .NET apps, check the `.csproj` file and make sure the latest version of the [Microsoft.Azure.Functions.Worker.Extensions.DurableTask](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask) package is referenced.
81
-
82
-
"Non-.NET apps" references the extension bundles, which automatically use the latest package.
83
-
84
79
## Set up your database
85
80
86
81
> [!NOTE]
@@ -218,13 +213,13 @@ To run your app in Azure, you need to create various resources. For convenient c
218
213
219
214
> [!NOTE]
220
215
> If you already have an Azure SQL database or another publicly accessible SQL Server instance that you would like to use, you can go to the next section.
216
+
>
217
+
> Refrain from enabling the **Allow Azure services and resources to access this [SQL] server** setting for production scenarios. Real applications should implement more secure approaches, such as stronger firewall restrictions or virtual network configurations.
221
218
222
219
In the Azure portal, you can [create an Azure SQL database](/azure/azure-sql/database/single-database-create-quickstart). During creation:
223
220
- Enable Azure services and resources to access this server (under _Networking_)
224
221
- Set the value for _Database collation_ (under _Additional settings_) to `Latin1_General_100_BIN2_UTF8`.
225
222
226
-
Enabling the **Allow Azure services and resources to access this server** setting is _not_ a recommended security practice for production scenarios. Real applications should implement more secure approaches, such as stronger firewall restrictions or virtual network configurations.
227
-
228
223
### Create an Azure Functions app and supporting resources
@@ -301,7 +296,7 @@ az role assignment create --assignee "$clientId" --role "Storage Blob Data Owner
301
296
302
297
#### Azure SQL Database
303
298
>[!NOTE]
304
-
> Authenticating to the MSSQL database using managed identity is _not_ supported when hosting a Durable Functions app in the Flex Consumption plan. Use connection string for now. Thus, if your app is hosted in the Flex Consumption plan, skip to the [set app application settings](#set-required-app-settings) section.
299
+
> Authenticating to Azure SQL database using managed identity is _not_ supported when hosting a Durable Functions app in the Flex Consumption plan. If your app is hosted in the Flex Consumption plan, skip to the [set app settings](#set-required-app-settings) section.
305
300
306
301
1. Start by setting your developer identity as the database's admin.
307
302
@@ -315,7 +310,7 @@ az role assignment create --assignee "$clientId" --role "Storage Blob Data Owner
315
310
az sql server ad-admin create --resource-group $resourceGroup --server-name <SQL_SERVER_NAME> --display-name ADMIN --object-id "$assignee"
316
311
```
317
312
318
-
1. Connect to the SQL database created previously using tools such as [Azure Data Studio](/azure-data-studio/download-azure-data-studio) or [SQL Management Server Studio](/ssms/download-sql-server-management-studio-ssms) to grant access to the managed identity. Or you can run the following [SQLCMD](/sql/tools/sqlcmd/sqlcmd-utility) command to connect:
313
+
1. Connect to the SQL database created previously using tools such as [Azure Data Studio](/azure-data-studio/download-azure-data-studio) or [SQL Management Server Studio](/ssms/download-sql-server-management-studio-ssms). Or you can run the following [SQLCMD](/sql/tools/sqlcmd/sqlcmd-utility) command to connect:
If you're using a simple connection string to authenticate, you can find it by going to the SQL database resource on Azure portal, navigating to the **Settings** tab, then clicking on **Connection strings**:
347
+
For Flex Consumption apps, use a connection string to authenticate for now. You can find it by going to the SQL database resource on Azure portal, navigating to the **Settings** tab, then clicking on **Connection strings**:
0 commit comments