microsoft teams
1807 TopicsTeams app update stuck in Certification for almost three weeks
Hi everyone, We submitted an update to our Teams app Condens on October 26. Since Oct 26, 2026, 10:55 PM UTC, it has been in the Certification step in Partner Center, and nothing has changed since. Partner Center estimates under 5 business days for this step. Details: Product ID: WA200008643 Listing: https://marketplace.microsoft.com/en-us/product/wa200008643 Submitted changes: packages, marketplace listings and availability Status: In progress, step “Package availability” under Certification We emailed email address removed for privacy reasons on November 9 and followed up since, but haven’t received a response. Has anyone seen something similar recently? Is there another channel we should use to escalate a stuck submission? If someone from the Teams Store team sees this, we’d really appreciate a look. Thank you! Matej77Views0likes2CommentsTeams Registration presence not displaying 'Offline'
We're using the Microsoft Graph API for some Teams presence checks and alerting for registrations going 'Offline'. This works fine is doing a planned reboot of a system (software client or Microsoft Teams Room (MTR) device), the presence status shows 'Offline'. The point of the alerting is to know when that change of presence/availability happens unexpectedly. Let's take the example of a Teams Room device where the network cable is unplugged. I'd expect to see the presence of that user turn quickly to 'Offline'. It doesn't! Instead it sits at 'Away'. I've tested this using different users with an MTR (network cable removed, license is 'MTR Standard') and software login on iPadOS (application force closed). This is really odd default behaviour and at the time of writing this is 2 hours later and both registrations shows as 'Away' still. You'd think that after (at most) 15 minutes the status would change to 'Offline'. Can this be behaviour be changed? Or is this a bug? Any ideas?827Views0likes1CommentBot not receiving message events in shared channels (RSC)
Hi folks, Running into an issue with a bot in Microsoft Teams shared channels. I've configured RSC permissions to listen for new messages. This works as expected in standard channels - I receive events for every new message. However, in shared channels, the behavior is different: I only receive events when the bot is explicitly tagged Regular messages in the channel don’t trigger any events Permissions currently granted: Channel.ReadBasic.All (Application) ChannelMember.Read.All (Application) ChannelMessage.Read.All (Application) Has anyone faced this with shared channels? Is this expected behavior or am I missing something in setup? Thanks!566Views0likes6CommentsCustom video filters for MS Teams
Hi, I've been experimenting with the Teams Video Filters platform that was announced in public preview in 2023 and have successfully built a proof of concept. Before investing further, I'm trying to understand Microsoft's current direction for this capability. While the APIs and documentation still exist, I haven't found much recent discussion, roadmap information, or examples of new apps being built in this space. Can anyone from Microsoft comment on: Whether Video Filters remains an actively supported extensibility platform Whether new third-party filter apps are still encouraged Whether there are plans for further investment in this area I'm mainly trying to assess whether this is a good long-term bet for a commercial Teams app, or a feature area that has effectively plateaued. Thank you and BR, Sergey.200Views0likes0CommentsStatic Tab and Chat Tab Order Is Not Persisting in Microsoft Teams
manifest file: "staticTabs": [ { "entityId": "schedule", "name": "Schedule", "contentUrl": "...", "websiteUrl": "...", "scopes": ["personal"] }, { "entityId": "conversations", "scopes": ["personal"] } ] the Schedule tab is intentionally place before conversations: it initially appears correctly, but after navigating away from the app and returning, Teams places Chat/Conversations before Shcedule. I'm using schema version 1.12. The tabs are configured in the specified order in the manifest file, and the expected tab order is displayed correctly when the app is initially opened. However, when I navigate to the Chat section, the tab order changes and does not persist as defined in the manifest file.174Views0likes0CommentsAPI: get video recording link via Microsoft Teams
Hi teams. What are some ways to get video recording link URLs of a teams meeting via API (Graph/Sharepoint/OneDrive)? Is it possible to get the recording URL from the calendar event? I do see the embedded video link when I am editing a recorded event in my calendar. Saw some previous post of getting access via Chat messages - callRecordingUrl: https://techcommunity.microsoft.com/t5/microsoft-365-developer-platform/get-the-link-to-the-recording-of-teams-meeting-from-the-graph/idi-p/2675306 (what are the auth required to make function calls to get this?) Wondering if there are any update on this, thanks1.7KViews0likes4CommentsHow to Download Video Clip from Microsoft Teams Programmatically
I’m developing a bot app for Microsoft Teams, and part of its functionality involves handling videos recorded using the Teams widget(see screenshot attached). I am receiving a video clip link in the bot app's backend message. Where is this video file uploaded and how can I download the video clip using that link? I have attempted the SSO auth via Entra ID to fetch the auth token and attached it against the GET request to the video clip link as the bearer token. But still getting 401 errors? Need help and guidance in this matter. Thanks.807Views0likes7CommentsApp Validation failing for no clear reason
We're trying to get our (very simple) Teams App listed on the app store, but during the App Validation we keep getting the same error: "Unable to upload the manifest.zip file in MS Teams." as seen below: Downloading the report doesn't give any more information, it only lists the only successful validation step ("BotID should be registered") and the error doesn't appear there. I've validated the manifest.json file against the schema, tried reuploading the same manifest to a different org (creating a new app and bot) - validation fails there too. Does anyone have any pointers? Here is my (anonymized) manifest file: { "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.19/MicrosoftTeams.schema.json", "manifestVersion": "1.19", "version": "1.1.1", "id": "[redacted]", "developer": { "name": "[redacted]", "websiteUrl": "https://www.[redacted].com", "privacyUrl": "[redacted]", "termsOfUseUrl": "[redacted]" }, "icons": { "color": "color.png", "outline": "outline.png" }, "name": { "short": "[redacted]", "full": "[redacted]" }, "description": { "short": "[redacted]", "full": "[redacted]" }, "accentColor": "#4A3AFF", "bots": [ { "botId": "[redacted]", "scopes": ["personal"], "supportsFiles": false, "isNotificationOnly": false, "commandLists": [ { "scopes": ["personal"], "commands": [ { "title": "help", "description": "Show what this bot does and how to connect your account" }, { "title": "connect", "description": "Get a fresh link to (re-)connect your account" } ] } ] } ], "staticTabs": [ { "entityId": "conversations", "scopes": ["personal"] }, { "entityId": "about", "scopes": ["personal"] } ], "permissions": ["identity", "messageTeamMembers"], "validDomains": ["app.[redacted].com", "auth.[redacted].com"] }442Views0likes2CommentsTeams Personal Bot Identity Cache issue
Hi all — looking for guidance on a Teams custom app + bot naming issue. We have a custom Teams app with a bot. The app catalog/admin/dev portal surfaces show the correct app name, and the manifest + Azure Bot configuration appear correctly aligned, but the Teams personal chat surfaces still show the old/wrong bot name. What looks correct: Teams app manifest name.short / name.full have the correct app name Manifest bots[0].botId points to the expected bot ID Azure Bot resource → Configuration → Microsoft App ID matches that bot ID Azure Bot resource → Bot profile display name has the correct name Teams Developer Portal basic information shows the correct name Teams Admin Center shows the correct app short name What is still wrong: Teams left sidebar chat name shows the old/wrong name Chat top header shows the old/wrong name Inline bot sender/name in the conversation shows the old/wrong name The issue reproduces for multiple users It persists after sign out/sign in, uninstall/reinstall, republish, and retesting We may also be seeing a package/version propagation issue: after publishing an updated app package with a newer manifest version, Teams Admin Center still appears to show the previous version. Has anyone seen this before with personal bot apps? Specifically trying to understand: What is the authoritative source for the personal bot chat roster/header/sender display name?461Views0likes1Comment