Development & automation
What we learn moving organisations onto the Microsoft cloud. Method, not opinion.
Three web parts in the PnP samples, and what the review taught me
Three SPFx web parts of ours are published in the official Microsoft 365 PnP samples repository. The interesting part is not that they were accepted. It is the difference between the first submission, which needed nine commits and six rounds of automated validation, and the third, which passed on the first attempt. What changed was not the code.
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.
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.
Sending email from an application, without a single password
Microsoft turned off SMTP with a password. The answer is not to store a better secret: it is to store no secret at all. Managed identity, Microsoft Graph, and Mail.Send tied to a group of mailboxes. Here is the whole configuration, mistakes included.
Nothing matches your search.