Gemma 4 is now significantly faster in Ollama 0.31 on Apple Silicon via multi-token prediction (MTP), powered by MLX. Performance is now up to 90% faster when used with coding agents, as measured using the Aider polyglot benchmark.

How to implement httpclient streaming in C# with .NET 10 -- covering HttpCompletionOption.ResponseHeadersRead, ReadAsStreamAsync, Server-Sent Events, progress tracking, and memory benchmarks.

June brings one of the most significant updates to SharePoint Framework in recent years with the introduction of SharePoint Copilot Apps. Where May was about reaching general availability of SPFx 1.23 and setting our foundation, June is about pointing that foundation at what comes next, and the headline is a big one. We are thrilled to celebrate the announcement of the upcoming SharePoint Copilot Apps, a new chapter that brings AI-first, Copilot-connected experiences to the model millions of you already build on every day. Alongside that, we shipped SPFx 1.23.2, a focused quality release that strengthens the platform and gets us ready for the new and edit panel override capability.

This continues to be a community-driven journey. The momentum we saw through the spring, at events, in open source, and in the steady stream of feedback you share, is exactly what shapes the direction we’re announcing now. Whether you filed an issue, contributed a fix, joined a community call, or told us what you wished SPFx could do, your input is in this release and in the roadmap ahead.

Announcing SharePoint Copilot Apps

The biggest news this month is the announcement of SharePoint Copilot Apps, our vision for how developers will build intelligent, Copilot-connected experiences directly on the SharePoint platform. This is the natural evolution of everything we’ve been signaling over the past several updates around AI and Copilot, now taking concrete shape.

SharePoint Copilot Apps are designed to let you:

• Build solutions that are Copilot-ready by default, surfacing your data and actions to Microsoft 365 Copilot
• Reuse your existing SPFx skills, tooling, and investments to reach AI-powered scenarios faster
• Connect business data and user experiences into intelligent workflows across SharePoint, Teams, and Viva
• Extend the reach of your apps into the places where users already work, with Copilot as a first-class surface

Note: “SharePoint Copilot Apps” is the working name during public preview and may change before general availability.

We are looking forward to hearing your feedback as the preview becomes available. Early community input will help shape both the developer experience and the roadmap toward general availability.

Here’s a quick introduction video on the art of possible with the upcoming SharePoint Copilot Apps – My Day is an example scenario on what could be created.

We will be starting public preview of SharePoint Copilot Apps in July 2026 with target to ship the feature generally available later 2026. You can see more details on the upcoming preview from following assets:

• Going beyond text in Microsoft 365 Copilot – Introducing SharePoint Copilot Apps – blog post
• Introducing SharePoint Copilot Apps – Going beyond text in Microsoft 365 Copilot – video
• Introduction to SharePoint Copilot Apps developer experience – video
• Build UX components for your Copilot agent – My Day scenario – SharePoint Copilot Apps – video

SharePoint Framework 1.23.2 is now available

Building on the 1.23 general availability milestone, we’ve shipped SPFx 1.23.2. This is a deliberately focused release centered on quality, reliability, and getting the platform ready for the next set of extensibility capabilities.

Highlights of this release include:

• Issue fixing and platform quality, addressing a set of reported issues to keep solutions stable at enterprise scale
• Readiness for new and edit panel override, groundwork that prepares the platform for overriding the new and edit panels in lists and libraries, a capability we’re bringing online in an upcoming release
• Security and dependency hygiene, addressing npm audit vulnerability issues to keep your build pipelines clean

See details on the 1.23.2 release on the release notes:

• SharePoint Framework 1.23.2 release candidate release notes

While 1.23.2 focuses on quality and reliability, it also lays the groundwork for upcoming capabilities such as SharePoint Copilot Apps and list and library panel customization. It ensures that as we light up Copilot Apps and panel override, you’re building on a dependable base.

Looking ahead – AI, Copilot and upcoming investments

With SharePoint Copilot Apps now announced, our investments are more clearly focused than ever on enabling AI-powered solutions and intelligent experiences across Microsoft 365. The early signals we shared in April and May are now becoming real direction.

Our roadmap investments remain focused on:

