AI and the SharePoint Developer: A Field Guide for the Next Two Years

I founded the SharePoint Developer Network LinkedIn group years ago, and it grew past fourteen thousand members. Membership requests used to arrive in clusters — people switching firms, juniors getting their first SPFx engagement, the occasional new MVP. I could roughly predict the rhythm of the SharePoint developer world from the inbox.

That rhythm has slowed. Significantly. Over the last eighteen months the requests have thinned to a trickle. The new members are still good people; there's no quality drop. There are just markedly fewer of them.

A LinkedIn group is a lagging indicator. By the time the requests slow, the underlying shift has already happened.

This is not a piece about AI eating jobs. It's a piece about which SharePoint developer roles compound under AI and which ones get hollowed out. The answer is uncomfortable, but it's actionable, and that combination is the only kind of answer I find useful.

The signal beyond my inbox

A few markers worth tracking. None of them prove anything alone, but they rhyme:

• Hiring posts have shifted from SPFx developer toward M365 platform developer or Copilot solution architect. Different scope, different rate, different career trajectory.
• PnP community commit cadence is healthy on the Graph and Copilot extensibility side and noticeably slower on the SPFx-specific tooling side.
• Microsoft's own conference content has rebalanced from "build a web part" toward "build a declarative agent."
• The certification roadmap has reweighted toward Power Platform and Copilot fundamentals. SPFx is still there. It's not the headline anymore.

Each of those is plausibly explainable in isolation. Together they describe a single reallocation: Microsoft's investment center of gravity inside its developer ecosystem has moved, and the platform's external community is repricing accordingly.

What's actually changing under SPFx

SPFx isn't being deprecated. That isn't the issue. The issue is that the surrounding investment landscape has rotated:

• Declarative agents are the front-of-house extensibility model for Copilot now. TypeSpec-defined, manifest-driven, surfaced inside Microsoft 365 Copilot. This is where the platform team is putting its energy.
• SharePoint Embedded has reframed SharePoint as a developer-addressable content fabric for ISVs, not just a workload. New surface, new audience, different conversation with the customer.
• Graph-first patterns dominate the integration story. SPFx web parts that consume Graph endpoints are fine. SPFx web parts that wrap legacy CSOM are technical debt accruing interest.
• Power Platform has absorbed the CRUD tier. The "build a list and a form on top of it" engagement that used to be a five-day SPFx job is now a two-hour Power Apps build, and your clients know this.
• Copilot Studio sits between Power Platform and pro-code, and is increasingly where business stakeholders prototype before the dev team ever sees the requirement.

SPFx is now one entry in a much wider menu, and it's no longer the default entry. A developer who only does SPFx is a developer who only addresses one of the five active surfaces above. Pricing follows scope. Scope, here, has narrowed.

Why general AI tooling doesn't quietly fix this

The optimistic framing — use Copilot or Cursor and your SPFx productivity goes up 3x — does not survive contact with enterprise SharePoint.

Try it. Ask any general-purpose AI coding assistant to generate a column definition with a specific lookup target. Or a permission grant against a specific scope. Or a content type reference. Or a search schema mapping. You will get plausible-looking output that is subtly wrong about field internal names, column types, permission scopes, tenant configuration, or all four at once.

The reason is structural. LLMs are trained on text. SharePoint domain semantics are typed. The model knows what SharePoint code looks like. It does not enforce what SharePoint code is. In an enterprise tenant with real governance rules, the difference between looks-like and is shows up as a production outage, an audit finding, or a compliance violation that lands in someone's quarterly review.

Net effect: AI-assisted SPFx, today, increases output volume without increasing trustworthy output volume. The senior developer's job has shifted toward reviewing AI output instead of writing it — which feels productive but compresses the rate the work commands. You spend the same hours, you bill the same hours, the deliverable is the same shape. Only the AI vendor captures the productivity gain.

The two careers that survive

In every platform transition I've watched (and I've watched several), the same pattern holds: the middle hollows out and both ends of the skill curve get more valuable. Here, the two ends are these.

1. The compliance / governance specialist

