Getting a 401 when trying to create a conversation
Hello ! Using the node botbuilder SDK, I am trying to setup my bot to proactively create a conversation in a public channel on Teams. However, I keep getting 401 responses from the API, with no further details. You can find my code attached bellow: const adapter = new CloudAdapter( new ConfigurationBotFrameworkAuthentication( { MicrosoftAppId: process.env.MS_BOT_APP_ID, MicrosoftAppTenantId: process.env.MS_CLIENT_ID, }, new ConfigurationServiceClientCredentialFactory({ MicrosoftAppId: process.env.MS_BOT_APP_ID, MicrosoftAppPassword: process.env.MS_BOT_CLIENT_SECRET, MicrosoftAppTenantId: process.env.MS_CLIENT_ID, }), ), ); await adapter.createConversationAsync( process.env.MS_BOT_APP_ID!, Channels.Msteams, "https://smba.trafficmanager.net/teams/", null, { activity: { type: "message", text: "This is a test message", textFormat: "markdown", }, bot: { id: `28:${process.env.MS_BOT_APP_ID}`, name: "Zygon" }, isGroup: true, tenantId: process.env.MS_TENANT_ID, channelData: { channel: { id: channelId } }, }, console.log, );
New Teams Interface – can't pin /favorite entire teams
CoPilot wrote this post... in fact its proposed title was New Teams Interface – Missing Basic Functionality & Creating Chaos for Admins, so I think it's sensing a bit of annoyance at the new UI... I’m posting this out of sheer frustration after wrestling with the new Microsoft Teams layout. I'm an IT admin responsible for managing Teams across multiple users, and the recent interface update has made that nearly impossible. Key issue: You can no longer pin or favourite entire teams—only individual channels. This is a huge regression in usability. For power users and admins, being able to organize entire teams was essential. Now, everything’s buried under scattered views, vague icons, and non-intuitive menus. I’ve gone through every menu and setting imaginable. “Show,” “Pin,” “Back to classic”—none of it helps because Microsoft simply removed the feature. Even Copilot (Microsoft's own AI tool) couldn’t make sense of what was missing until we both realized the function was outright gone. That’s saying something. This change is actively hurting productivity for both end users and those of us tasked with supporting them. Updates should make things better—not hide or remove critical features without proper notice or alternatives. Microsoft, please rethink this. Stop redesigning without considering the real-world implications for businesses trying to stay organized. — If others are feeling the same pain, let’s get this some visibility. The more upvotes and replies, the louder the message
How to resolve "Failed to submit this app" error?
Hi Team, Just from Today, while submitting teams custom app via Developer Portal, error "Failed to submit this app." started to occur. I have tried with below condition but this error always occurs. Error also occurs on the app which we can submit update till yesterday. What is happening and how can we resolve it? (from this error message, we couldn't guess anything about the reason..) Checked: ・Publish from outside Developer Portal (apps > manage apps > send app to organization) succeeded so seems Developer Portal related Issue. ・For all apps, no validation error in "Publish to store" is found. Manifest itself seems to be fine. ・Create new custom app with minimum configuration and publish but failed with same error. ・Tried publish from both Teams client and Browser but failed with same error. ・Try same operation with different tenant but failed with same error.
Unable to get custom Teams app supported in shared channel
Hello everyone, I'm developing a Teams app which is working fine apart that I cannot the app supported in Teams shared channels. The app is a configurable tab app with no bots and no personal / static tabs Here is my manifest file: { "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.23/MicrosoftTeams.schema.json", "manifestVersion": "1.23", "version": "1.6.5", "id": "135a5af5-6bf3-XXXX-XXXX-XXXXXXXXXXXX", "developer": { "name": "COMPANY", "websiteUrl": "https://www.company.com/", "privacyUrl": "https://www.company.com/privacy", "termsOfUseUrl": "https://www.company.com/termsofuse", "mpnId": "XXXXXXX" }, "icons": { "color": "color.png", "outline": "outline.png" }, "name": { "short": "APP name", "full": "Full app name" }, "description": { "short": "A useful configurable Teams app", "full": "useful Teams app" }, "accentColor": "#FFFFFF", "configurableTabs": [ { "configurationUrl": "https://app.example.com/setup", "canUpdateConfiguration": true, "scopes": [ "team" ], "context": [ "channelTab" ] } ], "supportedChannelTypes": [ "privateChannels", "sharedChannels" ], "webApplicationInfo": { "id": "e11ad337-b136-XXXX-XXXX-XXXXXXXXXXXX", "resource": "api://app.example.com/e11ad337-b136-XXXX-XXXX-XXXXXXXXXXXX" }, "bots": [], "composeExtensions": [], "permissions": [ "identity" ], "validDomains": [ "app.example.com" ] } Does anyone have a similar issue? I've also tried to recreate the app using the Teams Developer Portal, but with no luck. Thank you Tobias
