HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin
Rollout Pause – Line Key Configuration via Teams Admin Center
The rollout of line key configuration in Teams Admin Center for Teams phones is paused worldwide to address feedback and improve shared device license support. Admins should configure line keys directly on devices temporarily. Audit logging and reporting via TAC may be affected until the experience resumes.
Introduction
We’re temporarily pausing the rollout of the line key configuration experience in Teams Admin Center (TAC) for Teams phone devices. This pause applies to tenants in Worldwide, GCC, GCCH, and DoD environments. The pause allows us to address feedback and improve the experience, particularly for shared device license scenarios.
When this will happen
Effective immediately, the rollout is paused. A revised rollout timeline will be communicated in a future Message center post once improvements are validated and tested.
How this affects your organization
If your organization uses Teams phone devices, you may notice that the line key configuration experience in TAC is currently unavailable. This affects all supported environments. Admins can continue to configure line keys directly on the device as a temporary workaround.
What you can do to prepare
No action is required at this time. We recommend continuing to use on-device configuration until the TAC experience resumes. We’ll provide updated guidance and documentation once the rollout restarts.
Compliance considerations
| Compliance Area | Impact |
|---|---|
| Does the change modify, interrupt, or disable any capabilities (Purview)? | Yes – The pause may temporarily affect audit logging and reporting for line key configurations managed via Teams Admin Center. |
| Does the post describe features/components that have been retired or altered? | Yes – The line key configuration experience in Teams Admin Center is temporarily disabled. |
| Does the post describe any known errors or limitations that were addressed? | Yes – Inconsistencies were identified in shared device license scenarios, prompting the rollout pause. |
Message ID: MC1142621
