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
Nine Power Platform responsibilities, from environments to Microsoft support, running past the project handover with no end date
Power Platform

Power Platform managed services: what running the estate involves after go-live

Power Platform managed services cover what a project leaves behind: environments, data policies, capacity, licences, alerts, releases and the support gaps.
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.

Seven steps of a Power Platform foundation set from the outer boundary inward, from owner and admin roles to support before makers arrive
Power Platform

Power Platform landing zone: what to set up before makers arrive

Microsoft’s current docs do not define a Power Platform landing zone. What they cover instead, and what to set up before makers arrive, with
Six outputs of a GP migration assessment: lifecycle dates, tool prerequisites, customisation inventory, integration list, history decision, and a priced, dated plan
Dynamics 365

GP migration assessment: what it should produce

A GP migration assessment should produce dates, a readiness check against Microsoft’s migration tool, an inventory of what it will not move, and a
Three questions to put to a CSP partner before signing: who you buy from, what they can access, and how you leave
Azure

Choosing a Microsoft CSP partner: who you buy from, what they can access, how you leave

Choosing a CSP partner: direct-bill or indirect reseller, GDAP admin roles, tenant ownership, new commerce terms and how to leave, checked against Microsoft.
Timeline: AX 2012 R3 support ended January 2023; Windows Server 2012 R2 final update October 2026; Windows Server 2016 support ends January 2027; SQL Server 2016 updates end July 2029; Windows Server 2016 updates end 2030
Dynamics 365

AX 2012 support: what running it now exposes you to

AX 2012 support ended in January 2023. The platform under it is now running out too. What staying on AX exposes you to, and
Three requirements in a managed Fabric request: platform uptime and break-fix support from Microsoft, and data on time, which nobody provides by default
Microsoft Fabric

Fabric managed services: what a 24/7 SLA actually covers

Fabric managed services are usually sold on a 24/7 SLA. What Microsoft already covers, what it leaves to you, and what to ask a
Eight decisions settled before a Dynamics 365 Customer Service build, starting with the licence tier
Dynamics 365

Dynamics 365 Customer Service implementation: what to decide first

A Dynamics 365 Customer Service implementation is mostly decided before the build. The eight decisions that set the timeline, in the order to take

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