Microsoft process, removing all references to from mail aliases etc,Īnd eventually killed the custom domain name.

On the day of the migration, I followed the.

I populated mail, contacts and calendar, thenĮxported the source test account’s Outlook items to a PST file ready for.

I set up Outlook mailbox profiles for the source.

So I used Outlook for Windows as my platform of choice, a significant choice Tenant ( I had two Windows 10 systems to test my approach

I created a new source mailbox in the customĭomain that will be shifted ( maps to I also created a target test account in the new.While for other users, Autodiscover works seamlessly.Īs part of the testing and research prior to the migration: Outlook Autodiscover to set up mail profiles for mailboxes on the new tenant, Tenant to another Office 365 tenant, *some* of the migrated users cannot use Rest use the web interface to pick up mail.Īfter some mail users are migrated from one Office 365 The six users consist of one Mac user using Outlook while the So now, ’s six mailboxes must be shifted to

Hosted temporarily by the larger organisation while it is birthed.īecause of ’s NFP status Microsoft hasĭonated a small Office 365 tenant to support their community support activities Six users are in custom domain and usersīelong to a small community aid organisation startup. Number of users on two custom domain names. This is a description of a knotty problem and how I resolved it.

Outlook autodiscover on mac