Retainer
Managed Fabric Administration
A foundation stays governed only if someone keeps it that way. This retainer is that someone: capacity, cost, workspaces, access, refreshes, and the shared models, watched and maintained month to month.
What it covers
The estate, kept in the state you paid for
- Capacity and cost. Utilization watched, refresh windows kept from colliding, and a monthly cost report leadership can read.
- Workspaces and access. New workspaces created to the standard, access granted the right way, sprawl caught early.
- Refresh failures. Diagnosed and fixed at the cause: extract, model, or schedule.
- Semantic model lifecycle. Changes to shared models made without breaking the reports that depend on them; retired content actually retired.
- Governance upkeep. The ownership register, certification labels, and catalog kept current as the estate changes.
Who it is for
Teams that own Fabric but cannot staff it
Most healthcare reporting teams are sized for building reports, not for administering a capacity-based platform. The retainer covers the administration so the team keeps building. It follows naturally fromFabric Foundations, and it also fits estates that were stood up elsewhere.
Terms
Tiers, response times, and price
Next step
Describe your estate
Capacity size, workspace count, and how many shared models you run is enough to size the retainer.