Skip to content
MSP Business

UniFi Fabrics for MSPs: How to Run Client Sites in Site Manager

Scopable Team12 min read
UniFi Fabrics for MSPs: How to Run Client Sites in Site Manager

UniFi Fabrics is how an MSP runs a portfolio of UniFi client sites from Site Manager: one Fabric per client, your techs in an MSP Group, roles scoped by site, and Blueprints for new sites. Ubiquiti made it official in April 2026 with no license fee, and the MSP pieces kept landing through the summer.

The tooling is good now. The part that still goes wrong is the business layer: who owns each console, which changes are included in support, and which Fabric work is a project you should be quoting.

Quick answer

UniFi Fabrics groups a client's UniFi sites in Site Manager under shared people, roles, policies, and orchestration. For MSPs, the working model is one Fabric per client, attached to your MSP account by the client's invitation, with your team managed centrally through an MSP Group and your identity provider. The tooling handles access and configuration. Ownership, approvals, and billing are still yours to define.

Quote the Fabrics migration as project work

Split ownership cleanup, UniFi OS migration, identity setup, Blueprint build, and API reporting into scoped line items, then carry them onto the client roadmap for the QBR.

How MSPs set up Fabrics today

Ubiquiti's April 2026 post, "The New Site Manager - Now Official", brought sites into a unified Fabric with role-based management, identity provider integration, cross-site visibility, the Orchestration Engine and Canvas, a new API, and no licensing fees. Its January post, "Introducing UniFi Fabrics", had framed it as early access with isolated customer environments and device templates.

The MSP layer came after that. Ubiquiti's Site Manager 5.8 release notes (July 2026) added MSP Groups: create your MSP team, import employees from your identity provider, and manage their access across customer Fabrics from one place. The same release lets you require SAML sign-in through your IdP for Fabric and MSP Group admins.

In practice the setup looks like this:

  1. Each client gets its own Fabric. Sites can move between Fabrics without an ownership transfer, so you can clean up a messy portfolio without rebuilding it.
  2. The client invites you. ShiftCTRL's walkthrough of MSP access (August 2026) describes the customer sending the invitation from their own account, with your team joining as invited admins rather than owners. The client keeps the Owner role unless you agree otherwise.
  3. Your techs live in an MSP Group. Import them from Microsoft Entra or another IdP, then assign roles per Fabric, per site group, or across all sites. Ethan F's Fabrics SSO write-up notes that imported users start with no site access, which is the right default.
  4. Offboarding happens in the directory. Disable the employee in your IdP and their access across every customer Fabric goes with it. Site Manager 5.7 added deactivation for IdP-synced users.

That last point is the quiet win. Before MSP Groups, a departing tech could still be an admin on 40 client consoles because nobody remembered to remove them.

What Blueprints and Canvas change

Blueprints are reusable site templates generated from an existing site. Ubiquiti's Site Manager 5.5 release notes list WiFi, networks, firewall, DNS, protection, content filtering, and network lists as covered, with Network 10.3 and UniFi OS 5.1 as the floor. Site Manager 5.7 added applying a Blueprint to a site that already exists, which matters more to MSPs than greenfield builds.

Zero Touch Provisioning sits on top. You pre-build the site in the Fabric, the installer uses a Magic Link on site, and the site comes up with your VLANs, firewall policies, and SSIDs already in place.

Canvas pushes settings from the Fabric down to sites. Ghost Syght's review (May 2026) notes that Canvas-enforced settings can't be changed from the site's own Network application. Good for drift. Bad if a tech fixes something locally at 6 p.m. and doesn't realize the Fabric will win.

For an MSP, that changes three things:

  • Standards become enforceable. A firewall rule set you push once is the same at every site, which makes your standard real instead of aspirational.
  • Mistakes travel faster. A bad change pushed from the Fabric hits every site in it. Change approval needs to be written down before you lean on this.
  • Onboarding gets priceable. When a new site is a Blueprint plus an install, you can quote it as a repeatable package with a known labor range.

The margin risk is in the second bullet. A cleaner admin layer reduces repetitive work, and it can also create quiet revenue leakage if every new template, exception, and rollback turns into free engineering.

The MSP decision table

