FIELD NOTES / SITUATION → SOLUTION
Reasoning for systems in motion.
Long-form analysis of narrow Microsoft 365 and business-system failures. Recognise the situation, follow the repair, then inspect the controlled runbook.
The fixed-price Microsoft 365 estimate arrived before anyone inspected the system
A composite modernisation estimate where an apparently certain price hides unresolved scope, architecture, migration, acceptance and operating risk.
The meeting summary disclosed what the transcript kept restricted
A composite Teams meeting-intelligence failure where authorised source access becomes an unauthorised derivative published to a broader Microsoft 365 audience.
The migrated project record opens by URL but disappears from SharePoint search
A composite SharePoint migration failure where files arrive successfully but crawl eligibility, metadata mapping, permissions and retrieval remain unproved.
The production app still follows a hotfix that no longer exists in development
A composite Dataverse release failure where a successful managed deployment is hidden by an active unmanaged layer and mismatched target configuration.
The cloud workflow depends on one Windows gateway nobody can rebuild
A composite Power BI and Power Automate continuity failure where one gateway host, recovery key and network path carry every on-premises dependency.
The integration needs one SharePoint site but can write to every site
A composite Microsoft Graph failure where a single-site document integration retains tenant-wide application permission after its prototype becomes production.
The confidential project file will not delete after the sensitivity label is removed
A composite Microsoft Purview failure where sensitivity, retention and SharePoint controls are treated as one label and the wrong repair is attempted.
The shared mailbox workflow creates every case twice
A niche Power Automate failure where one customer email becomes two cases after overlapping runs, connector retries and an unsafe replay.
The Power Automate owner left on Friday
A niche recovery pattern for a business-critical flow whose owner, Outlook connection and approval chain disappeared with a departed employee.
The SharePoint farm came back, but the portal did not
A recovery sequence for a legacy SharePoint portal after certificate expiry, undocumented service identities and an IIS binding drift.
The guest is in Teams but SharePoint says access denied
A precise diagnostic for cross-tenant guests who can chat in Teams but cannot open the files tab or linked SharePoint site.
The Power Pages portal shows every record—or none
A record-isolation solution for an external portal where Dataverse table permissions alternate between data exposure and unusable access denied errors.
Microsoft 365 governance begins with named owners and inspectable controls
A programmatic Microsoft 365 baseline for privileged roles, applications, SharePoint sharing, Power Platform environments and control evidence.
Four inventories that make a SharePoint migration priceable
A programmatic SharePoint discovery method for ownership, disposition, dependencies and acceptance before migration waves are priced.
Test Power Pages against the hardest record-isolation path
A Power Pages fit assessment built around relationship-based Dataverse access, ALM, failure paths, negative personas and measured cost.
Trace every meeting summary claim to an authorised source segment
A technical meeting-intelligence design for transcript acquisition, claim lineage, audience calculation, human approval, audit and controlled derivatives.
LASP discovery starts below the application layer
Independent tender research showing how lower-layer evidence, service-state mapping and proof slices produce a pricing-grade LASP replacement brief.
Build a public technical profile from a controlled claim register
A programmatic public-evidence model connecting approved claims, primary sources, ProfilePage schema, field notes, technical documents and link checks.