![]() ![]() ![]() ![]() SQL Server Authentication from a client on any computer.Windows Authentication when the client and server are running on the same computer.I have been unable to connect a client on one machine to SQL Server on another machine using Windows Authentication when logged into Windows with my Office 365 Azure AD credentials (i.e.I just built my first computer with a SQL Server instance since switching to the new Windows authentication method, and: The transition has been a little rocky, but I have the basics working, like sharing folders and setting file permissions with the new Office 365 AD users. This is only using the lightweight Azure AD that backs Office 365 when you log into Windows using a Microsoft "work or school" account. My machines are still just part of a workgroup, not a domain. NOTE: In case you're unfamiliar with this setup, it's essentially using a lightweight Azure Active Directory (AD) instance that supports my Office 365 subscription. Now my Windows username is AzureAD\MichaelMannion, instead of a local name like citra\Michael (where "citra" is the name of the local Windows computer). Here's the relevant Windows Settings screen: I've recently switched to logging into Windows with my Office 365 credentials, instead of with a local Windows user. In this scenario, Windows automatically recognizes me as the "same" user (albeit with a different SID) and allows me to connect without additional prompts for credentials.Īmong other things, I could use a SQL Server client on one machine to connect to a SQL Server instance on another machine via Windows Authentication. Historically, I've created a local user on each computer with the same username/password in order to share resources, such as filesystems and SQL Server. These computers are part of a Windows workgroup - they are not joined to a domain. I have a home office with several Windows computers for testing. ![]()
0 Comments
Leave a Reply. |