Microsoft started rolling out the Teams Queues app to its GCC High and Department of Defense cloud environments this month, according to Microsoft 365 Roadmap item 565218. The feature, which reached general availability in July 2026, gives service desk leads and call center supervisors inside the most sensitive government tenants the same native queue management tools commercial customers have been using for months. For the first time, workers in defense agencies and federal contractors can view live call metrics, adjust routing, and coach agents without leaving Microsoft Teams.
What the Queues App Actually Delivers
The Queues app turns the Teams client into a lightweight operations console for call queues and auto attendants. Instead of treating call routing as an administrative task that requires PowerShell commands or frequent trips to the Teams admin center, authorized users can perform daily adjustments directly in a pane that sits alongside their chats and channels.
Depending on the permissions an admin assigns, a queue lead can see how many calls are waiting, how long the longest caller has been holding, and which agents are signed in. They can review historical reports on queue performance. They can add or remove agents from a queue, change the opening hours, swap out the greetings, and tweak how calls overflow when nobody answers.
The app also supports real-time coaching and monitoring features—Monitor, Whisper, Barge, and Takeover—that let supervisors listen in, offer advice only the agent hears, join the call directly, or even take over the conversation. These functions are not open by default; an administrator must explicitly delegate them to specific individuals through Teams voice application policies. That granularity matters a lot in environments where call recordings and information barriers are tightly regulated.
Who Can Use It and What's Required
Microsoft classes the Queues app as a Teams Premium capability, which means three things must be true before a user sees it in their Teams sidebar. The user needs a Teams Phone license, a Teams Premium license, and their account must be voice-enabled. Additionally, they have to be a member of at least one call queue, because the app shows data only for queues the user is authorized to manage.
The licensing combination isn't new—it’s been the rule for commercial tenants since the app first shipped. But it's worth double-checking now because government cloud tenants often handle license assignments through separate procurement channels and may have Teams Phone already deployed without Teams Premium add-ons. Microsoft warns that it can take up to 48 hours after a Teams Premium license is assigned for the Queues app to appear.
Users also need the right level of permissions. The app is visible only if an admin grants access through a Teams voice application policy that links the user to specific queues and defines what they can do—view basic metrics, change membership, alter routing, or use monitoring features. Without that policy, even a fully licensed user won't see the app.
Why This Matters for Federal and Defense IT
This release closes a feature gap that federal and defense IT managers have been asking about for over a year. Commercial organizations have been able to let help desk supervisors manage queues without escalating to an admin, while GCC High and DoD tenants had to rely on administrative consoles or make due with limited visibility. For a military service desk answering hundreds of calls on a Monday morning, the ability to move agents between queues or flip a routing rule in real time can directly affect a base's operations tempo.
From a compliance standpoint, bringing the Queues app into sovereign clouds means that all the call data stays within the boundaries that the Department of Defense and other federal agencies require. The app uses the existing Teams infrastructure for transport and storage, so an agency's existing data residency and encryption settings apply automatically. There's no separate connector or external service to approve.
It also reduces administrative overhead. In many agencies, adjusting a queue's hours before a federal holiday meant filing a ticket, waiting for a Teams admin to make changes in the admin center, and hoping it propagated before the end of the day. Now a designated supervisor can do it in ten seconds. Over time, that responsiveness can measurably improve citizen service and internal operations.
What Administrators Should Do Right Now
The rollout status is still "rolling out," which means GCC High and DoD tenants will see the app appear over the course of July rather than on a single cut-over date. Admins should treat the next several days as an opportunity to get ahead of the configuration work.
Start with licensing: run a report to identify users who need the app and confirm they hold both Teams Phone and Teams Premium licenses. For agencies that have been holding off on Teams Premium, this might be the trigger to add it, because many of its other features—like real-time translations, meeting recaps, and advanced webinar controls—are already valued in the commercial sector.
Next, review the call queues and auto attendants themselves. Ensure each queue has a group of agents assigned and that the queue lead or supervisor is clearly defined. Create the necessary voice application policies. If supervisors will need monitoring capabilities, craft policies that explicitly grant Monitor, Whisper, Barge, and Takeover. The default Teams voice application policies do not include those permissions.
Then, consider how your users will find the app. By default, the Queues app is enabled for qualifying users, but it's not pinned to the Teams sidebar. Using a Teams app setup policy, push the app to the top of the left rail for your designated queue managers so they don't need to search for it. You can do this in the Teams admin center under Teams apps > Setup policies.
A word of caution: the Queues app is part of the broad "Microsoft apps" category. If you previously disabled that category to block other Microsoft apps, turning it back on will also make Queues, Insights, and Tasks available. Microsoft advises against disabling the category wholesale without understanding the impact. Instead, use app permission policies to control which users see the app.
Finally, after you've assigned licenses and configured policies, be patient. The documentation says it can take up to 48 hours for the app to show up for a newly licensed user. If it doesn't appear, verify that the user is a member of at least one call queue and that your app permission policies are not hiding the app.
How We Got Here: The Journey to Sovereign Clouds
Microsoft's sovereign clouds—GCC High and DoD—have always lagged behind the commercial service when it comes to feature releases. The delay isn't just technical; each new capability undergoes additional compliance reviews, security assessments, and packaging changes so that it works in environments where data must remain within U.S. borders and meet strict access control standards.
The Queues app first appeared in the commercial roadmap in early 2024 and rolled out through the middle of that year. As soon as it was available, government customers began asking when they would get it. Microsoft added roadmap item 565218 in early 2026, setting the tentative date for July. Now, that date has arrived, and the feature is showing up in the Teams client for qualifying users inside those protected tenants.
This release is part of a broader effort Microsoft has made to bring Teams Premium capabilities to government clouds. Earlier in 2026, several Teams Premium meeting features—such as intelligent recap and live translated captions—also became available in GCC High and DoD. The pace seems to be accelerating, which is good news for agencies that want feature parity without taking on extra compliance risk.
What to Watch Next
The arrival of the Queues app is one piece of a larger puzzle. Many government contact centers are exploring whether they can replace standalone call center platforms with Teams-native tools. While the Queues app is not a full contact center solution, it makes Teams Phone more capable as a light call-routing layer. Microsoft's roadmap includes deeper contact center integrations through third-party partners like Genesys and Avaya inside Teams, but those often require additional compliance work before they can land in sovereign clouds.
For now, GCC High and DoD tenants should focus on getting the Queues app deployed and seeing how it fits into their daily operations. As Microsoft continues to close the feature gap, the line between a traditional PBX and a cloud-based collaboration suite will keep thinning—even behind the locked doors of government IT.