What’s the best way to reconfigure Outlook and OneDrive after a Microsoft 365 tenant migration?

One thing I would not overlook is autocomplete. Rebuilding the profile can make users think all their cached recipient suggestions have disappeared. A migration tool may preserve that data, while a basic profile reset usually will not. If you script the process, decide whether preserving autocomplete is important and back it up or migrate it before deleting the old profile.

A policy or script that creates a fresh Outlook profile and lets autodiscover configure the new mailbox can work well when the environment has the necessary directory integration. Deployment tools can preserve items such as autocomplete and provide a nicer user workflow, but they also add licensing and administrative overhead. For a no-domain, no-Intune customer, I’d test the NinjaRMM script thoroughly before paying for an additional product.

For a client without a domain or Intune, scripting this through the RMM is a reasonable approach. Run the script in the logged-in user’s context, remove the old Outlook profile, clear stale Microsoft credentials from Credential Manager, disconnect OneDrive, and launch its setup again for the new account. Old cached credentials are often what cause repeated sign-in prompts after the profile has been recreated.

The timing matters too. Run it after the mail cutover is confirmed and notify users that they’ll need to sign in again. Don’t deploy it to everyone simultaneously, because Outlook and OneDrive may download large amounts of data and overwhelm the customer’s connection. Roll it out in waves or stagger it over several days.

Be careful about treating this as only an Outlook profile reset. You may also need to remove the old work-account connections, unlink OneDrive, and refresh the Office sign-in state. If you only rebuild Outlook, remnants of the old tenant can still cause authentication problems.

For a managed, domain-joined device, a full reset and reprovisioning can be the cleanest option, especially when Intune is involved. For unmanaged local profiles like this customer’s, a carefully tested user-context script is much less disruptive.

At larger sites, onsite technicians can still work if the process is well organized. On one project, technicians handled the Windows profile work first, then refreshed Outlook, OneDrive, and an Office application such as Word so the Office sign-in state was updated properly. Around 90% of roughly 100 users were completed in a day; the remaining users were away, traveling, or working different shifts and had to be handled separately.