Forum Discussion
Advocate IVODBC driver connect to Fabric
Hey schneiw
You're doing everything right, using the non-interactive "Microsoft Entra ID Password authentication" option, credentials are correct, MFA is excluded, and it even works fine in SSMS. So honestly, you'd expect the ODBC driver to behave the same way, just take the username and password and connect. But instead, it throws that annoying “InteractionRequired” error anyway. Really confusing. From what I’ve seen, and based on that GitHub issue you linked, it does seem like the ODBC driver (especially version 18) is acting up in scenarios like this. Even though you're not using interactive auth, it's still trying to trigger something interactive behind the scenes, which kind of defeats the purpose. It feels like the driver is either not fully honoring the selected auth method or maybe it’s hitting some unexpected behavior when used in linked server setups or background processes.
__________________________________________________________________________________________________________________________If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
Regards,
Akhil.
Hey schneiw
You're doing everything right, using the non-interactive "Microsoft Entra ID Password authentication" option, credentials are correct, MFA is excluded, and it even works fine in SSMS. So honestly, you'd expect the ODBC driver to behave the same way, just take the username and password and connect. But instead, it throws that annoying “InteractionRequired” error anyway. Really confusing. From what I’ve seen, and based on that GitHub issue you linked, it does seem like the ODBC driver (especially version 18) is acting up in scenarios like this. Even though you're not using interactive auth, it's still trying to trigger something interactive behind the scenes, which kind of defeats the purpose. It feels like the driver is either not fully honoring the selected auth method or maybe it’s hitting some unexpected behavior when used in linked server setups or background processes.
__________________________________________________________________________________________________________________________
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
Regards,
Akhil.
Advocate IVThanks for confirming.
I tried the Service Principal option and that one works fine. I guess we just have to wait for MS to fix the bug.
Thank you, I will accept your answer as solution.