Industries → Cloud MSPs / M365 Partners
PSA built around the Microsoft 365 partner workflow
CIPP integration for tenant management. License tracking + seat-based recurring billing. RMM-attached endpoints on the customer record. M365 onboarding projects with milestone billing. The PSA for MSPs who live in the Microsoft partner ecosystem.
Why cloud MSPs deserve a different PSA
Cloud-focused MSPs don't ship hardware. They don't typically run on-prem RMM deployments. Their value is in identity, M365 tenant configuration, conditional access, license optimization, and the recurring billing that comes with all of it. A PSA built around field-tech dispatch + ticket SLA scoring is missing the layer they actually live in.
Capabilities cloud MSPs use most
CIPP Integration
Manage your customer Microsoft 365 tenants from inside OriginPSA. Surface license counts, user provisioning, conditional access policies on each customer record. Sync runs on demand or scheduled — no manual reconciliation between CIPP and your PSA.
Per-Customer M365 License Tracking
Customer's purchased license counts (E3, E5, Business Standard, Premium) live on the customer record. Reconcile against actual assigned counts via CIPP. Surface the gap (over-allocated, under-allocated) on the billing review screen so you don't bill for seats they're not using.
Recurring Seat-Based Billing
Recurring invoice templates with seat-count pegged to actual M365 assignments. Customer adds a user in M365 → next invoice picks up the additional seat automatically. Pro-rate mid-cycle changes if your contracts require it.
RMM Integration for Cloud-Attached Endpoints
NinjaOne RMM integration surfaces device + organization sync directly into OriginPSA. Cloud-managed endpoints, M365 tenants, and RMM device records all live on the same customer record — no triple lookup across vendor portals.
M365 Tenant Onboarding Projects
M365 cutover work runs as a real project: phases (discovery, identity sync, mailbox cut, post-cut hypercare), milestones tied to license activation, signed change orders if scope grows. Customer sees status via the portal without seeing internal cost.
SAML SSO via Entra ID
Your tenant's staff log into OriginPSA via Entra ID SAML — the same identity store you're already managing for the customer base. No separate user list, no separate MFA enrollment.
Common workflows
- Per-customer seat billing on the recurring invoice. License count flows from CIPP → customer record → recurring invoice template. Customer's monthly invoice reflects the actual seats they're consuming, not the original signup count.
- Conditional access + retention as billable services. Configure conditional access policies, retention rules, and DLP on the customer's M365 tenant via CIPP, log the work as a project, bill via milestone or T&M. The work surface and the billing surface are the same record.
- Cross-customer M365 reporting. Sum license consumption across all your customers for vendor renewal forecasting. Built-in reports show seats by SKU, by customer, by month — no spreadsheet export from CIPP required.
What it's not
OriginPSA includes a CIPP integration — it's not a CIPP replacement. You still run your CIPP instance; OriginPSA reads + writes through it on a schedule and surfaces the results on your customer records. If you don't use CIPP today, the M365 features still work via direct Microsoft Graph integration for inbound email, calendar, and SSO — but the deeper tenant-management story assumes CIPP.