Nothing matches your search.
All articles
- Migrations
A SharePoint cutover stops being reversible when the new farm accepts writes
Keeping the old farm available preserves a fallback environment. It does not preserve changes accepted by the new one. A decision matrix and an offline counterexample separate routing recovery from data reconciliation.
Keep reading → - Development & automation
A hybrid SharePoint integration needs more than a successful sign-in
A Java or .NET API can authenticate a caller while the downstream SharePoint operation still has the wrong authority. Compare the identities, contracts and failure boundaries before choosing a gateway or extracting legacy functionality.
Keep reading → - Development & automation
Writing to two systems is not a transaction
An application that saves one change in two systems has two outcomes, and nothing commits them together. What Microsoft's architecture guidance says about why the copies drift apart, where a transaction across two systems does exist, and what makes the result recoverable: one record of the change, delivered at least once to a consumer that ignores repeats, and compensation for what cannot be derived.
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