Skip to content

Responsibilities

This page gives the split of responsibilities between the platform team and the workload team for the Base Fabric Data Platform. The platform team is XMMS under a managed-service contract, or the customer's own team when the platform is self-managed (Operating models). The generic split for spokes is on Responsibilities.

The service description uses the RACI model: Responsible does the work, Accountable owns the result, Consulted is asked before or during, Informed is told afterwards. In the table, "Platform team" is the party that the service description calls Xebia, and "Workload team" is the party it calls the customer.

RACI

Activity Workload team Platform team
Platform services
Fabric capacity provisioning and scaling I R/A
VNet data gateway management I R/A
Workspace services
Workspace creation and configuration C R/A
Lakehouse and Warehouse provisioning C R/A
OneLake data management R/A I
Connectivity
ADLS, SQL, Oracle and workspace-to-workspace connections C R/A
Managed private endpoints C R/A
Storage
Storage account provisioning and management I R/A
Customer-managed key rotation I R/A
Private endpoints for storage I R/A
Governance
Cost management (capacity) C R/A
Tagging C R/A
Management and monitoring
Platform monitoring I R/A
Workload monitoring R/A C
Platform alerts and notification configuration C R/A
Security
RBAC management C R/A
Customer-managed keys I R/A
Network isolation I R/A
Compliance alignment R/A C
Platform management
Terraform pipelines I R/A
Terraform modules and code I R/A
Workload Git repositories R/A C

In practice

Topic Platform team Workload team
Change Makes or reviews the pull request, runs the pipeline Raises the request. Opens the pull request for changes in its own scope.
Workspace content Items, data, models, notebooks, semantic models
Workspace admins (optional Admin group) Adds the group to the configuration Maintains the group membership and manages workspace users
Credentials of connections Reads them from the Key Vault by name Who stores the secret values and keeps them valid is agreed per deployment
Access to data sources Done outside this solution, at the source. Agree per source who grants it.
Failed baseline pipeline Retries, then reports to the owner Fixes the data or source issue
Recovery of workloads Recovers infrastructure and storage within RPO and RTO Recovers pipelines, notebooks, semantic models and data products
Compliance Aligns the technical configuration Formal certification and compliance
Grafana (optional) Deploys and administers, adds users to groups Builds dashboards and ingestion of pipeline logs

Self-managed

When the platform team is your own team, the platform column is yours: you own the Terraform repository, the pipelines and the monitoring, and you define support hours and response times yourself. Read the RACI as the default split of the solution.