<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sql on Sminkware.com</title><link>https://sminkware.com/blog/sql/</link><description>Recent content in Sql on Sminkware.com</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2026, Jeroen Smink.</copyright><lastBuildDate>Thu, 25 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sminkware.com/blog/sql/index.xml" rel="self" type="application/rss+xml"/><item><title>Credential-less SQL Authentication for Azure SQL</title><link>https://sminkware.com/credential-less-sql-authentication-for-azure-sql/</link><pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate><guid>https://sminkware.com/credential-less-sql-authentication-for-azure-sql/</guid><description>&lt;p>Azure SQL lets you authenticate with Managed Identities. No username or password in your app.&lt;/p>
&lt;p>Microsoft Entra authentication must be configured in two places: on the Azure SQL resource itself and inside the database. I only figured that out after spending quite a bit of time troubleshooting.&lt;/p>
&lt;p>My Web App&amp;rsquo;s managed identity had &lt;code>Contributor&lt;/code> on the SQL server, but connections still failed with &amp;ldquo;Login failed for user&amp;rdquo; until I ran &lt;code>CREATE USER&lt;/code> inside the database. RBAC on the Azure resource is not the same as a database login.&lt;/p></description></item></channel></rss>