Source note · Troubleshooting Teams call queues and auto attendants
An auto attendant or call queue nested behind a voice app that has already answered the call does not need a resource account, even if it transfers calls externally; the resource account on the first voice app receiving the call is the one that must be licensed.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone
- Subsystem
- nesting
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Planning - Nested Call Flows - Microsoft Teams — Microsoft · tier 2 current vendor documentation · How to nest call flows > Directly reference the Teams Phone Agent, Auto Attendant, or Call Queue
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams call queues and auto attendants: source note teams-call-queue-troubleshooting-nested-no-resource-account. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-call-queue-troubleshooting-nested-no-resource-account
BibTeX
@misc{warmtransfer-claim-teams-call-queue-troubleshooting-nested-no-resource-account,
title = {Troubleshooting Teams call queues and auto attendants: source note teams-call-queue-troubleshooting-nested-no-resource-account},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-call-queue-troubleshooting-nested-no-resource-account},
note = {Source note teams-call-queue-troubleshooting-nested-no-resource-account, checked 2026-09-25}
}