Insights · Microsoft · Data · AI

Field notes from enterprise Microsoft delivery

Written by the architects who build and run these platforms for clients. Fabric, Azure, Power BI, Copilot and the governance that holds them together.

Written from delivery

Every piece is written or reviewed by the architects who build and run these platforms for clients.

Sourced, not summarised

Where we state a number we say where it came from, and when we last checked it.

Built to be used

Patterns, runbooks and checklists you can take straight into your own environment.

Latest article
Two panels comparing an AX 2012 upgrade: carries across the database upgraded in place with full transactional history and configuration and master data, rebuilt covers overlayered code as extensions, integrations against new patterns and operations on a shared model, with a note that upgrade runs only from R2 or R3 and not from virtual companies or data partitions
Dynamics 365

AX 2012 to Dynamics 365: what upgrades and what gets rebuilt

AX 2012 to Dynamics 365 has an upgrade path, but only from R2 or R3 and not for every system. What carries across, what
Read the article

All articles

Browse by topic.

Pick a topic to filter the list below. Long-form, technical, and written from delivery rather than from a product page.

Two panels comparing an AX 2012 upgrade: carries across the database upgraded in place with full transactional history and configuration and master data, rebuilt covers overlayered code as extensions, integrations against new patterns and operations on a shared model, with a note that upgrade runs only from R2 or R3 and not from virtual companies or data partitions
Dynamics 365

AX 2012 to Dynamics 365: what upgrades and what gets rebuilt

AX 2012 to Dynamics 365 has an upgrade path, but only from R2 or R3 and not for every system. What carries across, what
Horizontal bar showing where the first-year budget goes on a 50 to 150 user finance and operations implementation: licences 10 to 15 percent, services, data, integration and change 85 to 90 percent
Dynamics 365

Finance and operations implementation: what it really costs

A finance and operations implementation costs far more than its licences. What Microsoft publishes, where the budget really goes, and what to price first.
Three stacked layers showing where access is decided in Microsoft Fabric: a dashed domain box that labels and delegates but controls no access, a solid workspace layer where roles decide who gets in, and an item and data layer covering permissions and row and column security
Microsoft Fabric

Fabric governance: domains do not control access

Fabric governance is built on domains and endorsement, but a domain never decides who can see data. Certification is the control that changes behaviour.
Horizontal bar chart of the most common shape of Power Platform adoption: community running ahead at 300, strategy and vision and business value at 200, and support and governance still at 100, where makers support their own apps and environments are creatable by all
Power Platform

Power Platform adoption is not a usage number

Power Platform adoption is usually reported as a user count. Microsoft’s maturity model says that is the wrong measure, and a maker community proves
Two cards comparing what exists before anything runs: AKS shows six nodes recommended for production before the first request, Container Apps shows zero because it scales to zero with nothing to patch while idle, and AKS earns its place with API access or deny-by-default network policy
Azure

Container Apps vs AKS: the choice is who runs it

Container Apps vs AKS is usually settled by habit. Microsoft names two narrow reasons to need AKS, and neither is that the application is
Two nested boxes: an outer box for what a user can already reach, decided by permissions, and a smaller inner box for what Copilot may process, narrowed by labels, DLP and the EXTRACT right, showing Purview shrinks only the inner box
Copilot & AI

Purview and Copilot: what it can actually stop

Purview and Copilot are sold together, but Purview never changes what a user can reach. It only narrows what Copilot processes, and it has

Next step

Most people arrive here mid-problem.

Pick whichever sounds like your situation. It routes to the people who would actually handle it, not to a form.

Schedule a discovery call

We bought Copilot licences and cannot show what they returned.

The readiness assessment we run before any rollout: what Copilot can currently surface, and to whom.

See how it works

We are on Fabric but nobody has tested a recovery.

A continuity review against what the platform genuinely replicates, which is less than most teams assume.

See our Fabric practice