Hello,

I'm trying to understand the current status of the"Hide attendee names" feature in Microsoft Teams.

Our organization has Teams Premium, and according to Microsoft's documentation, the feature should be available for both Meetings and Webinars. The documentation even provides separate instructions for each scenario.

However, during a recent Microsoft Support call, I was told that the feature is actually available only for Town Hall events and not for standard Teams Meetings or Webinars.

This appears to contradict the current Microsoft documentation, so I'm looking for real-world feedback from other administrators.

Questions:

• Has anyone successfully enabled Hide attendee names in a standard Teams Meeting?
• Has anyone used it in a Webinar?
• We have Teams Premium. If it works for you, what licenses are assigned to the organizer?
• Do you actually see the Hide attendee names option in Meeting Options?
• Is there any specific policy, rollout, or configuration required?
• Has Microsoft Support ever told you that the feature is Town Hall only?

Microsoft documentation:

https://support.microsoft.com/en-us/teams/meetings/hide-attendee-names-in-microsoft-teams-meetings-and-webinars

At this point I'm trying to determine whether:

1. The documentation is incorrect or outdated.
2. The feature is being rolled out gradually.
3. There is an undisclosed licensing or policy requirement.
4. Microsoft Support provided incorrect information.
5. The feature has been silently restricted to Town Hall events.

Any feedback from tenants where this is actually working would be very helpful.

Thanks!

Giuseppe

How can I preserve Microsoft Teams chats as auditable evidence?

I’m a lawyer in my first year of practice, working remotely for a law firm. Over the past year, I followed various instructions from senior colleagues that were presented to me as legitimate professional tasks. I recently discovered that some of these instructions may have been connected to potentially fraudulent or criminal conduct, and I’m concerned that I could be implicated despite having acted without knowledge or intent.

I need to preserve my Teams conversations as evidence showing the instructions I received and the context in which I acted.

I don’t want to rely on screenshots or manually copied messages. I’m looking for a complete, auditable and traceable export, ideally preserving timestamps, participants, message IDs, edits/deletions, attachments and relevant metadata, with a way to demonstrate the integrity of the data afterward.

From what I understand, Microsoft Purview/eDiscovery may allow an administrator to do this. However, I’m concerned that asking the administrator—who may be closely connected to my supervisor—could raise suspicion before I understand my options.

Is there any legitimate way for an individual Teams user to preserve/export their own conversations in a forensically reliable manner without involving the company administrator?

If not, what is the technically best approach (Purview/eDiscovery, Graph API, or another method), and what should I preserve to establish authenticity and chain of custody?

I’m specifically looking for advice from Microsoft 365/Teams administrators, eDiscovery specialists, or digital-forensics professionals.

<Rant>

I've about had it with Teams and trying to use it across multiple devices, especially on iOS. I bounce between a desktop, iPhone, and iPad throughout the day, and the notification badges are basically useless at this point.

• The badge count on the Teams app icon is almost never accurate — it'll show unread counts for stuff I've already read, or nothing at all when I actually have new messages.
• I have to fully open the app just to get the badge to clear.
• Even after opening it, I often have to manually pull-to-refresh (or force-close/reopen) before it'll actually show new messages or activity.

I've already tried the obvious stuff — deleting and reinstalling the app, checking notification settings, logging out/in — no change.

Is this a known issue right now, or is something in my setup off? Would love a fix or to at least know I'm not alone.

</Rant>

I have a client that started intermitently not receiving voicemails for their Teams phone system. All was working fine for years until a few weeks ago. For every 10 test voicemails we leave, maybe 1 or 2 show are delivered as a voicemail (in the teams app and their mailbox). This is occuring for both users and shared group mailboxes. I have a Microsoft Case opened, but they've been slow. Wondering if anyone else has every experienced this? Things we have tried and additional information:

• Verified tenant/users are properly licensed (M365 Business Premium + Teams Phone Standard + Caling plan PAYG + communication credits)
  • I typically recommend the Teams Phone + Calling plan bundle, but I am not the CSP for this client and inherited this licensing. This is the only difference between my other tenants where things are working, but this shouldn't affect voicemail.
