Compare build and buy
A SharePoint helpdesk you build, or a service desk that runs on SharePoint
Plenty of IT teams build a helpdesk from SharePoint lists and Power Automate. It can work well. Here is what that build gives you, the platform limits it meets, and what a finished service desk such as Orbit ITSM adds.
What a do-it-yourself build gets right
A SharePoint list for tickets, a form for requests and a few flows for email can be stood up quickly by someone who knows Microsoft 365. Small teams ask for exactly this: tickets raised from Teams, as simple as possible, without another app.
- Uses the Microsoft 365 licences you already have for a basic build.
- Your data stays in your tenant, under your permissions.
- You own it completely and can change anything.
- A small company on Microsoft Q&A describes a shared Teams channel where everyone sees every request, and asks how to create tickets from Teams with SharePoint. Source: Microsoft Q&A: ticketing in SharePoint and Teams ↗, as at 22 Oct 2026.
Platform limits a build runs into
These come from Microsoft's own documentation and apply to anything built on SharePoint lists and Power Automate.
- SharePoint Online's list view threshold is 5,000 items by default. Views and queries that touch more items than that are blocked unless the list is designed around it. Source: Microsoft Learn: list view threshold ↗, as at 23 Oct 2026.
- A cloud flow that keeps failing, or is consistently throttled, for 14 days is turned off. Source: Microsoft Learn: Power Automate limits ↗, as at 23 Oct 2026.
- Premium connectors and some Power Apps designs need licences beyond standard Microsoft 365 plans; Microsoft Q&A has tenants being prompted for a Power Apps licence. Source: Microsoft Q&A: Power Apps asking for a licence ↗, as at 22 Oct 2026.
What a finished service desk adds
The hard part of a helpdesk is rarely the list. It is the process around it, and who keeps it running a year later.
- Requests, incidents, approvals, assets, onboarding and offboarding, and a knowledge base, already designed to work together.
- Process aligned with ITIL and ISO practices (aligned, not certified).
- Approvals in Microsoft Teams or Outlook, where people already work.
- Someone else maintains it, instead of the one person who built the flows.
Orbit runs on the same platform
Orbit ITSM keeps its records in SharePoint, signs people in with Entra ID and runs workflows in Power Automate. That keeps data in your tenant, but it also means Orbit meets the same platform limits as a build: the list view threshold, flow limits and Microsoft licensing still apply.
Ask us to show how Orbit's lists and flows are set up for your expected volumes before you commit.
| Build it yourself | Orbit ITSM | |
|---|---|---|
| Where data lives | Your tenant | Your tenant |
| Platform limits | Apply | Also apply |
| Licence beyond Microsoft 365 | None for a basic build | One flat annual Orbit licence per organisation (not per agent, no tiers): ask us |
| Process design | Yours to design | Built in, ITIL-aligned (not certified) |
| Ongoing upkeep | Whoever built it | Maintained product, with full source code |
| Track record | Your own | New, no customers yet |
When to keep building it yourself
- You have a handful of requests a week and one person handling them.
- You have someone who enjoys maintaining flows and has time to.
- You want no licence beyond Microsoft 365 at all.
Where Orbit falls short
- Orbit is new and there are no customers yet, so there are no references or reviews to check.
- Reporting is lighter than in mature service desk platforms.
- Mature platforms have years more depth in asset discovery, CMDB, add-on marketplaces and mobile apps.
- Orbit's flat annual fee is not published yet, so there is no figure to compare until you ask us.
- Orbit is aligned with ITIL and ISO practices, not certified.
Next steps
Click through the live demo, then book 20 minutes and we’ll go through it against how your service desk runs today.
The demo runs as Vertex Group, a fictional organisation, with fictional data.
Sources
- Microsoft Q&A: ticketing in SharePoint and Teams ↗ (as at 22 Oct 2026)
- Microsoft Learn: list view threshold ↗ (as at 23 Oct 2026)
- Microsoft Learn: Power Automate limits ↗ (as at 23 Oct 2026)
- Microsoft Q&A: Power Apps asking for a licence ↗ (as at 22 Oct 2026)
Competitor details change. Check the source before you rely on a figure. Product names are trademarks of their owners.