Notes from the field.
What we learn moving organisations onto the Microsoft cloud. Method, not opinion.
One agent is an integration. A hundred is a governance problem.
Agents got production identities before they got a stable way to record what they did. Microsoft Entra Agent ID is generally available, with sponsors and expiry dates. The OpenTelemetry conventions for agent traces are still experimental. That gap is not a detail: it decides what you can responsibly put into production this year, and it turns an AI question into a governance one.
Agents decide. Code executes. Knowing the line is the job.
The promise is that agents replace applications. In the systems we build, they do not. An agent is very good at understanding a request, weighing options and choosing a tool. It is the wrong place for a payment, a tax rule or a permission check. This is where the line falls, and why putting it in the wrong place is expensive.
AI solved syntax. It did not solve judgement.
Three independent measurements, taken between 2025 and 2026, all point the same way: AI-generated code passes over 95% on syntax and 55% on security, and that second number has not moved in two years. The part you write got cheap. The part you decide did not.
The state of SharePoint in 2026: what is gone, what is current, and what to build on
Every year someone declares SharePoint dead. It never was. But in a matter of months, real parts of it reached the end of the line: the Add-in model and Azure ACS retired in April, and SharePoint Server 2016 and 2019, InfoPath and SharePoint Designer left support in July. Here is what actually ended, what replaced it, and what to build on now, on-premises and in the cloud.
Windows 10 has ended: Windows 11 is the minimum, not the plan
Support ended in October 2025. Whether a fleet is already on Windows 11, paying for Extended Security Updates, or simply exposed, the decision underneath is the same: swap the PCs, or use the forced move to modernise the workplace behind them. This is the how, with the Intune, Autopilot and Azure commands, and the reason the same Windows 10 is free to keep alive in the cloud.
SPFx 1.23.2: upgrading is not changing a number
The previous version was pulled from npm for regressions, and that is the warning: the risk of upgrading the SharePoint Framework is almost never in the SharePoint runtime, it is in the build. What changed in Heft, in Sass and in npm audit, with the code showing how it was, how it is, and how it will be.
Nothing matches your search.