Skip to content

Leave Request Approval in Teams with Power Automate

Leave requests by email get buried, and the shared calendar is never quite right. Here is how to run leave approval in Teams with a form, an approval step and the calendar updated for you.

| 4 min read

A calendar with one day highlighted, a sun, and a speech bubble with a checkmark

Leave request approval on Microsoft 365 needs three parts: a simple form where staff request leave, a Power Automate approval that goes to their manager in Teams or Outlook, and a flow that records the decision, updates a shared leave calendar and tells the employee. The manager approves with one click, and nobody keeps a separate spreadsheet of who is off.

In most small businesses, leave is requested by email, approved with a reply, and added to a calendar by whoever remembers. It works until two people in the same team are both off and nobody noticed.

What does a leave request process need?

Part What it does
Request form Dates, type of leave, a note. The employee's details fill themselves in
Approval Goes to the employee's manager in Teams and Outlook
Record Every request and decision kept in one list
Calendar Approved leave appears on a shared team calendar
Balance Days taken counted against the allowance, if you track it

How does the employee request leave?

Through a short Power Apps form, a Microsoft Form, or a form inside Teams. They pick the dates and the leave type and submit. The app can show their remaining balance and who else in the team is already off on those days, before they send it.

How does the manager approve it?

Power Automate sends an approval to the manager, found automatically from your Microsoft 365 org chart. It arrives in Teams and in Outlook, and the manager approves or rejects with an optional comment. The Approvals connector used for this is standard in Microsoft 365, as Microsoft notes in its approvals guide.

If the manager doesn't respond within the time you set, the flow reminds them, then sends it to a deputy. The reminder and escalation pattern is covered in How to Build a Power Automate Approval Flow.

What happens after approval?

The flow records the decision, adds the leave to a shared calendar so the team can see it, and tells the employee. If you track allowances, it updates the balance. If the request is rejected, the employee gets the manager's comment, and nothing is added to the calendar.

Does the org chart need to be right?

Yes, and this is the most common reason a leave flow sends approvals to the wrong person. The flow uses the manager recorded on each person's Microsoft 365 account. Check those before going live, and keep them updated when people change teams.

Frequently asked questions

Can it handle half days and different leave types? Yes. Leave type is a choice list, such as annual, sick, unpaid or study, and half days are an option on the form. Each type can follow its own approval rules.

Can HR see everything? Yes. HR sees every request and decision in one list, filtered by team, type or month, which replaces the spreadsheet they would otherwise keep.

What about sick leave that can't be requested in advance? The employee or their manager records it after the fact. It skips the approval and goes straight to the record and calendar.

Does this replace our HR or payroll software? No. If your HR software already handles leave, use it. This suits businesses that don't have one, or whose HR software doesn't connect to how the team works day to day.

Getting it set up

A leave approval is one of the quickest processes to move off email. A sign-off flow for one request type is a fixed price from $1,800 and goes live in two to three weeks. If you want to talk it through, book a 30-minute 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.