Announcement ID | MC883198 | Published Date | 09-04-2024 | |
Service | microsoftteams | Last Updated | 09-04-2024 | |
Category | Stay informed | Expiration Date | 02-24-2025 | |
Roadmap ID | 411577 | Action Required by Date | ||
Tags | Admin impact, New feature, User impact |
Summary |
---|
Microsoft Teams phone devices will soon allow non-touch phone users to customize speed dial using line keys and sidecars. This feature, part of Microsoft 365 Roadmap ID 411577, will roll out from mid-October to late December 2024, depending on the region. It will be enabled by default and requires the latest application update. |
More Information |
---|
Coming soon to Microsoft Teams phone devices: Quickly access frequently dialed contacts and numbers and set up custom contacts and speed dial on the line key buttons and sidecars for non-touch phone devices certified for Microsoft Teams. This feature applies to non-touch phones and touch phones with sidecar/expansion modules. When this will happen:General Availability (Worldwide, GCC): We will begin rolling out mid-October 2024 and expect to complete by late October 2024. General Availability (GCC High): We will begin rolling out mid-November 2024 and expect to complete by late December 2024. How this will affect your organization:Before this rollout: Users are not able to set up speed dial using line key buttons. After this rollout: Your users will be able to configure custom contacts and speed dial using the line key buttons and sidecars for phone devices certified for Microsoft Teams. This feature is on by default. The initial setup process for configuring line keys on non-touch phones: Left: A non-touch phone with no line keys assigned as speed dials for contacts. Right: A non-touch phone with line keys assigned as speed dials for contacts: A sidecar with line keys assigned as speed dials for contacts: 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. |