Microsoft Bookings for interview scheduling

Microsoft Bookings works for candidate interviews. Microsoft lists them as a Bookings use case and gives "applicant ID for candidate interviews" as its example of a custom field. But Bookings knows nothing about requisitions, stages, scorecards or your applicant tracking system (ATS), so the setup decisions are yours. This guide covers the decisions specific to recruiting, for coordinators, talent teams and the admin who supports them. Allow half a day to build and test a page for one hiring team.

This guide describes Microsoft Bookings settings. It isn't legal or employment advice. What you may ask candidates, and how long you keep their data, depends on where you hire and on your own policies.

Before you start#

• Licences. Whoever creates the page needs a Microsoft 365 plan that includes Bookings. Every interviewer in a Teams interview needs a licence that supports Teams meeting scheduling. Candidates need nothing.
• A mailbox on your own domain. The page's mailbox address is in its link and sends every confirmation, so use something like interviews@yourcompany.com. Microsoft warns that invites from an onmicrosoft.com default domain can land in junk, and changing it later takes PowerShell.

One shared page, or Bookings with me for each interviewer#

When we tested a personal page in September 2026, the booking carried only name, email, notes and time zone, and Microsoft emailed the booker a 6-digit code before creating it. If you use Bookings with me, ask candidates to put their applicant ID in the notes and to keep the page open until the code arrives. Shared Bookings vs Bookings with me has the full comparison.

The rest of this guide assumes a shared page.

Pages and services per role and stage#

A service has one duration, location, question set and set of interviewers, so build one per stage, role and format:

Decisions that matter in recruiting:

• Everyone with the page link sees every published service. Give a confidential search its own page, with Disable direct search engine indexing of booking page turned on.
• Send service links, not the page link. Each service has its own Service booking page URL, so a candidate for one role lands on that role's interview. See linking to one service.
• Hidden doesn't mean private. With Publishing options off, Microsoft says the service can only be booked from the Calendar in the Bookings web app. Microsoft doesn't document whether its direct link still works, so test it before you rely on it for a "link only" interview.
• Watch the service count. Microsoft says a page should have no more than 50 services, and roles times stages fill that quickly. Use one page per department or hiring campaign.
• Tag the source. Add ?RefID= per job board or agency, such as ?RefID=jobboard_dataeng. In our September 2026 tests, the value survived a reschedule and reached the export's Tracking data column, but not the interviewer's Outlook event. Power Automate exposes it as TrackingData.

The settings themselves are documented in services in Microsoft Bookings.

Panel interviews with several interviewers#

Set the service's Assign staff page to Multiple staff and select the panel. Microsoft says each booking is then made "with all of the assigned staff members", and only at times when every one of them is free. Things to plan for:

• Every extra panelist shrinks the slots. One busy diary removes the time for everyone, so keep self-service panels small.
• No "manager plus any one engineer". The workaround is one service per combination (several staff in one meeting). Past two or three, have a coordinator book from the Calendar.
• Interviewers outside your tenant are Guests. Microsoft says they "will not be able to share free/busy information", so keep agency or external interviewers off self-service panels.
• One time zone for all staff. The FAQ says there's "no provision to set time zone for staff", so enter hours in the business time zone or give each region its own page.
• "Anyone" means random. Screens go to a free recruiter at random, with "no way to ensure equal distribution" (any-available-staff guide).
• Reschedules can change the interviewer. Microsoft says a customer rescheduling through Manage booking can change "the date, time, and staff member". On a technical interview where the candidate must meet a particular engineer, assign only that engineer to the service.

Teams links and the interview lobby#

Turn on Add online meeting on remote interview services. Each booking gets its own Teams link, which goes into the interviewers' events and the candidate's emails. Microsoft says external attendees can join in a browser without downloading Teams.

• Use the lobby on purpose. Microsoft recommends a Teams meeting policy that admits "People in my organization" automatically, so the panel can confer while the candidate waits in the lobby. Bookings can't set meeting options itself (Teams meeting options).
• Decide recording outside Bookings. Set it in Teams policies, and tell candidates in the confirmation.
• Confirmation links work like keys. In our September 2026 tests, the manage page opened from a confirmation email showed the Teams link, and offered Reschedule and Cancel, with no sign-in. Don't paste candidate confirmations into ATS notes that many people can read, and don't forward them to agencies.

Missing links are covered in why the Teams link is missing, and the settings in Teams meetings and virtual appointments.

Questions to ask candidates, and what not to#

Custom questions are set per service under Custom fields. Tick Required for the ones candidates must answer. Ask only what you need to route and prepare the interview:

• Applicant or requisition ID (required). It's the only reliable way to match a booking to the application in your ATS.
• Role applied for, as a single-choice question, if one service serves several roles.
• Phone number, only on phone screens. Phone is a built-in field, so make it required on those services and turn it off elsewhere.
• "Do you need any adjustments for the interview?" Make it optional free text, and ask about adjustments rather than about health.

Don't ask on the form what you wouldn't ask at interview: age or date of birth, family status, health, religion or nationality. Pay history questions are restricted in a number of US states and cities; check with HR or legal. In our September 2026 captures, the public page offered only free-text and single-choice questions, with no file upload, and a 3,000-character notes box. Turn notes off or label it, or candidates paste in their CV.

Who sees the answers matters more in recruiting than in most uses:

• Everyone with page-wide access. Microsoft says Viewers "can see all the bookings on the calendar", as can Administrators and Schedulers, so a hiring manager made a Viewer reads every candidate on the page. Team members "manage bookings on their own calendar". Make interviewers Team members, or Guests, and check what a Team member sees before launch (staff roles).
• Exports and flows. Answers appear in the export's Custom Fields column and in CustomQuestionAnswers in Power Automate.

