Skip to content

Commit fb69a7f

Browse files
committed
fix PR breaks
Signed-off-by: Hannah Hunter <[email protected]>
1 parent f8ff5f0 commit fb69a7f

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/azure-functions/durable/durable-functions-mssql-container-apps-hosting.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,8 @@ Your Durable Functions also needs an Azure SQL Database as its storage backend.
171171
- Enable Azure services and resources to access this server (under **Networking**)
172172
- Set the value for **Database collation** (under **Additional settings**) to `Latin1_General_100_BIN2_UTF8`.
173173

174-
> [!NOTE] Enabling the **Allow Azure services and resources to access this server** setting isn't a recommended security practice for production scenarios. Real applications should implement more secure approaches, such as stronger firewall restrictions or virtual network configurations.
174+
> [!NOTE]
175+
> Enabling the **Allow Azure services and resources to access this server** setting isn't a recommended security practice for production scenarios. Real applications should implement more secure approaches, such as stronger firewall restrictions or virtual network configurations.
175176
176177
### Configure identity-based authentication
177178
Managed identities make your app more secure by eliminating secrets from your app, such as credentials in the connection strings. You can choose between [system-assigned and user-assigned managed identity](/entra/identity/managed-identities-azure-resources/overview). This article demonstrates setting up user-assigned managed identity, which is the recommended option as it isn't tied to the app lifecycle.
@@ -210,7 +211,7 @@ Managed identities make your app more secure by eliminating secrets from your ap
210211
### Set up app settings
211212
1. Start by storing the SQL database's connection string as a [secret](../../container-apps/manage-secrets.md) in the container app. Find the connection string by going to the SQL database resource on Azure portal, navigating to the **Settings** tab, then clicking on **Connection strings**:
212213
213-
:::image type="content" source="/media/quickstart-mssql/mssql-azure-db-connection-string.png" alt-text="Screenshot showing database connection string.":::
214+
:::image type="content" source="./media/quickstart-mssql/mssql-azure-db-connection-string.png" alt-text="Screenshot showing database connection string.":::
214215
215216
The connection string should have this format:
216217
```bash
@@ -226,7 +227,7 @@ Managed identities make your app more secure by eliminating secrets from your ap
226227
> Authenticating to the MSSQL database using managed identity isn't yet supported when hosting a Durable Functions app in Azure Container Apps. Only connection string is supported today.
227228
>
228229
> If you forget the password from the previous database creation step, you can reset it on the SQL server resource:
229-
> :::image type="content" source="/media/quickstart-mssql/mssql-azure-reset-pass-2.png" alt-text="Screenshot showing reset password button.":::
230+
> :::image type="content" source="./media/quickstart-mssql/mssql-azure-reset-pass-2.png" alt-text="Screenshot showing reset password button.":::
230231
231232
1. Store the connection string as a secret:
232233
@@ -242,7 +243,7 @@ Managed identities make your app more secure by eliminating secrets from your ap
242243
1. Add these settings required by the app:
243244
- `AzureWebJobsStorage__accountName`: <STORAGE_NAME>
244245
- `AzureWebJobsStorage__clientId`: <IDENTITY_CLIENT_ID>
245-
- `AzureWebJobsStorage__credential`: <managedidentity>
246+
- `AzureWebJobsStorage__credential`: <MANAGED_IDENTITY>
246247
- `SQLDB_Connection`: <SQLDB_CONNECTION_STRING>
247248
- `FUNCTIONS_WORKER_RUNTIME`: <APP_LANGUAGE>
248249

0 commit comments

Comments
 (0)