Announcement ID | MC805197 | Published Date | 06-25-2024 | |
Service | microsoftteams | Last Updated | 08-13-2024 | |
Category | Stay informed | Expiration Date | 12-31-2024 | |
Roadmap ID | Action Required by Date | |||
Tags | Admin impact, Feature update, User impact |
Summary |
---|
Microsoft is updating Teams Phone license handling to allow migration between phone number types without unassigning Direct Routing and Operator Connect Numbers when a Calling Plan license is added. Rollout starts late July 2024, with no admin action required before the rollout. Users can have any number type with the required license. |
More Information |
---|
We are making it easier to migrate between phone number types by updating Microsoft Teams Phone license handling. With the new changes, Direct Routing and Operator Connect Numbers will no longer be unassigned when a Calling Plan license is added to a user. The user can also get any type of numbers (Direct Routing, Operator Connect, Microsoft Calling Plan) if the required license is present on the user account. When this will happen:For Teams PowerShell General Availability (Worldwide and GCC): We will begin rolling out late July 2024 and expect to complete by late July 2024. For Teams admin center General Availability (Worldwide and GCC): We will begin rolling out late July 2024 and expect to complete by mid-August 2024 (previously early August). How this will affect your organization:Before this rollout: Any existing Direct Routing and Operator Connect numbers assigned to a user account may become unassigned when a Calling Plan license is added. After this rollout The existing Direct Routing and Operator Connect number on a user account will not be unassigned when a Calling Plan license is added. This new behavior is on by default and accessible to all Teams Phone admins with appropriate permissions. What you need to do to prepare:This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate. |