• Enabling developers to build Copilot-ready and AI-enhanced applications
• Simplifying how solutions integrate with Microsoft 365 data and services
• Providing more flexible and modern tooling to accelerate development
• Expanding real-world business scenarios through extensibility

We are evolving SPFx not only as a development model, but as a key foundation for building intelligent, enterprise-ready solutions for the AI era. SharePoint Copilot Apps is the clearest expression yet of that direction, and more details on how the pieces connect will follow as we move capabilities closer to public preview.

Thank you for your feedback – Spring 2026 survey

Our Spring 2026 feedback survey closed in early June, and we want to thank everyone who took the time to respond. Your input directly informs the priorities you see in this update, including how we’re sequencing quality work with future releases and the direction behind SharePoint Copilot Apps.

Remember, feedback is always open. If something works well, tell us. If something doesn’t, tell us. If you have ideas on what should come next, we want to hear them.

Roadmap

We are continuing to evolve towards a more predictable, quarterly-oriented release cycle, and we’ll keep the public roadmap updated as schedules and features firm up. Here is the current set of investments planned for upcoming SPFx releases:

Version 1.23.2 – June 2026 (shipped)

• Issue fixing and platform quality improvements
• Readiness for new and edit panel override support for lists and libraries (server side support coming in July)
• Addressing any new npm audit vulnerability issues

Version 1.24 Public Preview – July 2026

• SharePoint Copilot Apps public preview
• Addressing any new npm audit vulnerability issues

Version 1.24 General Availability – September 2026

• SharePoint Copilot Apps general availability
• SPFx CLI general availability (GA) – Includes updated open-source templates
• Navigation customizers, options to override navigation nodes and/or experiences with SPFx components
• Addressing any new npm audit vulnerability issues

Top of mind

These are features that are top of mind and which we want to address as soon as possible.

• React 18 support for SPFx solutions. Work continues on updating the out-of-the-box web parts to the React 18 level. We can enable it broadly only once that work is complete; until then it applies to custom web parts. Based on current progress internally, we should be getting this support by the General Availability of SharePoint Framework 1.24.

We encourage you to keep sharing feedback to support our planning for the upcoming semesters. We already have an extensive list of ideas and enhancements in mind, and we’re 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, now including SharePoint Copilot Apps.
• 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 that access your content and business information efficiently and expose them easily to your end users.

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’re planning to build experiences for Copilot, Microsoft 365 & Power Platform, we strongly recommend joining our community calls and the broader Microsoft 365 and Power Platform Community activities, covering Microsoft 365 Copilot, Power Platform, SharePoint, Microsoft Teams, Copilot Studio, Microsoft Graph, Microsoft Viva, and more. You can find call details and community assets at https://aka.ms/community/home.

You might also be interested in our SharePoint partner showcase series, where we highlight solutions built with SharePoint. Each episode includes a video and a blog post with additional details. If you’re building something with SharePoint and would like to be featured, let us know through the sign-up form and we’ll contact you to schedule a recording.

Follow us on LinkedIn or X to stay up to date on Copilot, Microsoft 365 & Power Platform announcements.

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

As many of us head into the summer season, we’ll skip the end of July roadmap update and return at the end of August. In the meantime, please continue sharing feedback through GitHub, community calls, and social media.

Happy coding! Sharing is Caring! 

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

Aspire Roadmap (2026 → 2027)

Hi everyone 💫

What a year! Since last July, 128 of you merged 3,191 pull requests, closed 2,277 issues, shipped 31 releases, and pushed Aspire past 6k ⭐stars⭐ on GitHub — shipping most of the vision we wrote down along the way: TypeScript AppHost, aspire publish, and aspire deploy all hit GA, Kubernetes/AKS deployment matured, and aspire agent + skills brought agentic workflows in the box. Thank you — for every issue, PR, stream, and bug report. 💜 (The Q2 2026 update recaps it all.)

Last year, the story was simple: Aspire is for any app in any language. This year, the story is about depth, not breadth. The apps you're building are bigger and more serious, and the way you build them has changed. Last year, AI was "spicy autocomplete". Now, agents are writing most of our code, CI/CD and infra demands have exploded, and your everyday loop has changed fundamentally. This year is about making Aspire ready for real distributed apps, and for the agents building them alongside you.