Decision areaBefore FabricsWith Site Manager, Fabrics, and MSP GroupsWhat MSPs still need to define
Multi-site administrationController-by-controller workOne Fabric per client, all visible from your MSP accountWhich client environments belong in the standard model
Tech accessIndividual invites on every consoleMSP Group synced from your IdPWho approves admin access, emergency access, and role changes
Client boundariesBuried in the MSP's internal processClient owns the Fabric and invites the MSPWho owns each console, billing relationship, and recovery path
New sitesHand-built from memory or a runbookBlueprints and Zero Touch ProvisioningWhat the standard site includes and what counts as an exception
Configuration driftFixed when someone noticedCanvas enforces Fabric-level settingsWho can change the Fabric standard and how changes are approved
API workDirect controller access was often requiredFabric API and Cloud Connector through UniFi CloudWhich reports, scripts, and automations are included in support
Quote scopeNetwork changes were easy to absorb casuallyStandardization can be packaged more clearlyWhat is recurring support versus billable project work

This is why Fabrics belongs in sales operations as well as engineering chat. If you standardize on Ubiquiti, it affects discovery, scope, QBRs, quoting, and renewals.

The API is useful, and it is still project work

Ubiquiti's Site Manager 5.5 release notes consolidated the API documentation across UniFi applications, added API key scopes at the site and application level, and introduced a Cloud Connector that proxies API requests through UniFi Cloud to the console (UniFi OS 5.0.9 or newer).

Art of WiFi's comparison of local admin, direct API keys, and Site Manager API keys explains why that matters. Going through unifi.ui.com avoids direct controller reachability, which helps with client sites behind CGNAT, dynamic IPs, or restrictive firewalls. The same article notes the trade: you depend on Ubiquiti cloud, the console must be cloud-adopted, and the legacy self-hosted Network Application is out.

Ghost Syght calls the API "early days," and that matches what MSPs report. So define API work like a project before you promise it:

  • Which data will be pulled?
  • Which actions, if any, can be changed by script?
  • Which clients are eligible?
  • What happens when Ubiquiti cloud is unavailable?
  • Who reviews API keys and their scopes?
  • What reports are promised to the client?

If the answer is "we'll figure it out later," it is not ready for your managed services agreement.

What MSPs should quote differently

Fabrics makes standardization more attractive and raises the cost of sloppy scope. If UniFi is your preferred network standard, put it on the client roadmap as a real sequence: discovery, ownership cleanup, console architecture, firmware readiness, identity model, migration, acceptance criteria, and support handoff.

That belongs in your MSP project scoping process and in the scope of work template, because client expectations will not respect your internal boundaries unless you write them down. For a UniFi-specific starting point, the UniFi project scope template covers survey, hardware, labor, and handoff lines.

Quote these items separately when they apply:

  • Ownership cleanup: moving from personal vendor accounts, ex-employee access, or mystery admin roles to a client-owned Fabric with documented control.
  • Architecture migration: shifting from legacy self-hosted Network Application into a UniFi OS console or UniFi OS Server model that Site Manager supports.
  • Identity setup: binding the client's IdP, mapping groups to roles, enforcing SSO, and setting an admin review cadence. Ghost Syght lists the consoles that support IdP binding (UDM Pro, UDM SE, UDM Pro Max, EFG, UNVR Pro, ENVR, ENVR Core) and UniFi OS 4.4 or newer, so older gateways may turn identity work into a hardware line.
  • Blueprint build: turning your standard into a Blueprint, testing it on one site, then applying it to existing sites.
  • Reporting and API work: anything beyond basic health review, especially custom dashboards or automated evidence.
  • Exception handling: sites that cannot move yet because of business constraints, hardware age, compliance needs, or client politics.

This is also a margin conversation. If the standard reduces ongoing support work, price the recurring agreement accordingly. If it creates migration labor, quote it. The margin protection guide for MSP pricing and quoting gets into that split, and the MSP quoting software workflow shows how the line items carry from roadmap to quote.

Practical checklist before you standardize on UniFi Fabrics

