Outlook Calendar + ATS Integration: Interview Scheduling for Microsoft 365 Teams

Microsoft 365 and recruitment: the integration opportunity

Microsoft 365 is the dominant productivity platform in enterprise organisations globally. Outlook is where calendars live, Teams is where conversations and video meetings happen, and Exchange is the server infrastructure underpinning it all. For the HR and recruitment teams inside these organisations, this creates a problem: their ATS and their scheduling infrastructure operate in separate systems, and bridging them manually consumes hours of recruiter time every week.

The gap is most visible in interview scheduling. A recruiter advancing a candidate to an interview stage needs to: identify the interviewers who should participate, check their availability, find a time slot that works for everyone, create an Outlook calendar invite, generate or include a Teams meeting link, send the invite to the interviewer, and separately notify the candidate with the interview details. Each of these is a manual step. For a recruiter managing five active pipelines simultaneously — each with multiple candidates at the interview stage — this overhead is not marginal. It is a substantial portion of every working day.

Outlook Calendar ATS integration eliminates the manual component of this workflow entirely. The ATS reads interviewer availability directly from Outlook, creates invites automatically, generates Teams meeting links on scheduling, and notifies both interviewer and candidate without the recruiter touching a calendar application. The recruiter's job becomes confirming the interview, not orchestrating it.

This article explains exactly how Outlook Calendar integration works with an ATS, what it requires technically, and what changes — for recruiters, interviewers and candidates — when the integration is live.

How Outlook Calendar + ATS integration works

At the technical level, Outlook Calendar ATS integration operates through Microsoft's Graph API (for Microsoft 365) or Exchange Web Services (for Exchange On-Premises). The connection grants the ATS specific, scoped permissions: read access to calendar availability and write access to create calendar events. The ATS does not gain access to email content, file storage, or any Microsoft 365 service outside the explicitly granted calendar permissions.

Once the connection is established, the integration works in two directions. The ATS reads availability — querying Outlook to determine when each interviewer has free time. The ATS writes events — creating calendar invites that appear in the interviewer's Outlook calendar just as if they had been created manually in Outlook itself.

From the recruiter's perspective, the workflow is: select the candidate to interview, select the interview stage, select the interviewers to include, and choose from the available time slots that the ATS has identified by reading the Outlook calendars. On confirming the schedule, the ATS creates the Outlook invite, sends it to all participants and sends a separate notification email to the candidate with the interview details. The recruiter has made one decision — the time slot — and the system has handled everything else.

From the interviewer's perspective, a new calendar appointment appears in their Outlook with the candidate's name, the interview format, the Teams meeting link for remote interviews, and any preparation materials attached. They accept or decline from Outlook exactly as they would with any other meeting invite. If they decline, the recruiter receives a notification in the ATS to reschedule.

From the candidate's perspective, they receive a confirmation email from the ATS containing the interview time, format, interviewer name and the Teams join link if applicable. They do not need an Outlook account or any Microsoft software — the candidate notification is a standard email.

Checking availability across Microsoft 365 accounts

One of the highest-value capabilities of Outlook Calendar integration is multi-interviewer availability checking. When a role requires a panel interview — or when different stages involve different interviewers — finding a time that works for everyone is a coordination problem that consumes significant recruiter time without the integration.

The manual version involves checking each interviewer's calendar individually (which requires access to their calendar, not always granted), proposing times by email, waiting for responses, iterating when proposed times conflict, and eventually confirming a slot — a process that can span multiple days and multiple email threads for a single interview.

With Outlook Calendar integration, the ATS queries all required interviewers' calendars simultaneously and presents only the slots where everyone is available. The recruiter sees a filtered set of options — typically showing the next available slots across the following week or two — and selects the most appropriate. If the candidate has provided availability windows through a self-scheduling tool, the ATS can also intersect those with the interviewers' availability to find mutual slots.

The accuracy of this availability check depends directly on how well interviewers maintain their Outlook calendars. An interviewer whose calendar shows large blocks of unscheduled time but who is actually occupied with unlogged meetings will produce inaccurate availability data. This is a people management issue, not a technical one — and it is addressable through a brief team communication about calendar hygiene when the integration is rolled out.

Microsoft Teams meeting links in interview invites

For organisations that have moved to remote or hybrid interviewing — which now encompasses the majority of first-stage and many final-stage interviews — generating a Microsoft Teams meeting link is a required part of the scheduling process. Without integration, this is a separate manual step: the recruiter or hiring manager creates a Teams meeting, copies the link, pastes it into the Outlook invite, and includes it in the candidate notification. When done correctly it adds two to three minutes per interview; when done inconsistently it creates situations where candidates receive an interview confirmation with no joining instructions.

With Outlook Calendar ATS integration that includes Teams connectivity, this step is automated entirely. When the interview format is set to remote, the ATS creates a Teams meeting via the Microsoft Graph API, retrieves the join link and embeds it in two places: the Outlook calendar invite sent to the interviewer and the confirmation email sent to the candidate. Both parties have the link from the moment scheduling is confirmed, without any manual link generation or copying.

