How to Configure Call Queues, Auto Attendants, and Resource Accounts in Microsoft Teams Phone

Modern enterprise voice infrastructure requires agile, cloud-native call distribution to route customer inquiries, technical support requests, and internal switchboard traffic efficiently. Microsoft Teams Phone replaces complex on-premises PBX hardware with cloud-based voice routing primitives: Auto Attendants (interactive voice response systems), Call Queues (hunt groups and call distribution engines), and Resource Accounts (service identities bound to phone numbers and licences).

For Microsoft 365 administrators and telecommunications engineers, correctly architecting these components ensures seamless call handling, accurate holiday schedule failover, and optimal agent presence routing across desktop, mobile, and IP desk phone endpoints.

Architectural Overview: The Teams Voice Routing Hierarchy

Inbound PSTN calls follow a deterministic traversal path through the Microsoft 365 voice fabric:

Component	Architectural Role	Licensing & Identity Requirements
Direct Inward Dialling (DID)	Public telephone number assigned via Microsoft Calling Plans, Direct Routing, or Operator Connect.	Telco carrier allocation bound to an Entra ID Resource Account.
Resource Account	Disabled Entra ID user object representing the application endpoint.	Requires a free Microsoft Teams Phone Standard – Virtual User licence.
Auto Attendant (AA)	Interactive Voice Response (IVR) greeting caller, evaluating business hours, and parsing DTMF/voice commands.	Bound to a Resource Account if receiving direct external dial-in traffic.
Call Queue (CQ)	Holds callers in queue, plays periodic comfort announcements, and distributes calls to agents.	Bound to a Resource Account for direct dialling or transfers from an Auto Attendant.
Call Agents	Individual users, Microsoft 365 Groups, or Teams Channels that receive inbound voice calls.	Individual users require a Teams Phone Standard licence.

Provisioning Resource Accounts and Assigning Virtual User Licences

Every Auto Attendant or Call Queue that requires an assignable telephone number or internal SIP uri must be anchored to an Entra ID Resource Account.

Step 1: Create the Resource Account in Teams Admin Center

1. Navigate to the Microsoft Teams admin center (admin.teams.microsoft.com).
2. Expand Voice > Resource accounts.
3. Click Add.
4. Specify the account attributes:
   • Display name: e.g. Main Line Auto Attendant or Tier 2 Support Queue.
   • Username: e.g. [email protected].
   • Resource account type: Select either Auto attendant or Call queue.
5. Click Save.

Step 2: Assign the Virtual User Licence

In the Microsoft 365 Admin Center (admin.microsoft.com), locate the newly created user object under Active users and assign the free Microsoft Teams Phone Standard – Virtual User licence. This grants the account the right to hold phone numbers without incurring commercial subscription costs.

Step 3: Assign a Telephone Number via PowerShell

# Connect to Microsoft Teams PowerShell module
Connect-MicrosoftTeams

