A leave-management integration connects Microsoft Teams to a separate leave system. Teams can present commands, links, or notifications, while the leave system continues to own policies, balances, approvals, and audit records.

The main parts

A production integration usually needs four boundaries:

  1. Account connection. An authorised company administrator connects the correct Microsoft tenant to the correct leave account.
  2. Employee linking. Each Microsoft identity is matched to an employee inside that account.
  3. Command handling. The integration accepts only supported activities and maps each command to an authorised leave-system action.
  4. Notifications. Approved message types are delivered to a configured conversation or channel without exposing credentials or private leave data.

The exact experience varies by provider. Some integrations only send notifications. Others support balance commands, request links, interactive forms, approvals, calendars, or scheduled summaries. Confirm each capability rather than assuming that “Teams integration” means a complete in-chat workflow.

Authentication and tenant isolation

Microsoft sign-in and bot messages are different trust boundaries. A provider should validate signed authorisation state during account connection and validate Microsoft-issued activity credentials for bot traffic. It should also bind each request to the expected tenant, account, and employee before reading or changing leave data.

Credential storage, token refresh, replay protection, permission scope, and safe error logging are part of the integration—not optional operational details.

Rollout checklist

Before enabling an integration for everyone:

  • verify the exact Microsoft tenant, application ID, redirect address, and permissions;
  • install it for a restricted pilot group;
  • test every advertised command and notification;
  • confirm that links open the correct company context;
  • repeat an activity and prove the underlying action occurs once;
  • test expired or revoked credentials;
  • test uninstall, reinstall, and reconnect behaviour; and
  • confirm the experience in Teams web, desktop, and mobile.

Marketplace or organisation-catalog availability should also be stated precisely. A private pilot, tenant upload, and public Teams Store listing are different release stages.

Leave Balance availability

Leave Balance for Microsoft Teams is currently a limited, invite-only pilot. It does not have a public Teams Store listing, and we do not publish a general-availability date. The Leave Balance web app remains the system of record, including for leave requests and approvals.

Request pilot access to discuss your tenant and intended workflows. We confirm the candidate scope and safeguards during onboarding.

You can take advantage of the free 14 days trial and explore Leave Balance.