- Organisation
- Carne Group
- Predecessor
- Third-party local data centre hosting product-specific virtual-machine compute resources
- Destination
- Microsoft Azure landing zones using Azure Site Recovery, Azure Backup and Terraform
- Workload
- All compute resources supporting Carne Group products
- Stage
- Completed data-centre compute migration
- Retirement status
- The named product-supporting compute estate exited the local data centre; storage, network, SaaS and unrelated external dependencies are not fully enumerated.
- Confidence
- High
- Next trigger
- A dated cutover statement, formal facility exit confirmation or later IaaS-to-PaaS completion milestone.
Programme context
Carne Group depended on a third-party local data centre for virtual-machine provisioning, backup and operational changes. Regulatory guidance enabling cloud adoption and the company's need for greater resilience and autonomy created the migration boundary.
Why this matters: The source states a completed data-centre compute move, identifies the Azure implementation pattern and separates the finished migration from later cloud-native modernisation.
Migration timeline
| Date or stage | Milestone | What changed | Evidence status |
|---|---|---|---|
| Prior operating state | Source condition | Product compute ran in a local third-party data centre with provider-dependent provisioning and backup operations. | Source-stated predecessor |
| About six months | Migration execution | Azure Site Recovery replicated virtual machines into product-specific Azure landing zones. | Source-stated duration |
| Prior year | Completion milestone | All product-supporting compute resources had moved to Azure before the March 2026 story. | Source-stated completed state |
| 13 Mar 2026 | Evidence milestone | Microsoft published the current customer account. | Dated primary evidence |
Workload migration matrix
| Workload | Predecessor | Destination | Status by 24 Jul 2026 |
|---|---|---|---|
| Product-supporting virtual-machine compute | Third-party local data centre | Microsoft Azure landing zones | Completed |
| Backup, recovery and resilience controls | Provider-mediated backup and restoration | Azure Backup, Azure Site Recovery, Azure Policy and Azure Monitor | Operational |
| Post-migration application modernisation | IaaS-hosted virtual machines and legacy middleware | Azure App Service, Azure SQL, Azure Service Bus and other PaaS services | Ongoing; not part of the completed migration claim |
Implementation and architecture
- Terraform-based landing zones separated each product environment.
- Azure Site Recovery replicated compute and data states before a controlled cutover.
- An application gateway already pointed to on-premises endpoints, allowing the team to switch backend targets after migration.
- Azure Backup, Azure Policy and Azure Monitor were added to the post-migration operating model.
- Later migration from virtual machines to cloud-native services remains a separate programme.
Known unknowns and contradictions
- The exact final cutover date.
- The full list of storage, network and external dependencies that remained outside the compute migration.
- Whether the third-party facility contract or every associated service was formally terminated.
- The completion date for later IaaS-to-PaaS modernisation.
No missing fact is inferred to convert the bounded compute migration into a whole-estate retirement claim.
PlatformTrace analysis
The strongest evidence is the explicit statement that all compute resources supporting Carne products moved from the local data centre to Azure. The source also clearly separates that finished lift-and-shift from later modernisation of databases, Windows services, messaging and traffic management.
PlatformTrace therefore records a completed data-centre compute migration with residual non-compute scope preserved as unknown.
Evidence ledger
- Microsoft customer story, 13 March 2026
Direct Carne Group statements identify the source data centre, all-compute scope, Azure target, six-month duration, implementation pattern and ongoing post-migration modernisation.
Corrections and updates
24 July 2026 — Initial Verified long-format dossier published after complete five-lane intake, central filter reconciliation and fresh primary-source reopening. Later milestones will be appended rather than silently replacing this state.