<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft Teams on The Black Cloud</title><link>https://theblackcloud.tech/tags/microsoft-teams/</link><description>Recent content in Microsoft Teams on The Black Cloud</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2026, The Black Cloud.</copyright><lastBuildDate>Mon, 02 Nov 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://theblackcloud.tech/tags/microsoft-teams/index.xml" rel="self" type="application/rss+xml"/><item><title>AI - GitHub Copilot in Microsoft Teams, from notifications to pull requests</title><link>https://theblackcloud.tech/blog/aigithubcopilotinmicrosoftteams/</link><pubDate>Mon, 02 Nov 2026 08:00:00 +0000</pubDate><guid>https://theblackcloud.tech/blog/aigithubcopilotinmicrosoftteams/</guid><description>&lt;p>I really like the idea of this, especially if you are using GitHub.com 😉 Turning a Teams conversation about a bug into a proposed fix makes a lot more sense than just adding another notification to the pile.&lt;/p>
&lt;p>My sticking point is self-hosted GitHub Enterprise Server. This new Copilot workflow is not documented for GHES, so for organisations keeping their repositories there, the announcement is less useful. If that support arrives, I can see a lot more value in this 😊&lt;/p></description></item></channel></rss>