This script creates a new migration batch and moves migration users from one batch to the new batch.
This script moves Exchange Online migration users to a new migration batch. The script creates the new batch automatically. The name of the new batch is based on the following:
- Custom prefix, provided by the BatchName parameter
- Batch completion date
- Source batch name
The new batch name helps you to easily identify the planned completion date and source of the migration users. This is helpful during an agile mailbox migration process.
- Exchange Online Management Shell v2
List of migration user email addresses that should move to a new migration batch
Path to a CSV file containing a migration users, one user migration email address per line
The name of the new migration batch. The BatchName is the first part of the final full Name, e.g. BATCHNAME_2022-08-17_SOURCEBATCHNAME
Switch indicating that the new migration batch should start automatically
Switch indicating that the new migration should complete migration automatically NOT implemented yet
[DateTime] defining the completion date and time for the new batch
Email addresses for batch notification emails
The string pattern used for date information in the batch name
./Move-MigrationUsers -Users JohnDoe@varunagroup.de,JaneDoe@varunagroup.de -CompleteDateTime '2022/08/31 18:00'Move two migration users from the their current migration batch to a new migration batch
THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER.
- My Blog: https://blog.granikos.eu
- Bluesky: https://bsky.app/profile/stensitzki.bsky.social
- LinkedIn: https://www.linkedin.com/in/thomasstensitzki
- YouTube: https://www.youtube.com/@ThomasStensitzki
- LinkTree: https://linktr.ee/stensitzki
For more Office 365, Cloud Security, and Exchange Server stuff checkout services provided by Granikos
- Website: https://granikos.eu
- Bluesky: https://bsky.app/profile/granikos.bsky.social