All Teams Bots Not Working At All
This morning all of a sudden all our Teams bots stopped working. These are bots built using bot framework running on Azure Bot Teams Channel. Is this related to the current Teams API issue we talking about? All of a sudden all our client and test bots stopped working. But the Web Channel is working as expected. Only the teams channel. We even checked with ngrok and its not even hitting the service. We checked the app registrations and their credentials as well to ensure not issues there too. Completely lost whats happening. Help?
Add Teams Chat Member API call inexplicably Failing
I have tried every possible permutation of this API call that I can imagine. Nothing works. I already started a thread on this, but now it appears to be glitched and I can no longer reply to message sin that thread for some reason. What can I do to contact Microsoft Support and speak directly to their API team? The responses I have gotten all appear to be AI generated and NONE ARE CORRECT. I really need help, from a human, that actually might understand what's going on here. Please help. "#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation." <- I am receiving this error despite the fact that we already have several users in this channel with that same type. This API call is intended to invite a user to an existing group chat. This should really be a very simple thing. 1. ALL users in the group chat already have type = '#microsoft.graph.aadUserConversationMember' so the error message doesn't even make sense. 2. This IS a Group chat. NOT a channel. NOT a one on one chat. 3. The Inviter has permission to invite users to this groupchat through the frontend. (and in fact can do so using the frontend.) Why is this API call failing? I have tried scrubbing the API call of special characters, I have tried using the beta endpoint, I have tried several different formats for the input. ERROR: {"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation.","innerError":{"date":"2026-02-10T19:11:28","request-id":"XXXXX","client-request-id":"XXXXXX"}}} POST URL: https://graph.microsoft.com/v1.0/chats/IDHERE/members BODY: { "chatType": "group", "\u0040odata.type": "#microsoft.graph.aadUserConversationMember", "user\u0040odata.bind": "https://graph.microsoft.com/v1.0/users/IDHERE", "roles": [] }
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.Issue with Teams 'Add a User to Group Chat' API call?
I am getting a very strange error when trying to add a new user to an existing group chat using a GraphQL call. I have looked through the documentation, asked AI, and even contacted Microsoft support and no one can seem to explain why this API call is failing. Below is the API call that I am making. I can find no reason that I should be receiving the error message '#microsoft.graph.aadUserConversationMember' To get the basic questions out of the way.... Yes, the account making the API call DOES have permission to add users to the channel (and can do so using the frontend as normal.) Yes, the thread in question is a group chat, so adding members to that chat should be a valid command. Yes, ALL members in the group chat currently have the type '#microsoft.graph.aadUserConversationMember', so it is definitely a valid type for users in this channel. Yes, I have tried both the beta and stable channel; each gives the same error message. Yes, the invited user is internal to our organization, and is a valid target for the invite (invites work through frontend as well.) No, I cannot use the 'add member to channel' endpoint, because the chat is a group chat, not a channel. I can only assume, at this point, that the error message is a red herring and there's something else wrong with my API call?Why am I receiving this error message when trying to add a member to a pre-existing group chat? Thanks in advance for any assistance. POST to URL: https://graph.microsoft.com/beta/chats/[[THREAD_ID]]@thread.v2/members BODY: { "@odXXX.type": "#microsoft.graph.aadUserConversationMember", "roles": [], "email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/users/[[USER_ID]]" } ERROR MESSAGE: {"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odXXX.type' is not valid for this operation.","innerError":{"date":"2026-01-29T18:10:32","request-id":"<PII:moderator removed>","client-request-id":"<PII:moderator removed>"}}}
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 ANDY
AADSTS50105 error message is unreadable for end users — UX improvement suggestion
1. What’s wrong with the current error message a. It’s written for administrators, not users The message exposes: Internal system names (AADSTS50105) GUIDs (aaaabbbb-cccc-dddd-eeee-ffff01234567) Identity provider jargon (“direct member of a group with access”) None of this helps the person who sees the error decide what to do next. b. The actual problem is buried in a wall of text The real issue is simply: You don’t have permission to access this app. Instead, the message forces users to: Read a long paragraph Decode domain-specific language Guess which part matters Cognitively, this is high effort for low payoff. c. “Contact your administrator” is vague and unhelpful Users ask: Which administrator? IT? Security? App owner? Their manager? What should they say? Without context, users either: Ignore the error Forward screenshots randomly Open the wrong support ticket d. Error codes without guidance increase support load AADSTS50105 may be meaningful internally, but: Users don’t know whether to Google it Support teams receive unclear tickets (“it doesn’t work”) This paradoxically raises support cost instead of lowering it. 2. What a better error message should do A good error message answers four questions in order: What happened? Why did it happen (in plain language)? What can the user do next? Who specifically can help? And it does so in under 30 seconds of reading time. 3. Example of a much better error message You don’t have access to [APPLICATION] Your account (email address removed for privacy reasons) isn’t currently authorized to use [APPLICATION]. This usually means: You haven’t been added to the required security group, or Access hasn’t been requested or approved yet. What to do next If you believe you should have access, contact IT Service Desk or your [APPLICATION] owner and request access. Helpful details to include in your request Application name: [APPLICATION] Your email: email address removed for privacy reasons Error reference: Access not assigned (Error ID: AADSTS50105 — for IT use) 4. Optional but high-impact improvement: Add a “Request Access” button or link One-click takes users to: ServiceNow / Jira / internal form Auto-populates app name and user email Administrators configure support link when configuring the applicationMulti-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...
