Teams Channel Cross Tenant Migration

-

 

Teams Channel Migration

Starting with the generics of Teams Team/ Channel migrations. There can be not Team without a corresponding M365 group. This implies, that other services are available and Teams is heavily depending on those. Mainly it is SPO/ OneDrive. It is used for files in Teams.

Not talking about the M365 Group provisioning here in detail, but the important sequence you must follow is:

1.       Create a user mapping file and provision target users

2.       Provision M365 groups in target tenant
all member user must exist

Note for M365 Groups:
There is no tool available yet, which could keep M365 Groups in persistent sync. Therefore, delta sync’s are required.

Other services used by or from within Teams are e.g. Tabs, Wiki & Planner. Shared Mailbox are not part of the Teams integration, but other apps made available in Teams might.


Secondly, Teams has shared channels and private channels. Both have their own complexity.

·       Private channel require a Teams “hull” provisioning and cannot be delta provisioned.

·       Shared Channels required a user mapping source to target for Guest User
Guest User must be provisioned before the provisioning and migration starts
(Note: at the point of writing this article, shared channels are in public preview)

 

Let’s talk about a “hull” provisioning. After M365 Groups are copied, the process of provisioning services starts. A Teams hull, consist of the readiness of SharePoint Online, OneDrive and Site, further the entire Channels in Teams. This is the structure only, without any content.
It is advised before doing any content migration, ensure the especially for PRIVAT and SHARED Channels, the structure “hull” is re-provisioned/ copied again.
Than a FREEZE must be applied, because any changes to the private channel (memberships) will not be reflected.

It is not required using a single migration tool for this holistic process, rather it could be segregated into different tools. Only for the provisioning incl. the involved users, it is recommended doing it with the same tool.

You can even use different tool for say, SharePoint sites and OneDrive. You have to evaluate the content making the right decision with set of tool will support you best and which method you could apply for those service and reuse them from other migration tasks.

 

The other important topic is, that OneDrive must be provisioned and migrated before you can migrate chats into the channel. Messages might contain documents shared, those files you will find in ODB. Applying the shared permissions again, and further LINKING the file to the chat message require those to be present in the target already.

 

Sequence for Teams Team migration (Team/ Channel)

1.       Provision users and guest users in target

2.       Have user mapping file ready and complete

3.       Provision the M365 Groups in target

4.       Synchronize the Teams “HULL”/ structure incl. private/ shared channels
(Teams provisioning)

5.       Start content migration for OneDrive, SharePoint and Mailbox (pre-load)

6.       REPEAT: Provision the M365 Groups in target

7.       REPEAT: Synchronize the Teams “HULL”/ structure incl. private/ shared channels
(Teams provisioning)

8.       Freeze source Teams Team and services assigned along

9.       Initiate final migration of all service (at least ODB, SPO)

10.   Start Chat Migration / Channel


Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
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
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more