Post 4 covered upgrade.md as it exists today. This companion post proposes four concrete, testable extensions — an explicit rollback path when a report can't be fully applied, an incremental strategy for multi-major-version jumps, running the existing test suite as part of verification, and machine-readable JSON output for agent-driven diffing — each framed as a future contribution to SharePoint/spfx-dev-skills, not a criticism of it.
SPFx Can’t Hold Application Permissions — Here’s Exactly Which Copilot APIs That Rules Out, and the SharePoint Copilot Apps Preview That Bridges the Gap
SPFx can call Microsoft Graph, but it can never hold an application permission — a structural fact of the browser execution model that quietly rules out several Microsoft 365 Copilot APIs no matter how the manifest is configured. This post traces the exact rule API by API, shows the documented AadHttpClient-to-backend pattern for everything SPFx can't reach directly, and evaluates SharePoint Copilot Apps — Microsoft's own preview answer to packaging SPFx with Copilot — as the series closes with a design-review checklist and the complete 13-post map.
The Upgrade Playbook: How AI Agents Should (and Shouldn’t) Touch Your SPFx Version
Scaffolding fails safe — a bad attempt just gets deleted. An upgrade runs against a project that already works, so the cost of getting it wrong is much higher. This post walks the spfx-dev-skills upgrade.md reference end to end: the clean-git-state precondition, version detection via .yo-rc.json, the exact m365 spfx project upgrade commands, applying the report in order without overwriting customizations, and the build-clean bar for calling an upgrade done.
Microsoft Copilot Studio Agents: “Actions” Is Now “Tools,” MCP Has Been GA for Over a Year, and Org-Wide Publishing Requires Admin Approval
Microsoft Copilot Studio is one product with two licensing tiers — and the Agent Registry approval step that makes an agent visible org-wide is the step most publishing tutorials end one screen before. This post maps the complete authoring surface: all eight knowledge source types with their verified limits, the "Actions" to "Tools" terminology rename and what changed, MCP integration confirmed GA since May 2025 with the federated-connector distinction explained, and the five-step publishing path to Microsoft 365 Copilot including the admin center approval step makers most often miss.
Four Ways We’d Extend SPFx Scaffolding (And the Exact Commands to Test)
Post 2 covered create.md as it exists today. This companion post proposes four concrete, testable extensions — scaffold commands for Library and Adaptive Card Extension, a workflow for adding components to an existing solution, the --sharepoint-version flag for on-premises targets, and a post-scaffold validation/commit step — each framed as a future contribution to SharePoint/spfx-dev-skills, not a criticism of it.
Stop Letting AI Hang on yo @microsoft/sharepoint: Non-Interactive SPFx Scaffolding
Interactive Yeoman prompts are invisible to AI coding agents — they hang, or worse, pick the wrong menu item. This post walks the official spfx-dev-skills create.md reference line by line: environment checks with m365 spfx doctor, the fully flag-based scaffold command for web parts and extensions, dependency install discipline, and toolchain-aware packaging for Heft vs. gulp.
Declarative Agents vs. Custom Engine Agents: One Needs a Copilot License, One Doesn’t — and Copilot Studio Builds Both
Declarative agents run on Microsoft's orchestrator and require a Microsoft 365 Copilot license for every user — but cost nothing to host. Custom engine agents require you to supply the orchestration layer and pay for hosting — but your users need no Copilot license at all. This post explains the architectural split behind that licensing inversion, shows how to read either agent type from the app manifest, resolves the Copilot Studio taxonomy confusion (Agent Builder always produces declarative agents; the full platform can produce either), and provides a verified decision framework — including three binary differentiators and an eight-question pre-commit checklist — sourced from the official Microsoft 365 extensibility documentation updated August 2026.
Your AI Coding Agent Doesn’t Know SPFx — Here’s the Skill Pack That Fixes It
AI coding agents hang on interactive Yeoman prompts, invent package versions, and hand-roll UI instead of using Fluent UI — because generic training data doesn't know SharePoint Framework's narrow conventions. SharePoint/spfx-dev-skills is an official agent skill pack that fixes this: this post breaks down what it is, how it's structured, and two rules worth adopting today even without an AI agent.
Microsoft 365 Copilot Connectors: Two Connector Types, Three Mandatory Labels, and the One Admin Step Most Deployments Miss
Microsoft 365 Copilot connectors come in two architecturally distinct types — synced connectors that index a copy of external content into the Microsoft 365 semantic index, and federated connectors that fetch data live via MCP at query time — and custom connectors can only be built for the synced type. This post covers the four-step custom connector build lifecycle, the three mandatory semantic labels (iconUrl, title, url) that gate Copilot surfacing, the admin inline-results step that most deployments miss, the licensing table that determines which experiences your tenant can actually use, and a seven-point pre-go-live checklist that catches silent failures before they reach production.
The Future of SPFx Scaffolding: Roadmap, GA Timeline, and What’s Coming Next
`@microsoft/spfx-cli` is targeting GA around September 2026 — though as of this writing that date looks increasingly likely to slip, and Microsoft's own sources disagree on whether it ships with SPFx 1.24 or 1.25. After GA, the Yeoman generator receives its final update. This post covers the Phase 2 and 3 roadmap, the MCP server front-end for AI-assisted scaffolding, and how SPFx developers can prepare today.