CCDev3 - Ignite roundup on Dev Story for Copilot and Agents

Nov 29, 2025

In this engaging discussion, Garry Trinder, a Cloud developer advocate at Microsoft, dives into the latest from the Ignite Conference. He shares insights on the renaming of Azure AI Foundry to Microsoft Foundry, highlighting its broad platform vision. Garry explores new features like the Foundry portal’s visual workflow designer and the streamlined publishing to Teams. They also touch on the integration of Claude models and emphasize the importance of experimenting with language models while maintaining responsible AI practices. A must-listen for tech enthusiasts!

Ask episode

AI Snips

Chapters

Transcript

Episode notes

INSIGHT

Foundry Rename Signals Bigger Scope

Microsoft Foundry (formerly Azure AI Foundry) signals a broader ambition beyond Azure and centralizes agent management.
The new Foundry portal simplifies model discovery, builds, and agent publishing into one UX.

ADVICE

Publish Agents From Foundry Portal

Publish Foundry agents directly to Teams and Copilot from the new portal to skip manual manifest workflows.
Use the portal for quick distribution but test thoroughly before using in production.

INSIGHT

More Model Choices In Foundry

Claude models are now available inside Microsoft Foundry, expanding the model choices in-platform.
Foundry also includes a model router to recommend faster, cheaper models for tasks.

Get the Snipd Podcast app to discover more snips from this episode

Get the app

Send us a text

In this episode of Copilot Connection, Kevin McDonnell and Garry Trinder discuss the latest developments from the Ignite Conference. They delve into the renaming of Azure AI Foundry to Microsoft Foundry, the new features of the Foundry portal, and the integration of Claude models. The conversation also covers the importance of experimentation with language models, updates on the Teams SDK, and the nuances of the Agent 365 SDK. In this conversation, Garry and Kevin delve into the latest advancements in Microsoft 365, focusing on Agent 365, MCP servers, and the integration of low-code solutions. They discuss the potential of natural language processing in enhancing user interactions, the significance of declarative agents, and the importance of responsible AI practices, particularly in the context of red teaming. They may also chuckle at renames more than they should...

Takeaways

Renaming products often indicates a broader vision beyond their original scope.
The new Microsoft Foundry portal simplifies the process of managing AI agents.
Publishing agents to Teams and Copilot has become more streamlined and user-friendly.
Claude models are now integrated into the Microsoft ecosystem, enhancing AI capabilities.
Experimentation with different language models is crucial for optimizing performance.
Understanding the purpose of each tool in the Microsoft ecosystem is key to effective use.
The Teams SDK has been rebranded, reflecting its expanded functionality.
The Agent 365 SDK builds on existing frameworks to enhance agent capabilities.
MCP servers need to be exposed for use.
Low code options are available for MCP management.
Declarative agents are evolving with TypeSpec innovations.
Red teaming is essential for testing AI agents.
Responsible AI practices are crucial in agent development.
User feedback is vital for improving Microsoft technologies.
MCP is becoming a standard for data interaction.

Links
Ignite Book of News

Azure AI Foundry is now Microsoft Foundry

Deploy and use Claude models in Microsoft Foundry - Microsoft Foundry | Microsoft Learn

Teams AI Library is now Microsoft Teams SDK

Microsoft Graph is Work IQ....

Agent 365 SDK

MCP Management Server

Kevin's example of MCP in Copilot Studio