Custom questions best practices covers wording, and custom questions in Microsoft Bookings lists every setting.

Confirmations, reminders and follow-ups#

On each service's Notifications page:

• Confirmation. Use Additional information for Email Confirmation for length, preparation, building and ID instructions, and who to contact to change the time.
• Reminders. Send the candidate one the day before and one an hour before. A staff reminder gives panelists time to read the application; keep candidate details out of its text.
• Follow-ups. They go out after the appointment whatever the outcome, so send at most a neutral thank-you, never next steps. We haven't verified whether one goes out after a cancelled interview.
• Staff contact details. If interviewers' details shouldn't reach candidates, an admin can turn on Block sharing staff details with customers. It applies across the tenant.
• SMS needs Teams Premium, and Microsoft documents the supported countries inconsistently. See SMS reminders.

Set Send customer replies to (Business information) to the recruiting inbox. See emails, reminders and SMS.

Stopping late reschedules and repeat bookings#

One reschedule of a four-person panel moves four diaries. What you can control, as of October 2026:

• Self-service bookings can always be changed. Microsoft says customers who booked on the page "will still have the Manage Booking button and all of its options", even with Let customers manage their appointment when it was booked by you or your staff on their behalf off. That setting covers staff-made bookings only (stopping rescheduling).
• Have a coordinator book final panels. Use a hidden panel service, book it from the Calendar, and leave the setting above off. Microsoft says customers then can't reschedule or cancel. We've only tested self-service bookings, so try one staff-made booking before you rely on this.
• Use lead time as the cutoff. Lead time in hours sets how far ahead customers "must book or cancel". A 24-hour value also stops bookings for tomorrow morning. Set it per service by turning off Default scheduling policy (scheduling policy).
• Get told about every change. Tick Notify when a booking is created or changed, and turn on staff notifications.
• Repeat bookings. Bookings has no per-customer limit, so one candidate can book three screening slots. Check the Calendar and cancel duplicates. On Bookings with me, single-use links prevent this.
• Confirmed emails only. Require a one time password to create bookings makes candidates confirm their email with a code first. It catches mistyped addresses, which matters when the confirmation holds the only Teams link.

Candidate data, privacy and retention#

Microsoft says all Bookings data is stored in Exchange Online, and that "compliance policies for shared mailboxes in Exchange also apply for Bookings mailboxes". For recruiting, that leads to some concrete steps:

• Put the booking mailbox under your candidate retention schedule. Microsoft doesn't document any automatic deletion of customer records, so every candidate stays in the Customers list until removed. Ask your compliance admin to cover the mailbox with your applicant retention policy.
• Clean up on a schedule. Remove a candidate's appointments first, then the customer record, which doesn't take the appointments with it. Where Bookings stores data lists the steps and the copies elsewhere.
• A page per campaign makes deletion simpler. When its retention period ends, an admin deletes the mailbox. That's permanent, so check for legal holds first (deleting a booking page).
• Link the candidate privacy notice. Turn on Customer data usage consent with your own wording (Microsoft records when the box is ticked). Under Business information, enter the URL of your candidate privacy notice, not the customer one.
• Exports are candidate data. Only Administrators can download the TSV export. Microsoft gives its window as four months in one article and 120 days in the FAQ.

The limits: no ATS integration, and the Power Automate route#

As of October 2026, Bookings has no native connection to any ATS, and Microsoft documents none. The supported route is the Microsoft Bookings connector in Power Automate:

• Triggers: an appointment is created, updated or cancelled. The only documented action lists the booking pages you administer.
• Who can build it: only staff with the Administrator role on the booking page, which is different from tenant admin rights. Each booking mailbox allows 5 flows. The connector is in preview and isn't available in GCC, GCC High or DoD.
• What you get: the candidate's name, email and phone, CustomQuestionAnswers (including the applicant ID), the staff members, JoinWebURL and TrackingData. Use SelfServiceAppointmentId to match the same interview across triggers. The update trigger doesn't say what changed, so store the start time and compare.

A typical flow finds the application by applicant ID (falling back to email), logs the interview with time, interviewers and Teams link, then updates or cancels it on the other triggers. Whether your ATS has a connector, and whether it or an HTTP call is premium in your plan, depends on the vendor and your licence. The build pattern, with deduplication and error handling, is in Bookings to a CRM with Power Automate. Connector limits are in the Power Automate connector.

Other gaps: no approval step, no scorecards or feedback, no booking several stages in one go, and no availability from Google Calendar.

Test before candidates see it#

• Book each service from a private browser window with a personal email address and a test applicant ID.
• Check the confirmation wording, the Teams link, the lobby, and each panelist's Outlook event.
• Open the appointment as a Team member and as a Viewer, and confirm who can see which candidates.
• Reschedule from the confirmation email and check your notification and flow pick it up, then delete the test customer.

Doing this with BookingsXP#

If candidates book from your careers site, BookingsXP embeds the recruiting page as a widget and records which job board or campaign each screening booking came from. It writes that source into the booking notes, where our test booking showed it in the Outlook event. With Store bookings switched on, signed webhooks and Zapier, Make, n8n or Power Automate recipes can send each new booking to your ATS; reschedules and cancellations still need the Bookings connector. With it off, BookingsXP keeps no candidate details. See /features/webhooks. BookingsXP is independent and not affiliated with or endorsed by Microsoft.