What’s changing?

• The isBroadcast property is deprecated and will be removed from the onlineMeeting resource.
• Creating Teams Live Events meetings by using this property will no longer be supported.

What should you do instead?

• Webinars (virtualEventWebinar)
• Town halls (virtualEventTownhall)

• Registration management
• Session and presenter configuration
• Attendance reporting
• Integration with Teams client for a seamless experience

Timeline

• March 31, 2026: Removal in beta.
• June 30, 2026: Removal in v1.0.

Why this matters

The post Deprecation notice: Teams Live Events meeting creation via Microsoft Graph appeared first on Microsoft 365 Developer Blog.

• Configuration hot reload – Dev Proxy automatically restarts when you change the config file
• Stdio traffic proxying – Intercept, inspect, and mock stdin/stdout/stderr traffic
• New --api-port command-line option
• LatencyPlugin now supports delays greater than 10 seconds
• CORS support for the Dev Proxy web API
• Multiple bug fixes and improvements

Configuration hot reload

Why this matters:

Stdio traffic proxying

How it works:

• Inspect messages in Chrome DevTools Network tab (appear as stdio:// URLs)
• Mock responses using the new MockStdioResponsePlugin
• Simulate latency with the existing LatencyPlugin
• Use placeholders like @stdin.body.id in your mock responses

New --api-port command-line option

LatencyPlugin improvements

What changed:

CORS support for Dev Proxy web API

Bug fixes

• -e flag now works correctly – Starting Dev Proxy with environment variable presets no longer throws a FormatException
• AuthPlugin ApiKey validation fixed – The plugin no longer incorrectly reports missing ApiKey.Parameters when they’re properly configured
• GenericRandomErrorPlugin method matching – Error responses without a specified HTTP method now correctly match all methods (GET, POST, PUT, DELETE, etc.) instead of only GET
• MockResponsePlugin Content-Type handling – No more spurious JSON parsing warnings when using form data or other non-JSON content types
• CRUD API data file hot reload – Data file changes now take effect immediately without restarting Dev Proxy

Dev Proxy Toolkit 1.12.0

• Custom installation paths — New devProxyPath setting for non-standard Dev Proxy locations
• Smarter config validation — Config section properties are now validated against the Dev Proxy schema, catching invalid values, unknown properties, and schema version mismatches
• Enhanced diagnostics — More precise highlighting, unique diagnostic codes with documentation links, and new warnings for empty urlsToWatch and optional plugin configurations
• More quick fixes — Add optional or missing plugin config sections, update schema versions across files, and remove unknown properties
• Better plugin support — AuthPlugin and LanguageModelFailurePlugin fixes, plus new snippets for GraphConnectorGuidancePlugin and MockStdioResponsePlugin

Why upgrade to v2.1.0?

• Faster iteration – Configuration hot reload means no more manual restarts
• MCP server testing – Inspect, mock, and debug stdio traffic with familiar workflows
• More flexibility – Runtime port configuration and unlimited latency simulation
• Cleaner experience – Multiple bug fixes reduce friction and noise

Try it now

The post Dev Proxy v2.1 with configuration hot reload and stdio proxying appeared first on Microsoft 365 Developer Blog.

Many solutions need a reliable way to store and retrieve per-folder configuration data alongside mailbox content—whether that’s application state, settings, or other metadata scoped to a folder.  The userConfiguration resource supports multiple payload styles so you can store what best fits your scenario: 

• binaryData: arbitrary binary data 

• xmlData: serialized XML 

• structuredData: key-value pairs of supported data types 

API capabilities

The beta release includes full CRUD support for userConfiguration objects: 

• Create a new userConfiguration 

• Get an existing userConfiguration 

• Update an existing userConfiguration 

• Delete a userConfiguration 

For example, you can read a configuration from either the signed-in user (/me) or a specific user (/users/{id}), scoped to a mail folder: 

• GET /me/mailFolders/{mailFolderId}/userConfigurations/{userConfigurationId}

• GET /users/{usersId}/mailFolders/{mailFolderId}/userConfigurations/{userConfigurationId}

Permissions (least privileged) 

The API uses dedicated permissions for mailbox configuration items: 

• Get supports MailboxConfigItem.Read (least privileged) and MailboxConfigItem.ReadWrite (higher privileged) 

• Create requires MailboxConfigItem.ReadWrite

• Update requires MailboxConfigItem.ReadWrite 

• Delete requires MailboxConfigItem.ReadWrite 

As always, choose the least privileged permissions your application needs. 

Get started 

The easiest way to begin is to explore the API surface and try calls interactively.

Review the resource and method docs: 

• userConfiguration resource type 

• Create userConfiguration

• Get userConfiguration

• Update userConfiguration

• Delete userConfiguration

Use Graph Explorer to test requests quickly: 

• Graph Explorer | Try Microsoft Graph APIs 

We’d love your feedback 

As you explore the User Configuration API in beta, we want to hear what’s working well and where we can improve—especially around usability, gaps, and real-world scenarios. 

Send feedback to: exouserconfigurationapifeedback@microsoft.com 

The post Introducing the Microsoft Graph User Configuration API (preview) appeared first on Microsoft 365 Developer Blog.

Since launching this monthly blog series in September 2025, our goal has been to provide clear insight into the SPFx roadmap and maintain an open and predictable communication rhythm with our ecosystem. With the January 2026 update, we continue that commitment by highlighting the near term roadmap, the addressing vulnerabilities with 1.22.2, and our longer term investment areas that will support developers building modern Microsoft 365 experiences.

Your feedback continues to shape the direction of SPFx. Real world observations and suggestions from customers and partners have guided our priorities, informed design decisions, and helped validate the work that moves from preview to production readiness. This collaboration ensures that SPFx evolves in a way that supports enterprise scale solutions and delivers the flexibility that teams expect when building across Microsoft 365.

Looking ahead, 2026 is set to be an important year for SPFx. In addition to the new monthly minor release model, we are preparing a set of roadmap updates that focus on developer productivity, long term sustainability, and better alignment with the evolving Microsoft 365 platform investments. These upcoming investments remain grounded in stability, performance, and the ability to build richer and more integrated user experiences. As always, we will update the public SPFx roadmap and share details through these monthly posts as plans continue to progress.

See details on the 1.22.2 release on the release notes:

• SharePoint Framework 1.22.2 release notes

Roadmap

We are evolving towards a quarterly release cycle, providing more predictability on new feature introductions and updates. We will update the public roadmap with any schedule and feature updates as we move forward in this journey.

Here is the set of investments which we are planning to ship within the upcoming SPFx releases:

January 2026 – debugging toolbar in SharePoint Online

This will be a server side update without a requirement to provide a client-side updates as new SPFx version.

• New debugging toolbar improving the in-page development experience when workbench is not used. Debugging toolbar will eventually replace the workbench page to enable you easily debug in any page in SharePoint Online.

Version 1.23 – February/March 2026

This release focuses on open sourcing the templates and tooling to create SPFx solutions, enabling our ecosystem to optionally build their own templates. We also want to focus on providing additional value for optimizing developer experience and providing new extensibility options.

• Open-sourcing SPFx solution templates via GitHub and opening them for community contributions.
• A new open-sourced SPFx CLI for replacing the existing Yeoman generator – You will be able to introduce your company specific templates or adjustments on the scaffolded baseline for the SPFx solutions. We are decoupling the CLI itself from the SPFx release versions.
• Command set improvements for lists and libraries – grouping and potentially other improvements.
• New and edit panel override in lists – support panel level override on the Microsoft Lists and SharePoint lists with SPFx.

Version 1.24 – May/June 2026

This version continues providing new extensibility options aligned with the future direction of SharePoint. We are also expecting to have other new features and capabilities as part of this release, which will be disclosed a bit later.

• Navigation customizers – Options to override navigation nodes and/or experiences with SPFx components.
• Other features will be shared later.

We also continue further innovation in the AI space with a focus on both customer features and developer tooling. More on this in future roadmap updates during 2026.

We encourage you to continue providing feedback to support our product planning for the upcoming semesters. We already have an extensive list of ideas and enhancements in mind but are always interested in your input.

What’s next?

We continue expanding the SharePoint platform to unlock more innovation across Microsoft 365:

• SharePoint Framework (SPFx) for building rich, AI powered and business integrated solutions with custom user interfaces directly in Microsoft 365.
• SharePoint Embedded to bring SharePoint content into your own apps hosted outside of Microsoft 365 with your own user interface.
• Agents and AI to create intelligent, adaptive experiences to access your content and business information efficiently and expose those easily for your end users.
• Microsoft Graph to access data and insights everywhere using our standard API surface.

We encourage you to explore these capabilities and see how they can help you build the next generation of solutions for your organization and customers.

Follow us also on LinkedIn or in X to stay up to date on Microsoft 365 Platform announcements.

Got feedback or input on this blog post – leave a comment and we will get back to you

Happy coding! Sharing is Caring! 

The post SharePoint Framework (SPFx) roadmap update – January 2026 appeared first on Microsoft 365 Developer Blog.

Introducing Evals for Agent Interop

As a first step, we’re launching ‘Evals for Agent Interop’, a starter evaluation kit debuting. ‘Evals for Agent Interop’ provides curated scenarios and representative data that emulate real digital work, along with an evaluation harness that organizations can use to self-run their agents across Microsoft 365 surfaces (Email, Documents, Teams, Calendar, and more). It’s designed to be simple to start, yet capable enough to reveal quality, efficiency, robustness, and user experience tradeoffs between agent implementations, so organizations can make informed choices quickly.

Get started: Download the starter evals and harness from our repo. We currently support Email and Calendar scenarios, and we’re rapidly expanding the kit with new scenarios, richer rubrics, and additional judge options. (https://aka.ms/EvalsForAgentInterop).

Leaderboard: Strawman agents, frameworks, and LLMs

To help organizations benchmark and compare, we’re introducing a leaderboard that reports strawman agents written using different stacks, a combination of agent embodiment frameworks (ex., Semantic Kernel, Lang Graph) and LLMs (ex., GPT 5.2). This gives organizations a clear view of how various approaches perform on the same scenarios and rubrics. The leaderboard will evolve as we add more agent types and frameworks, helping organizations determine the right set of agents for their Agent 365 Tools.

Why it matters

Customers want to more easily optimize their AI agents to their unique business. Enterprise AI is shifting from isolated model metrics to customer-informed evaluation. Businesses want to define rubrics, calibrate AI judges, and correlate offline results with production signals, tightening iteration cycles from months to days to hours. As Microsoft, we realize that customers expect to bring their own grading criteria and scrutinize datasets for domain fit before they trust an agent in their environment. ‘Evals for Agent Interop’ is purpose-built for this new reality, unifying evaluation needs in one path: start with pre-canned evals, then tailor to your context.

How Evals for Agent Interop works

‘Evals for Agent Interop’ ships with templated, realistic and declarative evaluation specs. The harness measures programmatically verifiable signals (schema adherence, tool call correctness, policy checks) alongside calibrated AI judge assessments for qualities like helpfulness, coherence, and tone. This yields consistent, transparent, and reproducible results that teams can track over time, compare across agent variants, and share across organizations.

How it will evolve into a full evaluation suite 

We’re building toward a full suite that helps organizations choose the right set of agents to run on their Agent 365 Tools:

Product teams within Microsoft define rubrics, train and calibrate judges, ship scenarios and data, and correlate offline scores with production metrics.

Customers bring their own data and grading logic via a that becomes the single source of truth for both offline grading and online guardrails at runtime. We’ll support custom tenant rubrics, with LLM or human grading for ambiguous cases.

Packaged governance includes audit trails, documented rubrics, and privacy posture aligned to usage. Over time, we intend to co-publish capability manifests, tool schemas, and calibration methods to foster transparency and community validation.

What can organizations do with the Evals for Agent Interop kit?

With ‘Evals for Agent Interop’, organizations can compare multiple agent candidates head-to-head on the same scenarios and rubrics, quantify quality and risk controls, and verify improvements (for example, a fine-tuned model or a different LLM) before broad rollout. As we expand the suite, these offline signals will align with online evaluation, so organizations can move from confidence to controlled deployment. Faster, safer, and clearer accountability.

Where to start (and what’s next)? 

Clone the GitHub repo (https://aka.ms/EvalsForAgentInterop) with the starter evals and Harness. Run the included scenarios to baseline your agents and understand gaps.

Tailor rubrics to your domain, then re-run to see how agent behavior shifts under your constraints.

We’ll expand ‘Evals for Agent Interop’ with new scenario families (document collaboration, communications, scheduling and tasking), richer scoring, and broader judge options, while integrating more tightly with Agent 365 Tools so evaluations and runtime guardrails share one source of truth.

The post Introducing the Evals for Agent Interop starter kit appeared first on Microsoft 365 Developer Blog.

What you can do with the Copilot Studio extension for Visual Studio Code

As agents grow beyond a few topics and prompts, teams need the same development hygiene they use for apps: source control, pull requests, change history, and repeatable deployments. The VS Code extension brings that workflow to Copilot Studio so makers and developers can collaborate without losing governance or velocity.

The extension supports a simple loop that fits naturally into your SDLC:

1) Clone an agent to your local workspace

Pull the full agent definition from Copilot Studio into a folder on your machine, so you can work locally with the full context of your agent.

2) Edit confidently in VS Code

Make changes to your agent components (topics, tools, triggers, settings, knowledge references) using a structured agent definition format and your existing VS Code workflow. The extension also provides IDE help like syntax highlighting and IntelliSense-style completion so edits are faster and less error-prone.

3) Review changes before they land

