Microsoft is set to bring a long-awaited convenience to Teams Phone users: starting in August 2026, voicemail messages left for Auto Attendants will appear inside the Teams Queues app, alongside missed-call records. The change, detailed in the Microsoft 365 Roadmap under ID 567457, means customer-facing teams can review voicemail and call history without leaving the same operational screen.

What’s Changing

Currently, Teams already supports shared voicemail for Auto Attendants and Call Queues. Calls can be directed to a voicemail destination backed by a Microsoft 365 group, distribution list, or mail-enabled security group, letting multiple people access incoming messages. And voicemail linked to a Call Queue already shows up in the Queues app under the associated missed-call entry in shared call history.

The missing piece has always been Auto Attendant voicemail. A caller who dials into a front-door menu, navigates options, and finally ends up in a shared voicemail box leaves a message that agents can’t see inside Queues. Instead, staff must monitor a separate group mailbox or Outlook delivery. The new feature plugs that gap. According to the roadmap, once deployed, any voicemail left after an Auto Attendant call will appear in the Queues app right next to the missed-call record—just like Call Queue voicemail does today.

This matters for any number that doesn’t route directly to an agent queue: after-hours calls, departmental lines, holiday messages, or main switchboard numbers where a receptionist isn’t always available. An agent or supervisor can now open the Queues app, scan the shared call history, and listen to any voicemail that a caller left at the Auto Attendant stage, all within the same flow they use for live call handling and queue management.

Why This Matters for Different Teams

For a support team handling customer inquiries, the practical benefit is context. An incoming call that reached the Auto Attendant, waited, and then went to voicemail is no longer a disconnected event. Agents see it in the same timeline they already monitor. If a missed-call notification arrives with a voicemail attached, they can immediately review the message and return the call without switching to Outlook or a separate group mailbox. The call and its context—when it came in, from which Auto Attendant menu—remain tied together.

Sales and service teams gain a similar advantage. A prospect who dials the main number and lands in a “leave a message” queue after hours won’t sit in a siloed mailbox. The next morning, a salesperson can open Queues, spot that call, and act on the voicemail directly. It reduces the chance of messages getting lost across multiple tools.

For IT admins and supervisors, the change simplifies oversight. Instead of verifying whether agents are checking a separate mailbox, they can use the Queues app’s existing monitoring capabilities to see unanswered Auto Attendant calls and their voicemails in one view. The app already serves as a hub for managing Call Queues and Auto Attendant settings; adding this visibility turns it into the primary place to handle all customer voice interactions.

The Backstory: Shared Voicemail in Teams

Teams Phone has incrementally built out shared voicemail features. The ability to route calls to shared voicemail destinations has existed for years, but Teams originally left voicemail management to email clients. That worked for some organizations, but it forced teams to monitor group mailboxes alongside their call-handling tools. The Queues app, introduced as a centralized workspace for call management, began surfacing queue-related voicemail a while ago. Yet Auto Attendant voicemail was conspicuously absent.

Microsoft’s own documentation once indicated that Auto Attendant shared voicemail would appear in Queues during the second quarter of 2026. The roadmap now pins a more specific target: August 2026. No reason was given for the refined date, but it aligns with a pattern of Microsoft first teasing broader Q2 availability and later committing to a month as development wraps up. The feature is listed as “in development” for general availability worldwide in Microsoft’s multi-tenant cloud, with no mention of GCC or other clouds yet. That suggests the roll-out will first hit standard commercial tenants.

Admin Checklist Before the Rollout

If your organization uses Auto Attendant menus—whether for off-hours routing, departmental directories, or a main switchboard—there are a few steps to take now, well before August, to ensure you’re ready.

1. Check your Auto Attendant configuration. The feature requires that calls reaching the Auto Attendant are already set to route to a shared voicemail. If your Auto Attendant simply disconnects after hours or plays a message without offering to record, nothing will appear in Queues. Confirm that the relevant call flows direct to a shared voicemail destination.

2. Verify group ownership and membership. Shared voicemail is delivered to a Microsoft 365 group, distribution list, or mail-enabled security group. Microsoft strongly recommends using a distinct group for each Auto Attendant or Call Queue. If you’ve been reusing one group across multiple voice applications, stop now. Reusing a single group can expose voicemail to the wrong people—for instance, a support agent might accidentally hear a sales prospect’s message. Create separate groups and update your routing rules accordingly.

3. Confirm Queues app access and licensing. The Queues app is part of Teams Phone operations. Users who need to see Auto Attendant voicemail here must have the appropriate Teams Phone license—typically a Teams Phone Standard or Teams Phone with Calling Plan license, or an E5 plan that includes it—and must be authorized to access the relevant queues and auto attendants. Check that the intended agents, supervisors, and receptionists have the app pinned and can sign in. A quick audit now prevents a scramble in August.

4. Rehearse the workflow once the feature hits preview. Microsoft often rolls out new capabilities to a subset of users first. If your tenant gets early access, have a small pilot group test the experience. Confirm that voicemail appears where expected, that the correct people see it, and that no messages spill over into unintended groups. Use the feedback to fine-tune permissions before enabling it for everyone.

Looking Ahead

August 2026 is a target, not a guarantee. Microsoft’s roadmap dates can shift, and the actual tenant-by-tenant rollout could extend over several weeks. Still, the firming up of the date from a vague Q2 to a specific month signals development is on track.

Once the feature lands, organizations that previously relied on email-based voicemail workflows may finally be able to consolidate. IT teams can then shift training and documentation away from group mailboxes and toward the Queues app as the single pane of glass for managing customer calls—live, missed, or voiced. Long term, this likely sets the stage for deeper integration between voicemail, transcription, and AI-driven call summaries inside the Queues app, but those remain speculation for now.