Microsoft has started rolling out multi-line calling support to Teams Phone on Android and iOS, closing a major gap between the mobile and desktop experience that forced road warriors to carry extra devices or sign into separate accounts just to present the right business number.

Roadmap item 565131 entered general availability in July 2026 for worldwide standard multi-tenant customers, according to the Microsoft 365 roadmap. The update gives mobile workers the ability to make and receive calls through up to 10 assigned phone numbers—all from one Teams account. A unified call history, line-aware notifications, and filters now live on the small screen.

What Actually Changed on Your Phone

The mobile Teams client now mimics the desktop multi-line experience first announced in April 2026. Four capabilities form the core of this release:

  • Outbound line selection: Before you dial a number, a line picker sits below the dial pad. Tap it to choose which of your assigned business numbers will appear on the recipient’s caller ID. The sequence—pick the identity, then enter the number—forces a deliberate choice instead of a post-call “oops.”
  • Incoming call context: When someone calls you, Teams shows which of your lines they dialed. A salesperson with Chicago and Dallas numbers immediately knows which market the caller intended to reach. That determines the greeting, the customer record they pull up, or even whether a legal disclosure is required.
  • Unified call history: All incoming and outgoing calls appear in one chronological list, but each entry carries a tag identifying the line involved. No more switching accounts to piece together activity. A mobile worker covering three regions can see every missed call without logging out and back in.
  • Filter by line: The recent-calls filter lets you narrow the view to one or more assigned numbers. A store manager on the go can check missed calls for a single location, ignoring the rest.

These features are simple on paper, but together they turn the Teams mobile app into a credible replacement for a multi-line desk phone. You keep one presence state, one authentication token, and one calling interface—while juggling several telephone identities.

Microsoft says the rollout is currently “rolling out,” which means availability may vary between tenants and devices even though the July 2026 target has passed. The feature requires a functioning Teams Phone deployment with numbers already assigned and properly licensed.

What It Means for You

The impact depends on your role:

For mobile workers and frontline staff
Field engineers, home-health aides, real estate agents, and traveling executives can finally leave the office without leaving one of their business lines behind. Instead of carrying a second phone or giving customers a personal mobile number, they dial out through an approved business identity. Incoming calls display the line that was dialed, preserving the context that often gets lost when calls are forwarded or looped through a queue.

For IT administrators
The feature reduces account sprawl. You can assign multiple numbers directly to a user instead of creating separate Teams accounts or relying on caller ID substitution policies. That simplifies onboarding when an employee takes on an additional region, brand, or department. But it also introduces a new change-management challenge: users must be trained to select the right line before dialing, because the technical permission doesn’t guarantee behavioral adoption.

For small businesses
An owner who handles sales, support, and supplier relations can now publish three distinct numbers yet answer them all from one Teams mobile app. The same goes for a professional practice that uses separate numbers for each location. Consolidation means fewer devices and a clearer boundary between business and personal calls—as long as everyone understands that Teams Phone licensing and PSTN connectivity still apply; this is not a free consumer feature.

How We Got Here

Teams Phone has steadily evolved from a collaboration add-on into a full PBX replacement. Microsoft added cloud call-control, direct routing, operator connect, and Teams Phone Mobile—a service where a carrier SIM number doubles as the user’s Teams number. But the one-user-one-number model didn’t match reality for many employees.

A regional salesperson might need local numbers in five cities. An attorney might represent three practice areas. Historically, organizations patched this gap with shared line appearances, call queue workarounds, or separate user accounts—each bringing administrative overhead and muddled call records.

Microsoft first tackled the problem with “user multi-line,” which lets administrators assign up to 10 phone numbers to a single Teams Phone user. The desktop and Teams-certified phone devices gained general availability in April 2026. Now, the mobile clients catch up, meaning the line picker, notifications, and unified history travel with the employee.

Why did mobile take longer? On a small screen, the interface must clearly expose the active calling identity without cluttering the dial pad. Microsoft’s design places the line picker directly beneath it, uses compact badges in history, and relies on a filter instead of separate tabs for each line. It’s a minimalist approach that demands clear labeling and a little practice.

What to Do Now

If your organization uses Teams Phone, you can take concrete steps to deploy multi-line calling on mobile:

  1. Audit your numbers and workflows. Document which published numbers exist, who currently answers them, and how outbound caller ID is handled. Decide whether a number truly belongs to one person or should stay in a call queue, auto attendant, or delegation model. Multi-line isn’t the right answer for every scenario.
  2. Verify licensing and PSTN compatibility. Confirm that your users, number types (user, service, toll-free), connectivity model (Operator Connect, Direct Routing, etc.), and countries support the configuration. Some operator restrictions on caller ID manipulation may still apply.
  3. Label lines for small screens. A user staring at “Line 2” or a 10-digit phone number on a mobile app will guess the wrong identity half the time. Use short, meaningful labels like “Dallas Sales,” “Aftercare,” or “West Counsel.” Test visibility on actual Android and iOS devices before broad rollout.
  4. Run a pilot with clear feedback loops. Select a handful of users who will genuinely need multiple lines. Have them test placement of outbound calls, incoming notification clarity, history filtering, and callbacks. Pay special attention to how notifications appear when the device is locked or in a focus mode.
  5. Review emergency calling configuration. Multi-line adds complexity. Each assigned number, network location, and device must be accounted for in your emergency calling policies. Train users explicitly on whether to call 911/112 through Teams or the native dialer in different situations.
  6. Train before you turn it on broadly. The technical assignment is the easy part. Employees accustomed to one default number may forget to pick a line. Emphasize a simple rule: check the selected line before every external call whose identity matters. Show them how to return a call from the history log using the appropriate line, not the first one that appears.
  7. Monitor for wrong-line calls and support tickets. In the first weeks, watch for patterns: users dialing with the wrong identity, missed notifications due to battery optimization settings, or confusion between Teams and the native cellular dialer. Adjust training and line labels accordingly.

For users: After your admin assigns multiple numbers, open the Teams mobile app, navigate to Calls, and look for the line picker below the dial pad. Before you enter a number, tap it and select the appropriate business identity. When an incoming call arrives, glance at the line label before answering to orient yourself. To filter recent calls, open the history and tap the filter icon—choose one or more lines to narrow the list.

Outlook

The July 2026 release achieves core mobile parity, but three practical challenges loom:

  • Default line selection. Users will clamor for a “preferred” number that sticks for routine calls, with a quick switcher for exceptions. Currently, you pick each time you dial—a feature and a friction point.
  • Click-to-call integration. Many mobile calls start outside Teams: tapping a phone number in an email, a CRM app, or a web page. How Teams prompts for line selection in those flows will determine whether the feature actually gets used outside of deliberate dial-pad calls.
  • Reporting and administration at scale. Today’s unified history is a user-facing convenience. Admins will need per-line analytics—call volume, missed calls, quality metrics—to manage dozens of multi-line users. PowerShell and Microsoft Graph coverage will indicate how seriously Microsoft treats this as an enterprise feature.

For now, the roadmap specifies availability only in worldwide standard multi-tenant cloud. Government, sovereign, or specialized cloud environments must wait for separate announcements.

The mobile multi-line feature won’t replace call queues, contact centers, or compliance platforms overnight. But it does eliminate one of the last reasons a mobile worker needed to carry a second phone or cloud work identity. The line picker is small; the implications are not.