Nothing matches your search.
All articles
- Development & automation
A green gate did not make the release deployable
A release of this site passed every check in its release gate and was refused by the deployment client before a single file was uploaded. What the gate proved, what only the platform's own validator decides, and how a test written from the same assumption as the code it tests agreed with an error instead of finding it.
Keep reading → - Governance & security
Documentation is a claim until the system is read against it
A configuration document governs a Microsoft 365 or Azure estate only while it is bound to the system it describes: an owner, a documented reading of the actual state, a comparison and a date to read it again. What NIST SP 800-53 and Microsoft's guidance ask of documentation, how Compliance Manager keeps a recorded status apart from a read one, and three Microsoft 365 settings where the document and the tenant can disagree unnoticed.
Keep reading → - Development & automation
A readiness probe that checks the database
A probe answers one question for one consumer, and a probe that checks a shared database turns the database's failure into every instance's failure at once. What Azure App Service and Kubernetes do with that answer, how ASP.NET Core keeps liveness and readiness apart, and what we would check on each probe.
Keep reading → - Azure & Cloud
What a slot swap promises, and what it abandons
A deployment slot swap warms the new version, moves production traffic to it without dropping requests, and keeps the old version one swap away. It does not protect the work running on the old instances, stop timers and WebJobs running in both slots, carry the identity and some settings across, or undo on the way back what the new version wrote.
Keep reading → - Azure & Cloud
A missing .NET trace does not establish that the operation never ran
Instrumentation, sampling, export and query scope each limit what a trace search can establish. A local ActivitySource experiment separates business execution from the observations that survived.
Keep reading → - Governance & security
The last Graph page is not proof of tenant coverage
A successful response, an exhausted page chain and a complete population are three different claims. A small offline experiment shows where an apparently reliable collector can silently change one into another.
Keep reading →
Categories
- Keep reading →
AI & agents
6 - Keep reading →
Azure & Cloud
3 - Keep reading →
Company
1 - Keep reading →
Development & automation
15 - Keep reading →
Governance & security
6 - Keep reading →
Microsoft 365 & SharePoint
3 - Keep reading →
Migrations
5
Send us a message
or write to hello@ph7x.com