Dear Santa, For Christmas please arrange for my Microsoft ID to be at peace with the World. 


For some time, I’ve been trying to live in a seamlessly joined up digital World. iPhone, PC, Mac, my car, my tablets (Surface, iPad & Android) all talking nicely to each other, all my diaries, all my inboxes, all my reminders, on every device, all in sync. Nirvana.

I’ve come close but each success brings a new hurdle to fail at. With each failure, I can’t help a wistful look at my Betamax video recorder, while I scream, silently to myself, ‘Surely it can’t be happening again!’.

In search of a backend that works with everything I’ve migrated from the dizzy uplands of Office 365 to the dark side that is Google G-Suite, and then back to Office 365 again. More of this in another post, but the news I wish to bring before my humble reader today (you know who you are) is that along the way I broke my Outlook.com, fixed it, broke everything else and, after much angst, fixed that too…

Having migrated my whole life to G-Suite, my outlook.com account lay fallow for some time. In migrating back to O365 I wanted to return to Outlook.com too (It’s where my Arsenal FC fixture list is sync’d, obviously vital). They say that absence makes the heart grow fonder, but in this case Outlook.com was basically sulking and refused to show me any of my data merely telling me that it’s server had had quite enough of my non-presence and would never talk to me again. After consulting Mr. Google I logged in to account.live.com, created myself a brand new @outlook.com email address, made it my primary alias and, hey presto! All my data was back. Hoorah! No idea what weirdness is going on in Microsoft’s back-end, but then, I’m not sure I want to know what weirdness is going on in Microsoft’s back-end.

Anyhoo, with Outlook.com working and my O365 migration done I moved on to some actual work…

Next job; publish the Xamarin forms app I’m working on to my Azure dev App Service slot. But it was not to be. When I tried to publish V2017 told me I had to re-enter my credentials. The pseudo code for the process would look something like this…

While (BeingAwkward == true)

{

    Switch (GetRussellsMicrosoftIdFromHim())

{

    Case RussellsAtOutlookComId:

BeingAwkward = true;

Break;

 

    Case RussellsOldId:

BeingAwkawrd = true;

Break;

    

Default:

BeingAwkawrd = true;

Break;

}

 

If (BeingAwkward == true || BeingAwkward == false || AnythingElse())

{

    BeingAwkward = true;

} else

{

    BeingAwkward = true;

}

}

 

 

After a happy half hour playing with this infinite loop I consulted Mr. Google again; I called Grey Matter for help (brilliant peeps, by the way); I emailed Scott Guthrie (who’s problem it isn’t, but who is, as we all know, a thoroughly bloody nice bloke). Armed with all this top notch help I soon eventually discovered the problem and the fix…

  • Creating a new alias for my Microsoft account had somehow signed me up for Visual Studio Dev Essentials which had overwritten my paid for subscription (!?).
  • To fix this I had to…
    • Go to the Volume Licensing Service Centre, sign in with my old primary Microsoft ID alias
    • Go to Relationship Summary
    • Select the right agreement (why are there two? I don’t know)
    • Change the associated email address to my new Outlook.com address
    • Logout of Visual Studio 2017 & quit
    • Clear the Visual Studio User cache (Lots of stuff on Google)
    • Restart Visual Studio & re-entered my credentials

 

Peace & calm return to the Gilbert household. Microsoft Id’s & aliases playing nicely once more, even amongst themselves. The sun shines brightly in the Azure blue sky. Who knows, the Gunners may even get something out of Crystal Palace tonight.