The lock-lab API still embeds a SQL username and password for Azure SQL. How should the app authenticate instead?
Select an answer to reveal the explanation.
Short Explanation
Apps shouldn’t carry SQL passwords in their pockets. Give the API’s managed identity a contained user, let it grab an Entra token, and leave the password era behind.
Full Explanation
Workload authentication to Azure SQL with Microsoft Entra uses a managed identity or service principal represented as a database user, with the client obtaining an access token instead of a SQL password. Embedding or even Key Vault–stored SQL passwords still rely on SQL authentication and are weaker than identity-based access when Entra database authentication is available. Disabling Entra authentication moves in the wrong direction.