Managed Cloud Platform (MCP)

The Managed Cloud Platform is the Azure landing zone that Xebia Microsoft Managed Services (XMMS) builds and releases. It is delivered as code: a shared, versioned code repository and one configuration repository per customer.

The platform is run by a platform team. That is either XMMS, under a managed-service contract, or the customer's own team, when the customer bought the platform to maintain it themselves. This documentation covers both: see Operating models.

What is it, and who uses it

flowchart TB
    root["What is it / who uses it"]
    root --> platform["Platform team = XMMS (managed) or customer team (self-managed)"]
    root --> consumers["Consumers / DevOps teams"]
    platform --> tech["What is it (tech) and how does it work"]
    tech --> code["Code: tools, provisioning, building and releasing"]
    tech --> config["Config: hub and spoke configuration"]
    consumers --> spoke["A spoke = their product"]

You are…	You need to know…	Start here
New to the platform (anyone)	Why the platform is built the way it is	General: platform philosophy
Platform engineer (XMMS or the customer's own platform team)	What the platform is technically, how it is deployed, how to build, release and configure it	Platform
Consumer (a DevOps or workload team of the customer)	What you get, what the limits are, what you do yourself, how to request and change things	Consumers

More reference

Topic	Page
Layers, domains, management groups, hub and spokes	Architecture reference
Core, direct and additional services; spoke variants	Service types
Decisions, exceptions, categories of change, service levels	Governance
Guardrails for workload teams and the platform	Design principles
Reusable design guidance (firewall rules, regions, DNS, agents, VPN)	Design guidance

The platform in one paragraph

A hub provides the shared networking, security, governance and monitoring. Each workload gets spokes: one Azure subscription per workload and spoke environment, connected to the hub. The hub is deployed in layers with Terraform, first to a canary copy of the hub and then to prod. Everything runs from pipelines in the configuration repository, which pin a released version of the code repository. Nobody changes Azure by hand.

Sources

These pages are based on:

Repository	Used as
xms-cloud-platform-code	Source of truth for how the platform works (Terraform, Xebia.Mcp module, pipelines)
xms-cloud-platform-config	Reference configuration repository (XDEV tenant)
XMS	The previous platform documentation, including the operator guide this site builds on

Where the code and older documentation disagree, these pages follow the code on main (checked on 15 October 2026).