# Microsoft Teams Microsoft Teams is a collaborative platform with a developer platform for building agents, apps, workflows, and integrations. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Porting a Discord Bot to Microsoft Teams with GitHub Copilot CLI DevFeed: [Porting a Discord Bot to Microsoft Teams with GitHub Copilot CLI]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Daniel Doubrovkine]() Topics: [GitHub Copilot CLI](), [Microsoft Teams](), [Artificial Intelligence](), [Discord](), [AdventureX 2025]() Tags: [ai](), [discord](), [github-copilot-cli](), [hackathon](), [microsoft-teams](), [porting](), [ruby](), [strava]() ### AI overview The article compares a manual 2023 port of a Strava chat bot from Slack to Discord with a 2026 port to Microsoft Teams completed with GitHub Copilot CLI. The Teams port took three days and involved authentication, app-manifest, tenant distribution, and Azure setup work. ### Source excerpt Slava (slack-strava) connects a Strava account to a chat and posts a card for every activity, complete with map, pace, and elevation, plus commands like connect, disconnect, stats, and leaderboard. In 2023 I ported Slava to Discord by hand, evening by evening over about three weeks, and it took most of that stretch to get a working bot called Strada (discord-strava). This week I ported the same app to Microsoft Teams as Strata (teams-strava) in 3 days instead of the 3 weeks the Discord port took, using time carved out during the Microsoft Global Hackathon. By "I", I mean GitHub Copilot CLI and I. The 2023 Baseline discord-strava's git history is a fair record of how long a manual port takes. The first commit, "Initial fork from slack-strava," landed July 30, 2023. "Most interactions working" was three days later. Getting install/help/error-handling polish took through August 20: 2023-07-30 23:56 Initial fork from slack-strava. 2023-08-02 23:46 Most interactions working. 2023-08-03 06:18 Remove PNG retrieval, Discord displays redirects correctly. 2023-08-03 06:26 Removed clubs. 2023-08-03 08:28 Fixed model specs. 2023-08-03 18:20 Fix API specs. 2023-08-04 19:44 Fix command specs. ... 2023-08-08 10:34 Countinously poll with 1 minute intervals. 2023-08-20 22:59 Improved install button and text. 20 commits spread across 9 evenings over roughly three weeks (there's a real job and a life in between those timestamps). All hand-typed, with GitHub Copilot's inline autocomplete helping the way it helped everyone in 2023, but no agent driving the actual porting work. The 2026 Port teams-strava's git history is a single continuous Copilot CLI session, 107 conversational turns over three calendar days, and the timestamps compress dramatically: 2026-09-14 11:05 Initial port of discord-strava to Microsoft Teams 2026-09-14 16:39 Fix local dev setup and personal-scope install handling 2026-09-14 16:43 Fix 400 error replying to personal-scope install notice 2026-09-15 08:29 Document ## Honoring #IconsOfQuality: Gaurav Singh DevFeed: [Honoring #IconsOfQuality: Gaurav Singh]() Original publisher: [Read original article]() Author: Rajrupa Roychowdhury Published: 2026-09-15T11:29:38Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Software Testing](), [Test automation](), [Microsoft](), [Microsoft Teams](), [CI/CD](), [Meta](), [Artificial Intelligence]() Tags: [ai-agents](), [ci-cd](), [icons-of-quality](), [microsoft](), [microsoft-teams](), [quality](), [software-testing](), [test-automation]() ### AI overview BrowserStack profiles Gaurav Singh, a Senior Software Engineer at Microsoft, as an Icon of Quality. The article highlights his work on scalable engineering systems, testing infrastructure, CI/CD pipelines, developer productivity, mentorship, and the role of determinism and feedback loops in automated testing. ### Source excerpt To celebrate the relentless passion and invaluable contributions of leaders in software quality, BrowserStack is proud to honour Icons of Quality. ## Chat SDK now supports reactions and ephemeral messages on Teams DevFeed: [Chat SDK now supports reactions and ephemeral messages on Teams]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-07-31T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Microsoft Teams](), [SDKs](), [Bots](), [API](), [Routing (disambiguation)]() Tags: [api](), [bots](), [microsoft-teams](), [release](), [routing](), [sdk]() ### AI overview Chat SDK's Microsoft Teams adapter now supports reactions and ephemeral messages through the same API used by other adapters. The release also adds author email details, custom token factories, native direct-message status, improved conversation routing, and more accurate mention conversion. ### Source excerpt Chat SDK's Microsoft Teams adapter now supports reactions and ephemeral messages through the same API as other adapters. Bots can add and remove reactions on Teams messages, and call thread.postEphemeral() or channel.postEphemeral() to send native, targeted messages that only the intended user sees, like permission prompts. This release also adds: Author emails: Incoming Teams messages include the author's Microsoft Graph email, with their user principal name as a fallback. Custom token factory: Pass a token function in TeamsAdapterConfig to supply your own access tokens, so bots on runtimes without Azure IMDS can authenticate without a static client secret. Native DM status: Progress messages now show as a native Teams status in direct messages. Conversation routing: Group conversations are no longer misidentified as direct messages, so they're always handled correctly. Mention conversion: Email addresses, @handles inside URLs, and mentions inside code spans are no longer turned into Teams mentions. Read the Teams adapter documentation to get started, or learn more about ephemeral messages and reactions. Special thanks to onmax for their contributions to this release. Read more ## Fact-checking PagerDuty's Opsgenie alternatives comparison table DevFeed: [Fact-checking PagerDuty's Opsgenie alternatives comparison table]() Original publisher: [Read original article]() Author: Tom Wentworth Published: 2026-07-28T14:21:14Z Content type: opinion Language: en Sources: [The incident.io Blog]() Topics: [incident](), [incident management](), [Incident response](), [Slack](), [Artificial Intelligence](), [dashboards](), [Microsoft Teams](), [API](), [Terraform](), [issue tracker]() Tags: [ai](), [api](), [article](), [comparison](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [microsoft-teams](), [outage](), [post-mortem](), [slack](), [slack-incident](), [terraform]() ### AI overview The article fact-checks PagerDuty's comparison table for Opsgenie alternatives, arguing that its description of incident.io is inaccurate. It presents incident.io as an end-to-end AI incident management platform with on-call scheduling, alert routing, incident response, dashboards, mobile access, status pages, investigation, post-mortems, insights, workflow automation, API access, and Terraform support. ### Source excerpt PagerDuty published a new comparison table about incident.io. Once again, it describes a product we don't recognize. So once again, we're correcting the record, row by row, with receipts. ## Chat SDK adds Novu support DevFeed: [Chat SDK adds Novu support]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-06-22T14:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Command-line interface](), [Microsoft Teams](), [Slack]() Tags: [agent](), [bridge](), [channel](), [cli](), [documentation](), [identity](), [mapping](), [microsoft-teams](), [oauth](), [sdk](), [slack](), [support](), [telegram](), [tokens](), [whatsapp]() ### AI overview Chat SDK adds Novu support through a vendor-official adapter, allowing one handler set to connect agents to Slack, Microsoft Teams, WhatsApp, Telegram, and email. Novu manages credentials, identity, delivery, OAuth, and tokens, while a CLI command configures a channel and adds its credentials to the project. ### Source excerpt Chat SDK now supports Novu with the new vendor-official adapter. One handler set puts your agent on Slack, Microsoft Teams, WhatsApp, Telegram, and email. Novu handles credentials, identity, and delivery, keeping OAuth and tokens outside your app and mapping each channel to one user. Your agent always knows who they're talking to. Your agent can also send proactive notifications and handle the replies in the same loop, on whichever channel the customer used. One CLI command connects a real channel to your agent: It signs you in, creates a bridge agent, sets up the channel you pick (e.g., Slack), and adds the credentials to your project. Read the Novu documentation to get started. Read more ## Chat SDK brings agents to your users DevFeed: [Chat SDK brings agents to your users]() Original publisher: [Read original article]() Author: Eric Dodds Published: 2026-03-19T04:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [SDKs](), [Bot](), [Messaging](), [TypeScript](), [Bots](), [API](), [Discord](), [Google Chat](), [Microsoft Teams](), [Slack](), [Google]() Tags: [agent](), [agents](), [api](), [apis](), [bots](), [coding-agents](), [developers](), [discord](), [github](), [integration](), [library](), [messaging](), [microsoft-teams](), [platform](), [platforms](), [sdk](), [slack](), [streaming](), [telegram](), [typescript]() ### AI overview Chat SDK is a TypeScript library for building bots and agents that work across Slack, Microsoft Teams, Google Chat, Discord, Telegram, GitHub, and Linear from a single codebase. It abstracts platform-specific messaging APIs through adapters, covering differences in streaming, formatting, branching logic, event routing, and reaction handling. ### Source excerpt In early March, we gave the entire organization a challenge: figure out how to multiply your output. People created agents. Mostly chat bots, but dedicated ones, purpose-built for real workflow augmentation: the agents were doing things automatically that would otherwise be tedious and time consuming. Initially people built individual interfaces for their agents, and AI SDK made that easy with out-of-the box model integrations and AI Elements to simplify UI design. Then we hit a constraint. People wanted to interact with the agents in Slack, meaning everyone had to figure out how to integrate with Slack's API. Then the problem got worse. Once the agents were in Slack, people wanted to integrate them with even more platforms, like Discord, Github, and even issue trackers like Linear. Each of those introduced a new integration adventure for every agent. It hit us. Instead of asking people to come to agents, we needed to deliver agents to the places they were already working. Chat needs integration abstraction We realized we had made it easy for our teams to create agents, but we needed to make it easier to extend them for adoption across platforms. This is true for every company. People are already using Microsoft Teams, WhatsApp, Telegram, and Google Chat, and agents need to be available in all of them. That's exactly what the Chat SDK does: makes agents available across enterprise and consumer chat platforms. Just like the AI SDK unified model provider APIs into a single interface, we built Chat SDK to abstract the quirks of messaging APIs into a simple framework for developers and their coding agents. Developers no longer need to think about the way streaming might differ from one platform to the next, or how formatting, branching logic, or even reaction-handling should be tackled for individual APIs. Write once, deploy everywhere Chat SDK is a TypeScript library for building bots that work across Slack, Microsoft Teams, Google Chat, Discord, Telegram, GitHub, and ## Introducing: incident.io for Microsoft Teams DevFeed: [Introducing: incident.io for Microsoft Teams]() Original publisher: [Read original article]() Author: Ed Dean Published: 2024-08-13T14:06:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [Microsoft Teams](), [Slack](), [Netflix]() Tags: [communication](), [engineering](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [legal](), [microsoft-teams](), [netflix](), [on-call](), [outage](), [post-mortem](), [slack-incident]() ### AI overview incident.io is now available on Microsoft Teams, bringing incident creation, dedicated incident channels, alert context, updates, role assignment, and action tracking into Teams. The article presents this as an expansion of incident.io's existing incident-response products, which were previously available through Slack. ### Source excerpt The wait is finally over. Introducing: incident.io for Microsoft Teams 🔥 ## A Journey from Hackathon to Production DevFeed: [A Journey from Hackathon to Production]() Original publisher: [Read original article]() Author: Chirayu Asati Published: 2023-11-29T14:22:33Z Content type: article Language: en Sources: [Android@Microsoft - Medium]() Topics: [AdventureX 2025](), [Microsoft Teams](), [Mobile](), [Product Management](), [Software Engineering]() Tags: [collaboration](), [engineering](), [events](), [hackathon](), [ideation](), [journey](), [microsoft](), [microsoft-teams](), [mobile](), [product](), [product-management](), [production](), [software](), [software-engineer](), [team]() ### AI overview A Microsoft Teams Mobile software engineer describes how a hackathon idea to simplify scheduling meetings from group chats was developed into a production feature. The article covers the original user problem, reducing the process from more than eight steps to three, and collaboration among product management, design, and engineering using the RICE prioritization framework. ### Source excerpt Hey there, I am Chirayu and I'm taking you on the journey of transforming a mere idea into a fully-fledged, efficient feature that requires a compelling tale of innovation. I'm a Software Engineer at Microsoft Teams Mobile and I had the privilege of being part of this remarkable journey from the beginning. This story is not just about the technical process but the innovation, collaboration, and dedication of the teams to overcome challenges creating incredible impact. It all started when I was feeling too lazy and frustrated to schedule a meeting with folks in my hackathon group chat because I had to go to the meeting scheduler and search everyone by name, add them one by one and then schedule the meeting. Too hectic, isn't it? Is being lazy bad? No way, see this quote from the Gates. So, whenever we are lazy, we have an opportunity to make things easy for ourselves and the world. The Idea As described above, if you want to schedule a meeting while chatting in a group, you would have to: User flow to schedule a meeting from chat in Teams Mobile beforeUser flow to schedule a meeting from chat in Teams Mobile after As you can see in the above image, scheduling a meeting from chat takes 8+ steps in Teams Mobile so the idea is to reduce this to just 3 simple steps: This streamlined approach would save valuable time and simplify the process. This concept sparked the beginning of our journey. About Microsoft Global Hackathon Hackathon is a great way for ideation, innovation, collaboration & fun and Microsoft is renowned for its commitment to hackathons, conducting events like CodeFunDo in colleges and the Microsoft Global Hackathon for its employees. After demonstrating the potential of our hack, it was time to go down the road to turn it into a fully-fledged product feature accessible to millions of people on the planet. R.I.C.E. The initial phase of transitioning from a hack to a production-ready feature involves discussions with the Product Management team to craft a c ## What's new in Figma: August 2022 DevFeed: [What's new in Figma: August 2022]() Original publisher: [Read original article]() Author: Chandler Sopko Published: 2022-08-30T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Microsoft Teams](), [Usability](), [Accessibility](), [User interface design]() Tags: [accessibility](), [figma](), [integrations](), [latest-features](), [microsoft-teams](), [plugins](), [updates]() ### AI overview A monthly roundup of August 2022 updates to Figma and FigJam, including a Microsoft Teams app for collaboration, usability improvements, easier diagram creation, education-focused resources, Chromebook beta updates, and new plugins and integrations. ### Source excerpt A monthly round-up of the latest features, fixes, and finesse we've added to Figma and FigJam. ## Collaboration's next chapter with Microsoft's Jon Friedman DevFeed: [Collaboration's next chapter with Microsoft's Jon Friedman]() Original publisher: [Read original article]() Author: Ted Brown Published: 2022-08-18T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Microsoft Teams](), [Microsoft]() Tags: [collaboration](), [design](), [design-systems](), [figma](), [integration](), [microsoft](), [microsoft-teams](), [remote]() ### AI overview This Q&A discusses collaboration with Microsoft's Jon Friedman following Figma's integration with Microsoft Teams. It covers working across design, engineering, product, and marketing tools, collaborating in Figma and FigJam within Teams, distributed and hybrid work, design systems, and organizational culture. ### Source excerpt A Q&A with the design and research leader on the heels of Figma's integration with Microsoft Teams. ## Envoyer: Extended Deployment Timeouts and New Notification Channels DevFeed: [Envoyer: Extended Deployment Timeouts and New Notification Channels]() Original publisher: [Read original article]() Author: James Brooks Published: 2020-09-17T10:02:00Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Deployment](), [Discord](), [Microsoft Teams](), [Slack]() Tags: [deployment](), [discord](), [microsoft-teams](), [slack]() ### AI overview Envoyer has extended deployment timeouts for Premium Plan customers from 10 to 15 minutes, while Basic and Plus plans remain limited to 10 minutes. It also now supports Slack, Microsoft Teams, and Discord as notification channels. ### Source excerpt We're excited to announce a few changes we've just shipped to [Envoyer](https://envoyer.io). Extended Deployment Timeouts ----------------------------- Starting today, all customers on the **Premiu...