So, this year, three focus areas guide us there:

• 🔗 Agent-ready — Aspire is built for the agentic era: build agents and agentic workflows, use agents inside your dev/test loop, and make your app something agents can run, inspect, and reason about.
• 🏗️ Scales with your team — Aspire scales to real distributed apps: big graphs, many repos, serious testing, and production deployment.
• ⚙️ Built to ship — We're investing in our own foundations — releases, CI, and infrastructure — so Aspire reaches you faster, more reliably, and with higher quality.

⚠️ Disclaimer: This roadmap is directional, not a commitment. It reflects our current thinking and areas of active exploration, but plans may evolve as priorities shift, feedback is incorporated, or technical constraints emerge.

🧑‍💻 Local Developer Experience

This is where we start. Aspire already orchestrates big, real distributed apps — this year we refine that experience until the size of your system stops being something you feel, iterating on a large app as fast as a single project, for you and the agents working alongside you.

• Start only what you need — Launch groups bring up just the slice of the system you're working on.
• Change your app host without restarting — Reload AppHost changes live, so edits to your app model take effect without a full restart.
• Stop waiting on builds — Project Resource v2 moves .NET build coordination into the AppHost runtime, so the host starts without waiting on every project.
• One app across many repos — Multi-repo support composes an app spanning repositories and orchestrates multiple app hosts.
• Run on more container runtimes — Debug against the runtimes you actually use, including WSL containers on Windows and Apple's container framework.
• History that survives restarts — Dashboard state and telemetry persist across restarts and crashes, so you keep your loop's history.
• A CLI that feels fast — Performance work across the CLI you notice day to day.
• Agents work where you work — Go beyond logs and telemetry, giving an agent working through Aspire deeper debugging context from your running app.

🧪 Testing

Testing is the biggest gap left from last year's roadmap, and this year it's a priority. What we hear most — especially from teams onboarding large internal services — is the cold-start cost of booting the whole app just to run one test. The goal is simple: testing a distributed app should feel as fast and focused as testing a single piece of it.

• Run only what a test needs — Start just the slice of the app graph a test touches instead of booting the whole thing, via launch groups / conditional startup.
• Testing support for all languages — Bring end to end tests to all languages in a first-class way.
• Less waiting before tests start — Project Resource v2's build-coordination work cuts the wait before a test AppHost is ready.
• Real or mocked dependencies, ready fast — Stand up real or stubbed container dependencies that are easy to author and quick to run, with better reuse across runs.
• Watch tests as they run — A live dashboard shows service behavior in real time while your tests execute.
• Debug CI failures locally — Capture dashboard state from a CI run and replay it on your machine to find what broke.
• Coverage in your pipeline — Collect and report code coverage as part of the test run.

🌐 Polyglot

Polyglot is the baseline now — and agents make it matter more than ever. With an agent in your loop, you can reach for the right language for the job, not just the one your team already knows. This year, we widen the circle and deepen what's already there.

• More languages, first-class — First-class app-host authoring expands beyond C# and TypeScript to Python and Go.
• Rust goes first-party — Rust app host support graduates from the Community Toolkit into the first-party repo, shipped and supported like the rest.
• Samples that teach humans and agents — More quickstarts and end-to-end samples in every language, rich enough to give agents the guidance they need on typed config, connection wiring, and telemetry — the role client integrations used to play.
• Write integrations in any language — Use any language to author Aspire integrations for hosting your own services, containers, and other resources.

🛠 Tooling & Extensibility

Aspire is more powerful when others can build on it. This year we open up the CLI, the editor, and the integration ecosystem — for the community, for partners, and for the agents working through Aspire.

• Build on the platform — Extension points to let the community extend the Aspire Dashboard, CLI and VS Code experience, not just use them.
• Integrations beyond the box — Discover and add third-party integrations from the CLI with custom feeds, so the ecosystem isn't limited to the built-in Aspire.Hosting.* packages.

🔌 Integrations (incl. Hosting & Auth)

