Azure Client VMs are an awesomely cool way to have a Windows 8.1 client in the cloud for development efforts. Assumedly you've setup your Azure Client VM and created a developer account to run under. (If you haven't see the resource links at the end of this post). But once you've got a dev account running in Azure, how do you associated a Windows Store account for your dev environment.
By associating in a Microsoft account with your DEVACCOUNT in your Client VM, a number of new capabilities will come your way. Once a Microsoft account is associated you are now "cloud enabled". At the very least, you'll be able to use OneDrive to host a shared file environment for both accounts you can use to transfer files in and out of your Client VM. You'll also be able to use Roaming Storage in your application. Roaming storage allows you to write settings into a special area of your application which is shared across all instance of an application running under that Microsoft account.
Let's look at how to setup a Microsoft Account for your Azure Client VM
Your are now signed in with your Microsoft account
And you can see how firstname.lastname@example.org is now our primary account for this Windows 8.1 instance.
Next up - Signing in from scratch with your Microsoft account to your client VM - http://blogs.msdn.com/b/devfish/archive/2014/05/27/signing-in-with-your-microsoft-account-dev-eye-for-azure-client-vms.aspx .
!!! Remember to shut down your VM if you're not using it to avoid charges.
DEV EYE FOR AZURE CLIENT VM SERIES
I've tried this and I don't see in the Accounts screen the ability to connect my local account that was used to create the VM with a Microsoft Account.