Commands › Microsoft Teams
Start-CsExMeetingMigration
This cmdlet manually trigger a meeting migration request for the specified user.
Quick start script
# Start-CsExMeetingMigration — quick start (serv365.ai)
# 1. Connect (app-only shown; interactive: omit the certificate parameters)
Connect-MicrosoftTeams -CertificateThumbprint $thumb -ApplicationId $appId -TenantId $tenantId
# 2. Run and inspect
Start-CsExMeetingMigration | Format-List
# 3. Export for evidence / drift tracking
Start-CsExMeetingMigration | Export-Clixml .\CsExMeetingMigration-$(Get-Date -Format yyyyMMdd).xmlSyntax
Start-CsExMeetingMigration [-SourceMeetingType <MmsSourceMeetingTypes>] [-TargetMeetingType <MmsTargetMeetingTypes>] [-Identity] <UserIdParameter> [<CommonParameters>]Parameters (3)
| Parameter | Type | Required | What it controls |
|---|---|---|---|
| -Identity | UserIdParameter | Specifies the Identity of the user account to be modified. A user identity can be specified by using one of four formats: 1. The user's SIP address 2. The user's user principal name (UPN) 3. The user's domain name... | |
| -SourceMeetingType | Object | The possible values are: * **All:** indicates that both Skype for Business meetings and Teams meetings should be updated. This is the **default value**. * **SfB:** indicates that only Skype for Business meetings... | |
| -TargetMeetingType | Object | The possible values are: * **Current:** specifies that Skype for Business meetings remain Skype for Business meetings and Teams meetings remain Teams meetings. However audio conferencing coordinates might be changed,... |
Reference facts derived from Microsoft documentation, © Microsoft, licensed CC BY 4.0; restructured with original guidance by serv365.ai.