Nothing matches your search.
All articles
- AI & agents
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.
Keep reading → - AI & agents
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.
Keep reading → - AI & agents
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.
Keep reading → - AI & agents
Can your AI assistant read documents the user cannot see?
A badly built RAG searches with the application's identity, not the asker's, and the assistant answers with what the person should not see. The fix is not a filter someone can forget to write: it is passing the user's token and letting Azure AI Search enforce permissions inside the engine.
Keep reading → - Development & automation
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.
Keep reading → - Microsoft 365 & SharePoint
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: SharePoint Online Add-ins and Azure ACS for SharePoint Online 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.
Keep reading →
Categories
- Keep reading →
AI & agents
6 - Keep reading →
Azure & Cloud
1 - Keep reading →
Company
2 - Keep reading →
Development & automation
9 - Keep reading →
Governance & security
3 - Keep reading →
Microsoft 365 & SharePoint
2 - Keep reading →
Migrations
3
Send us a message
or write to hello@ph7x.com