While the migration from Skype for Business to Microsoft Teams has many moving parts, one item you don't need to worry about is updating meetings. Microsoft provides the Meeting Migration Service (MMS), which automatically converts your existing Skype for Business meetings to Microsoft Teams meetings. However, there are some scenarios where automatic migration does not occur, and you need to know how to verify that meetings were migrated successfully. In this post, I will cover when migrations occur and how to configure your tenant for automatic migrations.

Migrating from Skype for Business to Microsoft Teams involves more than technical changes. User adoption and change management are paramount to a successful migration. Users not only need to continue interacting with each other between the different clients, but they will often need to rethink their current collaboration workflows to maximize Microsoft Teams' capabilities.

While migrating chat and voice workloads to Microsoft Teams requires significant planning, migrating users' existing meetings is a bit easier. Microsoft provides the Meeting Migration Service or MMS. This service will automatically update a user's scheduled Skype for Business meetings to Microsoft Teams meetings. The automatic upgrade avoids requiring users to delete existing meetings and manually reschedule them as Microsoft Teams meetings. However, MMS does not work in every scenario, so let's cover when the service is and is not triggered.

Meeting Migration Service triggers ^

The Meeting Migration Service will update existing meetings in the following scenarios:

  • When a user is migrated from Lync or Skype for Business on-premises to the cloud (that cloud could be Skype for Business Online or Microsoft Teams)
  • When a user is upgraded to Teams Only or Skype for Business with Teams Collaboration and Meetings policy
  • When an administrator changes a user's audio conferencing settings
  • When using the Start-CsExMeetingMigration PowerShell cmdlet

However, MMS is not triggered in these scenarios:

  • The user's mailbox is hosted in Exchange on-premises
  • The user is being migrated from the cloud back to Lync or Skype for Business on-premises

In these scenarios, the user will need to download and install the Meeting Migration Tool to their local system to migrate their meetings themselves.

Configuring automatic meeting migrations ^

The Meeting Migration Service is enabled by default in the tenant. If you want to disable automatic meeting migrations, you will need to create a remote PowerShell connection out to Skype for Business Online. For more information on how to perform this, check out Microsoft Docs: Manage Skype for Business Online with PowerShell.

Once you have created the remote session, you can view the status of MMS using the Get-CsTenantMigrationConfiguration cmdlet and viewing the MeetingMigrationEnabled setting.

Get-CsTenantMigrationConfiguration
Viewing tenant migration settings

Viewing tenant migration settings

To disable automatic migration, use the following command:

Set-CsTenantMigrationConfiguration -MeetingMigrationEnabled $false

Configuring audio conferencing migrations ^

The Meeting Migration Service can also be triggered when an administrator changes a user's audio conferencing configuration. Examples of changes include:

  • Assigning or removing an audio conferencing license
  • Moving users to a new audio conferencing bridge
  • When an administrator changes or resets the conference ID for a user

The configuration for audio conferencing migrations can be separately enabled or disabled in the tenant. You can still have automatic migrations for other scenarios but disabled for audio conferencing changes. To verify the audio conferencing migration settings, you can run the Get-CsOnlineDialInConferencingTenantSettings cmdlet and view the value of AutomaticallyMigrateUserMeetings:

Get-CsOnlineDialInConferencingTenantSettings
View audio conferencing migration settings

View audio conferencing migration settings

To disable audio conferencing change migrations, you can run the following command:

Set-CsOnlineDialInConferencingTenantSettings  -AutomaticallyMigrateUserMeetings $false

Viewing migrations in action ^

Now that we understand when meetings are migrated and how to configure automatic migrations, let's view a migration in action. Here is a meeting invite scheduled using Skype for Business:

Skype for Business meeting invitation

Skype for Business meeting invitation

When MMS migrates a Skype for Business meeting, the service updates the meeting location and meeting join information to a Microsoft Teams meeting. The meeting text outside of the meeting join information block will remain the same, as will any meeting attachments. However, Skype for Business meeting content such as whiteboards and polls will not be retained.

In this scenario, I will trigger the meeting migration by assigning the Teams Only policy to a user, effectively migrating a user from Skype for Business to Microsoft Teams. I will do this by navigating in the Teams admin center to Users > Select the user, and on the Account tab, edit the Teams upgrade settings. When you select Teams Only mode, there is a switch to migrate the user's meetings. You can override the meeting migration on a per-user basis using this setting. Once you have configured the user's settings, click Apply.

Trigger the migration service by assigning a user to Teams only

Trigger the migration service by assigning a user to Teams only

View migration status ^

Once the policy change has triggered the migration, you can view the status by going back to your Skype for Business Online PowerShell session. The cmdlet to view the status is Get-CsMeetingMigrationStatus. Since I'm only concerned with an individual user's status, I will use the Identity parameter and input the user ID.

Get-CsMeetingMigrationStatus -Identity <User Principal Name>
View individual users migration status

View individual users migration status

Notice the state is currently "Pending." By default, the migration job will queue up and wait 90 minutes before starting the process. If it runs into any errors, it will attempt to migrate the meeting up to nine times in the next 24 hours.

There are a few other parameters to use with the status command. You can use the State parameter to find meeting migrations based on status. It accepts values such as:

  • Pending
  • InProgress
  • Failed
  • Succeeded

You can also specify a StartTime and an EndTime to find migrations within a time window or use the SummaryOnly parameter to get an overview of migrations for the tenant.

Verifying migration success ^

After a while, the migration service will process the pending request and migrate the meeting to Microsoft Teams. You can run the status command again to verify the migration was successful:

View completed migration status

View completed migration status

The user's calendar shows that the meeting invitation has been updated to a Microsoft Teams meeting; the meeting text and attachments have stayed the same.

Update with Microsoft Teams meeting information

Update with Microsoft Teams meeting information

One additional item to note: migrating a meeting will send a calendar update notification to the invitees. These are the same messages sent to attendees when the meeting organizer changes something in a meeting, such as the time and date or content within the message body. You should educate your users prior to the migration so they know that they may start receiving meeting updates to ones they've already accepted.

Summary ^

The Meeting Migration Service is a great addition to the Skype for Business and Microsoft Teams cloud service. Automatically migrating users' meetings removes one action item from your tasks during the migration. Your only responsibility during the migration is to verify meetings were successfully migrated and to reach out to users to resolve them when they are not successful.

Subscribe to 4sysops newsletter!

Questions on upgrading to Microsoft Teams from Skype for Business?

avataravatar
0 Comments

Leave a reply

Please enclose code in pre tags

Your email address will not be published. Required fields are marked *

*

© 4sysops 2006 - 2021

CONTACT US

Please ask IT administration questions in the forums. Any other messages are welcome.

Sending

Log in with your credentials

or    

Forgot your details?

Create Account