Preview what changed, compare cloud vs local, and resolve conflicts before you apply updates. This helps teams avoid overwriting each other’s work and makes collaboration practical at scale.

4) Apply changes back to Copilot Studio

Sync your updates to the cloud to test behavior and create evals as part of your normal iteration loop.

5) Deploy with the processes your team already uses

Use standard Git workflows and integrate agent definitions into automated deployment processes. This is the missing piece for teams that want agents to move through environments with the same rigor as code.

Built for development teams

The extension is designed for the way engineering teams actually work:

• Standard Git integration for versioning and collaboration
• Pull request-based reviews so changes are discussed and approved
• Auditability over time, with a clear history of modifications
• VS Code ergonomics: keyboard shortcuts, search, navigation, and a local dev loop

This extension is especially helpful if you:

• Manage complex agents with many topics and tools and need fast search and navigation
• Collaborate with multiple people and need PR workflows for safe changes
• Want agent definitions in source control and environment sync through DevOps pipelines
• Prefer building with your IDE plus an AI assistant for faster iteration

Develop Copilot Studio Agents using GitHub Copilot  

The Copilot Studio extension for Visual Studio Code lets you build and refine your Copilot Studio agent with AI help in the same place you write code. Use GitHub Copilot, Claude Code, or any VS Code AI assistant to draft new topics, update tools, and quickly fix issues in your agent definition, then sync changes back to Copilot Studio to test and iterate. The result is a faster inner loop with fewer context switches and a workflow that fits how development teams already work.