The Teams meeting created this way is a fully functional meeting with the correct title (typically the candidate's name and role), the correct scheduled time, and access for all invited interviewers. It does not require any additional configuration or management. If the interview is rescheduled, the ATS updates the Teams meeting and the Outlook invite simultaneously.

Exchange Server and Exchange Online: compatibility

Microsoft's calendar infrastructure exists in two forms: Exchange On-Premises (also called Exchange Server) and Exchange Online (which is the cloud version included in Microsoft 365). Understanding the compatibility of each with ATS calendar integration matters for IT planning and for assessing the setup effort involved.

Exchange Online, as part of Microsoft 365, uses the Microsoft Graph API for calendar access. This is the modern integration path: OAuth-based, well-documented, actively maintained and not dependent on any specific network configuration. The connection is initiated through a standard authorisation flow and requires Microsoft 365 administrator consent for the specific permissions the ATS needs. Once authorised, the integration operates entirely through HTTPS to Microsoft's cloud services.

Exchange On-Premises (Exchange 2013, 2016, 2019 and Exchange Server Subscription Edition) uses Exchange Web Services (EWS). This requires creating a service account in Active Directory, granting that account impersonation rights (the permission that allows it to read and write calendar data on behalf of other users), and configuring the ATS with the EWS endpoint URL and service account credentials. This is a more involved IT-level configuration than the cloud OAuth flow, but it is entirely standard for organisations that have deployed Exchange connectors for other enterprise software.

Hybrid environments — where some users are on Exchange On-Premises and others have migrated to Exchange Online — are the most complex scenario and require careful planning. In practice, most hybrid Microsoft 365 deployments route all calendar operations through Exchange Online even for users with on-premises mailboxes during the migration period. If your organisation is in a hybrid state, confirming the routing with your Exchange administrator before configuring the ATS integration is the right approach.

Recruiter calendar management: keeping your own availability current

The Outlook integration serves not only to check interviewer availability but also to manage the recruiter's own calendar. Recruiters who are scheduling dozens of interviews per week need their own Outlook calendar to accurately reflect their scheduling obligations — otherwise they risk double-booking their own time or appearing available to interviewers when they are not.

When Treegarden creates an interview appointment in Outlook, it creates it for the interviewers but the recruiter's ATS dashboard also reflects the scheduled interview. For recruiters who want their own Outlook calendar to show interview scheduling commitments — for example, when another colleague checks their availability — they can connect their own Microsoft 365 account to the integration and have scheduling events reflected on their personal calendar as well.

Good recruiter calendar hygiene also means blocking time for activities that are not interviews but that affect scheduling capacity: team meetings, intake calls with hiring managers, candidate debriefs and candidate feedback sessions. These blocks, visible in Outlook, prevent the ATS from offering those slots to hiring managers or candidates expecting recruiter attendance at an interview.

The overall discipline is simple: the Outlook calendar should reflect reality, not aspirations. When it does, the ATS availability engine produces accurate suggestions. When it does not, the ATS suggests times that turn out to be unavailable and the recruiter is back to manual coordination — the exact problem the integration was meant to solve.

Outlook vs Google Calendar integration: key differences

Many ATS platforms support both Outlook and Google Calendar integration. For organisations that have standardised on Microsoft 365, Outlook integration is the natural choice — but understanding the functional differences between the two integrations is useful context when evaluating options or when an organisation has a mixed environment.

The core functionality is identical: both integrations read interviewer availability in real time and create calendar invites automatically on scheduling. The differences are at the edges. Outlook integration generates Microsoft Teams meeting links for remote interviews; Google Calendar integration generates Google Meet links. Outlook uses OAuth (Microsoft 365) or EWS (Exchange On-Premises) for authentication; Google uses Google OAuth. The invitation email format differs slightly, as Teams and Meet have different visual styles for joining links.

For mixed organisations — where some employees use Microsoft 365 and others use Google Workspace — the ATS should ideally support both integrations simultaneously. A recruiter on Microsoft 365 and an interviewer on Google Workspace can still coordinate through the ATS, with the interviewer receiving a calendar invite in their preferred format. This scenario is increasingly common in organisations that have undergone mergers or acquisitions where different entities use different productivity platforms.

The practical recommendation is straightforward: use whichever integration matches your organisation's primary productivity platform. If your organisation uses Microsoft 365 and Outlook as the standard, configure the Outlook integration and train your team on it. If Google Workspace is the standard, configure Google Calendar integration instead. Attempting to run both integrations in parallel for the same recruiter or interviewer creates complexity without benefit.

Frequently asked questions about Outlook Calendar ATS integration

How does Outlook Calendar integration work with an ATS?

Outlook Calendar ATS integration uses OAuth (for Microsoft 365) or a connector (for Exchange On-Premises) to give the ATS read access to interviewer calendars. When a recruiter schedules an interview, the ATS checks all required interviewers' availability in real time, identifies open slots, and creates Outlook calendar invites automatically — including a Microsoft Teams meeting link if the interview is remote. No manual invite creation or availability chasing is required.

Does Outlook Calendar ATS integration work with Exchange On-Premises?

Yes. Exchange On-Premises is supported, but the setup process differs from Microsoft 365. Exchange On-Premises requires an Exchange Web Services (EWS) connector configured at the IT level, whereas Microsoft 365 uses a straightforward OAuth-based connection that HR administrators can configure without IT involvement. Both methods provide equivalent scheduling functionality once configured.

Can the ATS generate Microsoft Teams meeting links automatically?

Yes. When an interview is scheduled and the meeting type is set to remote, the ATS creates a Microsoft Teams meeting through the Graph API and embeds the join link in the Outlook calendar invite sent to both the interviewer and the candidate. Neither party needs to create a meeting manually — the link is present in the invite from the moment scheduling is confirmed.

What is the difference between Outlook and Google Calendar ATS integration?

Both integrations achieve the same core outcome — real-time availability checking and automatic calendar invite creation — but they differ in authentication method, meeting platform and organisational context. Outlook integration uses Microsoft OAuth or EWS, generates Teams meeting links and is used by organisations on Microsoft 365 or Exchange. Google Calendar integration uses Google OAuth and generates Google Meet links. The choice follows whichever platform your organisation uses; most ATS systems support both.