Using the Small Window for Incoming Teams Calls
A recent improvement is the introduction of a small window for incoming Teams calls. It doesn’t sound like a great step forward, but switching to the small window is a surprisingly useful step. The sad thing is that many users won’t know that the option to switch exists because it’s buried in Teams settings. If you’re a busy person who takes lots of Teams calls, switching is definitely recommended. https://office365itpros.com/2026/06/30/incoming-teams-call-window/
How much should Teams presence influence call routing
One thing I've noticed recently is that many Teams Phone environments still treat presence as a destination state rather than a routing input. A typical flow might look like: Caller selects an option Call is transferred User is unavailable Caller ends up in voicemail or another queue Technically the routing worked. From the caller's perspective, it often didn't. I'm curious how others are approaching this. Are you using Teams presence as part of your call-routing logic? For example: Available → transfer immediately Busy → offer an alternative path In a meeting → capture context Offline → route elsewhere Or are traditional queues and escalation paths still sufficient for most scenarios? Interested to hear what people are doing in real deployments.
Stop Automatic Calling when Screensharing
I screenshare a lot in my position; I call the coworker (Phone/Headset) and train them on what I need them to look at. I am in a large office building, and the automatic calling of the receivers' PC is disruptive, as I do not was the whole office to hear my conversation or have people hear my trainee. I see no way to disable the team auto-call once I start to screen share or in the Options. All my coworkers feel this frustration as well. I do use the computer microphone/speaks aspect when working from home, but would disable it totally, if it would stop the auto-call. I do not want it to affect meeting invites to others, as others around the country can use their PC speak/microphone, if they want. Please advise.
Direct Routing PSTN calls to Teams Auto Attendant does not forward to Shared Voicemail
Hi all, I’m running into a strange issue with a Teams Auto Attendant and I’m hoping someone here has seen it before. We have a Direct Routing number where business hours calls go to a Call Queue, which works, and after hours calls should go to Shared Voicemail for a Microsoft 365 Group. If I call the Auto Attendant from inside our Teams tenant, the after-hours Shared Voicemail works correctly. I can leave a message and the voicemail is delivered to the group inbox as expected. If I call the same number from the PSTN over Direct Routing, I hear the after-hours greeting, so the schedule and call flow are clearly being hit, but once the greeting finishes I get: “Sorry, we cannot connect your call at the moment, please try again later.” I have already verified that the resource account has the correct Teams Phone Resource Account license, Enterprise Voice is enabled, the LineURI is assigned, the Online Voice Routing Policy is assigned, the Direct Routing route and SBC look healthy, the Auto Attendant is associated with the correct resource account, the after-hours call flow points to the correct Microsoft 365 Group, and the group mailbox exists and is healthy. What makes this more confusing is that redirects to internal or tenant-side destinations work, but redirect to Shared Voicemail from a PSTN-originated call does not work. I also tested redirect to an external PSTN number, and that fails with the same error as well. Because the after-hours greeting plays correctly, and because internal Teams calls can successfully leave voicemail in the shared mailbox, I do not think the issue is with the Auto Attendant configuration itself or with the Microsoft 365 Group mailbox. At this point it looks more like the handoff or redirect path for PSTN-originated calls over Direct Routing is where things break. Has anyone run into this with a Teams Auto Attendant, Shared Voicemail, and inbound PSTN over Direct Routing? I’m trying to figure out whether this is a known limitation, a bug, or if there is some specific setting related to PSTN-originated redirects that I am missing. Thanks!
Question about Teams Phone licensing
Hi everyone, I have a question about Teams Phone licensing: If I have some users who have Teams Phone to make and receive external calls, when one of them receives an external call, can they transfer it to another user who only has a regular Teams license but not a Teams Phone license? Or does the user I want to transfer the call to also need a Teams Phone license? I couldn't find a KB article that clarifies this. Thanks regards
Teams auto selecting "Missed Calls"
I have the calls tab selected. On that tab I have "All" selected. I then click the Activity tab. Teams is selecting "Missed" on that tab. Why is it selecting "Missed"? The issue is when I click back to the calls tab Teams then selects the "Missed" on the calls area. Now if I click on "All" on the Activity tab and then click back to the Calls tab everything is fine. Seems like it is auto selecting stuff for me I didn't ask it to do.
Teams duplicates contacts until it maxed out at 15000
Hi, I have a weird issue with some users, Teams seems to be duplicating old Skype for Business contacts until it maxes out at 15000 contacts. I have been digging into it a bit and found out the location of the folder through Exchange powershell but I can't clear or delete it. Skype for Business is phased out and disabled in my tenant for a long time now so I couldn't do much there, I can't login to it through powershell. We've had Teams since like 2017 so I suspect this is a niche legacy issue popping up recently somehow. Manual deleting is possible through the browser environment but that is such a hassle because it keeps glitching if you delete per 100 and skipping pages and stuff, need to refresh constantly. Just a pain, it would take days. And no guarentee its not coming back either. See screenshots. Does anyone know why this is happening and how to fix this? Thanks for reading, cheers!Shared Number Group Channel Operator Options Missing in Microsoft Teams 260043.403
After updating to Microsoft Teams version 260043.403, options in Group Channels related to shared number / calling queue operator availability appear to have changed. Previously, when selecting a channel associated with a calling queue, operators could: View a list of all queue operators See each operator’s availability for that specific calling queue (not general Teams presence) Change their own availability for that queue With this update, the ability for operators to change their availability now appears to be located under Settings → Calls. However, the channel-level view that displayed the availability of other operators seems to have been removed entirely. Can someone confirm whether the operator availability view within Group Channels has been deprecated, or if it is now accessible elsewhere in Teams?
Teams Calls using Transfer with consult
Hi all, I have a Yealink MP56E2 desk phone with the extension EXP50. When adding "Consult Transfer" to a line key on the extension then the text "Consult with" plus the contact name is added to display on the extension. Consult with is displayed on the first of two lines, taking away a lot of space. Even worth if you change the language to German. Then only 3-4 characters remain to display the contact name. See pictures below. Has anyone managed to change the leading text? In my opinion, no text is needed as the Icon already indicates the "Consult Transfer" function.
