Teams PhoneMarch 25, 20266 min read

Microsoft Teams Now Supports Multiple Phone Numbers Per User — Here's What It Means for Admins

Chandra

Chandra

SwiftM365 | Building for the M365 community

A Feature Admins Have Been Asking For — Finally Arriving

For years, one of the most common frustrations with Microsoft Teams Phone has been the inability to assign more than one phone number to a single user. If you had an executive who needed a US and UK number, or a support agent covering multiple hotlines, you were stuck with workarounds involving Call Queues, Auto Attendants, or SBC-level call rerouting.

That's about to change. Microsoft is rolling out multi-line support for Teams Phone, allowing administrators to assign up to 10 telephone numbers to a single user account. This is tracked under Microsoft 365 Roadmap ID 557716.

Rollout Timeline

PhaseTimeline
Targeted ReleaseEarly April 2026 → Late April 2026
General Availability (Worldwide)Late April 2026 → Mid-May 2026
This is a phased rollout — if your tenant is on Targeted Release, you'll see it first.

How It Works

Once the feature is available and an admin assigns additional numbers to a user:

  • All assigned numbers appear as separate lines in the Teams Calls app
  • Incoming calls clearly show which line is ringing
  • Users can select which number to use for outbound calls (caller ID selection)
  • Works across Teams desktop, mobile, and certified desk phones
  • On Teams-certified devices, lines can be mapped to physical line keys for quick call handling
  • No user configuration needed — numbers appear automatically after admin assignment
  • Real-World Use Cases

    International Teams

    Assign a US, UK, and Singapore number to one account manager who supports customers across multiple markets. Each customer sees a local number when they call or get called.

    Executive Assistants

    Executives often manage several business entities. Assistants support multiple executives. Multi-line ensures both roles can make and receive calls through one unified Teams interface without juggling accounts.

    Helpdesk and Support Teams

    IT helpdesks and client service desks often manage several hotline numbers. Instead of complex Call Queue configurations, you can now assign all hotline numbers directly to the agents.

    Branch Office Coverage

    A regional manager covering three office locations can have a direct number for each branch — all ringing on the same Teams client.

    What Admins Need to Know

    It's Off by Default

    This feature doesn't auto-enable. You'll need to actively configure it for your users.

    Admin Requirements

    You need the Teams Administrator role (or equivalent permissions) to manage multi-line assignments.

    Assignment Process

    The assignment is done through the Teams Admin Center or PowerShell. You can assign up to 10 numbers per user — these can be Direct Routing, Calling Plan, or Operator Connect numbers.

    No Extra Licensing Required

    This is included with existing Teams Phone licensing. You don't need additional licenses per line — just the phone numbers themselves.

    Before This Feature: The Workarounds

    If you've been dealing with multi-number requirements before this rollout, you've probably used one of these:

  • Call Queue approach — Create a CQ for the extra number, add the user as an agent. Works but messy — the user sees it as a queue call, not a direct call.
  • SBC-level rerouting (Direct Routing) — Configure your SBC to translate incoming calls on a secondary number to the user's primary number. Effective but requires SBC-level configuration changes for every user.
  • Auto Attendant forwarding — Set up an AA that immediately forwards to the user. Adds latency and complexity.
  • Separate accounts — Some organizations created secondary accounts. This is the worst approach — doubles licensing costs and creates confusion.
  • All of these become unnecessary once multi-line rolls out to your tenant.

    How SwiftM365 Helps

    Whether you're setting up Direct Routing for the first time or reconfiguring voice routes for multi-line support, SwiftM365 generates the PowerShell scripts you need:

  • Voice Configuration — Dial plans, VRPs, PSTN usages, and voice routes for 203 countries
  • Bulk Phone Number Assignment — Assign numbers to hundreds of users via CSV
  • Bulk Policy Assignment — Apply voice routing policies, calling policies, and dial plans in bulk
  • EV Readiness Check — Verify all 18 parameters before activating Teams Phone
  • All scripts run locally in your PowerShell — zero tenant access, completely free.

    Visit swiftm365.com to get started.

    Key Takeaways

  • Up to 10 numbers per user — no more workarounds
  • Rolling out April-May 2026 — check your tenant's release ring
  • Off by default — admins must configure it
  • No extra licensing — included with Teams Phone
  • Works everywhere — desktop, mobile, and certified devices
  • This is one of the most requested features in Teams Phone history, and it's finally here. If you manage voice deployments, start planning which users will benefit from multi-line now — so you're ready to configure it as soon as it hits your tenant.

    ---

    Need help setting up voice configuration for your Teams deployment? Visit swiftm365.com or reach out via our feedback page.

    Chandra

    Written by Chandra

    Passionate about simplifying Microsoft 365 administration for the community. Building free tools so admins can focus on what matters.

    0
    0

    Comments (0)

    Sign in to join the conversation

    No comments yet. Be the first to share your thoughts!

    Subscribe to our blog

    Get the latest posts delivered to your inbox