Why does the go-live assessment gate projects nobody…

Why does the go-live assessment gate projects nobody scheduled for?

Your programme plan owns the cutover. It does not own the Go-live Readiness Review, because that review is not a project task — it is the condition Microsoft attaches to the existence of your production environment. And Microsoft's own pages describe who runs it, in what format, and where, three different ways.

This is a risk brief: each wording quoted, the published deadline, and the prerequisites that block submission before anyone has read a single answer.

Fact one: the review gates the environment, not the plan

Prepare for go-live (ms.date 2026-06-12) states it from Microsoft's side: "Microsoft provisions the production instance when the solution is ready and after project readiness is validated as part of the Go-live Readiness Review with Microsoft." The review is [GA] — the standing process, not a preview.

**The requirement** — "You must complete this review for every implementation project before you can deploy a production environment." (Go-live FAQ)
**The symptom teams meet first — "The Production button in LCS becomes available only after you complete the Analysis, Design & develop, and Test phases of the LCS implementation methodology and complete a Go-live Readiness Review** with Microsoft." (same page)
**The deadline* — "No later than four weeks before the go-live" — the Duration/When* cell of the review row (Prepare for go-live)
**The manual review service level** — "The review might take up to three business days for the initial report, plus more time for any risk mitigation that is required." (same page)
**The AI review path** — "The review process completes on the same day… the production slot is automatically released in Lifecycle Services within few minutes." (same page)
**What happens after — "After the go-live review is successfully completed, the Configure** button is enabled for the production environment." Deployment then "takes approximately 30 minutes." (same page)

Fact two: the prerequisites block submission, not just approval

This is what turns a four-week deadline into an eight-week one. Several prerequisites carry an asterisk, and Prepare for go-live explains it: "You must complete all steps that are marked with an asterisk (\*) before you submit the project for review in the portal. The project shows as blocked for review until you mark those steps as completed."

The asterisked items, verbatim: add key customer team members to the Lifecycle Services project; "upload and activate the final subscription estimator in Lifecycle Services"; the go-live date in Lifecycle Services "correctly represents the go-live date that you're targeting"; and "Complete all relevant tasks and phases in the Lifecycle Services methodology."

The unasterisked ones are the expensive ones: "User acceptance testing (UAT) and performance testing are complete or almost complete in a Tier-2 (or higher) environment. Don't use Tier-1 environments for UAT or performance testing." A project that meets that at the point of submission has not lost a form. It has lost a test cycle.

Fact three: where the review happens has moved, and the page that says so is malformed

Most projects no longer email a FastTrack engineer. "For most projects, you complete the go-live readiness review in the Dynamics 365 implementation portal," and "Partners and customers can submit the go-live readiness review in the Dynamics 365 Implementation portal without involving Microsoft" (both on Prepare for go-live) — through the onboarding wizard described on the Implementation Portal overview.

Then comes the sentence a Power Platform admin center customer needs, and it is buried. The Prepare for go-live page carries a Note opening "There are four exceptions that don't use the FastTrack for Dynamics 365 implementation portal:" and then lists three numbered items. Two are exceptions — US Government cloud projects, and tenant moves. The third is not an exception at all. In full: "The following steps apply to Lifecycle Services projects. These steps do no apply to implementations that you manage in the Power Platform admin center." We quote the typo as printed.

That matters because new Lifecycle Services cloud project creation is [DEPR]: "Starting February 16, 2026, you can't create new cloud implementation projects in Microsoft Dynamics Lifecycle Services for Dynamics 365 Finance, Dynamics 365 Supply Chain Management, and Dynamics 365 Project Operations" (project creation freeze). A new customer starting a cloud project for one of those three apps after that date is, by Microsoft's own scoping sentence, outside the article that documents this gate — on-premises implementations, Commerce projects, AX 2012 upgrades and tenant moves all still get a Lifecycle Services project — and the admin-center pages describe provisioning, not review. "You manage finance and operations apps in the Power Platform admin center with zero Microsoft Dynamics Lifecycle Services footprint" (ms.date 2026-07-23), and "You can create a UPE" — a unified production environment — "by provisioning a new production environment with an ERP template, or by converting an existing sandbox to production." The Convert to production tutorial lists three preparation steps — review outstanding tasks, communicate the downtime window, "Confirm production licensing and deployment readiness for business use" — and names no review.

