Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant Migration Specialist)

 How to structure Teams with Groups   With Teams Client 2.1 there are new, helpful features released. Often we see, that we are part of TOO MANY TEAMS. This is primarily, if Teams is used as a Information and Community board too. This is ok, but it has disadvantages in the form of Teams becomes not over seeable any longer. The well-known setting option allows you to "hide" or "show" Teams. But this isn't all. Might want Teams which are more frequently used in your upper sort order. OR Teams which are less frequent used or not that important, further to the end of your list.

 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

Hi all, this is part 2 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 1 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

  Cross-Tenant Synchronization for seamless application access is now generally available! - Microsoft Community Hub Cross-tenant access settings for secure collaboration now generally available! - Microsoft Community Hub More learning can be found here: What is a cross-tenant synchronization in Azure Active Directory? - Microsoft Entra | Microsoft Learn

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 modify the AD hide at

During the last month, Microsoft updated the Teams experience. The important feature turning off incoming video has moved to a new position. Click " VIEW " and than " MORE OPTIONS " -> " Turn off incoming video "

 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 even a m

If you want to test the new amazing (but not jet feature rich) Teams client. Really awesome is the speed and I can't await that all features are available Here it comes and how to enable. You have to navigate into Team Admin Center.

 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.slideshare.net/th

Dedicated White Paper to Microsoft TEAMS CROSS-TENANT Migration. The guide includes Teams Team/Channels, private/ personal chat and Enterprise Voice  (Direct Routing) migration explanation and recommendations. It is written for decision maker, project manager and solution architects. Download @ SlideShare  https://www.slideshare.net/thomaspoett/cross-tenant-migration-microsoft-teams

  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.     Cross-Tenant Domain Sharing Conf

  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 user must have an XML reader and message can only be found by an XML search. This makes it difficult finding messag

  Cross Tenant User Migration Approach and considerations In any Tenant 2 Tenant migration the migration approach you have to consider based on: ·        Migration Tools ·        Communication/ Work clusters ·        User and shared data The combination and dependencies of the above will guide you to the best possible decision, how you migrated a tenant and merge it into the target environment. Migration of data is time consuming. We explained the tenant limitation (throttling) in a chapter above. Nevertheless, pre-loading of data into the target tenant is crucial including the sequence required for planning.   Migration Tools There are multiple vendors on the market providing tools, tool sets. They either run on-premises, in Azure or have developed their own cloud-based solution. Principally you will consider a mix of different tools and vendor. Most companies run a hybrid environment. This is in most cases for the users and groups synced between the on-premises Ac