Combining @domain.com and @domain.onmicrosoft.com

[Velvis]

Moving a single user to M365 hosted account. Email is flowing like it should (ie email sent to domain.com is being received like it should) but their @domain.com address is tied to a standard Microsoft account (no actual email associated with it) so they need to use the @domain.onmicrosoft.com address to login to M365. Is there a way to make it so they can just login to M365 with their domain.com account?

 

[nlinecomputers]

Did you make the domain the default login? https://learn.microsoft.com/en-us/microsoft-365/admin/setup/domains-faq?view=o365-worldwide

 

[nlinecomputers]

Note that having the same email address for a personal Microsoft Account and a Microsoft 365 account can cause issues. It is best to log in to the personal account and create a new @outlook.com email address for that account, make it the default login, and then delete the conflicting address. Nothing will be lost that is associated with that account.

 

[Velvis]

Did you make the domain the default login? https://learn.microsoft.com/en-us/microsoft-365/admin/setup/domains-faq?view=o365-worldwide

Yes it is the default.

 

[Velvis]

Note that having the same email address for a personal Microsoft Account and a Microsoft 365 account can cause issues. It is best to log in to the personal account and create a new @outlook.com email address for that account, make it the default login, and then delete the conflicting address. Nothing will be lost that is associated with that account.

I will check that out. Thank you.

 

[nlinecomputers]

On 365 You also have to change the default alias login for the user if you created the user before changing the domain default.

 

[callthatgirl]

Almost every client I have has this issue. It's a gift and a horror story at the same time. I make sure to check this during my onboarding for every client, can haunt you later down the road. I don't always detach the personal accounts but if you don't, Outlook sometimes doesn't connect without the regfix. Still a nightmare either way.

 

[YeOldeStonecat]

I myself have a personal Microsoft account based on my work email address...that I've had for many many years (pre-365 years)...and then when 365 came out we jumped on that...of course..work email address for that too. It's really not a big deal. Things still work great.

Couple of ways to work this.
*...ANY time you log into office.com you should be presented with a CHOICE of "Log into your work/school, or log into Microsoft <personal>". You click the work/school. Once the apps are set the first time...they should remain settled.
*If the computer was setup with the user profile as the personal Microsoft account, nuke it, join AzureAD...and then log in with the Azure profile which will set that user profile as the work/school account and lock it in from there. Just like if you had a local active directory, any...rather...ALL...workstations you setup on that network, you have them "join the domain"...right? You don't leave workstations in "workgroup mode" for those. So with 365..set them up right...join AzureAD. It lets everything drive home perfectly...and all the computer profiles (MEMs version of group policy) you setup for the computers properly take hold and everything runs like a dream.

I have quite a few clients that have both personal and work MS accounts with the same password. Not my job to manage their personal MS accounts, but I never let them interfere with their wok accounts. Microsofts login will always challenge you with that "choose a work/school account, or your personal account" popup...where you click on the one you want.

So..join AzureAD.

 

[brandonkick]

Note that having the same email address for a personal Microsoft Account and a Microsoft 365 account can cause issues. It is best to log in to the personal account and create a new @outlook.com email address for that account, make it the default login, and then delete the conflicting address. Nothing will be lost that is associated with that account.

This is what I would do. "un hook" the user@domain.com from the standard microsoft account and then add the domain to the 0365 account, and cut over the user names.