Skip to content

A Maintenance Request System on Microsoft 365: SharePoint List, Power Apps and Power Automate

Fault reports by email and phone get lost. Here is how to run maintenance requests on the Microsoft 365 you already have, with one register of jobs, an owner for each, and reminders when work stalls.

| 9 min read

A wrench beside a phone showing a list of maintenance jobs with status labels and a small bell for reminders

A maintenance request system on Microsoft 365 uses a SharePoint list as the register of jobs, a Power Apps form or a Microsoft Form for reporting faults, and Power Automate to route each job to the right person, chase it when it stalls, and get sign-off before it closes. For most facilities teams, all of it runs on standard licences.

The usual starting point is a shared inbox, a phone at reception, and a spreadsheet someone updates when they can. Jobs get done. Nobody can say which ones have been open for three weeks.

What does a maintenance request system need to do?

Five things, whatever the size of the portfolio. Take in a fault from anyone who spots one, give it a single owner, let the person who reported it see where it stands, chase it when it stalls, and have someone check the work before the job is closed. Everything else is a refinement of those five.

  1. Intake. One way in for every fault, so nothing lives only in a corridor conversation.
  2. Ownership. Each job goes to one named person, picked by building and trade.
  3. Visibility. The reporter can see the status without phoning anyone.
  4. Follow-up. Overdue jobs are chased automatically, then escalated.
  5. Sign-off. Finished work is checked before the job closes, and before a contractor is paid.

Should requests go in a SharePoint list or Dataverse?

A SharePoint list, for most in-house teams. It comes with Microsoft 365, it is quick to set up, and staff can open it in a grid view when they want to scan everything at once. Choose Dataverse when you track assets with their own maintenance history, or when contractors must see only their own jobs.

What you need SharePoint list Dataverse
One register of jobs for an in-house team Good fit More than you need
A maintenance history for each asset Possible with lookups, gets awkward Built for it
Contractors who see only their own jobs Item-level permissions, hard to maintain Row-level security
Licence for the people using the app Standard, usually covered by Microsoft 365 Premium, per app or per user

The trade-offs are covered in more depth in Dataverse vs SharePoint Lists. The rest of this article assumes a list, because that is where most facilities teams should start.

What should the request list look like?

Two lists. A Requests list holds the jobs, and a small Routing list says who owns each combination of building and trade. Keeping ownership in its own list means that when a technician leaves, you edit one row instead of editing a flow, and your supervisor can make that change without calling a developer.

The Requests list needs these columns, and very little else:

Column Type Why it is there
Building and location Choice or lookup So jobs can be routed and grouped
Trade Choice Plumbing, electrical, HVAC, general
Priority Choice Decides the due date and who hears first
Description Multiple lines of text What the reporter saw
Reported by Person Who gets the status updates
Assigned to Person The single owner
Status Choice New, Assigned, In progress, Awaiting parts, Awaiting check, Closed
Due date Date Set by the flow from the priority

Photos go in as attachments on the item. Keep them modest. Microsoft's performance guidance for canvas apps (checked November 2026) notes that image and attachment sizes slow down how fast list data reaches the app, and that every column defined on the list is sent back with each record, whether the app uses it or not. Both are good reasons to keep the list lean.

How do tenants and staff report a fault?

Through two front doors that feed the same list. Your own staff use a Power App on their phones, which knows who they are, lets them pick the building from a list and attaches a photo. Tenants, visitors and anyone outside your Microsoft 365 tenant use a Microsoft Form, which a flow copies into the list as a new request.

The form route uses the Microsoft Forms trigger, When a new response is submitted, followed by Get response details, which Microsoft describes in its overview of flows with Microsoft Forms. The flow then creates the item in the Requests list, so from that point on a tenant's report and a technician's report are handled identically.

How does Power Automate route, chase and escalate jobs?

With three flows. The first assigns each new job and confirms it to the reporter. The second runs every morning and chases anything past its due date. The third asks for sign-off when a technician marks a job as done. Together they replace most of the follow-up a coordinator now does by hand.

Flow 1, on a new request. Look up the owner in the Routing list by building and trade, fill in Assigned to, work out the due date from the priority, and notify the owner by email or a Teams message. Send the reporter a confirmation with the item number, so they have something to quote.

Flow 2, every morning. A scheduled flow finds jobs that are not closed and are past their due date. It reminds the owner, and once a job has been overdue for longer than you have agreed, it tells their manager as well, using Get manager (V2) from Office 365 Users. How long "too long" is should be agreed with the team before you build. That number is a management decision.

Flow 3, when status changes to Awaiting check. Send an approval to the building manager or the person who reported it. Approve, and the job closes with the date recorded. Reject, and it goes back to In progress with the reviewer's comment attached.

Approvals have one limit to design around. A cloud flow run lasts at most 30 days, and pending steps such as approvals time out after that, according to Power Automate's limits page (checked November 2026). Give the sign-off its own timeout, well inside that window, and decide what happens when it expires. The full pattern, with reminders and escalation, is in How to Build a Power Automate Approval Flow.

How does the person who reported it see progress?

They hear about it without asking. The simplest version is an email from the flow at each status change: assigned, in progress, done. Staff who use the app also get a "My requests" screen showing their own reports. Either way, "has anyone looked at this?" stops arriving at reception.

Notify on status changes only. An email for every edited description is noise.

What licences does a maintenance system need?

On the design above, standard ones. SharePoint, Microsoft Forms, Office 365 Outlook, Office 365 Users, Teams and Approvals are all standard connectors. Microsoft classes an app that only uses standard connectors as a Standard app, which people can run with a Power Apps for Office 365 plan, as well as with a per app or per user plan.

That definition comes from Microsoft's page on app license designation (checked November 2026). Moving the data to Dataverse, or calling a building-management system through a custom connector, makes the app Premium, and each user then needs a per app or per user plan. The Approvals connector is standard too, according to Microsoft's approvals guide.

What goes wrong in a typical first version?

Location typed as free text. "Block B", "B block" and "Bldg B" are three buildings to a flow. Use a choice or a lookup.

No owner for a building and trade combination. The flow has nowhere to send the job, and it sits unassigned. Give every combination an owner, even if it is a fallback.

Closing without a check. If the person who did the work also closes the job, the sign-off step exists on paper only.

Frequently asked questions

Can tenants report faults without a Microsoft 365 account? Yes. A Microsoft Form can be set so that people outside your organisation can respond, and a flow turns each response into a request. Ask for an email address on the form, because that is the only way the flow can send them updates.

Can it handle planned maintenance as well as reactive jobs? Yes. Keep a list of planned tasks with how often each repeats, and a scheduled flow creates the job in the Requests list when one falls due. From then on it is routed and chased like any other request.

What about plant rooms and basements with no signal? A canvas app can be built to work offline, with some conditions on how it runs and where the data lives. They are set out in How to Build an Inspection App in Power Apps.

When should we move from a list to Dataverse? When you start tracking assets with their own history, when contractors need access limited to their own jobs, or when several apps work on the same data. Plan that move, rather than discovering it is needed once the list is full of live jobs.

Getting it set up for your buildings

The facilities and property management page shows what this looks like across requests, inspections and visitor logs, and how a project with me runs. If you want to talk through how faults reach your team today, book a free 30-minute consultation. If a list and a form will do the job without me, I'll tell you on the call.

Last updated

Working through this on a real project?

30 minutes, no cost, no pitch. Describe what you are building and I’ll tell you what I would do.