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

This week:

Deprecation notice: Teams Live Events meeting creation via Microsoft Graph

Mastering User Settings in SharePoint Framework

Navigating Microsoft Teams Docs: A Developer Survival Guide

You can also listen to the audio-only podcast: Thoughtstuff Podcast – Tom Morgan on Teams Dev: Weekly Update 9 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 and had a great week. A couple of things to talk through this time.

Microsoft Graph Deprecation: Live Events

I’m going to spend some time on this first item. It’s a deprecation notice about creating Microsoft Teams Live Events meetings via Microsoft Graph. This functionality has been around for a few years — enabling the creation of live meetings through the API. However, it’s changing because Live Events are being retired in favor of virtual events.

Specifically, the isBroadcast property used when creating an online meeting is being deprecated. Going forward, setting this property to true won’t be allowed. Instead, users should look to use webinars or town halls, both of which now have API support.

On the surface, this change seems manageable. But my concern is about the short window in which this update is occurring. Microsoft announced this change via a blog post on February 3rd. The beta endpoint will stop supporting the property at the end of March — which is fair given beta is inherently unstable. But more concerning is that the V1 endpoint will see the same change by the end of June — just five months later, and only three months after the beta cut-off.

This feels very short notice considering v1 APIs are supposed to be stable. There are clauses in the terms that mention a two-year window for changes — something we’ve not seen honored consistently. While Microsoft likely has the telemetry to understand usage patterns, from a developer perspective, this kind of short-notice change is disruptive, especially when running production services or software that depends on it.

Storing User Settings via Microsoft Graph

On a more positive note, Paolo Pialorsi — an ex-MVP now at Microsoft — has written an excellent blog post on mastering user settings in the SharePoint Framework (SPFX).

He proposes an approach that makes use of Microsoft Graph and OneDrive for Business to persist application-specific settings per user. This was new to me — I would typically have reached for my own data store or a configuration file. But for SPFX or Teams-based solutions, storing this in app-specific folders via Graph is elegant and scalable.

Every user gets an app-specific folder structure as part of their OneDrive, and app developers can use this space to write and retrieve settings. It also ensures per-application isolation, aligns well with Azure AD registered applications, and behaves much like managing settings on local drives.

Paolo’s post walks through the exact steps to implement this setup, how to handle permissions, and how to structure and retrieve settings. The approach is robust and applicable beyond SPFX — definitely worth a read if you’re building anything accessing Microsoft Graph.

Navigating Teams Documentation: A Developer’s Survival Guide

Lastly, a pick that made me smile — Andrew Connell’s blog post titled “Navigating Microsoft Teams Docs: A Developer Survival Guide.”

He discusses the various challenges developers face finding accurate information in Microsoft documentation. While everything is somewhere in the docs — finding it can feel like an archaeological dig. You almost need to know the age of the Teams feature to figure out where to start looking.

He highlights problems like outdated recommendations, overlapping SDKs, and fragmented documentation across platforms — with some hosted on Learn, others as GitHub entries or blog posts.

Andrew lays out the issues clearly and provides useful strategies for navigating the mess. It’s a good reminder that this struggle is shared and that there are ways to get better at coping with it — trial, error, and experience go a long way in building your own toolkit for success.

That’s it from me this week. Whatever you’re working on — have a great week, and I’ll speak to you again next time.