SQL Server Database Engine
Core component of SQL Server for storing, processing, and securing data
Creating LinkedServer between On-Prem SQL to Azure SQL MI
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 30%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Santosh
41
Reputation points
Hi,
is it possible to use security option (Be made using the login's current security context )with lnikedserver from on-prem SQL to MI ?
Our MI is enabled for windows auth and we are successfully connect MI in SSMS using windows auth from on-prem client.
when I use this option in linkedserver and try to access linked server with windows auth I get following error.
Login failed for user '<token-identified principal>'. Reason: Could not find a user matching the name provided
SQL Server Database Engine
-
Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator2025-03-10T22:48:04.9566667+00:00 I can't say neither aye no nay to this one, because I don't know. But always in this case, there is a double-hop issue. That is, the on-prem server must be able to pass the security context to the remote server. This requires Kerberos, SPNs and other things I'm not good at.
But start checking in sys.dm_exec_connections that when connecting to the on-prem server that it does says KERBEROS and not NTLM.
-
Santosh 41 Reputation points
2025-03-11T12:29:11.12+00:00 SPN is already set for on-prem and connection is KERBEROS. I am even able to connect MI using windows auth from on-prem . the only issue when I create linked server form on-prem to MI
Sign in to comment
Sign in to answer