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
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.
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.

Chart showing that 60 to 70% of enterprise clients still run an active Power Platform CoE Starter Kit deployment, splitting in half between an inventory-only cohort whose migration is straightforward and a custom Dataverse cohort that needs a rebuild.
Power Platform

The Power Platform CoE Starter Kit is retired, and nobody told your tenant

The Power Platform CoE Starter Kit is no longer maintained. What the admin centre replaces it with, what it does not, and the gaps
Chart contrasting the cost of one grounded multi-step Copilot Studio turn: zero credits for a Microsoft 365 Copilot licensed user, and 17 credits for an unlicensed user, made up of 2 for the generative answer, 5 for the agent action and 10 for tenant graph grounding.
Copilot & AI

Copilot Studio licensing: who is talking decides the bill

Copilot Studio licensing turns on one question: who is talking to the agent. The same turn costs nothing or twelve credits, and enforcement disables
Azure spend by category, with untagged spend the largest single line on the bill
Azure

Azure cost optimisation starts at provisioning, not at the invoice

Azure cost optimisation is usually treated as a reporting problem. It is a provisioning problem. The controls that stop spend drifting before it starts.
A few Power Apps IT knows about beside a long tail of unaccounted apps, each needing a premium licence
Power Platform

Power Platform managed environments: the licence check is already running

Power Platform managed environments now notify unlicensed users, escalating every seven days. The requirement is not new. The enforcement is, and it is live.
The four Fabric throttling stages from overage protection through interactive delay and rejection to background rejection
Microsoft Fabric

Fabric capacity planning: what to read before you scale

Fabric capacity planning starts with the metrics app, not the purchase order. What to read before scaling up, and why doubling the SKU is
Microsoft 365 E7 at 99 dollars against its components bought separately at 117 dollars, a saving of 18
Copilot & AI

Microsoft 365 E7, or just add Copilot to what you already own?

Microsoft 365 E7 bundles Copilot in. But the list of plans that can add Copilot is far wider than most people assume, and an

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