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": [] }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>"}}}
Deleting AutoAttendants and CallQueue
Hello There are commands to delete AutoAttendants and CallQueue. But I get allways an error "Can't remove the Auto Attendant. Auto Attendant is still referenced by Endpoints Ids" Even if all Ressource Accounts are deleted a day before. These Auto Attendants and CallQueues are configured as Calling ID's When I manually delete them after removing there also an error that call queue time was to low. Is it possible to force the deletion. Regards JFM_12
The Teams Developer Portal needs administrative views
The Teams Developer portal needs some way for Teams service admins or Global admins to view everything that is being deployed to the catalog both in a published and unpublished state. Alternatively, develop some graph endpoints that could be turned into cmdlets in Microsoft Teams PowerShell module or the Graph PowerShell SDK module. As administrators we need the ability to help with keeping our tenant clean, so these kinds of views or endpoints would allow us to make sure that anything uploaded and not needed may be removed or reassigned if the underlying owner leaves and someone else needs to take over something they've been developing. I've submitted a feedback item to the portal - so please help by adding a vote to the entry to bring it up as an enhancement for the Teams Developer Portal services. The Teams Developer Portal needs administrative views or PowerShell/Graph capabilities to manage uploaded solutions and other artifacts · Community
Affordable Conference Room Setups for Small Businesses Using Microsoft Teams Resource Accounts
Our small business (around 40 users) recently migrated from Google to Microsoft 365, and we’re facing several challenges in optimizing our meeting rooms for Teams without incurring large costs. Here’s our current setup and the main issues we are encountering—hoping for advice or creative solutions from the community. Current Setup All computers are domain-joined. We created resource accounts for each of our three meeting rooms; these appear correctly as Rooms in Outlook and Teams booking menus. Each meeting room contains a standard desktop PC (not MTR-certified) running Windows, logged into Teams as the room’s resource account. Employees use the meeting room computer to join calls and manage the meeting calendar. Current Issues Wireless Presenting (Casting): Teams’ wireless casting feature appears to require MTR-certified hardware, which is financially out of reach for a business our size. Unplugging and plugging HDMI cables is cumbersome and error-prone, especially since not everyone uses a laptop, and reconnecting the room PC is often forgotten. Agenda & Calendar Privacy: When meetings are booked, the full Teams agenda and chat history remain accessible on the meeting room machine. That means anyone in the room can view past meetings/agendas, which isn’t ideal from a privacy perspective. Screen Sharing and File Security: To present from the meeting room PC, any files must be accessible by the resource account, creating additional security concerns and sharing/permission headaches. What We’re Looking For Affordable wireless presenting options for meeting rooms—ideally something that integrates smoothly with Microsoft Teams, but without requiring full MTR hardware. Best practices to lock down or reset the meeting room PC so meeting agendas, chats, and files are not visible after a session. Secure ways to allow guests to present (screen share, share files, etc.) without exposing company data or making users jump through complicated permission processes. If anyone has experience setting up small, cost-effective Teams Rooms, especially with regular PCs rather than dedicated MTR devices, advice would be greatly appreciated! Specific steps, hardware/software recommendations, or management tips would all be helpful. Thanks in advance for any guidance!