Microsoft will release new privacy controls for Teams delegated calling this August, giving people the power to lock an active call and keep their authorized assistants, managers, or help-desk staff from joining or resuming it. The update, listed on the Microsoft 365 roadmap under ID 567306 on July 7, also introduces optional warning tones that sound when a delegate enters the conversation.

What’s Actually Changing

A delegator in Teams Phone—someone who has assigned another user to make or receive calls on their behalf—will soon see a lock option during a live call. When toggled on, that lock prevents any delegate from barging in, listening silently, or retrieving a held call. The feature works on Teams desktop and Mac clients, and the roadmap marks general availability for August 2026 across all major cloud instances: commercial, GCC, GCC High, and DoD.

Alongside the lock is an audio cue. Organizations can optionally activate warning tones that play to all participants the moment a delegate joins or resumes a conversation. The tone is not an announcement of who joined or why; it simply signals that the call’s human perimeter just changed.

Both controls target a predictable friction: delegation relationships that are too static. Today, once a delegator grants an assistant or colleague the right to answer and manage calls, that permission typically stays wide open for the entire call session. The new lock flips the default. It lets the person whose line is represented become the active authority, narrowing access when the conversation demands it without destroying the delegation setup.

What It Means for You

For Managers, Executives, and Anyone Using an Assistant

You no longer have to choose between letting a delegate screen every call and disabling delegation entirely before a sensitive discussion. A call that starts as routine—a vendor check-in, a customer callback—can be locked as soon as the topic shifts to personnel matters, contract negotiations, or legal advice. The lock is a per-call control, so you keep your delegation roster intact and use the restriction only when confidentiality matters.

For Assistants and Delegates

The lock is a boundary that protects you, too. When you can’t re-enter a call, the system makes that prohibition visible rather than leaving you to guess whether your manager is simply away. That reduces the social risk of overstepping, especially if you’re expected to juggle multiple lines and retrieve parked calls. The warning tone also gives you a durable signal: if you do need to join, participants know it happened.

For IT Administrators and Compliance Teams

The feature arrives with a short checklist. First, it doesn’t create a new policy surface yet—so you’ll need to handle user adoption through training and documentation, not through central enforcement. Second, the lock and tones raise immediate audit questions: Will join attempts appear in call analytics? Can you report on how often a lock was used? The roadmap entry is silent on logging, which means compliance teams should test early and verify whether the events will satisfy internal or regulatory requirements.

How We Got Here

Teams delegation, also known as shared line appearance, was built to emulate a classic PBX assistant workflow: one person can screen, place, and retrieve calls on behalf of another. That model works beautifully until the call turns private. On a physical desk phone, lights and physical presence gave cues about who was handling the line. Teams collapses those signals into software states, and a delegate could join a call without any audible or visual tip-off.

Microsoft has been hardening Teams Phone for enterprise voice workloads for years, adding calling policies, PowerShell management, and government-cloud support. The lock and warning tones close a gap that many organizations didn’t know they had—until a board member asked why an assistant was silently listening to a merger discussion. By targeting all four cloud segments from the start, Microsoft signals that this isn’t a convenience add-on; it’s a governance tool for regulated tenants where confidentiality is a legal, not just a cultural, requirement.

What to Do Now

  1. Audit your delegation relationships. Run a report of all delegate assignments in your tenant. Look for stale entries (former assistants, rotated roles) that linger without business need. A lock won’t help if a delegator doesn’t know who still has access.
  2. Check licensing and policy alignment. Both delegators and delegates need Teams Phone licenses. Confirm that your calling policies enable delegation. The AllowDelegation setting is on by default, but review it across your policy assignments.
  3. Draft accountable guidance. Create a short internal guide that lists specific scenarios for using the lock. Vague advice like “use lock for confidential calls” is forgettable; concrete examples (HR discussions, legal consults, executive compensation, incident response) give users a clear trigger.
  4. Plan for endpoint gaps. The August rollout lands on desktop and Mac first. If your organization relies heavily on Teams phones or mobile clients, test what delegates see when a call is locked from a desktop. Server-side enforcement should hold, but the user experience may differ.
  5. Engage your compliance team early. Schedule a review of Teams audit logs and call analytics to document current capabilities. When the feature lands, you’ll need to verify whether lock events and delegate join tones appear in those logs. If they don’t, you may need to rely on user training or third-party tools until Microsoft adds reporting.

What to Watch Next

The roadmap entry doesn’t promise admin controls for the lock or warning tones. That will be the real inflection point. If Microsoft adds a LockDelegatedCalls policy or a PowerShell cmdlet to enforce tones, the feature moves from user empowerment to organizational control. Without those, expect a messy adoption curve where some teams use it habitually and others never discover it.

Also watch for endpoint parity. The feature is desktop-first, but delegation spans every Teams surface. If a delegator locks a call on their laptop and a delegate tries to join from an IP phone, the experience needs to be seamless and unmistakable—otherwise, the privacy boundary becomes unreliable.

The lock and tones may seem small now, but they represent a shift in how Microsoft thinks about shared communications. Live boundaries that respond to context, rather than static permissions set once and forgotten, are the kind of improvement that turns delegation from a cost-saving hack into a governed enterprise workflow. Get ready to test it, talk about it, and train your users before the first awkward silence turns into a compliance headache.