This probably seems like the obscurest of issues, but I suspect many people will encounter it, since Microsoft are encouraging us to make a non-conflicting alias primary. So… this all kind of makes sense once we put the pieces together, although it would be good if the Microsoft Account Manage How You Sign In to Microsoft page offered an explanation of why the alias cannot be made primary. The secondary issue here is that we hadn’t expected this restriction to take effect if the new alias didn’t in fact exist as an Azure AD username. In my case (and my colleague’s), we added aliases to our Microsoft Accounts from registered domain names before Microsoft put this registered domain name restriction in place and we were trying to make these e-mail aliases our new primary Microsoft Account username after the restriction was introduced. Organisations may register domain names with Azure AD either to prove ownership of a domain name for account creation, or for e-mail addresses/aliases.
After a bit of testing, it appears that the restriction is scoped at the Azure AD Registered Domain Name. This is precisely the restriction that Microsoft has put in place to prevent unnecessary Home Realm Discovery prompts, but we are unexpectedly seeing it when adding an alias. I would get this, “You can’t add a work or school/university email address as an alias to a personal Microsoft account. Then, after a helpful suggestion from Oren Novotny I tried removing and adding the alias to see if that changed anything. We tried a few things like signing on with the alias to see if that made a difference, but the option never appeared. Stuck! My colleague had five non-primary aliases, and just one of them was also missing this option. If I tried to remove the primary alias I was told to make the other alias primary first. However, when I tried to make my new alias primary, the option was missing. That prompt links to this support article. Interestingly, there is also now a link in some of these dialogue boxes which will prompt a user to resolve the issue by changing their conflicting Microsoft account username to some new alias.
Unsure if this is relevant to you? It is if you see this: This is natural, and expected behaviour, but Microsoft has been taking steps to improve this experience, as detailed in their Cleaning up the #AzureAD and Microsoft account overlap article. If you have a Microsoft Account (Live ID) username or alias that matches your Work or School Account (Azure AD) UPN, you will probably see a Home Realm Discovery prompt with annoying regularity.
0 kommentar(er)