Get started

1. Install the extension from the Visual Studio Marketplace
2. Clone your first agent from Copilot Studio
3. Make a small change locally
4. Use Apply Changes to sync back to Copilot Studio and test

Learn more and share feedback

We built this extension so agent development can feel like the way software teams already work: in your editor, with source control, and with AI help when you want it. Try it in your next agent update and let us know what you want to see next!

• Learn more in Copilot Studio docs
• GitHub issues and feedback

The post Copilot Studio Extension for Visual Studio Code Is Now Generally Available appeared first on Microsoft 365 Developer Blog.

Since launching this monthly blog series in September 2025, our goal has been to provide greater transparency, clearer communication, and a consistent view into the SPFx roadmap. With this December 2025 update, we’re taking the opportunity not only to share the latest roadmap perspective, but also to look back on the collective progress we’ve made throughout the year. From continued platform stability and performance improvements to deeper engagement with the community, 2025 has reinforced SPFx as a foundational pillar of Microsoft 365 extensibility.

None of this progress would be possible without your feedback. Throughout the year, your real-world input has directly shaped our investment decisions – guiding where we refine existing capabilities, expand extensibility scenarios, and prioritize future innovation. We’re deeply grateful to our customers and partners who have actively participated in conversations, previews, and early validations, helping ensure SPFx continues to meet the needs of modern Microsoft 365 solutions.