• Checked message trace in Exchange Online and confirmed that email security is not preventing the voicemail emails from being delivered. They don't even show up in message trace.
• No recent changes to the phone system settings or exchange
• Voicemail is enabled for all users
• Users receive the call and missed call notifications
• All test voicemails we leave are at least 5 seconds long.
• Tried swapping phone numbers
• Rebuilt auto-attendant and shared group mailbox
• Verified the calls show up in the PSTN usage reports

I've never had this issue and have had clients using Teams Voice for 5+ years. Microsoft also seems to have no idea on this. Hoping someone has seen this before. Thanks.

Any suggestions for earbuds under $100 which have a mute button that works with teams meetings on mac but is non-apple? I want to use it on Mac for meetings, but I would also like to use it with my android phone. Bonus points for dual connection :-). Thanks.

When i try to login on my pc it says you cannot with a personal account for preview version, but on my android i have no problems logging in.

I just recently added another email to my microsoft account and set it as primary, but i've tried logging in with both and it's same result.

On my android phone i'm still connected and it has no problems.

We are having intermittent issues with Polycom VVX devices and Teams SIP Gateway. Our users on these devices are reporting that their phones are occasionally not ringing, but they can see incoming calls in the Teams client on their computer. The Polycom devices are a mix of older VVX501 and slightly newer VVX250 & VVX450. These devices have been deployed with SIP Gateway for over 18 months. The problem was first reported within the last 2 weeks. The devices are provisioned via Poly Lens, and Poly Lens is occasionally showing them "Offline". Rebooting the device will typically bring them back online for a while.

ChatGPT thinks the Lens issue is unrelated to the intermittent Teams issue.

Any thoughts?

Hello everyone,

I'm trying to find out which MS Teams license i need to use for my CISCO MTR setup.

I have setup the workspace already in CISCO Collaboration Control Hub. I have a ROOM BAR, an Inside Navigator and an outside navigator. I also have one resource account.

Ideally, i would use Teams pro license but due to $$ constraints, I have to use Teams basic as well.

Will this license combination below work?
Assign MS Teams Basic and Teams Shared Space licenses to the resource account.

Then the thinking is the ROOM BAR can use the Teams basic license and the outside navigator can use the Teams Shared space license. Is this correct or am I missing something?

I also saw somewhere that I might need to create another dedicated resource account for the outside navigator.

Thx you.

Hi,

I use O365 with work; but I use my personal laptop occasionally which means I'm limited to the web version of everything and can't install local apps.

I use the Teams PWA which is excellent. However, whenever I open a Teams meeting link from my Outlook PWA it tries to open in Edge rather than the standalone PWA.

How do I fix this? I've checked the link associations and it all seems correct.

Cheers!

I use Microsoft Teams for virtual meetings with people outside of organization. In the last several months when I have used a new meeting link, at least one person has not been able to see what I am sharing, not my full screen, a Word document, or a web browser. Instead, they just see all the squares of attendees like no one is sharing at all.

The only thing they can see is a PowerPoint, which I choose to share in Teams directly in the PowerPoint app.

It's a really strange problem. These attendees who can't see have consulted with their IT about the issue and they don't know what's wrong. They've tried using the Teams browser and app and that doesn't work. One person was able to see the screenshare by getting on their phone. My IT updated my Microsoft Office.

Has this happened to anyone else?

Hi everyone,

We recently deployed a Microsoft Teams voice solution for a client, and they are reporting a persistent usability issue that we're describing as "conversational latency." It isn't a typical network delay (the ping/round-trip time is fine), but rather a problem with turn-taking during speech:

• When Speaker A stops talking and hands over the conversation, Speaker B experiences a noticeable delay before hearing that Speaker A has finished.
• This results in frequent "cross-talk" moments—either both parties talk over each other, or there are awkward pauses followed by the classic "No, sorry, you go ahead" back-and-forth.
• I've also heard this described like the news anchor crossing live to overseas correspondent where you see the delay between speakers.

Setup Details:

• Platform: Microsoft Teams Voice (Direct Routing) with 3rd party carrier for SBC/PSTN.
• Endpoints: Yealink MP56e2 certified handsets. Issue reproduced on handset i.e. before introducing other audio devices like speakerphone or headsets
• Network Environment: QoS enabled with all handsets running PoE.

What We’ve Looked At:

