Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

  In many tenant-to-tenant programs, the business need arrives before the migration plan: "We need to collaborate now." Microsoft's guidance reflects this reality by recommending that organizations establish a Multitenant Organization (MTO) for day-1 collaboration and then transition into migration readiness in a controlled way. Day-1 collaboration: what MTO enables MTO enables immediate cross-tenant collaboration without changing user credentials. Typical steps include: ·        Create the MTO in the Microsoft admin center. ·        Configure trust relationships and policies. ·        Sync users as B2B external members for cross-tenant collaboration. ·        Enable collaboration features (Teams, file sharing, profile cards). Moving from MTO to migration readiness: the key concept The transition from MTO collaboration to migration readiness is abo...

  Free & Busy Sync during Cross-Tenant Migration You have two options “migrating” mailboxes cross-tenant: -           Microsoft Cross-Tenant Migration this will move, reconnect a user’s mailbox in target and removes the source mailbox entirely -           Using a 3 rd party tool, copying the mailbox content and syncing calendars this will leave the source mailbox intact and can confuse users in the source environment, which user is now active (see the user adoption story)   Organization relationship in Exchange Online If you migrate the User Mailbox entirely, meaning, nothing is left behind in the source, you can use Organizational Free/Busy Lookup: This feature is named: Organization relationship in Exchange Online   This allows: -           Set up an organization relationship to share calendar information with...

 Hi all, this is part 7 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

 Hi all, this is part 6 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

 Hi all, this is part 5 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

 Hi all, this is part 4 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

 Hi all, this is part 3 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modif...

 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 User Adoption Process   Change & Adoption is the most critical task in any tenant-2-tenant migration. Not only users who are migrated are impacted heavily by the migration. Users in the target tenant too. Especially in the target tenant they will experience constant changes. New users and groups are appearing, but not “life”, not actively working in the tenant. Further, new services related content will sequentially appear, like SPO sites, Teams Channel, Yammer or others. Since data is flying in slowly, there must be a communication and identification in place, that user are enabled identifying data source in migration. Same applies, for user in the source environment. Content/ data migrated will be in read-only. Content could become unavailable due to accomplished migration to the target. All depends on the migration process, procedures and planning. This needs to be communicated to all users in proper manner. Talking about external users, there is...

 In this cross-tenant/ tenant-2-tenant migration book, I guide you through the holistic approach, which in deep exercise of Team Voice. I’m working as an Enterprise Solution Architect for Cross-Tenant migration, leading teams with more than 40 persons involved. Technically there are many more aspects, like 3rd party tools vs. Microsoft own solutions and scripts to be written. This book provides you an inside but not providing scripts and detailed configuration. Scripts and configurations are very much an individual approach for each cross-tenant migration. Two very special chapters will be released in 2023, handling and working with Guest User Access and Change & Adoption approach. Both are not only technically important but require a deeper look into their dependencies. Working on an end-2-end overview, technical considerations and understandable working template, this Migration book, it was work consolidated during the last 1 ½ years. DOWNLOAD HERE:  https://www.slidesha...

  Cross-tenant Shared DNS Space (Native Cross-Tenant Domain Sharing for Exchange Online)   Upcoming new features, describe and change migration approach, (private preview) Reference: Supporting Mergers, Acquisitions, and Divestitures in Microsoft 365 - Microsoft Community Hub   Microsoft has announced publicly a new expected solution architecture and some of the configuration and management tasks you must perform when utilizing native cross-tenant domain sharing functionality. Below, the step-by-step description to enable cross-tenant domain sharing for a single SMTP domain. (valid as long no major changes are introduced by MS) The domain will be Authoritative in the Tenant where you perform the primary domain management. Up on enablement for domain for cross-tenant domain sharing, you will be able to add the domain as an Internal Relay in additional tenants. An internal Relays is like in Exchange On-Premises relay configuration.     Cro...

  Personal Chat Migration into Azure Data Lake   Another approach, rudimentary described in the white paper is, migration or better said exporting Teams chat messages into Azure Data Lake solution.   To be said upfront, this is not a solution you or a consultancy company can do, rather you must engage Microsoft (MCS/PSS). This is an internal Microsoft solution using a private API for export.   There are several options on how data can be extracted: -           Single large XML file -           Individual XML files per Teams user There is no other way yet, rather than using XML. Further, you must purchase an Azure VM and Azure Storage. The costs aren’t too high and acceptable. After Chat message extraction, the consolidated XML file will be sent via email or copied into OneDrive.   Talking about user experience. This is not a user-friendly option! As u...

  Meeting Link Migration for Teams Note: both, first user Mailbox/Calendar and Teams must be migrated A 3 rd party tool is required to accomplish a meeting link migration. With Exchange Mailbox migration, all items, including calendar item will be migrated as they are. Calendar item with a link to a Microsoft Team meeting link back to the original Team meeting in the source tenant. The URL is retained. A Teams Channel meeting is not recreated in the target tenant. Those meetings must be rescheduled manually by the channel owner.   How it works (e.g. Quest): The meeting link migration task will create a new Team meeting with the original meeting details in the target tenant. It will set the target user as the organizer. The original meeting migrated to the target will be canceled. The cancellation will be automatically sent out to the organizer and recipients. Meeting Link Migration Considerations Before migrating Teams meetings and their respective link, be awa...