Weekly Update 10 November 2025 – Dev Resource Page, Teams SDK, AI Roadmap, Copilot-in-Country

This week:

New developer resource page for Microsoft 365 interoperability and data portability

Overview of Teams SDK (Teams AI Library)

Roadmap for AI in Visual Studio (November)

Microsoft offers in-country data processing to 15 countries to strengthen sovereign controls for Microsoft 365 Copilot

You can also listen to the audio-only version: Thoughtstuff Podcast – Tom Morgan on Teams Dev: Weekly Update 10 November 2025

Find all my videos at thoughtstuff.co.uk/videos. You can also subscribe to the audio-only version of these videos, either via iTunes, Spotify or your own podcasting tool.

Transcript (AI-generated)

Hello and welcome to another weekly update. I hope you’re doing well and keeping up with everything going on.

This week, I want to talk through a few interesting updates. First is a blog post from the Microsoft 365 developer blog. It’s centered around a new developer resource page for Microsoft 365 interoperability and data portability. This seems to come from a legal agreement with the European Commission to formalize values into legal commitments. The page outlines Microsoft’s commitments to making Microsoft 365 data interoperable and portable—essentially making it easier for users to extract their data from Microsoft’s ecosystem.

They’ve listed various APIs and resources, including Graph APIs (which they refer to as Exchange Online APIs). While the post itself is high-level and doesn’t dive into developer nitty-gritty, it’s still a helpful landing page if your organization needs an overview or you’re looking to understand existing extensibility options in Microsoft 365.

Next up, another rename. This time it’s the Teams AI library, which has now become the Teams SDK. The Teams AI library wasn’t that old—it helped developers quickly build AI-enhanced bots for Microsoft Teams. The rename to Teams SDK suggests broader scope, but in reality, it’s still focused on bot/agent behaviors and doesn’t cover other extensibility surfaces like tabs, message extensions, or meeting customizations. The rename might cause confusion, and I’d love to see more clarity during Ignite.

Still, if you’re trying to build a quick bot or agent for Microsoft Teams (and possibly Microsoft 365 at large), this SDK remains a solid option—it’s just under a new name now.

The Visual Studio team has published a new roadmap update which is worth checking out. They’re continuing to embed AI Copilot-style functionality throughout the Visual Studio experience. Some of the highlights include new test, debug, and chat agents; support for multiple agents at once; performance improvements; and integration with newer LLMs. These additions cover different parts of the application lifecycle, and it’s great to see Visual Studio still getting strong investment alongside VS Code. Each product serves different audiences and it’s valuable to have both continuing in parallel paths.

Finally, there’s a new blog post about Microsoft expanding in-country data processing for Microsoft 365 Copilot activities. This affects 15 countries initially—such as the UK, India, Australia, and Japan—and will expand to others including the US in 2026. It’s all part of strengthening data sovereignty and regional control. I thought Microsoft already offered something like this, but apparently not in this explicit form.

There’s often confusion between phrases like “data never leaves your tenant” and how that intersects with data processing locations. These nuances matter to IT admins and decision makers, so it’s important as developers to be aware and point folks to this information when needed.

Looking ahead, Microsoft Ignite kicks off next week (November 17-21), so depending on when you’re watching this, it might be quiet or the first announcements could be rolling out. Either way, it’s going to be exciting. Get everything lined up now so you can enjoy the event!

Have a great week, whatever you’re doing, and I’ll speak to you next time.