Looking ahead, 2026 is shaping up to be an exciting year for SPFx. While much of the roadmap remains intentionally steady, we are preparing several meaningful enhancements and new capabilities that we look forward to announcing and sharing more broadly in early 2026. These upcoming investments will continue to focus on developer productivity, long-term sustainability, and enabling richer, more integrated experiences across Microsoft 365. As always, we’ll keep the public SPFx roadmap updated alongside these monthly posts as plans continue to evolve.

Thank you for being such a vital part of the SPFx journey and for making 2025 a year of incredible collaboration and success

Roadmap

We are evolving towards a quarterly release cycle, providing more predictability on new feature introductions and updates. We will update the public roadmap with any schedule and feature updates as we move forward in this journey.

Here is the set of investments which we are planning to ship within the upcoming SPFx releases:

Version 1.22 – December 2025

This version will provide us with a new modernized baseline which does not have any npm audit issues and has a future proven toolchain to continue building experiences.

• General availability is planned on December 2nd 2025
• Addressing npm audit reported security issues on the dependency tree.
• Transitioning from Gulp to an open webpack based toolchain orchestrated by Heft.
• Update default TypeScript to v5.8

January 2026 – debugging toolbar in SharePoint Online

This will be a server side update without a requirement to provide a client-side updates as new SPFx version.