Use this before putting Fabric work into a roadmap or quote.

  • Confirm client ownership. Know who owns each Fabric, each console, each admin role, and each recovery path. The client should own their Fabric.
  • Verify platform eligibility. Check UniFi OS and Network versions against what you plan to use: IdP binding, Blueprints, and the Cloud Connector each have their own floor.
  • Build your MSP Group first. Import techs from your IdP and give them no access by default. Add roles per client as work is approved.
  • Map permissions by role. Do not give every tech global admin because it is faster on Tuesday.
  • Name the cloud dependency. If the client will not accept Ubiquiti cloud dependency, say so in the proposal instead of a technical footnote.
  • Write the change-approval rule. Canvas and Blueprints make a bad change travel faster. Decide who can change the Fabric standard.
  • Separate support from projects. Firmware cleanup, controller migration, Blueprints, reporting, and API work should have clear billing treatment.
  • Tie it to QBRs. Use the MSP QBR to show what changed, what risk dropped, and what still needs budget.

The checklist is boring on purpose. Boring is where MSP margin survives.

When Fabrics is a good fit

Fabrics makes sense when you manage a meaningful number of UniFi client sites and your team spends real time bouncing between consoles, fighting remote controller access, or rebuilding the same network by hand. MSP Groups alone pay off once you have more than a handful of techs touching client networks.

It also fits clients mature enough to care about governance. Role-based access, IdP-backed admin, and audit-friendly change habits are easier to sell when the client already treats network administration as business risk.

Ubiquiti's July 2025 post on UniFi OS Server for MSPs covers the self-hosted side. It describes UniFi OS Server as a way to host the control plane for many customer sites, with Site Manager as the cloud overlay for fleet health, role-based global admin, SSO, SD-WAN orchestration, policy objects, and audit trails.

When Fabrics is the wrong move

Skip it when the client refuses the cloud dependency that Site Manager and its API require. Skip it when the environment is stuck on legacy self-hosted Network Application and nobody wants to fund the migration. Skip it when the MSP has no internal permission model and hopes the tool will create discipline by vibes.

It also does not replace discovery. If you do not know what the client has, who owns it, what is failing, and what they can afford, Fabrics gives you a cleaner place to be wrong.

Related UniFi decisions

Fabrics usually shows up alongside another decision. These cover the common ones:

Bottom line

UniFi Fabrics, with MSP Groups and Blueprints, is a workable way for MSPs to run many UniFi clients from one place: client-owned Fabrics, IdP-backed tech access, and repeatable site builds with no license fee.

The business value still depends on scope. If Fabrics reduces admin toil, capture that in your managed services model. If it creates migration, identity, Blueprint, or API work, quote it. If it changes client risk, put it on the roadmap and bring it back to the QBR.

Scopable is not a UniFi operations tool. It helps MSPs turn standards, gaps, budgets, and client priorities into roadmaps, quotes, and follow-through. If Fabrics becomes part of your network standard, that decision should show up before the client asks, "So what are we paying for next quarter?"

Frequently Asked Questions

What is UniFi Fabrics for MSPs?

UniFi Fabrics is Ubiquiti's management layer over Site Manager for grouping multiple UniFi sites under shared administration and identity. For MSPs, the value is cleaner fleet visibility and role-based controls across client sites, not a replacement for scope, support ownership, or client approvals.

Is UniFi Site Manager useful for MSPs?

Yes, if you manage many UniFi sites and need one place to see site health, assign roles, and use SSO. MSP Groups let you sync your techs from your identity provider and manage their access across each client's Fabric. It does not remove the need to document who owns the console, who approves changes, and which work is included in the agreement.

Can MSPs use the UniFi Fabrics API?

Ubiquiti says Fabrics includes API-driven workflows and a Fabric API, and Art of WiFi notes Site Manager API keys connect through unifi.ui.com. Treat API work as billable engineering scope until you know the endpoints, auth model, and reporting requirements.

What are the risks of UniFi Fabrics for MSPs?

The main risks are cloud dependency, permission sprawl, unclear client ownership, and assuming multi-site visibility equals support scope. Art of WiFi notes the Site Manager API depends on Ubiquiti cloud and does not support legacy self-hosted Network Application.

Should MSPs standardize clients on UniFi Network?

Standardization can reduce training and quoting friction when the client fit is real. Do not force it into every environment. Scope discovery, migration work, firewall policy, support boundaries, and exception handling before you quote it.

Buyer path

Where this fits in Scopable

This article feeds the assessment and scoping cluster: collect findings, choose recommendations, and turn the real work into scope.

See assessment and scoping