Microsoft identities - argh!

Home | Blog | Bio and Contact | CSLA .NET | CSLA Store

08 February 2017

The concept of identity with Microsoft services is a mess, something I probably don’t have to tell any Microsoft developer.

Some services can only be attached to a personal Microsoft Account (MSA), and other services can only be used from an AD account. For example, MSDN can only be directly associated with an MSA, while Office 365 can only be associated with an AD account. Some things, like VSTS, can be associated with either one depending on the scenario.

I used to have the following:

  • - MSA with my MSDN associated
  • - Magenic AD account
  • - MSA with nothing attached (I created this long ago and forgot about it)

That was a total pain when I started using O365 and an AD-linked VSTS site with my AD account, because Microsoft couldn’t automatically distinguish between my AD and MSA accounts; both named As a result, every time I tried to log into one of these sites they’d ask if this was a personal or work/school account.

Fortunately you can rename an MSA to a different email address. I renamed my (essentially unused) account to a dummy email address so now I really just have two identities:

  • - MSA with my MSDN associated
  • - Magenic AD account

This way Microsoft automatically knows that when I use my AD login that it is a work/school account and I don’t have to mess with that confusion.

There’s still the issue of having MSDN attached to an MSA, and also needing to have some connection from my AD account to my MSDN subscription. This is required because we have VSTS sites associated with Magenic’s AD, so I need to log in with my AD account, but still need to ensure VSTS knows I’m a valid MSDN user.

Here’s info on how to link your work account to your MSDN/MSA account.

At the end of the day, if I’d never created that MSA account (many years ago) my life would have been much simpler to start. Fortunately the solution to that problem is to rename the MSA email to something else and remove the confusion between AD and MSA.

The MSDN linking makes sense, given that you need an MSA for MSDN, and many of us need corporate AD credentials for all our work sites.