Operating Models: Who Is "the Platform Team"?¶

Throughout this documentation, the platform team is the team that runs the Managed Cloud Platform (MCP): the hub, the pipelines, the configuration repository and the standard changes. The same product can be run in two ways.

	Managed service (XMMS)	Self-managed (customer platform team)
Who is the platform team?	Xebia Microsoft Managed Services (XMMS), under a managed-service contract	The customer's own team (or another partner they chose) that bought the platform to maintain it themselves
Who owns the code repository?	XMMS. Customers get released versions through the code sync.	XMMS publishes releases; the customer syncs and pins a version
Who owns the configuration repository?	XMMS operates it for the customer, with the customer as reviewer or approver where agreed	The customer's platform team
Who runs the pipelines and approves plans?	XMMS engineers, within the contract's change process	The customer's platform team
Who updates the platform to a new version?	XMMS plans it with the customer (What to do when a new version is released)	The customer decides when to move the pin and follows the upgrade guide
Intake for requests	The channel and tooling agreed in the contract (for example a ticket system)	The customer's own intake: ticket system, board or chat
Incident and service-request handling	Severities, response times and support hours from the contract	Defined by the customer (Operating responsibilities, Incident management)
Azure support (Microsoft)	Per contract	The customer needs its own Azure support plan
Security officer, identity team, SOC	Customer	Customer

What does not change

The product, the configuration format, the pipelines, the standard changes and the backwards-compatibility contract are the same in both models. Only who does the work and through which channel differ.

How to read the pages in this documentation¶

"Platform team" means whoever fills that role in your situation. If your organisation has a managed-service contract with XMMS, read it as XMMS. If you maintain the platform yourself, read it as your own team.
Contract-specific details (support hours, response targets, intake tool, contact addresses) are never fixed in this documentation. They are written as placeholders such as <support channel>. Your onboarding document or contract gives the real values.
Operator pages (Platform) are written for the people who run the platform. In the managed model that is XMMS, and the customer reads them to understand what happens on their behalf. In the self-managed model they are the runbook.
Consumer pages (Consumers) are for workload teams, in both models.

Who does what in each model¶

flowchart LR
    subgraph consumers["Workload teams (consumers)"]
        w["Request, use, build"]
    end
    subgraph pt["Platform team"]
        direction TB
        m["Managed: XMMS engineers"]
        s["Self-managed: customer engineers"]
    end
    subgraph xms["XMMS product team"]
        r["Releases, upgrade guides, release notes"]
    end
    w --> pt
    xms -->|"new versions"| pt
    pt -->|"configuration + pipelines"| azure["Azure: hub and spokes"]

Activity	Managed (XMMS)	Self-managed
Receive and triage requests	XMMS	Customer platform team
Prepare the change (pull request on the config repository)	XMMS	Customer platform team
Review and approve a change	XMMS reviewer; customer approves where the contract says so	Customer platform team (four-eyes inside the team)
Run `Plan` / `Apply` in the entry pipelines	XMMS	Customer platform team
Test on canary	XMMS	Customer platform team
Take a new platform version	XMMS proposes a window, customer agrees	Customer chooses the moment; reads release notes and upgrade guide
Monitor the platform, handle alerts	XMMS, during the contracted hours	Customer platform team, hours as defined by the customer
Rotate deployment identities	XMMS	Customer platform team
Define policies and firewall content	Customer security/architecture decides; XMMS implements	Customer security/architecture decides; the platform team implements
Spoke baseline and standard changes for workload teams	XMMS	Customer platform team

Moving from managed to self-managed (or back)¶

The Operating responsibilities page has a day-one checklist for a customer taking over the platform: alert receivers, Defender contact, deployment identities, approvals, version pinning. When going back to a managed service, the same list is the hand-over inventory.

Consequences for consumers¶

Topic	Managed (XMMS)	Self-managed
Where do I send a request?	Contract intake	Your own platform team's intake
How fast is a response?	Per contract	Per your platform team's own targets
Who do I call outside business hours?	Only if the contract includes after-hours support for the hub	Your organisation's own on-call, if it has one
Who approves exemptions and firewall rules?	Your security officer; XMMS implements	Your security officer; your platform team implements

See Support and How to request.