Weekly Update 2 February 2026 – SPFx Update, User Config API, Channel Apps update, Dev Proxy v2.1

This week:

SharePoint Framework (SPFx) roadmap update – January 2026

Introducing the Microsoft Graph User Configuration API (preview)

Apps for shared and private channels

Dev Proxy v2.1 with configuration hot reload and stdio proxying

You can also listen to the audio-only podcast version: Thoughtstuff Podcast – Tom Morgan on Teams Dev: Weekly Update 2 February 2026.

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. A couple more things to talk about this week.

It might be that the Microsoft engine is finally getting off the ground – just a slow start. It does seem a bit slower than usual, but we’re returning to a more normal cadence of posting. It’s nice to start seeing posts appear consistently in the places you’d expect them.

First up, on the Microsoft 365 Developer Blog, there’s an update to the SharePoint Framework (SPFx) courtesy of a blog post from Vesa Juvonen. It’s similar to last month’s update, but focused on January delivery. The standout for me is how the team actually delivered what they said they would. That consistency gives me confidence, not just in the team, but for everyone relying on SPFx. There’s evidence of ongoing investment and momentum behind the technology.

The main point of the January update is the new debug toolbar, which the December roadmap said would be delivered. It’s now part of the January blog post, confirming that work has been completed. The roadmap itself hasn’t significantly changed—so everything seems to be on track.

This kind of transparency isn’t for pointing fingers if delays happen, it’s really about communication. And Microsoft is showing they’re still committed to SPFx and haven’t moved on from it. The team is clearly funded and supported. Overall, that’s a really positive outcome.

Now, another interesting development – Microsoft Graph has new beta endpoints for user configuration, specifically focused on Exchange Online items. This effort is clearly part of the transition away from Exchange Web Access (EWA), which has been prolonged. Despite initial plans, Microsoft is now firm about deprecating it, even setting a hard stop date and warning tenants accordingly.

One difficulty with transitioning off EWA was that Graph didn’t previously offer comparable functionality. That gap made it impossible for developers to switch over. These new APIs aim to fix that. The Microsoft Graph userConfiguration API (in beta for now) allows storing configuration data per mail folder, which includes read, write, update, and delete operations.

It’s meant to do what it says: store metadata alongside mailbox context. I haven’t used it yet, but it looks like a straightforward CRUD interface. For those holding off migration due to missing features, this could be the green light you were waiting on. Yes, it’s in beta, but I expect a speedy general availability (GA) rollout to match the EWA deprecation deadline. If you try it and run into issues—report them. Microsoft wants feedback since this directly affects the deprecation timeline.

Moving on – another important update in Microsoft Teams: support for apps in shared and private channels. This has long been a pain point. For a while, apps were only supported in public and group scopes, but Microsoft has been closing those feature gaps. As of now, apps in shared channels are GA. Apps in private channels are in public developer preview—a big step forward!

There are still a few gotchas outlined in the updated blog post, so take the time to read through the capability matrix. Pay special attention to any highlighted limitations, especially if you’re building complex scenarios.

Lastly, Dev Proxy is reaching new heights with version 2.1.0. Quality-of-life improvements like configuration hot reload are great, but the headliner is STDIO proxying—that’s standard input/output. This means Dev Proxy can be used with MCP servers too, not just web traffic. It greatly expands its usefulness, especially as many developers shift towards MCP-based infrastructure.

The release includes the ability to wrap executables with the proxy and surface traffic in the network tab. You can also run multiple Dev Proxy instances and configure different ports. These updates demonstrate that the Dev Proxy team is being proactive, keeping the tool relevant and highly useful for developers. High marks all around.

That’s all from me this week. Have a great week ahead, and I’ll catch you next time!