Skip to content

Commit 8237e08

Browse files
committed
Note fix
1 parent 5903f94 commit 8237e08

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

includes/functions-sql-database-authentication-note.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@
22
author: ggailey777
33
ms.service: azure-functions
44
ms.topic: include
5-
ms.date: 12/09/2024
5+
ms.date: 12/16/2024
66
ms.author: glenga
77
---
88

99
> [!IMPORTANT]
10-
> For optimal security, you should use Microsoft Entra ID with managed identities to authorize requests against your database, when possible. Microsoft Entra authentication with managed identity authorization provides the best security over shared access key authorization, and you don't have to managed keys. For more information about using managed identities with your database, see [Tutorial: Connect a function app to Azure SQL with managed identity and SQL bindings](functions-identity-access-azure-sql-with-managed-identity.md).
10+
> For optimal security, you should use Microsoft Entra ID with managed identities for connections between Functions and Azure SQL Database. Managed identities make your app more secure by eliminating secrets from your application deployments, such as credentials in the connection strings, server names, and ports being used. You can learn how to use managed identities in this tutorial, [Connect a function app to Azure SQL with managed identity and SQL bindings](../azure-functions/functions-identity-access-azure-sql-with-managed-identity.md).

0 commit comments

Comments
 (0)