We have a few developers that work, connecting in through a VPN for access to the development SQL Server 2012. Historically they've used Win7 machines and develop the website against this database in Visual Studio, using the built-in webserver for debugging. This worked great forever. There is no domain, the user just creates an identical windows account on the dev server with identical username/password, we add the user to a DBAdmin group, and magic, it works.
With the advent of Win8, you can (and are pushed to) use a Microsoft Account (read: live/passport account) to log into your local machine. There are benefits to doing so, such as sync of app and OS settings between machines, etc., as well as not having to type in your live id/password everytime you do something.
If you convert your local account to a Microsoft Account, you can no longer use trusted connections to connect to the SQL Server, as it apparently completely subsumes your original local account.
Does anyone know of a way to create a user on say a Server 2003 or Server 2008 machine that will somehow match the live account being used? I imagine this is going to be a headache for people not just because of trusted connections, but also file sharing, though with file sharing there's a work-around of being able to connect with the account and check a box to save the username/password, that option doesn't exist for SQL Server connections.