Skip to content

How to Automate Access Requests and Approvals with Power Automate

Access requests by email leave no record, no owner and no end date. Here is how to run them through Power Automate so every grant is approved, logged, and removed when it should be.

| 6 min read

A key with an open padlock in its handle and a small clock, for access that is granted and later expires

To automate access requests with Power Automate, capture each request in a SharePoint list or Dataverse table and route it to the person who owns the resource for approval. Grant the access automatically where a connector can do it safely, or hand it to IT as a task. Give every grant an end date so access gets reviewed or removed instead of piling up.

Most teams handle access the same way: someone emails IT, IT forwards it to a manager, the manager replies "fine", and someone adds the person to a group. It works until an auditor asks who approved a particular person's access to the finance site, and the only answer is a search through three inboxes.

What goes wrong with access requests by email?

Three things, and they get worse the longer the process runs.

  • There is no record. The approval lives in someone's inbox. When that person leaves, so does the evidence.
  • The wrong person approves. A line manager can confirm that someone needs access, but only the owner of the system knows what access they should get. Email tends to skip the owner.
  • Access never ends. People change roles and keep everything they had before. Nobody removes access, because nothing reminds anyone to.

The third one is the expensive one. It is also the one automation fixes best.

What should an access request process look like?

Five steps. Each one does a job that email leaves undone.

  1. Request. A form (Microsoft Forms, or a Power App if you need lookups and validation) that asks what access, for whom, why, and until when.
  2. Record. The flow writes the request to a SharePoint list or Dataverse table before anything else happens. That record is the audit trail, and it shows the status to everyone involved.
  3. Approve. First the requester's manager confirms the need. Then the resource owner confirms the access level. Two stages, in that order.
  4. Provision. Grant the access automatically where it is safe to, or create a task for IT with the approved request attached.
  5. Expire. On the end date, the access is reviewed or removed, and the record shows which.

Which access can Power Automate grant on its own?

Approval can always be automated. Granting the access depends on whether a connector can do it, and on whether you want a flow holding that permission.

Access type Who should approve Can the flow grant it?
Microsoft 365 group or Teams team Group or team owner Yes. The Office 365 Groups and Microsoft Teams connectors have "add member" actions.
SharePoint site or site group Site owner Yes, through Send an HTTP request to SharePoint, run under an account that owns the site.
Security group in Entra ID Group owner Often. The Microsoft Entra ID connector can add users to groups. Check its licensing tier in your tenant first.
Shared mailbox Mailbox owner Usually not directly. Approve in the flow, then create a task for IT.
Line-of-business system System owner Depends on the system's API. Most teams approve in the flow and provision by hand.

A rule of thumb: automate the grant when the action is reversible and scoped to one resource. Leave it to a person when it touches anything tenant-wide.

How do you build the approval part?

Use one flow per request type, triggered when a new item lands in the requests list.

  • Stage 1, manager: Get manager (V2) on the requester, then an approval to that person. If they reject, update the record and tell the requester why.
  • Stage 2, resource owner: look the owner up from a small "Resources" list (resource name, owner, provisioning method), so ownership lives in data rather than inside the flow. Then send the second approval.
  • Reminders and escalation: an approver who goes quiet stalls everything. Give each approval a timeout, send a reminder when it times out, and escalate after a few days. The pattern is covered step by step in How to Build a Power Automate Approval Flow, and there is a reference build on GitHub with the settings and expressions.

Write the status back to the record at every step: Pending manager, Pending owner, Approved, Provisioned, Rejected, Expired. That one column answers most of the questions people would otherwise send by email.

How do you stop access piling up?

Give every request an end date, even if the default is a year away. Then add a second, scheduled flow:

  1. Run once a day.
  2. Find records where the end date has passed and the status is still Provisioned.
  3. Either remove the access (where the flow granted it) or send the resource owner a short approval: keep for another period, or remove?
  4. Record the outcome and the date.

This is the part auditors ask about, and the part almost nobody has when the process runs on email. It also turns the requests list into something useful: a live register of who has access to what, and why.

Do you need premium licensing?

Not for the core process. A SharePoint list, Microsoft Forms, the Approvals connector, Office 365 Users and Outlook are standard connectors, covered by the Power Automate rights in most Microsoft 365 business plans.

Premium comes in when you store requests in Dataverse, call a system through a custom connector, or use a connector your tenant classes as premium. Check these before you design, because they change where the record lives.

Where to start

Pick the access request your IT team handles most often. For most organisations that is Teams or SharePoint site membership. The flow can grant it end to end, so the improvement shows up in the first week.

Once that runs cleanly, add the expiry flow, then add other request types by adding rows to the Resources list rather than writing new flows. If you would rather have it built and fitted to your own approval chain, that is what I do under approval workflow automation.

Frequently asked questions

Can Power Automate grant access automatically? Yes, for anything a connector can change: Microsoft 365 group and Teams membership, SharePoint site groups, and Entra ID groups through the Entra ID connector. For anything else, the flow handles the approval and creates a task for whoever provisions it.

Who should approve an access request? Two people: the requester's manager, who confirms the need, and the resource owner, who confirms the access level. Keep a list of resources and their owners so the flow can look the owner up instead of hardcoding names.

How do I make sure access gets removed? Store an end date on every request and run a daily scheduled flow that removes expired access, or asks the owner to renew it. Record the outcome on the same item, so the list doubles as an access register.

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.