How to Delete Cutover Migration Batch & Assign Licenses to Office 365 Users?

If you want to Cutover migration to Office setup 365, then you need to follow the process :

for complete application visit

Verify you own the domain

Connect Office 365 to your email system

Create the cutover migration batch

Start the cutover migration batch

Route your email directly to Office 365


How to Delete the Cutover Migration Batch?


After you change the MX record and check that all email is being directed to Office 365 letter boxes, tell the clients that their mail is going to Office 365.

After this you can erase the cutover movement clump. Check the accompanying before you erase the movement clump.

All clients are utilizing Office 365 post boxes. After the bunch is erased, mail sent to letter boxes on the on-premises Exchange Server isn’t replicated to the comparing Office 365 post boxes.


Office 365 letter drops were synchronized in any event once after mail started being sent straightforwardly to them.

To do this, ensure the incentive in the Last Synced Time box for the relocation cluster is later than when mail began being steered straightforwardly to Office 365 letter drops.

When you erase a cutover relocation bunch, the movement benefit tidies up any records identified with the movement cluster and after that erases the movement group.

The bunch is expelled from the rundown of relocation groups on the movement dashboard.


In the Exchange admin center, go to Recipients > Migration.


On the migration dashboard, select the batch, and then choose Delete.


In the Exchange admin center, go to Recipients > Migration.


Verify that the migration batch is no longer listed on the migration dashboard.


Get office 365 here : office setup


How to Assign Licenses to Office 365 Users?


  1. Create an Autodiscover DNS record so users can easily get to their mailboxes:

After all on-premises post boxes are moved to Office 365, you can arrange an Autodiscover DNS record for your Office 365 association to empower clients to effectively interface with their new Office 365 letter drops with Outlook and versatile customers.

This new Autodiscover DNS record needs to utilize the same namespace that you’re utilizing for your Office 365 association.

For instance, if your cloud-based namespace is, the Autodiscover DNS record you have to make is

In the event that you keep your Exchange Server, you ought to likewise ensure that Autodiscover DNS CNAME record needs to point to Office 365 in both interior and outer DNS after the relocation so the Outlook customer will to associate with the right letter drop.


2. Decommission on-premises Exchange Servers:

After you’ve verified that all email is being routed directly to the Office 365 mailboxes, and no longer need to maintain your on-premises email organization or don’t plan on implementing a single sign-on solution, you can uninstall Exchange from your servers and remove your on-premises Exchange organization.


For more details, visit :



Leave a Reply

Your email address will not be published. Required fields are marked *