MANAGED SERVICE

ALM, hypercare and evergreen support for D365 F&O.

Service updates, deployments, environments, regression testing, security and user management, taken off your team's plate for good.

THE PROBLEM

One Version doesn't care how busy you are.

Microsoft ships four F&O service updates a year, and you have to take at least two of them. You can pause one at a time, never two in a row. There's no version of this where it stops.

Each one needs regression testing. Most estates we see don't have that automated, so every update becomes a week of manual clicking that nobody has time for. That's why so many estates fall behind, and why falling behind makes the next one worse.

Meanwhile environments drift out of sync, security roles accumulate years of exceptions, and deployments get done by whoever happens to be free that afternoon.

FIG. 01 / THE EVERGREEN CYCLE, ONE SERVICE UPDATE
RELEASE notes review IMPACT assessment REGRESSION sandbox DEPLOY + rollback plan PRODUCTION verify · report REPEATS: UP TO 4 SERVICE UPDATES A YEAR
SCOPE

Everything that keeps a live estate healthy.

Environments

  • ✓Environment management in LCS or the Power Platform admin center
  • ✓LCS to Power Platform admin center migration
  • ✓Sandbox copy and refresh scheduling
  • ✓Production-to-sandbox copy, point-in-time restore
  • ✓Data movement and golden configuration management

Updates and regression

  • ✓Service update planning and application
  • ✓Automated regression suite build and maintenance
  • ✓RSAT migration before support ends in May 2027
  • ✓Regression run against every update
  • ✓Release notes review and impact assessment

Deployment

  • ✓Package deployment and code merge
  • ✓Azure DevOps build and release pipelines
  • ✓Environment promotion and rollback planning

Security and users

  • ✓Role assignment and maintenance
  • ✓Segregation of duties review
  • ✓Licence compliance and right-sizing
  • ✓User provisioning and access review

Operations

  • ✓Batch job monitoring and tuning
  • ✓Performance review
  • ✓Incident triage and resolution
  • ✓Cutover and hypercare support
HOW WE MAKE UPDATES BORING

We build your regression suite once, then run it forever.

Service updates hurt because most estates don't have automated regression testing. So every update means manually re-testing the same processes, or taking the update and finding out in production.

During onboarding we build an automated regression suite against your actual processes: order-to-cash, procure-to-pay, month-end. After that, every update gets a regression run as part of the retainer.

The first update after that is the one where you notice the difference.

THE PART FINANCE CARES ABOUT

Your security roles now set your licence bill.

Microsoft works out the licence each F&O user needs from the highest privilege their security roles grant, not from what they actually do. One over-broad role can move a user from a Team Members licence to a full Finance or Supply Chain licence.

Roles drift. People change jobs, projects end, contractors leave, and the roles stay. We review role design and assignments with Microsoft's User Security Governance and licence reports, fix the roles that grant more than people need, and right-size assignments before your next true-up.

Happy to do this piece on its own if the wider conversation isn't a priority right now.

WHAT'S CHANGING

Two Microsoft deadlines worth planning for.

15 MAY 2027

RSAT loses support

Microsoft has marked the Regression Suite Automation Tool for deprecation. Test libraries built on it need a new home before they drift out of step with new releases. We migrate them and keep your update cycle running through the switch.

FROM FEB 2026

LCS gives way to the admin center

New Finance, Supply Chain and Project Operations customers are set up in the Power Platform admin center, and existing customers can now migrate environments across. We run the migration and update your runbooks, pipelines and access to match.

COMMERCIALS

Four tiers. No hourly billing.

TIER WHAT IT COVERS FROM
HYPERCARE Post go-live stabilisation, 4–12 weeks. Defect triage, data fixes, user support, knowledge transfer. [PRICE]
ONBOARDING One-time. Environment audit, regression suite build or RSAT migration, pipeline setup, security and licence baseline. [PRICE]
ESSENTIAL Service updates, deployments, code merge, basic monitoring. [PRICE] /mo
STANDARD Everything in Essential, plus DB refresh, user and security management, batch monitoring, regression runs. [PRICE] /mo
MANAGED Everything in Standard, plus named hours, SLA, performance tuning and licence reviews. [PRICE] /mo

Evergreen tiers run on a 12-month minimum, billed monthly in advance, 60 days' notice.

GETTING STARTED

Three to four weeks from signature to steady state.

WEEK 1 / AUDIT

We map your environments (LCS or Power Platform admin center), update history, deployment process and security model. You get the findings whether or not you continue.

WEEK 2 / BASELINE

Pipelines, refresh schedules, access, runbooks. Security and licence review.

WEEKS 3–4 / REGRESSION

We build the regression suite against your core processes, or move your existing RSAT library across.

ONGOING

Monthly reporting, update cycle management, quarterly review.

FAQ

The questions we always get.

Do you need production access?

Yes, for most of the scope. It's governed by our MSA, an NDA and IP assignment signed by every individual, and no production change happens without a rollback plan.

What if we already have an implementation partner?

That's fine. Most of our support clients keep theirs. We take the lifecycle work their consultants would rather not do, and they stay on the project work.

Can you support an estate you didn't implement?

That's the normal case. The audit in week one exists precisely for that.

What if we're several updates behind?

Also normal, and the reason to start. We'll scope the catch-up separately from the ongoing retainer.

We test with RSAT today. What happens in 2027?

RSAT keeps running, but Microsoft stops supporting it after 15 May 2027 and hasn't named a direct replacement. We move your test library to a supported framework, chosen with you based on your estate and who will maintain it, and run both side by side through one update before switching.

We're still in LCS. Do we have to move?

Not yet. Existing LCS projects keep working, but new customers can't create them any more and Microsoft is moving environment management to the Power Platform admin center. The migration is one-way and per environment, so we plan it around your update calendar rather than in the middle of one.

Minimum commitment?

Twelve months on evergreen tiers. Hypercare is a fixed term with no ongoing commitment.

When's your next service update?

If the answer is "not sure" or "we're behind", that's the conversation.

Book a call
CONTACT US

Tell us what's on your plate.

Twenty minutes, no deck. We'll tell you what's fixable and roughly what it costs. If we aren't the right fit, we'll say so.

Reply within one working day. See our privacy policy.