Integrating Microsoft Teams with leave management brings absence tracking into the collaboration platform your team already uses. Instead of switching between Teams and a separate leave system, employees can request leave, managers can approve it, and the team can see who is available — all within Teams. This reduces friction, speeds up approvals, and keeps absence information visible where work decisions happen.
This guide covers how to set up and use a Teams integration for leave management, including request workflows, approval processes, and team visibility.
Key Takeaways
- Teams integration centralises leave management in the platform your team uses daily.
- Adaptive cards or tabs provide structured leave request forms inside Teams.
- Approval notifications appear in Teams with one-click approve/decline.
- Out-of-office status updates automatically when leave is approved.
- The leave management system remains the source of truth — Teams is the interface.
Step 1: Choose a leave management system with Teams integration
When evaluating leave management systems, check for Microsoft Teams compatibility:
- Native Teams integration — the system provides a Teams app from the Microsoft AppSource marketplace.
- Adaptive cards — structured forms that display directly in a Teams chat or channel.
- Tab integration — a leave management tab pinned to a Teams channel showing the team calendar.
- Power Automate connectors — workflow automation between Teams and the leave system.
- Outlook integration — approved leave syncs with Outlook calendar automatically.
Many modern leave management systems offer native Teams integration. If yours does not, check for Power Automate or Zapier connectors.
Step 2: Install the Teams app
- Open Microsoft Teams and go to Apps.
- Search for your leave management system in the AppSource marketplace.
- Click Add to install the app in your Teams workspace.
- Authorise the integration with your leave management system credentials.
- Pin the app to relevant team channels for easy access.
Installation typically requires Teams admin permission. If you do not have this, request it from your IT administrator.
Step 3: Configure the leave request workflow
Set up how employees initiate leave requests from Teams:
Option A: Adaptive card
- Employee types a command (e.g.,
/leave request) or clicks a button in the leave app. - An adaptive card appears in the chat with fields for leave type, start and end dates, and reason.
- Employee fills in the form and submits.
- The request is sent to the leave management system and the manager.
Option B: Tab form
- A leave management tab is pinned to the team channel.
- Employee clicks “Request Leave” in the tab.
- A form opens within the tab.
- Submission flows to the leave management system.
Option C: Bot conversation
- Employee sends a message to the leave bot in Teams.
- The bot responds with a conversational form to collect the details.
- The request is processed.
Step 4: Set up approval notifications
Configure how managers receive and act on leave requests in Teams:
- Notification in Activity — the manager receives a Teams notification with the request details.
- Adaptive card with actions — the notification includes Approve and Decline buttons.
- One-click approval — the manager clicks a button and the decision is recorded.
- Chat notification — the leave bot sends a message to the manager’s chat with the request summary.
- Escalation — if the manager does not respond within a defined period, the request escalates.
The goal is to make approval a single action within Teams, not a login to a separate system.
Step 5: Enable team visibility
Make absence information visible within Teams:
Out-of-office status
- When leave is approved, the integration updates the employee’s Teams status to “Out of office” with the return date.
- The status automatically reverts when the employee returns.
Team calendar tab
- Pin a leave calendar tab to the team channel.
- The tab shows all approved leave for the team, colour-coded by leave type.
- Team members can see who is off on any given day.
Channel announcements
- A dedicated channel (e.g., “Team Leave”) receives automated posts when leave is approved.
- Posts include the employee’s name, dates, and leave type.
Outlook calendar sync
- Approved leave syncs with the employee’s Outlook calendar.
- Colleagues see the absence when scheduling meetings.
Step 6: Handle unplanned absences
For sick leave or emergency absence:
- Employee sends a message to their manager or in a team channel.
- The employee (or manager) logs the absence using the leave bot.
- The system records the absence and updates the team status.
- A return-to-work reminder is set for the next working day.
No approval is required for unplanned absence — it is logged, not requested.
Step 7: Use Power Automate for advanced workflows
Power Automate connects Teams to your leave management system for custom workflows:
- Auto-notify — when a leave request is submitted, Power Automate sends a notification to the manager in Teams.
- Approval chain — build multi-level approval flows where the request routes to different approvers based on leave type or duration.
- Calendar sync — automatically create an Outlook calendar event when leave is approved.
- Reporting — trigger a weekly absence summary posted to a Teams channel.
Power Automate connectors are available in the Power Automate portal and can be configured without code.
Common Teams integration mistakes
1. Making Teams the source of truth
Teams is the interface. The leave management system is the database. Never let Teams messages replace formal requests in the system.
2. Overloading channels with notifications
If every leave request generates a public channel post, the noise drowns the signal. Use DMs for manager notifications and a dedicated channel for team absence visibility.
3. No escalation process
If the manager is on leave or unavailable, the request must escalate. Configure a backup approver in the leave management system.
4. Ignoring Outlook calendar sync
Teams and Outlook are deeply connected. If approved leave does not sync with Outlook, colleagues will schedule meetings on days the employee is off.
5. Not updating out-of-office status
If the integration does not automatically set the Teams status, team members will not know who is available.
Putting it into practice
Five checks cover most Teams integration efforts:
- Choose a leave management system with native Teams integration or Power Automate support.
- Configure the request workflow using adaptive cards, tabs, or bot conversations.
- Set up approval notifications with one-click approve/decline for managers.
- Enable automatic Teams status updates and Outlook calendar sync.
- Test the integration with a small group before rolling out company-wide.
A leave management system that integrates with Microsoft Teams makes requesting and approving leave seamless — reducing friction, speeding up approvals, and keeping your team’s availability visible in the platform they use every day.
Frequently Asked Questions
How do I request leave from Microsoft Teams?
Use the leave management app in Teams — click “Request Leave” or type the slash command. An adaptive card or form appears where you select the leave type, dates, and reason. Submit and your manager receives it for approval.
Can managers approve leave directly from Teams?
Yes. Managers receive a notification with Approve and Decline buttons. One click updates the leave management system and notifies the employee.
Does the integration update my Teams status?
Yes. When a leave request is approved, the integration can automatically set your Teams status to “Out of office” with the return date. It reverts when you return.
Does approved leave sync with Outlook?
Most Teams-integrated leave management systems sync approved leave with Outlook calendar, so colleagues see the absence when scheduling meetings.
Can I use Power Automate for leave workflows?
Yes. Power Automate can route leave requests through multi-level approval chains, create Outlook calendar events, and send automated notifications — all without code.
This article is general information, not legal advice.
Last updated: 26 July 2026.