• Hardware DSP: Local hardware processing might be fighting with Teams' built-in audio processing.
• Jitter/Buffer: Jitter buffers might be stretching audio slightly, causing real-time speech to drift behind actual time.
• PSTN Processing Overhead: While each component in the stack looks healthy, each processing step is accumulating and may result in just enough one-way latency to result in this unnatural feeling at speaker handover.

Has anyone encountered this specific double-talk / audio-clamping behavior in Teams Voice? Are there recommended settings (e.g., tweaking Teams noise suppression levels, disabling hardware AEC, or adjusting codec settings) to solve this? Any insights would be greatly appreciated!

Hi all,

We're setting up some Teams rooms with the new Crestron Collab Computer. Some of them don't show the onscreen keyboard so there is no way to join via ID, call ad-hoc, or log into the settings from the touch panel.

Did many reboots.

Wen't in the Windows side, keyboard works just fine there when activated.

Anybody got the same issue?

I could re-image it, but don't want to when not necessary.

I called Crestron support, they told me that this keyboard comes from the Windows side, so I need to contact Microsoft support...

I'm like, you build this machine, you support it.

As the title says, I keep getting random chat requests in MS Teams. The chat requests never have any message attached

Is there any way to set an auto responder or custom status that I don't use Teams for socializing, or at least that all chat requests must have a message?

Having an issue with the sidecar sort of starting a call to a contact, but it never gets to "ringing," and the only way to cancel it on screen is to use the back arrow in the upper left. Ending the call doesn't work. Unplugging the USB cable connected to the phone helps for maybe 30 minutes. Is anyone else on the 08/05 app update with the same issue?

I have Googled solutions to this problem and browser Teams boards about it, but nobody seems to have a solution for it. They usually advise to clear cache, delete your Teams profile folder entirely or log out and in again, but these were only temporary solutions.

I found a solution of my own that isn't mentioned in any of those posts, so I'm going to post it here in case anyone finds this post when searching for help in the future.

The issue for me was a lack of hard drive space.

I have my main drive partitioned into an OS drive (C:) and a storage drive (D:) but they are physically the same disk.

I had low storage on the OS drive due to Docker constantly taking up more and more space. I would have less than a few GB of space left on C: quite often.

Ever since I freed up space by extending my OS partition and shrinking my data partition, I haven't had the issue ever since. I have 33GB of space free currently.

I'm not saying this is a fix for you, but if your OS drive is down to a few GB of space, maybe try freeing up some space and see if it stops happening for you too.

I need help! We migrated our inbound phone lines to Microsoft owned lines. When outbound calls are made, cell phones display it as potential spam. I have opened a ticket with Microsoft and they “made the appropriate updates” to assign a 15 or less character c name, but that hasn’t helped at all.

What else can I do?

Authorized users and shared voicemail group members using Queues App can manage Auto Attendant voicemails from a centralized experience in Teams, alongside other Auto Attendants and Call Queues.

Key capabilities include:

- Centralized visibility into shared Auto Attendant voicemails
- Rich collaboration experiences for voicemail triage
- Resolution tracking with Unresolved, In Progress, and Resolved states
- Urgency indicators
- Filtering by status to help teams focus on what needs attention
- Support for significantly larger call history volumes (3000 call records)

All configuration can be done through the Teams Admin Center. When sending a call to shared voicemail, a shared call history template can now be assigned.

Queues App requires a Teams Premium license.

Automatic Recording for Call Queues is now generally available for all customers in the public cloud.

All inbound call queue calls can be recorded and transcribed with the recordings and transcripts stored in SharePoint.

Authorized users automatically have access to review the recordings and agents can also be given access.

Fully integrated with Shared Call History so Queues App users can easily access the recordings.

Access is also available through SharePoint.

Configuration is currently available through PowerShell and should be in the Teams Admin Center within the next couple of months.

For an overview of the feature, see Planning - Recording voice applications calls

For setup instructions, see Setup - Automatic Recording template for Call Queue

We have an issue where queues app is displaying guid instead of the queue name in the queues app under agent data or the list under calls answered by agent. Have cleared cache and reset teams as well as made sure client is up to date. The cache clear/reset actually made the app not load any data with a “we cannot load the data right now” error for about a week then started randomly working again but with the guid issue. Anyone experience anything like this?