eDiscovery, records management, retention, regulatory constraints, sensitivity labels, audit trails. The work where "AI generated this" is not an acceptable answer to a regulator and a human in the loop is mandatory by law, not by preference. This corner of SharePoint development is structurally protected: the more AI is used elsewhere, the more demand grows for people who can certify what was used, where, and under what controls.

If you've been building eDiscovery automation, retention workflows, or M365 compliance tooling, this is your moat. Don't leave it. The market is going to need more of you, not fewer, and your work resists the rate compression hitting the rest of the platform.

2. The intent architect

The developer who has stopped writing code and started specifying what the system should do at a level above the code. Think: defining a domain-specific representation of a SharePoint solution — content types, permissions, workflows, integrations — and orchestrating agents that materialize the representation into running code, under typed constraints.

This isn't speculative. It's where the skill stack of a senior SharePoint developer (deep domain knowledge, governance instincts, typed thinking from years of CSOM, CAML, and PnP) has more leverage than any AI tool has on its own. The senior developer's accumulated mental model of "what a correct SharePoint solution looks like at scale" is exactly the constraint set that general-purpose LLMs are missing.

What dies in the middle

The pure component scaffolder. The developer whose value proposition was "I can build this SPFx web part faster than you can." That role is being repriced toward zero, because Copilot can scaffold the same web part in ninety seconds and Power Apps can replace the requirement entirely. The remaining work — making the web part actually correct in the tenant's specific governance context — is the intent-architect work, not the scaffolding work.

This is the uncomfortable part. If your billable identity is "I write SPFx," the runway is shorter than it feels. Not gone — shorter.

A 24-month preparation map

If the analysis is right, the preparation is concrete. In rough order:

1. Declarative-agent fluency. Learn TypeSpec, the manifest model, the Copilot extensibility surface. This is where Microsoft is investing. It will be the most-asked-for new skill in M365 hiring through 2027.
2. Graph-first refactor habit. When you touch SPFx, push every integration through Graph rather than legacy patterns. Future-proofs the work; aligns with the rest of the M365 dev surface.
3. SharePoint Embedded literacy. Even if you don't ship an SE app this year, understand the model. It changes how clients will think about SharePoint as a developer platform over the next three years, and the conversations shift accordingly.
4. Agent orchestration patterns. Not "how to write a prompt" — that was a 2024 skill. The 2026+ skill is decomposing a business intent into agent steps with typed boundaries and verifiable outputs. Senior judgment compounds here in a way it never did in pure prompt engineering.
5. DSL / grammar thinking. The most durable hedge against UI-frame churn is the ability to express a solution in a form that survives a UI change. Whether you adopt Langium, TypeSpec, or roll your own, the meta-skill is separating intent from implementation. Once you have it, you stop being held hostage by whichever framework Microsoft is excited about this month.
6. A vocabulary upgrade. "I built a SharePoint solution" is a 2018 sentence. I designed an intent layer that orchestrates declarative agents under tenant-specific governance constraints describes the same work in 2026 terms and prices accordingly. The work doesn't have to change; the description has to.

None of this requires abandoning the SharePoint expertise you've built. All of it requires using it differently.

What "developer" means in this stack now

The category has shifted under us. A SharePoint developer in 2027 isn't someone who writes SPFx components by hand. They're someone who:

• Specifies intent in a domain language the customer can read.
• Owns the semantic guardrails the AI agents operate within.
• Verifies the output against governance, compliance, and tenant constraints.
• Ships less code and more correctness.

The agents become executors. The humans become architects of the constraint system the executors run inside. That's not a downgrade. For senior developers it's a promotion that happens to be mandatory.

The only career-ending move

The only career-ending move I see, from where I sit, is treating SPFx as an identity rather than a tool. The skills compound — the type-thinking, the governance instincts, the domain depth — if you let them. They evaporate if you bind them to a single technology that's now one of five surfaces and not the most-funded one.

For what it's worth, I've been building tooling specifically for this transition: a Langium-based IDE for SharePoint and M365 development that puts AI agents inside a typed semantic boundary, so they cannot generate code that violates the platform's own rules. More on that in a follow-up.

For now, if your LinkedIn signal looks anything like mine, the first move is updating the inputs you're paying attention to. The second is choosing which of the two surviving careers you want.

The middle isn't going to wait for you.