Meeting Link Migration for Teams in Cross Tenant

-

 

Meeting Link Migration for Teams

Note: both, first user Mailbox/Calendar and Teams must be migrated

A 3rd 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 aware of the limitations from the tools chosen. Additionally, attendees outside your organization also receive cancelations and re-invites. This results in questions/ confusions, if those attendees aren’t informed before the migration occurs.

·       The attendee list is not updated to match the target domain.

·       A new meeting is only created if the migrating user is the organizer of that particular Team meeting.

·       Most 3rd party tools recreate present and future meetings, both one-time and recurring meetings. Meetings that happened in the past are migrated with Calendar migration.

·       Meetings recreated on target could result in meeting time zone updates to UTC. This is one of the limitations of the Microsoft Graph API.

·       The subsequent runs of the Meeting Link Migration Task will skip the meetings which were previously processed.

·       Properties like a flag and categories are not supported with this migration.

 

 

Note:

The cancellation email will be sent to the mailboxes of target attendees. If mail forwarding from the target to the source is not configured for them, the attendees in the source tenant will not receive the cancellation email. As a result, they will observe both the original meeting, which was cancelled, and the new one, created by the On Demand service.

Mailbox migration with the Migrate Calendar option selected, must be completed before starting this task.


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