• New debugging toolbar improving the in-page development experience when workbench is not used. Debugging toolbar will eventually replace the workbench page to enable you easily debug in any page in SharePoint Online.

Version 1.23 – February/March 2026

This release focuses on open sourcing the templates and tooling to create SPFx solutions, enabling our ecosystem to optionally build their own templates. We also want to focus on providing additional value for optimizing developer experience and providing new extensibility options.

• Open-sourcing SPFx solution templates via GitHub and opening them for community contributions.
• A new open-sourced SPFx CLI for replacing the existing Yeoman generator – You will be able to introduce your company specific templates or adjustments on the scaffolded baseline for the SPFx solutions. We are decoupling the CLI itself from the SPFx release versions.
• Command set improvements for lists and libraries – grouping and potentially other improvements.
• New and edit panel override in lists – support panel level override on the Microsoft Lists and SharePoint lists with SPFx.

Version 1.24 – May/June 2026

This version continues providing new extensibility options aligned with the future direction of SharePoint. We are also expecting to have other new features and capabilities as part of this release, which will be disclosed a bit later.

• Navigation customizers – Options to override navigation nodes and/or experiences with SPFx components.
• Other features will be shared later.

We also continue further innovation in the AI space with a focus on both customer features and developer tooling. More on this in future roadmap updates early 2026.

We encourage you to continue providing feedback to support our product planning for the upcoming semesters. We already have an extensive list of ideas and enhancements in mind but are always interested in your input.

What’s next?

We continue expanding the SharePoint platform to unlock more innovation across Microsoft 365:

• SharePoint Framework (SPFx) for building rich, AI powered and business integrated solutions with custom user interfaces directly in Microsoft 365.
• SharePoint Embedded to bring SharePoint content into your own apps hosted outside of Microsoft 365 with your own user interface.
• Agents and AI to create intelligent, adaptive experiences to access your content and business information efficiently and expose those easily for your end users.
• Microsoft Graph to access data and insights everywhere using our standard API surface.

We encourage you to explore these capabilities and see how they can help you build the next generation of solutions for your organization and customers.

If you are looking to build experiences for Microsoft 365, we strongly recommend joining our community calls and other Microsoft 365 & Power Platform Community activities covering Microsoft 365 Copilot, Power Platform, SharePoint, Microsoft Teams, Copilot Studio, Microsoft Graph, Microsoft Viva, and more. See community call details and other assets from https://aka.ms/community/home.

You might be also interested on our new SharePoint partner showcase series where we showcase different solutions build with SharePoint. Each episode has a video and blog post with further details. Are you building something with SharePoint and interested on doing a similar video with us? – Let us know by signing up with this form and we’ll get back to you for scheduling a recording.

We are also excited to share that we will be repeating the SharePoint Hackathon event during March 2026 (March 2-16) with updates submission categories, showcasing the different features and capabilities of SharePoint. We saw an impressive set of examples of ecosystem innovation across intelligent portals powered by AI and SPFx in 2025 and are looking forward on the community innovation with the new features and capabilities.

Follow us also on LinkedIn or in X to stay up to date on Microsoft 365 Platform announcements.

Got feedback or input on this blog post – leave a comment and we will get back to you.

Happy coding! Sharing is Caring!

The post SharePoint Framework (SPFx) roadmap update – December 2025 appeared first on Microsoft 365 Developer Blog.

What is Schema.org?

Why should Providers adopt Schema.org?

• Make your messages stand out: Highlight the most important information (e.g., delivery dates, check-in times) so users can see what matters at a glance.
• Enable connected workflows: When your data is structured, Outlook can power contextual workflows like calendar event creation, follow-up reminders, or status tracking.
• Improve discoverability: Structured emails are easier to search, classify, and act upon.
• Drive engagement: Partners who’ve adopted structured markups have seen up to 30% higher engagement rates.

Supported scenarios:

Get Started

