Best External Access configuration
I’m looking for guidance on the best Microsoft Teams configuration for the following goal: Objective Prevent random external domains from: Looking up users in Teams Sending 1:1 chats Making direct audio/video calls At the same time: External users invited to Teams meetings should not appear as AnonymousAllow only specific external domains
When External Access is set to “Allow only specific external domains” Scenario 1 If Microsoft Teams External Access is set to “Allow only specific external domains”, and a user from a domain not on the allowed list joins a meeting while signed into their work Teams account, Will they still appear with their actual name and organization, rather than as Anonymous? Is this correct? Scenario 2 If a user from a non-allowed domain joins the meeting link through a browser and selects “Join as guest”, Will they appear under the name they manually enter, instead of showing as Anonymous? Is this correct? Scenario 3 If a user joins without authenticating and meeting policy allows anonymous access, Will they appear as Anonymous only in that situation, and not because of the External Access restriction? Is this correct?External Accessbto “Allow only specific domains” How does this affect meeting participant identity?
Hi everyone, We have recently changed our Microsoft Teams External Access setting from: “Block only specific external domains” to “Allow only specific external domains.” This means only explicitly approved domains are allowed for 1:1 chat, calling, and federation. I would like clarification regarding how this impacts Teams meetings. Scenario: If a user from a domain that is not on the allowed list is invited to a Teams meeting: If they join the meeting while signed into their work/school Teams account, will they still appear with their authenticated name (e.g., Name (External))? Or will they appear as Anonymous because their domain is not permitted under External Access? My understanding is that External Access (federation) controls chat and calling, but meeting identity is governed separately by meeting policies and authentication status. Can someone confirm if this is correct? Thank you in advance for your guidance.
Group email addresses for Teams sometimes contain “+” or “/” characters
We are using Microsoft Teams in our organization. When creating multiple Teams with exactly the same team name, using ASCII alphanumeric characters only, we occasionally see that the automatically generated group email address contains unexpected characters such as “+” or “/”. I would like to know whether this behavior is expected or if it is specific to our environment. This issue seems to have been occurring since around August 2025. We manually create Teams using the Windows Teams client. For example, if we create several Teams with a simple name such as “example2026”, the corresponding group email addresses are generated in the following format: email address removed for privacy reasons However, in some cases, the XXXXXX portion includes characters like “+” or “/”. When creating around 50 Teams, this issue appears in a few of them. This causes two problems for us: A “+” character interferes with plus-addressing behavior. When a “/” is included, we cannot create events inside the Team. Has anyone else encountered this issue or knows why this happens? Any insights would be appreciated.Microsoft Teams PowerShell Module 7.6.0 is broken
Dear Community I have a few Script with Microsoft Teams PowerShell, witch authenticate via Access Token. Everything works fine until latest Microsoft Teams PowerShell Module Update 7.6.0. I got following Error with the Script. Connect-MicrosoftTeams : Could not load file or assembly 'Microsoft.IdentityModel.JsonWebTokens, Version=8.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. If I downgrade my environment from Version 7.6.0 to Version 7.5.0 and rerun my script, the authentication is working as expected. What is wrong here with latest PowerShell Module 7.6.0 and how can I resolve the issue Many thanks for sharing any hint or tip ANDYMulti-app camera - Stops Teams from detecting webcams
Hi. We have a load of shared meeting rooms that are setup with Jabra panacast webcams. When you open Teams it shows that no devices are connected but if you open the camera app or any other app like zoom the camera works fine. The only way to get it to work is to enable this setting. This settings for Multi-app camera cannot be enabled by Intune or powershell/regedit. There are some posts on reddit that suggest I am not alone and there are others having this issues too. So.. its either a bug with the Teams app itself or the windows OS Thanks, Cam
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.Apps notification settings missing in Teams settings
Hello Teams Community, I'm facing a strange issue with App notifications in Microsoft Teams. I've already researched this and found nothing. I've opened a Microsoft case and I'm waiting for an answer but it's taking longer than expected. So, I'm turning to you for expedited help! Scenario: You're an administrator in Teams. You've applied a setup policy for a pinned app like Viva Engage. After the policy is applied and the tool is launched, users complain that notifications are either too frequent or not frequent enough. You direct them to the Teams Notification and activity settings to control app notifications. The users go to Teams notification settings but report back to you that the App section of Teams settings doesn't exist. Problem Statement: Microsoft explicitly states in their documentation that in order for the App notifications section to appear, you must first add an app yourself within Teams and get at least one notification. But relying on users to add an app, somehow create a notification, and then remove it, just to access App notifications is impractical and would never work. Desired Outcome: I'm looking for a way to bypass this prerequisite and force the Apps section to appear in the Notifications and activity section without any user action whenever an app is pinned in the Teams admin center with a setup policy. I'm hoping this can work with any app, not just Viva Engage. Any help is appreciated. Thanks, Teams experts! -Rob
Teams admin centre - add the ability to setup a team completely (shared channels and/or groups)
I think the current teams setup workflow in admin centre is a bit flawed. We're trying out to create a team for every project that we do, but since these projects are done by many different departments it makes sense to use Shared Channels within each project and divide the data in such a way that it is stored in the site library of the channel that is the most fitting. For example creative documents in the channel for the creative department, and business documents in the business channel. To make things clearer to the end user we would like to structure each project the same. So it would be logical if an admin could create these shared channels while creating the project and not have to trust that a project manager is able to set things up correctly after they get assigned. (so being able to create a template would be nice...) So IMHO what is missing from admin centre: -ability to add shared channels. -ability to add teams (in this case department teams) to these shared channels. -ability to create a template with shared channels configured (is a little bit complex, because channel names need to be unique, so some sort of variables need to be taken into account... maybe these can be distilled from the main project team name...which is basically what we also intend) (maybe this could be done with Power automate if the ability to create shared channels is being added to an admin's abilities...) Another option, which would actually be much sweeter would be to skip Shared Channels altogether and add the ability to add Office 365 groups to the main Team, now we can only add members... I would like to work with Team groups, as it's much easier to manage and remove a user from a group than to have this user have to be removed from each project individually. But actually I think both options are a necessity...