# Assign a Direct Routing or Calling Plan telephone number to the resource account
Set-CsPhoneNumberAssignment `
  -Identity "[email protected]" `
  -PhoneNumber "+442079460991" `
  -PhoneNumberType CallingPlan

Configuring Multi-Level Auto Attendants (IVR)

Auto Attendants serve as the front door for inbound telephone traffic, orchestrating greetings, time-of-day logic, and menu choices.

Step 1: Define General Information and Operator Routing

1. In Teams Admin Center, go to Voice > Auto attendants > Add.
2. Enter a descriptive name (e.g. Corporate Front Desk AA).
3. Select your operating time zone and default language (e.g. English (United Kingdom)).
4. Specify an Operator destination (an individual receptionist or Call Queue) so callers can press ‘0’ to bypass automated menus.

Step 2: Configure Business Hours and Call Flow

1. Define operating shifts (e.g. Monday to Friday, 08:30 to 17:30).
2. Under First play a greeting message, choose either:
   • Add an audio file: Upload a high-fidelity .wav or .mp3 studio recording.
   • Type a greeting message: Leverage Microsoft Text-to-Speech (TTS) neural voices.
3. Under Route the call, select Play menu options.
4. Map DTMF dialling keys to destinations:
   • Key 1 > Transfer to Call Queue > Sales Queue.
   • Key 2 > Transfer to Call Queue > Support Queue.
   • Key 3 > Transfer to Auto Attendant > Regional Office AA.

Step 3: Set After-Hours and Holiday Call Handling

Configure dedicated after-hours flows to redirect callers directly to shared voicemail, playing an out-of-hours announcement and transcribing audio messages into a monitored Microsoft 365 Group mailbox.

Configuring Call Queues and Agent Distribution Algorithms

Call Queues receive transferred calls and distribute them across agents according to strict routing algorithms.

Step 1: Initialise the Call Queue

1. Navigate to Voice > Call queues > Add.
2. Assign a name (e.g. Global IT Service Desk) and bind the previously created Call Queue Resource Account.

Step 2: Assign Call Agents and Channel Binding

Teams supports two primary agent assignment architectures:

• Direct User/Group Assignment: Adds individual users or security groups. Agents manage availability via standard status toggles.
• Collaborative Calling (Channel Binding): Links the queue directly to a specific channel within a Team (e.g. IT Operations > Voice Inbound). All team members automatically become agents and share a unified voicemail history and call log inside the Teams client.

Step 3: Select the Agent Routing Method

Choose an algorithm tailored to your staffing profile:

Routing Method	Distribution Mechanism	Best Practice Scenario
Attendant Routing	Rings every available agent simultaneously. First agent to answer claims the call.	Emergency response desks and small front-office teams where rapid pickup is critical.
Serial Routing	Rings agents one at a time in a deterministic, ordered list until answered.	Hierarchical escalation teams where senior specialists only receive overflow calls.
Round Robin	Distributes calls equally across agents in a circular sequence based on historic call attempts.	Equitably distributes sales leads across account representatives.
Longest Idle	Rings the agent whose presence has remained in an idle/available state for the greatest duration.	High-volume customer support centres optimising agent workload balance.

Step 4: Enable Presence-Based Routing and Agent Opt-Out

• Presence-based routing: When enabled, the queue checks agent status in real time and suppresses ringing if an agent is Busy, In a call, Presenting, or Do Not Disturb.
• Conference mode: Always set Conference Mode to Turn on. This pre-connects the caller and agent to a multi-party conference bridge, reducing call connect latency from 3–5 seconds down to under 500 milliseconds.
• Agent opt-out: Allows agents to toggle their participation in specific queues via their Teams client settings during focused project work.

Troubleshooting Teams Phone Voice Routing Anomalies

When inbound calls drop, menus loop, or agents fail to receive calls, consult this diagnostic matrix:

Symptom	Probable Root Cause	Remediation Procedure
Inbound caller hears fast busy tone or “Number is not in service”.	Telephone number is not assigned to the Resource Account, or Virtual User licence has expired/unassigned.	Verify licence in Microsoft 365 Admin Center. Check number binding via Get-CsPhoneNumberAssignment -Identity <Account>.
Call Queue rings, but no agents’ devices ring.	Presence-based routing is enabled while all agents are in “Busy” or “Do Not Disturb” states, or agents have opted out.	Inspect agent presence status. Verify in Teams client under Settings > Calls > Call Queues that agents have not toggled the queue off.
Audio greeting does not play, jumping immediately to fallback.	Uploaded audio file has an unsupported codec or exceeds size limitations (maximum 5 MB).	Re-encode audio file to standard PCM 16-bit 44.1 kHz mono WAV, or replace temporarily with neural Text-to-Speech (TTS).
DTMF key presses are ignored by the Auto Attendant.	Inbound carrier SIP trunk is not negotiating RFC 2833 / RFC 4733 telephone-event payload formatting.	Inspect SBC (Session Border Controller) logs for Direct Routing trunks. Ensure DTMF payload type 101 is configured in SIP SDP.

Properly configuring Microsoft Teams Phone Auto Attendants and Call Queues provides enterprise organisations with a resilient, scalable, and responsive voice platform that effortlessly accommodates fluid hybrid working arrangements.