Posts

Showing posts with the label Cross tenant migration requirements

Notification for migrated Users during Cross-Tenant Migration

 It is important for users informing other about their status or migration. Therefore, Exchange Online offers good solution, the Out Of Office Message. User might even receive a new DNS domain in some cases. For good user experience, internal and external persons could be informed. Out of Office messages are also visible in Microsoft Teams. User the cmdlet  Set-MailboxAutoReplyConfiguration Example: Set-MailboxAutoReplyConfiguration -Identity user@contoso.com -AutoReplyState Enabled -InternalMessage "I'm migrated to TARGET." -ExternalMessage "Due to our company merger, I'm migrated to COMPANY, you will be able contacting me at user@target.com." -ExternalAudience All 

Cross-Tenant Comparison (Tenant to Tenant)

 The main head word in T2T comparison is the “Technology Harmonization”. Beside this, users will experience a different M365 feature usability, this is the other side to be identified and leads to the Change & Adoption approach.   Technology – what is different between source and target Several topics are included in this topic, not limited to technology only but overlap with user experience too. Commonly we start with the licensing comparison. This might mainly restrict the usage of services or limit the services towards migrated users. From here you analyze each service step-by-step. Not only data / storage limitation could apply. Like in personal OneDrive, where the target could have lower storage limits than in source. Areas like Guest User Access, Domain restrictions, Teams federation and other B2B configurations might lead to data migration/ usage limitations. It is advised to work with both side equally and see how the target environment is leading and if ...

Cross-Tenant (Tenant to Tenant) Migration Consideration and Planning Guide

Image
 A cross tenant / tenant to tenant (T2T) migration also named sometime cross-tenant migration can be introduced during merger and acquisitions of companies. Hereby a tenant, local or geo-tenant will be integrated / migrated into the corporate target tenant. Cross Tenant Migrations are very complex and time consuming . Complexity can even further increase if the migration tenant is in a hybrid configuration. Time consuming, especially due to strict performance limitations in reading from and writing into a tenant.  This MUST not be underestimated !   This first blog article, will help you taking all consideration into place.   General Technical Aspects: •        System accesses and read permissions for external migration staff as well as service accounts for migration tools require a structured and early alignment with Security. Limitations will cause technical errors and misunderstandings during migration design and rollout. ...