What we actually checked. We opened the Convert-to-production tutorial, the unified admin experience overview including its Lifecycle Services features not implemented in the Power Platform admin center table, the unified environment types article, and the 2025 wave 1 release-plan entry for unified production environments. None of those four pages mentions the Go-live Readiness Review or FastTrack. One names the portal: the unified admin experience overview's Lifecycle Services features not implemented in the Power Platform admin center table sends Methodology and Project settings and users to the "Dynamics Implementation portal" — without saying whether a go-live review travels with them. Three site searches surfaced no page that settles it. That is a statement about the pages we opened — not proof no such rule exists, and exactly the question to put to your account team in writing.

One label from the same article, because it cuts the other way. The ERP templates that create a unified production environment appear under Display name as "Finance (preview)", "Supply Chain Management (preview)", "Project Operations Integrated (preview)" and "Commerce (preview)" (the last marked "Available for trials only") — [PP] by their own display names — while the release-plan entry Deploy and manage unified production environments carries a green general-availability checkmark dated Sep 30, 2025 (release plan). Both pages are current. We are not adjudicating which governs.

Fact four: three pages, three descriptions of the review itself

Each row is verbatim. Read them against each other.

**Prepare for go-live (ms.date 2026-06-12)** — "Customer/Partner submits answers to review questions in the FastTrack for Dynamics 365 implementation portal. Microsoft FastTrack provides a review report." The workshop is a separate row applying "only to eligible projects that have FastTrack engagement" (source)
**Prepare your production environment to go live — Success by Design (updated 2026-07-15)** — "The Microsoft FastTrack for Dynamics 365 team does a go-live readiness review in a workshop format with all parties." Also: "You can also do your own go-live readiness review by completing all required activities and having the business stakeholders sign off on them." (source)
**Customer eligibility and partner qualifications (ms.date 2026-07-29)** — Customers who don't meet the eligibility requirements "are invited to take advantage of available self-guided FastTrack resources, which include… a go-live readiness assessment for select Dynamics 365 applications." (source)

A workshop with all parties, a portal questionnaire with an optional same-day AI reviewer, and a self-guided assessment read as three different demands on your people's calendars — although the eligibility page's own "go-live readiness assessment" link resolves to the Prepare for go-live article, so two of the three may be one process described twice. Which you get turns on eligibility, and the eligibility page states the test without a number: customers must "Meet a minimum annual spend across their Dynamics 365 licenses in new deployments of eligible Dynamics 365 applications" and be attached to a qualified partner. The threshold is not published.

Why it lands late — our argument, and it is ours

This section is T2: our read, not a Microsoft statement. The gate arrives late because every prerequisite belongs to a different owner and none of them owns the review. User acceptance testing belongs to the business. The sandbox tier belongs to whoever wrote the environment plan. The subscription estimator belongs to licensing. The methodology phases belong to the implementation partner. The go-live date field belongs to nobody in particular — and the project is blocked for review until someone sets it.

A gate whose inputs are distributed and whose owner is unnamed is discovered, not scheduled.

Where we would draw the line

We would not treat the same-day AI review as licence to submit later. The published deadline is still four weeks, and the AI path shortens the review, not the prerequisites — which are the long pole.

We would not let an optimization app become a go-live dependency. Every Optimizer we build is a companion app on Dataverse and Azure that reads posted Dynamics data and writes its decision back behind an approval step. It rides the same governed stack, and it should never be why a production environment is late.

And we would not report this gate as a green tick. It is a state on a Microsoft system, so the honest unit is the artefact: review submitted, risks mitigated, button enabled.

What to do this week

Record the go-live date currently stored in your Lifecycle Services project — or, on the Power Platform admin center, ask your partner where your implementation project lives. That field is an asterisked prerequisite and it silently blocks submission.
Check which environment tier your user acceptance and performance testing run in, against Microsoft's stated prerequisite quoted above.
Name the person who owns submitting the review, in writing, this week. Not the partner, not the programme — a person.
Ask Microsoft and your implementation partner, in writing, which of the three descriptions above applies to your project, and whether the project is FastTrack-eligible. Keep the answer.

About Cognilium Cognilium builds AI optimization apps for Microsoft Dynamics 365 — companion apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Dynamics is your system of record. Cognilium is your system of intelligence. https://cognilium.ai · https://www.linkedin.com/company/37180269/

If you are inside a Dynamics 365 go-live this year, book a fifteen-minute call and we will walk the platform decisions and the optimization layer with you on your own estate — no deck. https://cognilium.ai

Why does the go-live assessment gate projects nobody scheduled for?