Aspire's integration catalog is how your app connects to the services it relies on — and that includes hosting and authentication, which live here alongside everything else. This year we keep growing the catalog and strengthen the integrations teams lean on most.

• First-class Entra ID — Stronger, built-in support for authenticating with Microsoft Entra ID.
• Bring your own auth with Keycloak — Continued support for Keycloak as an auth provider.
• A growing catalog — More integrations across the board, including new data integrations like Horizon DB.

🤖 AI Apps

Aspire isn't just agent-ready — it's where you build and ship the AI apps themselves: agent-based apps, the models behind them, and the services around them, deployed to platforms like Foundry.

• Build agent-based apps — A first-class environment for composing agent apps and the models, services, and data they depend on, with templates and command integrations to scaffold common scenarios fast.
• Host and deploy to Foundry — First-class hosting for models and agents, deployed to Azure AI Foundry alongside the rest of your app.
• Aspire in the Copilot canvas — Bring the Aspire app model into GitHub Copilot's app canvas.

🚀 Deployment

Deployment grew up this past year — aspire publish and aspire deploy are GA, Docker Compose is stable, and Kubernetes deployment advanced fast. This year is about making deployment real-app-ready: production-grade, repeatable, and wired into the pipelines teams already run.

• Pipelines that live with your app — Generate GitHub Actions and Azure DevOps pipelines straight from your app host, so your deployment definition travels with your app model.
• Every target, production-solid — Take the targets that shipped — Docker Compose, cloud-agnostic Kubernetes, Azure (App Service, Container Apps, etc) and AWS — to consistent, GA-level quality for real workloads, with Kubernetes in particular as a focus. We're also ready to tackle Terraform and exploring GCP to widen the map further.
• Real dev/stage/prod environments — Mature environment modeling with environment-scoped config, secrets, and outputs.

⚙️ Infra

Some of the most important work this year is on our side of the repo — the pipelines, tests, and infrastructure that get Aspire into your hands. The goal is simple: ship Aspire faster, more reliably, and with higher quality, release after release.

• Greener builds — Harden our build and test infrastructure so CI is trustworthy, flaky tests get squeezed out, and both team and community PRs can merge with confidence.
• One command away, everywhere — Keep Aspire a single command to install across NuGet, npm, Homebrew, and WinGet, with automated, readable release notes every time.
• Seamless updates — Move cleanly between channels (daily builds for the bleeding edge, stable for production, and PR builds for specific testing).
• Use Aspire to influence Aspire — Take the learnings we have from building, shipping, and delivering Aspire, and use those to shape new features and experiences for you!

📚 Content & Community

• aspire.dev — Official docs, samples, and walkthroughs.
• YouTube — Demos, deep dives, and livestream replays.
• Aspire Conf 2026 — Catch every session on the Aspire Conf playlist.
• Follow along — Bluesky · X · Twitch · Discord

---

That's the year ahead: agent-ready, scaling with your team, and built to ship. Three bets, one goal — Aspire for any app, in any language, from your first line of code to production. Strong defaults, polyglot by default, and built-in awareness of your infrastructure and runtime stay at the heart of it.

We plan in the open and keep adjusting as we learn from you. If you want to talk through any of it — or just say hi 👋 — come find us in the Aspire Discord. See you there!

— @joperezr, @maddymontaquila, @davidfowl, and the Aspire team

2026-06-30

• Disabling the sandbox for the rest of the session now takes effect immediately, so shell and search commands stop re-prompting to bypass it mid-turn
• Subagent sessions keep parent tool restrictions
• Show warnings and errors when host custom agents fail to load
• Require session limits to be at least 30 AI credits
• Add Claude Sonnet 5 as a supported model
• Allow tool calls to continue when hooks time out
• Ctrl+Q now enqueues the highlighted slash-command argument completion
• MCP OAuth against Microsoft Entra servers behind a tenant vanity domain (e.g. Copilot Studio) no longer fails to refresh or re-authenticate (AADSTS9010010 / AADSTS90023)
• Prompt mode exit summary shows a resume hint to continue the session

After publicly touting pull request limits as a way to cut maintainer noise, GitHub is taking the same idea further with a new setting that lets repository admins restrict issue creation to collaborators only.