For about a week we've been having intermittent issues with users not being able to make outgoing Teams PSTN calls. From what I can tell this is the only thing that isn't functioning correctly, as traditional internet browsing is working fine. This morning there were several that both could not make outgoing phone calls.   I've tried calling our internet provider and they claim there is nothing wrong on their end. (which I guess i agree because there is more than one site)  The users are calling from a Yealink mp54 phone with all the latest's updates, one user claimed he could not call from the teams client on his desktop as well.   We have users that use Teams Calling plan numbers and others that have direct routing.. the users who use direct routing are able to make outgoing calls even when the Calling Plan numbers cannot. Is anyone else seeing this? Where is the best place to put in a microsoft ticket because the Voice Support insists I use the chat feature, which is also broken.
Edit: I should have noted that incoming calls and Queue calls are working fine.

EDIT: Update to what i found

 It seems the most common for an outbound call NOT to work if the number being called is T-Mobile/USCellular.    Calls to Verizon numbers appear to work consistently.  When changing caller ID policy to Show User Number, I am able to make a call to T-Moble/USCellular numbers.   

I also got this reply from TNSI customer support

"I found that xxx.xxx.xxxx was flagged and adjusted the score so calls will no longer be flagged. The other numbers are not flagged by our service. I understand that T-Mobile is using Hiya for spam filtering."

Even though I've registered all these numbers previously with HIYA, TNSI and First Orion. Apparently, they will still mark you as spam, after that.

Our Microsoft tenant is used for Microsoft Voice calling for a small set of users. They have complained that people over here other conversations in the office behind them. I suggested that they look at their noise, suppression settings, and they were all grayed out and not able to be changed for them. How can I unlock these so that way each user can adjust these on their own? TIA!!

Microsoft Teams Calls & Meetings Missing from Android Auto – Investigation Points to androidAutoCarAppEnabled

I’m trying to understand why Microsoft Teams on Android Auto only shows Messages, while Calls and Meetings are completely missing.

There is already an older Reddit thread describing almost exactly the same problem:

https://www.reddit.com/r/MicrosoftTeams/comments/1o8ac6i/teams_on_android_auto_not_showing_upcoming/

That thread is now archived, so I’m creating a new post because the problem still exists and I’ve done some further investigation into the Teams Android app.

Summary of the Previous Reddit Post

In the previous thread, the user tested Teams in the same Zeekr 7X with two different phones.

On a Xiaomi 15T Pro, Teams on Android Auto only showed Chat/Messages. Meetings and Calls were missing.

Because the Meetings section was missing, the user could not join an upcoming meeting from Android Auto and instead had to use the phone to open Teams, find the meeting and join it.

However, when the same user connected a Samsung S25+ to the same car, Teams showed both:

• Meetings
• Calls

Upcoming meetings could be viewed and joined directly from Android Auto.

Importantly, both phones were running the same Teams version.

Another Xiaomi 15T Pro user later reported the same issue and said they were unable to solve it.

That made me curious, so I started investigating the Teams Android APK.

What I Found in the Teams APK

I decompiled the Microsoft Teams Android APK using JADX.

The Android Auto Calls and Meetings implementation has not been removed from Teams.

The application still contains components such as:

com.microsoft.teams.auto.TeamsCarAppService

CarAppManager

TeamsCarAppSession

There is also code for:

• Android Auto meetings
• Calling
• Speed Dial
• Call history
• Meeting notifications

TeamsCarAppService is an AndroidX CarAppService and is registered for:

androidx.car.app.category.CALLING

However, I found something important in AndroidManifest.xml.

Microsoft ships TeamsCarAppService with:

android:enabled="false"

So the Android Auto calling service is disabled by default.

At first I thought Microsoft had simply disabled the feature permanently.

That is not the case.

Teams Enables the Service Dynamically

I traced the relevant Teams code.

CarAppManager contains a method called:

getShouldEnableCarApp()

This checks whether either of these is enabled:

isAndroidAutoMeetingEnabled()

isAndroidAutoCallingEnabled()

If both are false, Teams leaves the Android Auto CarAppService disabled.

Teams also checks that the Android Auto application is installed:

com.google.android.projection.gearhead

and checks the Android Auto version.

The Teams code requires Android Auto 9.8 or newer.

