Reference - Supported Configurations - Microsoft Teams

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/aa-cq-reference-limits-supported-configurations

Published

2026-09-04

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Microsoft Learn terms of use; source repository license not verified in this run; no-redistribution; short excerpts and locators only

Source notes citing this source

• Auto attendants support 54 text-to-speech locales but only 14 speech-recognition locales; choosing a locale without speech recognition disables voice inputs and limits dial-by-name to keypad entry. in context
• There is no per-tenant limit on auto attendants; each auto attendant has one after-hours call flow and up to 20 holiday sets of up to 50 holidays each. in context
• An auto attendant or call queue can have at most 15 authorized users. in context
• Greeting audio files may be WAV (uncompressed linear PCM), WMA (mono) or MP3, up to 5 MB, and typed greetings may be up to 1,000 characters. in context
• Web click-to-call into auto attendants and call queues is capped at 40 calls per minute across the whole tenant. in context
• A call queue supports up to 200 agents, of which at most 20 can be added as individual users; for larger teams, groups, channels or shifts only the first 200 Enterprise Voice-enabled members in alphabetical order become agents. in context
• Agent alert time can be set from 15 to 180 seconds, but agents using Teams on Windows with a Bluetooth audio device whose call buttons control Teams calls are capped at 120 seconds. in context
• Automatic recording, compliance recording, shared call history, and monitor/whisper/barge/takeover for call queues all require conference mode. in context
• When a voice app transfers to an external number, Calling Plan and Operator Connect display the original caller's number; for Direct Routing the result depends on the SBC's P-Asserted-Identity setting (Disabled, the default, shows the caller; Enabled shows the resource account number). in context
• An auto attendant supports one after-hours call flow, up to 20 holiday sets with up to 50 holidays per set, and up to 15 authorized users. in context
• Because the channel-based interface is desktop-only and channel queues can take up to 24 hours to go live, users-and-groups membership is probably the better fit for agents who mainly answer on mobile or desk phones, and a channel the better fit for desktop teams that collaborate on calls. inferred in context
• Call queue agent alert time can be set from 15 to 180 seconds. in context
• Greeting and music audio files can be WAV (uncompressed linear PCM), WMA (mono only) or MP3, and must be no larger than 5 MB. in context
• Channel-based call queues are supported on the Teams Windows and Mac desktop clients; agents on other devices can still answer calls but do not get the collaborative calling interface. in context
• When a voice app transfers to an external number, Calling Plan and Operator Connect present the original caller's number; for Direct Routing it depends on the SBC's P-Asserted-Identity setting: Disabled (default, recommended) shows the original caller, Enabled shows the resource account number. in context
• Serial routing order cannot be set when membership comes from a group, Shifts schedule group or Teams channel. in context
• Transfer mode (Conference mode off) is legacy and is set to be deprecated in the second half of 2026, with Microsoft promising at least three months' notice of the removal date. in context
• Transfer mode (conference mode off) is legacy; Microsoft says deprecation is planned for the second half of 2026, with the exact timeline confirmed and a Message center post at least three months before removal. in context
• Call queue agent alert time can be set from a minimum of 15 to a maximum of 180 seconds, but for agents on Teams for Windows with a Bluetooth device selected as the Teams audio device the maximum ring time is 120 seconds. in context
• Automatic recording, compliance recording, shared call history and monitor/whisper/barge/takeover for call queues all require conference mode to be enabled. in context
• Call queues assigned a Direct Routing number do not support Skype for Business clients, Lync clients or Skype for Business IP phones as agents, and support the Teams client only in TeamsOnly coexistence mode. in context
• When a voice app transfers to an external number, Calling Plan and Operator Connect show the original caller's number, while Direct Routing depends on the SBC's P-Asserted-Identity setting: Disabled (default, recommended) shows the original caller, Enabled shows the resource account number. in context
• Microsoft's supported-configurations reference says call queue transfer mode is set to be deprecated in the second half of 2026, with the exact timeline to be confirmed at least three months in advance. in context

Cite this source record

APA

WarmTransfer. (2026, September 4). Reference - Supported Configurations - Microsoft Teams. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-aa-cq-limits

BibTeX

@misc{warmtransfer-ms-learn-aa-cq-limits,
  title  = {Reference - Supported Configurations - Microsoft Teams},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-aa-cq-limits},
  note   = {Microsoft, accessed 2026-09-24}
}