Forum Widgets
Latest Discussions
TEAMS - Extra Space between Keyboard and Typing Window
Dear All, I am also facing the issue in TEAMS. During the typing, a large space appears between Keyboard and Typing Window. This is happening only in TEAMS app. I moved from my Nothing phone to Vivo X200Fe, then this problem started. This may be a bug in TEAMS to be fixed for VIVO phones. I use VIVO X200 FE with Android 16 and Google Keyboard. It's very annoying to see this big gap and making us uncomfortable while typing. Please help me how to resolve this. Thanks for your help. Mobile : Vivo X200FE Operating System : Origin OS Android 16 Teams Version : 1416 / 1.0.0.2026123608 Keyboard : Google Keyboard - Version 17.7.4.93236420
Who verifies Teams Meeting summary accurately reflects what was actually agreed in the meeting
Can we really trust AI-generated meeting summaries? Microsoft Teams and Copilot can create impressive meeting summaries, action items, and insights. But a question remains: Who verifies that the summary accurately reflects what was actually agreed in the meeting? In many organisations, meeting notes become the basis for: project decisions customer commitments compliance records accountability for actions Yet when there is disagreement, we often hear: "That is not what I said." "I don't remember agreeing to that." "The summary missed the context." How is your organisation handling this today? Do you: Trust AI-generated summaries as they are? Have a human review process? Keep the original transcript/audio as evidence? Use another approach? Interested to hear how Teams users are managing this challenge.
Blinking red light on Poly CCX 500 Teams phones
I have a few users that have a Blinking red light on the phone, they have no missed call, or activity notices. I have tried - This is usually caused by a missed call, or activity notices on the account signed into the phone, on the phone I go to “Calls”, once looked at the light generally goes off.
Create event sometimes returns 201 but no Teams meeting link
Hello, I am creating calendar events through Microsoft Graph and setting them as Teams online meetings. Most of the time it works correctly, but very rarely the API returns 201 Created and the event is created without the Teams join link in the response. I have already checked the following: isOnlineMeeting is always set to true. The correct online meeting provider is being used. The issue is intermittent, not consistent. The same integration normally creates Teams meetings successfully. What I need to understand is: Why can Graph return 201 Created but still omit the Teams meeting link? Is this a known intermittent issue with event creation or Teams meeting provisioning? Is there anything I should check in the response, headers, permissions, or follow-up GET call to verify the meeting link was actually created
Is Microsoft Teams a good Intranet?
Our company is fully on Microsoft 365, but employees still struggle to find basic information like policies, company updates, forms, department resources, and important links. Most of it is scattered across SharePoint sites, Teams channels, emails, and random folders. I want to turn Microsoft Teams into that hub where all of this lives, kind of like an intranet. Any suggestions?Bug? Teams thread permalink does not show the full thread history (Desktop + Web)
Hi everyone, I believe I've found a bug in the new Teams threaded channel experience and I'm trying to determine whether others can reproduce it. Scenario I have a long-running thread in a Teams channel. If I open the thread directly from the channel by clicking the reply count (e.g."340 replies"), I can see the complete conversation, including the most recent replies. However, if I: Open the thread Use Copy link Open the generated link Teams opens the thread, but only displays part of the conversation. Newer replies are missing even though they exist and are visible when opening the same thread directly from the channel. Note: I cannot share the permalink publicly because it points to content within my organisation. However, the link was generated by Teams itself using the thread's Copy link action. The issue is reproducible with any user who has access to the thread. What I've tested Teams Desktop Teams Web Same behaviour in both clients Opening via the channel reply count shows all recent replies Opening via the permalink shows only a partial thread Expected behaviour A thread permalink generated by Teams should open the same live thread view as clicking the reply count from within the channel. The full conversation history should be available and the latest replies should be visible. Ideally: The full thread history should be available. The latest replies should be visible. The link should open the current state of the thread, not an apparently truncated version. Actual behaviour The permalink opens the correct thread but appears to stop at an older point in the conversation, while newer replies remain accessible only when opening the thread from the channel itself. Has anybody else seen this behaviour with threaded channels? Screenshot 1 and 2: Correct behaviour Open thread via "340 replies" Show: Thread title Reply count (e.g. 340 replies) One or two recent messages (July 2026) Screenshot 3: Incorrect behaviour Open the same thread via the permalink Show: Same thread title Same thread Conversation stopping much earlier Missing recent repliesFeature request: Historical Agent Activity Timeline for Microsoft Teams Queues
Hi everyone, We're currently using the new Microsoft Teams Queues app for our IT Service Desk and are very pleased with the improvements Microsoft has introduced. One capability we feel is still missing is a historical Agent Activity Timeline. Today supervisors can only see an agent's current Opt-in/Opt-out status. There is no historical overview showing: When an agent opted in When an agent opted out Which agents were opted in at a specific moment Whether the change was made by the agent, a supervisor or automatically This makes it difficult to investigate: Missed calls Queue performance SLA deviations Staffing questions Incident investigations A simple historical timeline containing the timestamp, queue, agent and source of the status change would already provide tremendous value for supervisors and service desk managers. We've submitted this as a feature request through the Microsoft Feedback Portal: https://feedbackportal.microsoft.com/feedback/idea/2df346ee-bc89-f111-9b47-7c1e52444ef6 If you experience the same limitation, we'd really appreciate your vote. I'm also interested in hearing how other organisations deal with this today. Are you using manual checks, screenshots or another workaround? Thank you! Romain Weimer Head of ICT Operations and Support Witteveen+Bos
Auto Attendant & Call Queue Call forwarding to external numbers failing.
Hi all, Since this weekend users accross our org. have been noticing that AA/CQ that forward Calls to external numbers FAIL. This was not the case last week. Flow example : User dials number of AA, this AA has a menu which has Internal and external numbers. Internal numbers -> no problem. Externa numbers -> message (new never heard this): "Please Hold while we forward your call, .... Sorry we could not forward your call at this time, try again later". On user level we are not experiencing this issue when I redirect my calls from work number to external number there is no issue. What is very strange in this entire scenario is that we are EU bases, the resource accounts "Usage location" is on the proper country in EU. But in the Microsoft PSTN USAGE logs we see that the "Azure region for Media" is USSC, USEA, USWE, JPWE, JPEA, MAWE, KRCE where it should be EUWE, FRCE and EUNO ... But No Fail Codes, just Bye ... The dates hold up with the issue... before 26/07 everything passed over EU Region. After 26/07 everything passes over US, KR, MA, JP ... Anyone else having this issue ? Related to the new AI routing implementation gone bad ?