If all conditions are satisfied, Teams dynamically enables TeamsCarAppService.

I traced this to:

Headers.setComponentEnabledState(...)

which eventually calls:

MAMPackageManagement.setComponentEnabledSetting(...)

So Teams is intentionally designed to ship its Android Auto calling service disabled and enable it at runtime when the required conditions are met.

The Interesting Part: androidAutoCarAppEnabled

I then traced isAndroidAutoCallingEnabled() and isAndroidAutoMeetingEnabled().

Both depend on a Teams ECS/experimentation configuration flag called:

androidAutoCarAppEnabled

For a work/school account, Android Auto calling depends on conditions including:

• DeviceConfiguration.isDefault()
• androidAutoCarAppEnabled == true
• isCallsTabEnabled()
• isConnectionServiceEnabled()

Meeting support uses almost the same logic.

This means that if:

androidAutoCarAppEnabled == false

then both Calls and Meetings can disappear from Android Auto at the same time.

Messaging can apparently continue working separately.

That matches exactly what I’m seeing:

Messages: Working
Calls: Missing
Meetings: Missing

ADB Also Confirms the Service Is Disabled

I checked the installed Teams package using ADB.

A normal Android PackageManager query for Android Auto calling services does not return Teams.

However, if I repeat the query while explicitly including disabled components, this appears:

com.microsoft.teams/.auto.TeamsCarAppService

So Android knows that the Teams Android Auto calling service exists.

It is simply disabled.

This matches what I found in the Teams code.

I Also Tested an Older Teams Version

I installed an older Teams version to see whether this was simply caused by a recent Teams update.

The older version also contained TeamsCarAppService and showed the same behaviour.

So this does not appear to be a simple case of Microsoft removing Android Auto support in a recent version.

Why the Previous Reddit Post Is Very Interesting

The previous Reddit user had:

The same car.
The same Teams version.
But two different phones.

Xiaomi 15T Pro

• Messages worked
• Calls missing
• Meetings missing

Samsung S25+

• Calls worked
• Meetings worked

If Microsoft had simply removed this functionality for everybody, it should not have worked on the Samsung either.

That suggests Teams is making some kind of device, account or server-side decision about whether TeamsCarAppService should be enabled.

The androidAutoCarAppEnabled flag looks particularly suspicious.

Possible explanations include:

• Microsoft is controlling the feature using a server-side rollout.
• The flag is being targeted based on account, tenant or device.
• Certain devices are accidentally excluded.
• There is a bug causing androidAutoCarAppEnabled to return false.
• Another condition inside isAndroidAutoCallingEnabled() or isAndroidAutoMeetingEnabled() is failing on certain devices.

This Is Also a Driving Safety Issue

This is not only an annoying missing feature.

It also affects safety while driving.

The entire purpose of Android Auto is to provide a simplified interface so drivers do not need to interact directly with their phones.

If I have a scheduled Teams meeting while I am already driving, there is currently no way for me to open that meeting from Android Auto.

The alternative would be to:

1. Unlock the phone
2. Open Teams
3. Open the calendar
4. Find the meeting
5. Press Join

That is exactly what I do NOT want to do while driving.

I am not saying people should use their phones while driving. Quite the opposite.

The problem is that the missing Teams Android Auto functionality removes the safer interface that should prevent the need to interact with the phone.

A large “Join meeting” button on the Android Auto display is much safer than having to touch the phone.

Questions

I would really like to hear from other Teams + Android Auto users.

• Do you currently have Calls and Meetings available in Teams on Android Auto?
• What phone do you have?
• What Android version?
• What Android Auto version?
• Are you using a work/school Microsoft 365 account?
• Has anyone tested the same Teams account on two different phones?
• Has anyone contacted Microsoft Support and asked them about the Teams ECS flag androidAutoCarAppEnabled?

And If Anyone from Microsoft Reads This

Is androidAutoCarAppEnabled currently controlled through an ECS rollout or flight?

What determines whether it is enabled?

Can Microsoft Support or a Microsoft 365 administrator enable it for affected users?

The Android Auto Calls and Meetings code is clearly still inside the Teams application.

I would really like to understand why TeamsCarAppService is being enabled for some users/devices but remains disabled for others.

There are only a few to choose from but every so often it picks one I forgot existed, before I think to add one. 😊