Trouble with Autodiscover After Domain Move to New M365 Tenant

0
14
Asked By TechGuru123 On

I recently moved one of two domains from the same Microsoft 365 tenant to a new one. After I removed the domain from the old tenant and updated the DNS records accordingly, everything seemed to work fine for new users on new laptops. However, I'm facing significant issues with existing users who have established Windows profiles. I've removed their Outlook profiles, cleaned the registry of old references, cleared the Credential Manager, and flushed DNS, but Outlook keeps trying to connect to the old tenant instead of the new one. If I create a new Windows profile, it works fine, so the problem appears to be linked to the existing Windows profiles. Can anyone shed light on how Outlook resolves users to the correct Microsoft 365 tenant? Is it tied to a specific file, registry entry, or cached folder? I really need a solution that doesn't involve recreating profiles for over 75 users, as that would be too cumbersome!

6 Answers

Answered By OutlookNinja87 On

From my experience, sometimes after a tenant migration, it takes a few hours for everything to sync up properly. I would suggest waiting a bit and testing again; creating a new Outlook profile might actually work after that period.

Answered By FixerUpper19 On

You might want to check this script that could help solve your problem: https://learn.microsoft.com/en-us/office/troubleshoot/activation/reset-office-365-proplus-activation-state.

Answered By CloudChampion05 On

You can use your onmicrosoft.com domain for autodiscover. This might force it to look at the correct tenant.

Answered By AdminAdventures22 On

Outlook does cache autodiscover methods, and this cache might still be pointing to the old tenant. You can try accessing the files in %localappdata%/microsoft/outlook to manage this. There's also a registry setting that lets you disable cached autodiscover items.

Answered By SysAdminHero88 On

I've dealt with similar issues after migrating tenants. Sometimes, you need to delete and re-add the autodiscover DNS entry in your public DNS. Even if the entry looks unchanged, it doesn't always update correctly with Azure until you do this.

Answered By UserWhisperer99 On

Did you try clearing out these specific local app data folders and registry entries? It could help:

- %localappdata%PackagesMicrosoft.AAD.BrokerPlugin_cw5n1h2txyewy
- %localappdata%MicrosoftTokenBroker
- HKEY_CURRENT_USERSOFTWAREMicrosoftIdentityCRL
If you haven't done that, it might be worth a shot.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.