Notes from the field.
What we learn moving organisations onto the Microsoft cloud. Method, not opinion.
Migrating SharePoint 2016 and 2019 to Subscription Edition: the scripts
SharePoint 2016 goes straight to Subscription Edition. There is no hop through 2019, the method is database attach and nothing else, and the order of the service applications is not a preference. The whole sequence in PowerShell, from the inventory you take before touching anything to the crawl you run at the end.
SharePoint 2016, 2019, Subscription Edition and Online: what actually changes
2016 and 2019 both end support on 14 July 2026. Subscription Edition has no end date and cannot be bought outright. Online has features the others will never get, and Subscription Edition has two that are usually listed as impossible. A practical comparison, with the licensing that decides it.
Developing for SharePoint Server Subscription Edition: the practices that hold up
Subscription Edition is supported until at least 2035 and its SharePoint Framework ceiling has not moved since 2023. That combination is the whole job: a long runway on an older stack. This is how to build on it well, with code that runs on the version your farm actually accepts.
A Copilot agent manifest is a security boundary. Here is the linter for it.
Every scoping property in a Microsoft 365 Copilot agent manifest is optional, and in six places omitting one grants the widest scope instead of the narrowest. A JSON Schema validator approves those manifests, because nothing in them is invalid: something optional is missing. So we wrote the check that does catch it. It finds six problems in a manifest that passes every other test.
SPFx before version 1.0: three of our web parts in the official Microsoft samples
The SharePoint Framework developer preview came out in August 2016. Version 1.0 arrived in February 2017. Our first contribution to the official Microsoft 365 samples repository is dated October 2016, five months before there was a 1.0 to build against. Three of our web parts are in that repository today, and this is what each of them is for.
We are still measuring engineers by the part that got automated.
In 2025 DORA threw out its own scoreboard. The low, medium, high and elite tiers that the industry had quoted for a decade were replaced by seven team archetypes across eight measures. That is not a methodology footnote. It is the most used measurement framework in software admitting that the instruments no longer read the thing that decides whether a system survives.
Nothing matches your search.