Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
On a Mac with the same email address now tied to a new Microsoft 365 tenant, the old tenant is usually being selected because cached sign-in state is still present or because the address is colliding with another Microsoft account or tenant record.
Try this in order:
- Close all browser windows completely before testing again.
If multiple browser tabs or windows are open, some can keep the old identity active even after sign-out. - When working with multiple tenants, use separate browser sessions.
Use a different browser or an in-private/incognito window for each tenant. This is the recommended way to stay signed in to multiple Viva Engage tenants at once, and the same approach helps avoid tenant mix-ups during Microsoft sign-in flows. - In Outlook for Mac, remove the affected account and add it again.
Go to Tools > Accounts... and remove the old account entry if it is still present. Then add the account again with Tools > Accounts... > + Add Account. - During add-account, manually choose the provider if Outlook selects the wrong one.
When adding the account, if the provider is not selected correctly, use Not [Google, iCloud, Yahoo, etc.]? and manually choose the correct provider before continuing. - If the sign-in prompt shows “Which account do you want to use?”, resolve the account collision.
That prompt means there are two Microsoft accounts using the same email address: a Work or school account and a Personal account. To stop that prompt, one supported option is to rename the personal Microsoft account by changing its primary alias in Manage how you sign in. - If Outlook still keeps routing to the old tenant, try signing in with the new tenant’s
onmicrosoft.comaccount name instead of the unchanged email address.
A documented Microsoft Q&A workaround for this exact migration pattern on Outlook for Mac is to sign in using the mailbox username at the new tenant’sonmicrosoft.comdomain so Outlook binds to the new tenant instead of the old one. - If the problem continues, the old tenant association likely must be removed by an administrator.
Accepted Microsoft Q&A guidance for this scenario is that the address may still exist in the former organization’s tenant, or as a guest user there. In that case, the former organization’s Global Administrator needs to remove the account’s association with that tenant. - If the issue is with the primary employer tenant after a tenant migration, ask the current IT admin to investigate tenant-side configuration.
Microsoft support guidance for tenant redirection problems states that if sign-in goes to a different tenant than intended, this is a configuration issue that only the tenant admin can solve.
For the 3 other organizations, keep each tenant isolated by browser profile, separate browser, or incognito/private window. That is the cleanest supported way to avoid one tenant being automatically reused for another.