What Busy on Busy Actually Does
Without Busy on Busy, Microsoft Teams behaves the way most phone systems always have: if you're on a call and someone else calls you, the second call rings through anyway, giving you a call-waiting notification you can accept, decline, or ignore. That's the default, and it's fine for occasional calls — but for anyone whose job is genuinely back-to-back calls (support desks, reception, sales floors), a second ring landing on top of an active conversation is a distraction at best and a compliance problem at worst.
Busy on Busy changes that behaviour at the policy level. When it's enabled for a user, Teams checks whether they're already on a call, in a conference, or have a call on hold before it lets a new call through. If they are, the new call never rings at their end — instead, depending on how the policy is configured, it's either rejected outright with a busy signal, or redirected according to that user's unanswered-call settings (typically voicemail, or forwarding to a colleague). Either way, the person already on the phone is left alone to finish their call.
Busy on Busy vs. the Busy Status You Already See
This is the mix-up the name invites, and it's worth being explicit about: Busy on Busy is not another shade of the Busy presence badge you already know from Microsoft Teams' Busy status. That badge — the plain solid red dot that appears the instant a calendar meeting starts or you join a call — is a presence indicator. Busy on Busy is a call-routing policy. They can be true at the same time and have nothing to do with each other.
| Aspect | Busy status (presence) | Busy on Busy (calling policy) |
|---|---|---|
| What it is | The red dot on your profile picture | A rule for handling a second incoming call |
| What triggers it | A calendar meeting starting, or joining a call | Already being on a call, conference, or hold |
| What it changes | How your presence looks to everyone | Whether a second call rings, is declined, or is redirected |
| Who sets it | Automatic, or you manually | An admin's calling policy — user control is limited |
| Where it's configured | Nowhere — it's automatic | Teams admin center or PowerShell |
In other words: your status can say Busy with Busy on Busy turned completely off, and a second call will still ring through and interrupt you. Conversely, Busy on Busy can be silently active in the background — declining calls on your behalf — without your presence badge ever hinting that it exists. If what you're actually trying to manage is your visible status rather than call handling, how to keep Teams active is the right guide, not this one.
How to Turn Busy on Busy On or Off Yourself
Microsoft built a genuine self-service path for this: open your profile picture in Teams, go to Settings → Calls, and — if your admin has enabled it for you — you'll find a Busy on Busy section with three routing choices for what happens when you're already on a call: let the new call come through as normal, play a busy signal, or redirect it based on your existing unanswered-call preference (voicemail or forwarding).
The catch: that self-service picker only works if your admin has set your calling policy to UserOverride ("let users decide") and — per Microsoft's own support guidance — it currently only actually renders in classic Teams. Even with the right policy applied, it does not appear in the new Teams client. If you've gone looking for a Busy on Busy toggle in new Teams and come up empty, that's why — it isn't hidden somewhere else, it simply isn't surfaced there yet.
In practice, that means most people on new Teams — which is now the default client for the large majority of tenants — can't flip this themselves no matter how the policy is set. If you want it changed and you're on new Teams, the reliable path is asking your IT admin to update the policy directly, covered next.
How Admins Turn Busy on Busy On or Off for Everyone
Admins manage this from the Teams admin center, under Voice → Calling policies. Opening the Global policy (or a custom policy scoped to a specific group) surfaces a setting labelled around "Busy on busy while in a call, conference, or on hold", with three states:
- On — a second incoming call is rejected with a busy signal.
- Voicemail — a second incoming call is routed straight to the user's unanswered-call settings instead of ringing.
- Off — calls behave normally; a second call rings through and can be accepted, declined, or ignored.
Changing the setting on an existing policy applies to everyone that policy is assigned to, and typically takes a few hours to reach all clients. For anything more selective than the tenant default, create or assign a separate calling policy to the specific group — call-center agents, front-desk staff, on-call rotations — rather than changing the Global policy everyone else inherits.
How to Set Busy on Busy with PowerShell
For scripted rollouts or bulk changes, the same setting is controlled by the -BusyOnBusyEnabledType parameter on Set-CsTeamsCallingPolicy in the Microsoft Teams PowerShell module. After connecting with Connect-MicrosoftTeams, the four valid values are:
| Value | What it does |
|---|---|
Enabled | New or incoming calls are rejected with a busy signal. |
Unanswered | The user's unanswered-call settings take over — voicemail or forwarding. |
Disabled | New or incoming calls are presented to the user as normal. |
UserOverride | Hands the choice to the user in Calls settings — classic Teams only, as noted above. |
To disable Busy on Busy tenant-wide:
Connect-MicrosoftTeams
Set-CsTeamsCallingPolicy -Identity Global -BusyOnBusyEnabledType Disabled
To enable it only for a specific group, apply a named policy instead of Global, then grant it to the relevant users:
New-CsTeamsCallingPolicy -Identity "FrontDeskBusyOnBusy" -BusyOnBusyEnabledType Enabled
Grant-CsTeamsCallingPolicy -Identity "jane.doe@contoso.com" -PolicyName "FrontDeskBusyOnBusy"
Does Busy on Teams Turn Yellow?
No — and if you've seen a yellow dot and assumed it meant Busy, that's the actual source of the confusion. Busy in Microsoft Teams is always a solid red circle, never yellow. Yellow belongs to an entirely different family of statuses: Away, Be Right Back, and Appear Away all render as a yellow clock icon. A yellow badge almost always means Teams has marked you Away — most commonly from roughly five minutes of no keyboard or mouse activity — not that you're on a call. See every Teams status icon explained for the full colour reference if you're trying to identify a specific badge.
Why Do My Teams Keep Saying Busy?
Almost always because Teams is reading something real, not glitching. Busy fires automatically the instant an Outlook calendar event starts — even before you've joined the Teams meeting — and again the moment you connect to any call. If Busy is showing when neither of those is actually true, the usual culprits are a calendar event that's still technically "in progress," a call left connected on another signed-in device, or stale local presence state after your machine wakes from sleep. That's a different problem from Busy on Busy, which never changes your presence badge — it only decides what happens to a second call once you're genuinely Busy. For the full troubleshooting path on a stuck or wrong Busy badge, see Microsoft Teams Busy status explained.
Busy on Busy Isn't the Same as Staying Green
It's worth being blunt about the boundary here: nothing about Busy on Busy helps you stay Available between calls and meetings, and turning it on or off doesn't touch the problem most people searching Teams-status topics are actually trying to solve — Teams marking you Away after about five minutes of inactivity, roughly six times more aggressively than Slack's 30-minute window. Busy on Busy only ever governs what happens to a second call while you're genuinely on a first one; it has no effect on the idle timer, and it can't hold your status green while you step away from your keyboard. For that, how to keep Microsoft Teams active covers every real method, honestly, including the trade-offs of each.