<html>
   <body>
    <p>
      Dear Stuart, thanks for booking your flight with Scandinavian Airlines.
    </p>
    <p>
      <b>BOOKING DETAILS</b><br/>
      Passenger: STUARTMR TONGE<br/>
      Airline: Scandinavian Airlines (SK)<br/>
      Flight Number: SK532<br/>
      From: Heathrow Airport (LHR), Terminal 2<br/>
      To: Arlanda Airport (ARN), Terminal 5<br/>
      Departure: July 20, 2021 – 13:55 GMT<br/>
      Arrival: July 20, 2021 – 17:25 GMT<br/>
      Reservation Number: NFNEV5<br/>
      Status: Confirmed<br/>
    </p>
  </body>
</html>

<html>
  <head>
    <script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "FlightReservation",
"reservationId": "NFNEV5",
"reservationStatus": "ReservationConfirmed",
"underName": {
"@type": "Person",
"name": "Stuart Tonge"
},
"reservationFor": {
"@type": "Flight",
"flightNumber": "SK532",
"provider": {
"@type": "Airline",
"name": "Scandinavian Airlines",
"iataCode": "SK"
},
"departureAirport": {
"@type": "Airport",
"name": "Heathrow Airport",
"iataCode": "LHR"

},
"departureTime": "2021-07-20T13:55:00+00:00",
"arrivalAirport": {
"@type": "Airport",
"name": "Arlanda Airport",
"iataCode": "ARN"

},
"arrivalTime": "2021-07-20T17:25:00+00:00"
},
"reservedTicket": {
"@type": "Ticket",
"ticketedSeat": {
"@type": "Seat",
"seatNumber": null
}
}
}
</script>
  </head>
  <body>
    <p>
      Dear Stuart, thanks for booking your flight with Scandinavian Airlines.
    </p>
    <p>
      <b>BOOKING DETAILS</b><br/>
      Passenger: STUARTMR TONGE<br/>
      Airline: Scandinavian Airlines (SK)<br/>
      Flight Number: SK532<br/>
      From: Heathrow Airport (LHR), Terminal 2<br/>
      To: Arlanda Airport (ARN), Terminal 5<br/>
      Departure: July 20, 2021 – 13:55 GMT<br/>
      Arrival: July 20, 2021 – 17:25 GMT<br/>
      Reservation Number: NFNEV5<br/>
      Status: Confirmed<br/>
    </p>
  </body>
</html>

Partner With Us

The post Unlock your email potential with Schema.org appeared first on Microsoft 365 Developer Blog.

Declarative agents enable you to customize Microsoft 365 Copilot to help you meet the unique business needs of your users. With introduction of MCP support, it’s now much easier for developers to integrate their business workflows, SaaS, and LoB systems into Copilot via declarative agent.  

Let’s dive into how you can create your declarative agent using MCP server.  

Build your own MCP-based agent with Microsoft 365 Agents Toolkit

You can start building your own MCP-based declarative agent using the Microsoft 365 Agents Toolkit in Visual Studio Code. The toolkit provides a guided, simple yet powerful point-and-click experience to connect your agent to an MCP endpoint.  

To build an MCP-based agent: 

