I am planning a sfb on-prem to sfbo/teams migration and trying figure out a plan to assign users local conference bridge number as they get migrated online. I have already acquired handful of conference bridge service number in my tenant.
High level steps:
1. Acquire regional service number as conference bridge
2. Assign appropriate license to user account pre migration (sfbo/teams/audio conferencing)
3. Suspend Meeting Migration Service in tenant (so that it doesn't start sending meeting updates)
3. Migrate user account to online (move-csonlineuser)
4. Assign appropriate conference bridge and dial-out policy to users (Set-CsOnlineDialInConferencingUser, Grant-CsDialoutPolicy)
5. Resume Meeting Migration service in tenant (this should update meetings and send out updates)
First of all has any one done this before and can share feedback?
1. Is there any way to disable 'auto enablement' of Audio conferencing functionality on users upon Audio Conferencing license assignment?
2. If the answer for Question 1 is No, then what's the purpose of Enable-CsOnlineDialInConferencingUser cmdlet?
3. What is the best approach to disable MMS during migration and enable it post migration, i see 2 options (Set-CsTenantMigrationConfiguration -MeetingMigrationEnabled $false OR Set-CsOnlineDialInConferencingTenantSettings -AutomaticallyMigrateUserMeetings $false)
The idea is to avoid the service to send multiple meeting updates to the attendees during the migration process. AFAIK if we don't disable MMS there will be 2 set of updates sent.
First - When user account is moved form on-prem to online, these updates will include 'Default' conference bridge assigned to the tenant.
Second - When Audio Conferencing bridge number is changed to the local city based on users location.
I haven't been able to locate any documentation on this approach so any feedback from the community is much appreciated.