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
Four published Business Central limits shown as cards: 300 companies per environment, 3 TB of data, 6,000 OData requests per user, and 10 concurrent background sessions highlighted as the ceiling that binds first
Dynamics 365

Business Central vs Finance and Operations

Business Central vs Finance and Operations is asked as a headcount question. Microsoft publishes no user threshold, but it does publish the hard limits.
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.

Four published Business Central limits shown as cards: 300 companies per environment, 3 TB of data, 6,000 OData requests per user, and 10 concurrent background sessions highlighted as the ceiling that binds first
Dynamics 365

Business Central vs Finance and Operations

Business Central vs Finance and Operations is asked as a headcount question. Microsoft publishes no user threshold, but it does publish the hard limits.
Two panels answering which Power Platform projects need a baseline: fast-track for personal helpers under five developer days with no external dependencies, where adoption count is enough, and a hard gate for 50 or more users, premium licensing or auditable processes, requiring cycle time, error rate and labour hours before the sprint.
Power Platform

Power Apps ROI: the number you cannot recover

Power Apps ROI rests on a baseline most teams never capture. Every measure Microsoft lists is a before and after, and the before is
Decision diagram from the question what do we do if this does not arrive, branching to two answers: nothing, meaning it is an event for Event Grid or Event Hubs, and reconcile, raise a ticket or re-send, meaning it is a command for Service Bus.
Azure

Azure messaging services: the choice is command or event

Choosing between Azure messaging services starts with one question: is this a command or an event? Answer that and the product choice mostly makes
Four-step framework shown in sequence: organisational readiness covering who owns which data, then architecture, then governance baselines, then operational standards, with an arrow marking step one as where the framework starts and step two as where most assessments start.
Data strategy

A data platform assessment that starts in the wrong place

A data platform assessment usually starts with architecture. Microsoft’s own first step is ownership, and assessments that skip it produce designs nobody owns.
Process diagram of a GP to Business Central migration: connect puts the tenant read-only, replication into a staging schema can be rerun as often as needed, then a marked barrier reading no way back before the data upgrade into native ledger tables, followed by validation.
Dynamics 365

GP to Business Central migration: the three one-way doors

A GP to Business Central migration has three one-way doors: a read-only period, an irreversible data upgrade, and an overwrite most people never read
Grid representing every app and flow in a Power Platform default environment, where 80 to 90 per cent are abandoned experiments and one-off flows shown as muted squares, and a scattered 10 to 15 per cent are highlighted as business critical but unmanaged.
Power Platform

Power Platform governance: the guidance has not caught up

Power Platform governance guidance still points at a retired toolkit. What holds up, what does not, and the default environment setting that undoes most

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