1. Scaffold a new agent: In Visual Studio Code, choose Microsoft 365 Agents Toolkit, and select Create a new Declarative Agent. This sets up the project structure and manifest files for your Copilot agent.  
2. Add the MCP action: Choose Add Action –> Start with an MCP server in the toolkit. You’re prompted to enter your MCP server URL (usually https://<your-server>/mcp). That’s all you need – the toolkit will fetch the server’s list and description of its tools and automatically generate a plugin spec from it.  
3. Choose your tools: If your MCP server exposes many functions, you can select a subset to include in your agent (for security or simplicity). The toolkit lets you pick which tools to import and tools names, parameters, and definitions are defined in the manifest.   
4. Configure authentication: If the MCP server requires auth (which most do), the toolkit walks you through adding credentials. Currently SSO and static OAuth 2.0 is supported by default.  
5. Generate & review: After you provide the configuration information, the Agents Toolkit generates all the files and scaffolding. It updates the app manifest manifest.json to list the plugin, fills in the ai-plugin.json with the MCP actions, and adds the action into declarativeAgent.json . Essentially, it writes the “wiring” for you – no manual JSON editing required. You can review these files to see the imported actions and make sure everything looks right. 
6. Test and publish: With everything set, you can run the agent locally (the toolkit has a one-click Provision and Start debugging feature that sideloads your agent for testing in the Microsoft 365 Copilot app). Because the toolkit took care of registration and auth, your agent can immediately call the MCP server’s tools in response to user prompts. 

Optionally, you can define response semantics in the form of Adaptive Cards and write agent descriptions to improve relevance as well as tool chaining. To learn more about response semantics, see Adaptive Card response templates.

These steps require little code writing or manual editing to get started. The heavy lifting – reading the MCP schema, creating function definitions, hooking up OAuth – is automated by the toolkit, with you in full control.   

Publish MCP-based declarative agents

When you’re ready, choose how you want to distribute your agent. You can either: 

• Distribute via Agent store: Submit the package in Partner Center and it will go through the validation process. When it’s approved, it’s published in the Copilot store. For more information, see Publish agents.
• Deploy in your organization: Your IT admin can deploy these agents to all employees or select employees based on use case. For more information, see Manage Copilot agents. 

IT admins can manage MCP-based agents just like REST API agents.  

Partners pioneering MCP-based agents

A number of partners have already embarked on a journey to build MCP-based declarative agents. These agents provide a glimpse of what’s possible.  

monday.com 

monday.com is a flexible WorkOS that teams use to plan, run, and track their work in one connected place. With the monday.com agent inside Copilot, teams deliver results across projects, marketing, sales, operations, and engineering, all through natural language, without switching tools. 

The agent enables: 

• Project setup that starts instantly: Use monday’s MCP-powered agent to create new boards the moment a project is named, complete with custom columns like status, owners, dates, and more. 

• Faster task workflows: Add items, assign work, update statuses, or adjust timelines directly through Copilot commands, keeping teams aligned and unblocking progress in real time. 

• Clear insights and more intelligent decisions: Pull summaries, activity logs, and item-level detail to understand progress and spot risks. For example: “Show me all the tasks in ‘Blocked’ and who owns them.” 

Get started with the monday.com agent in Copilot and bring AI-powered execution directly into your workflow.

Canva

Canva, the world’s all-in-one visual communication platform, is bringing its design tools into the flow of conversation in Copilot. This makes it seamless to create design content in context, via the Copilot agent. 

• Content generation: Generate presentations, social posts and more with Canva AI.
• Asset management: Browse, search. and summarize existing Canva designs and assets in Copilot.

Try the Canva agent in Copilot today.

Sitecore 

Sitecore empowers global marketing teams to launch high-impact campaigns and experiences, personalize content for any audience, and optimize every digital touchpoint – all powered by the Microsoft ecosystem. It recently integrated its Marketer MCP with Copilot to empower marketers with fast, intelligent access to take action within Microsoft 365. This means: 

• Unified workflows in one interface: Eliminate tool-switching by creating pages, localizing campaigns, personalizing experiences, and running tests all in one place. 

• Agentic marketing: Work directly in Copilot to drive campaigns and utilize agents to multiply marketing output. 

• Enterprise-ready foundation: Confidently scale marketing with security, reliability, and global reach. 

Looking ahead 

The introduction of MCP support, along with REST APIs and message extensions in declarative agents, is a significant milestone for Copilot extensibility. It combines the standardization and power of MCP with the user-friendly, declarative model of Copilot agents, giving developers the best of both worlds. We’re already seeing increased velocity in agent development and innovative scenarios from our preview partners, and we expect many more to emerge as MCP enters broader use. 

If you have an MCP server (or plan to create one), now is the time to build an agent and integrate it with Copilot. The barrier to entry has never been lower – you can easily plug your service into Copilot with just a URL and a few configuration settings. The Agents Toolkit walks you through it, and you can also find step-by-step guidance. Our goal is to make MCP integrations seamless and robust for both developers and users. 

Happy agent building, and as always, let us know your thoughts through feedback in Copilot or leave a comment on this post as you explore MCP-powered declarative agents! 

The post Build declarative agents for Microsoft 365 Copilot with MCP appeared first on Microsoft 365 Developer Blog.

Your input and feedback have been invaluable to define the key features for our releases, both current and future. Thank you

You can find the full list of released details from the following documentation:

• SharePoint Framework 1.22 release notes

Key features in the 1.22 release

Key changes and updates in this release are as follows:

• Transitioning from Gulp-based toolchain to Heft-based toolchain.
  • Starting with SPFx v1.22, new projects use Heft as the build task orchestrator instead of a gulp-based toolchain used in SPFx v1.0 – v1.21.1 releases. This change represents a fundamental shift in how SPFx projects are built, configured, and customized, though the underlying bundling technology (webpack) remains the same.
  • See more details from following documentation: SharePoint Framework Toolchain: Heft & Webpack.

• Addressing npm audit issues in Yeoman package and on scaffolded solutions.
  • Previous versions of SPFx had npm audit reported issues, which have been all addressed with the 1.22 release. We are also working on updating the deprecated packages in upcoming versions.

• Updating default TypeScript version for the scaffolded projects to TypeScript v5.8

and more

You can see a live demo of the Heft based toolchain changes from the recording of the weekly Microsoft 365 & Power Platform community call on 25th of November. Specific SPFx 1.22 Heft tooling focused demo starts at 34:42.

Everyone is welcome to these weekly calls to stay up to date on the Microsoft 365 & Power Platform topics. See details on the community calls from https://aka.ms/community/calls.

Installing SharePoint Framework 1.22 

You can install SharePoint Framework 1.22 by using the following command which will install always the latest generally available version.

npm install @microsoft/generator-sharepoint@latest --global

What’s SharePoint Framework?

The SharePoint Framework (SPFx) is the leading extensibility model for Microsoft 365, powering custom solutions used by tens of millions of users every month across Microsoft Teams, Microsoft Viva, and SharePoint. SPFx enables developers, partners, and organizations to deliver tailored, high-value experiences that integrate seamlessly with the Microsoft 365 platform.

Designed around modern web standards and built for Microsoft 365’s multi-host ecosystem, SPFx provides a streamlined way to create solutions that are secure, reliable, and reusable – maximizing your development investment and accelerating time-to-value.

Whether you’re generating your first project with the SPFx Yeoman Generator or using the SharePoint Framework Toolkit, SPFx offers a consistent, flexible path to build and ship solutions across Microsoft 365 without rewriting your code for each surface.

Key capabilities of the SharePoint Framework for Microsoft 365 are the following:

• Build once, run everywhere – Use the same component across SharePoint, Microsoft Teams, and Viva without modifying your code. This cross-platform capability reduces development overhead and ensures a unified experience for end users.
• Zero-maintenance, automatic hosting – SPFx solutions are automatically hosted in SharePoint, eliminating infrastructure management and reducing operational cost. You focus on innovation – Microsoft 365 handles the hosting without extra cost.
• Seamless, Built-in Single Sign-On (SSO) – SPFx provides automatic SSO across Microsoft 365 experiences. No extra consent prompts, no additional configuration, and no security overhead for end users or admins.
• Content-driven, intelligent applications – Surface Microsoft 365 data via Microsoft Graph or integrate external systems to create rich, context-aware applications tightly aligned with organizational content and workflows.
• Powered by industry-standard web development – Built on modern web technologies: Node.js, npm, TypeScript, and your preferred JavaScript framework. SPFx avoids proprietary tooling and enables broad skillset reuse.
• Centralized governance and administration – Administrators can manage SPFx solutions from a central, unified interface, enabling streamlined deployment, consistent governance, and secure permission approval across Microsoft 365. This ensures organizations maintain full control over what solutions run in their environment and the data they can access.
• Built for enterprise scale – SPFx aligns with Microsoft 365’s security, compliance, and lifecycle management standards, making it ideal for enterprise-grade and partner-delivered solutions.

Additional resources and support

• • Please report any issues or feedback using following issue list – https://aka.ms/spfx/issues
    • We have engineering people monitoring any incoming issues and helping you to get unblocked or getting your questions answered.
  • Overview documentation
  • Getting started documentation
  • Build for Microsoft Teams using SharePoint Framework
  • Overview of Viva Connections Extensibility
  • Microsoft Learn – Extend Microsoft Viva Connections
  • SharePoint Framework Toolkit
  • CLI for Microsoft 365 – SharePoint Framework Upgrade tooling from previous versions to latest
  • SharePoint Framework web part samples
  • Viva Connections samples

If you are looking to build experiences for Microsoft 365, we strongly recommend joining our community calls and other Microsoft 365 & Power Platform Community activities covering Microsoft 365 Copilot, SharePoint, Power Platform, Microsoft Teams, Power Apps, Microsoft Viva, and more… More details here https://aka.ms/community/home

And, follow us on LinkedIn or in X to stay up to date on Microsoft 365 Platform announcements.

Happy coding! Sharing is caring! 

The post General Availability of SharePoint Framework 1.22 – A Major Refresh of the Build & Tooling Experience appeared first on Microsoft 365 Developer Blog.