“We opened a SharePoint list, connected Microsoft Forms, and the helpdesk is ready.” Three months later, nobody knows which ticket is with whom, the SLA report is calculated by hand in Excel and users still phone in. An organization using Microsoft 365 can build a serious IT support system with SharePoint, Power Apps, Power Automate and Teams without paying per user for a separate ITSM product; but to do so, the service model is designed first, then the data model and finally the interface. The steps below follow that order.
1. Write down the service model first
Before starting the technical setup, the following decisions should be put in writing:
- Record types: Incidents (something broke), service requests (something is wanted), changes (planned changes to a system) and security incidents are separate types and go through different flows.
- Service catalog and categories: Categories and subcategories such as hardware, software, accounts and permissions, email, network, ERP and printers; the responsible team for each category.
- Priority matrix: Automatic priority from an impact (how many people/processes are affected) × urgency (how long it can wait) table.
- SLA targets: First response and resolution targets for each priority; when the clock stops.
- Escalation chain: Who gets alerted at what percentage of the SLA.
- Roles: User, support staff, team lead, IT manager, auditor.
The category list should start short. A user who sees a dropdown with forty subcategories picks “Other” and the classification collapses. The approach that works in the field is to start with 8–12 main categories and split them after looking at three months of data. Don’t leave the priority matrix to the user either: ask users only about impact and urgency with plain questions, and let the system calculate the priority. Everyone marks their own request as “urgent”.
2. Build the data model
| List | Key fields |
|---|---|
| Tickets | Ticket no., type, category, subcategory, impact, urgency, priority, status, requester, assignee, team, created / first response / resolved / closed times, SLA targets, paused time, SLA status, related asset |
| Ticket activity | Ticket, action type (comment, internal note, status change, assignment), actor, time, visibility |
| Categories | Category, subcategory, responsible team, default priority |
| SLA definitions | Priority, first response (business minutes), resolution (business minutes), warning threshold |
| Working calendar and holidays | Day, start–end time, location; public holidays and half days |
| Assets (optional) | Device/application, owner, serial no.; can be fed from Intune via Graph |
Because SharePoint lists have a 5,000-item list view threshold, frequently filtered columns should be indexed from the start. Adding an index after the list has filled up can cause problems on a list that has passed the threshold; this is done on day one. Also bear in mind that a view can use at most 12 lookup-type columns; person and managed metadata columns count towards this number too. Adding every relationship to the ticket list as a lookup quickly uses up this limit.
Don’t build a formula for the ticket number based on the list ID in a calculated column. A calculated column produces an empty or wrong value because the ID hasn’t been assigned yet when the item is created. The number is written with Power Automate after the item is created.
If ticket volume is very high and complex relationships and row-level security are needed, Dataverse is considered; in that case additional licenses are required.
3. Separate the user and support team screens
The user portal should be simple: category selection, a short description, attachments, a list of their own tickets and status tracking. The support team screen, on the other hand, includes queues (assigned to me, my team’s, unassigned, at SLA risk), quick status changes, internal notes, merging and resolution codes. Both interfaces can be developed as Power Apps canvas apps and published as tabs in Teams.
Making sure users can’t see other people’s tickets and internal notes must be guaranteed with item-level permissions on the lists or with an architecture that provides access only through the application. Hiding them with a filter on a Power Apps screen isn’t security. A user with read permission on the list can open the list directly in SharePoint and see everything.
Take delegation warnings seriously on the support team screen. With a SharePoint data source, the Search() function isn’t delegable; by default Power Apps fetches only the first 500 records (up to 2,000 with the setting) and the search runs within that set. As the queue grows, old tickets “disappear” from search. In filters, delegation-supported expressions such as Filter() and StartsWith() are used on indexed columns.
4. Design the SLA engine
The SLA calculation is the part of a helpdesk that’s most often set up wrong. The source of the error is usually the same: the hour difference between two dates is taken, and nights, weekends and holidays are added to the duration. The right approach:
- When a ticket is created, the SLA targets (in business minutes) are read from its priority.
- Target times are calculated taking the working calendar and holidays into account.
- When the status is “awaiting user” or “awaiting vendor”, the start of the wait is recorded; when the status changes, the duration is added to the paused time field and the targets are pushed forward.
- A scheduled flow (e.g. every 15 minutes) checks open tickets; it sends a warning at the 75% threshold and an escalation when breached.
- First response is marked by the support staff’s first comment visible to the user; resolution by the “resolved” status.
Watch out for time zones. Power Automate processes date values in UTC; if the time isn’t converted to local time before comparing with working hours, the start of the working day shifts by three hours. Test scenarios must include a ticket opened on a Friday at 17:50, one opened on the eve of a holiday and one that spends the weekend in “awaiting user” status.
5. Connect notifications and Teams
Notifications shouldn’t create noise: ticket opened, response given and resolved notifications for the user; assignment and SLA warnings for support staff; escalations for the team lead. A system that sends an email on every field change gets redirected to the trash with an Outlook rule within two weeks. Cards sent to Teams as Adaptive Cards can include actions such as “take ownership” and “open”. For service requests that need approval (software installation, permission requests), Power Automate Approvals are used; details are in our approval flow guide.
The two flow mistakes we see most often in the field
The first is an infinite loop. If a flow triggered “when an item is modified” updates the same item, it triggers itself again. It’s restricted with a trigger condition so that it runs only when the relevant field changes or when the account making the update isn’t the service account.
The second is ownership. If flows and connections were created with the builder’s personal account, the helpdesk silently stops when that person leaves and their account is closed. Flows should run with the connections of a separate service account, have a second owner added and be managed within a solution.
6. Closure, reopening and satisfaction
A resolved ticket closes with the user’s confirmation or automatically after a set period. The user can reopen the ticket within a defined period; the number of reopenings is reported as a quality indicator. A reply email to a closed ticket should open a new record linked to the old one. A one-question satisfaction survey can be sent at closure. Long surveys don’t get filled in.
7. Reporting
The monthly report should include at least these indicators: tickets opened/closed, SLA compliance rate by priority, average first response and resolution time, workload by category, reopen rate, satisfaction and the most frequently recurring problems. The last indicator is the most valuable; a ticket opened every week for the same printer isn’t a support problem but an infrastructure problem. Sharing with Power BI may require additional licenses; in small setups, list views and Excel exports are enough to start with.
8. Verify licensing from the start
Microsoft 365 enterprise plans include Power Apps and Power Automate use with standard connectors such as SharePoint, Outlook, Teams and Approvals. Premium connectors such as Dataverse, SQL Server and HTTP, and Power BI sharing, require additional licenses (e.g. Power Apps Premium, Power Automate Premium, Power BI Pro). Adding a single premium connector halfway through the design can create a licensing need for everyone using the app. Since Microsoft licensing terms can change, design decisions should be verified against current Microsoft Learn licensing guides.
Frequently asked questions
What happens when the helpdesk list passes 5,000 records?
A list can hold millions of items; the 5,000 limit is the view threshold that can be scanned in a single query. Frequently filtered columns (status, assignee, category, created date) are indexed, views are filtered by these columns, and delegation-supported queries are used in Power Apps. Closed records can be moved to an archive list periodically.
How do we calculate SLAs correctly in Power Automate?
Business minutes are calculated instead of hour differences: working hours and holidays are read from a list, and waiting times are accumulated in a separate field on status changes. If the calculation is kept in a single child flow, all flows use the same logic and it becomes easier to test.
Can requests arriving by email automatically become tickets?
Yes. Messages arriving in a shared support mailbox can be turned into tickets with Power Automate; but rules must be defined for spam, auto-replies and linking reply chains to the existing ticket.
For audit evidence, see the helpdesk and ISO 27001/TISAX guide. For a turnkey setup for your organization: Microsoft 365 integrated helpdesk and SLA system. If you’ll use helpdesk records as audit evidence, organize processing and approval records within IT general controls and audit preparation.