That is a planned release, not an announcement that the controls are available now. Microsoft’s roadmap explicitly describes its release dates and feature descriptions as estimates subject to change.
What Teams mobile users will be able to manage
The roadmap description identifies four capabilities coming to the mobile experience:
- Create a call group.
- Add or remove group members.
- Configure how the group rings.
- Forward incoming calls to the group, or have the group ring alongside the user.
The practical benefit is straightforward: changing call coverage should no longer require switching to the desktop experience. For someone away from their PC, replacing an unavailable colleague in a call group could become a phone-sized task rather than a reason to reopen the laptop.
The announcement concerns management of a user’s call group, not a newly announced call queue or a replacement for Teams Phone administration. Microsoft’s existing documentation describes call groups as a way for colleagues to answer incoming calls on someone else’s behalf.
Forwarding and simultaneous ringing are different choices
Those two call-handling options serve different needs. Forwarding sends calls to the selected destination; simultaneous ringing lets the user and another recipient—such as a call group—receive the incoming alert together. Microsoft Support documents both behaviors in Teams’ existing calling settings.
In practical terms, forwarding suits a handoff, while simultaneous ringing suits shared coverage. The mobile update’s value is making those choices easier to change when plans change.
There are existing service limits worth knowing before reorganizing a group. Microsoft Learn says a call group can contain up to 25 users, but adding more than five members automatically changes its ringing order to Everyone at once. A user can own one call group and belong to as many as 25. These are documented service rules, not newly announced mobile capabilities.
What users and administrators should check
A mobile management interface should not be mistaken for universal eligibility. Microsoft’s existing group call-pickup documentation requires a Teams Phone license and Teams Only deployment mode for the participating users. Administrators control access through the AllowCallGroups Teams calling-policy setting. The roadmap description does not announce changes to those prerequisites.
There is also an important mobile troubleshooting detail: Microsoft Support says mobile devices receive call-group notifications only when configured for banner and ringtone. If colleagues are not being alerted, notification configuration deserves attention—not just group membership. Nothing in this announcement establishes that the planned management controls change that behavior.
For now, Microsoft’s documented existing setup starts at Settings and more > Settings > Calls > Manage call group, where users can create a group or edit its members and settings. That is useful context for the established experience, not a verified navigation path for the forthcoming Android or iOS interface.
The takeaway: this is a focused convenience improvement for Teams calling, with a December 2026 target. Its promise is less desktop dependency when adjusting call coverage—not a confirmed change to licensing, service limits, or notification delivery.