---
title: "How to add a Microsoft Teams link to bookings"
url: https://meet.barq.dev/guides/microsoft-teams-link-on-booking-page
updated: 2026-11-17
author: "Hammad Ali"
---

# How to add a Microsoft Teams link to bookings

> **Short answer:** Add an existing Teams joining URL to "Custom link or address" under your event's Location in Barq Meet. Every booking for that event uses the pasted destination; we don't create a new Teams room per appointment. Your connected Google Calendar still supplies availability. Test one 30-minute booking before sharing the page.


## What do you need before adding a Teams meeting link?

You need an existing Teams joining URL you're authorised to share, a Google-connected booking account and a test inbox. Start with the joining destination. This setup passes along a location you already have; it doesn't create the Teams meeting or connect your Microsoft calendar to the booking engine.


Check the existing link with the meeting's organizer before putting it into a reusable appointment type. The sources checked for this guide doesn't establish the expiry, lobby behavior or license rules for your particular Teams URL, so don't assume that every URL can be reused indefinitely.


Our [booking API and webhook feature overview](https://meet.barq.dev/features/api-and-webhooks) describes a different kind of integration. Adding a conferencing URL to a location field doesn't grant calendar access or create a connection to the conferencing provider.


## How do you place a Teams meeting link on a booking page?

Open the event's Basics section, set Location to "Custom link or address", then paste the joining URL into "Link or address". Check the event before sharing. A URL pasted into the wrong appointment type can give guests a working room that belongs to a different meeting purpose.


1. Open the appointment type that should use Teams.
2. In Basics, select "Custom link or address" under Location.
3. Paste the full guest joining URL into "Link or address".
4. Review the offered durations and "When people can book".
5. Save the changes and book through that event's public address using your test inbox.
6. Inspect the invitation's location and open the destination from the guest's side.


We store the custom location on the event and use it when creating bookings. We don't ask Teams to create another meeting, so testing two bookings should reveal the same supplied location instead of two newly generated Teams destinations.


Use a joining URL, not the organizer's editing page. A destination that works only while you're signed into the organizer account isn't a successful guest test.


## Will each Teams booking receive its own room?

No. An event with a pasted custom location supplies that same destination to its bookings. Reuse is the trade-off. A guest who retains the link retains that destination; adding a scheduling buffer doesn't change who has already received it or revoke access to the room.


Suppose a 30-minute consultation begins at 10:00 and ends at 10:30. A 15-minute after-buffer prevents this event's next appointment from starting before 10:45, subject to the other availability rules.


That gives you time between appointments. It doesn't create a second room for the next guest, and it doesn't establish how the existing Teams meeting admits participants.


If your meetings require a fresh Teams destination for every appointment, use a product that documents automatic creation. Don't promise confidentiality based only on the fact that a booking page checked for calendar conflicts.


## Does using Teams make Outlook my booking calendar?

No. The custom Teams field is a meeting location, while Barq Meet checks and writes bookings through Google Calendar. Choose the host calendar deliberately. Pasting a Microsoft conferencing destination doesn't tell the availability engine about a busy event that exists only in an unconnected Outlook calendar.


We let the host select Google calendars that should block time and choose where bookings are written. We also check availability again when the guest submits, but only against the calendars and rules configured for that host.


Microsoft Bookings documents automatic Teams meetings with unique links and supports shared staff booking, according to [Microsoft's Bookings overview](https://learn.microsoft.com/en-us/microsoft-365/bookings/bookings-overview), as of 16 Nov 2026. That's a documented reason for a Microsoft-centered organization to choose it.


Our [Microsoft Bookings comparison](https://meet.barq.dev/compare/barq-meet-vs-microsoft-bookings) examines that choice. Use the calendar system you need before comparing the appearance of its appointment page.


## How do you check that the Teams destination worked?

Make one booking with an inbox you control, then compare the guest invitation with the event's saved location. Test the complete path. A saved field confirms only that the editor retained text; opening the delivered destination tests whether the guest can use the address you supplied.


| Symptom | Likely cause | Next check |
| --- | --- | --- |
| Invite shows Google Meet | Wrong Location option remains selected | Reopen Basics for the exact event |
| Link opens an editing screen | Organizer URL was copied | Obtain the guest joining destination |
| Second booking uses the same URL | Custom location is static | Confirm reuse is acceptable for this event |
| Request exists but final invite hasn't arrived | Approval may still be pending | Check the request status before retesting |

If "Requires approval" is enabled under Booking page, approve the test request before checking the final [calendar invitation](https://meet.barq.dev/glossary/calendar-invite). Don't submit another booking merely because a pending request hasn't produced a confirmed meeting yet.


A test should include the actual date, guest time zone and expected 30-minute interval. Remove the test appointment afterwards so it doesn't consume availability you intend to offer clients.


## Can different events use different video locations?

Yes. One event can use a pasted Teams URL while another uses automatic Google Meet creation. Keep the appointment names clear. Guests selecting a consultation shouldn't discover only after booking that its location differs from the conferencing method you described in the invitation message.


Our [Zoom custom-location guide](https://meet.barq.dev/guides/zoom-link-on-booking-page) explains the same repeated-destination issue for an existing Zoom room. We generate Google Meet details for confirmed bookings when the Google Meet option is selected, including after approval when approval is required.


A custom Teams location has no separate paid tier in Barq Meet, with generous fair-use controls covering account use. Review [the current scheduling features](https://meet.barq.dev/pricing), then [create an appointment using your existing Teams URL](https://meet.barq.dev/app/sign-in) when the shared destination is acceptable for your meetings.

## Steps

1. **Obtain a Teams joining URL**: Use an existing guest destination you have permission to share. Confirm with its organizer that reusing it is acceptable.
2. **Open Basics for the event**: Select the appointment that should use Teams. Check its name and offered duration before editing the location.
3. **Choose Custom link or address**: Under Location, select the custom option and paste the URL into Link or address. Review the appointment's available hours.
4. **Book and inspect a test appointment**: Save the event, then book through its public page with a test inbox. If approval is enabled, approve the request before checking the final invitation.
5. **Open the delivered joining destination**: Check the location from the guest's invitation and confirm the expected room opens. Cancel the test after verification.

## Frequently asked questions

### Can I paste a Teams organizer link instead of a joining URL?

Use the guest joining destination, then open it from the recipient's side. An organizer editing URL can require your signed-in account and doesn't demonstrate that a guest can reach the intended meeting from their invitation. Test the joining address from a guest account and inspect any admission requirements, instead of assuming a URL copied from the organizer's editor will work for someone outside that session.

### Will canceling an appointment invalidate its Teams URL?

Don't assume that. Canceling the booking changes the appointment record, while the custom location is a pre-existing destination you supplied. This setup doesn't create or revoke Teams rooms, so manage the original meeting through its organizer. Manage the room's access and lifecycle in Teams separately from the appointment, since removing a calendar booking doesn't by itself promise that a pasted reusable video address stops working.

### Can an Outlook-only host use this method for conflict checks?

No. This guide requires the host's Google Calendar connection for availability and booking writes. A Teams location changes the joining destination, while an Outlook calendar that isn't connected won't supply conflict information to this booking setup. Check the host calendar integration before offering dates, because supplying a Teams meeting location doesn't let this Google-connected booking page inspect an unsupported Outlook diary for conflicts.

## Related pages

- [How to use a Zoom link with a free booking page](https://meet.barq.dev/guides/zoom-link-on-booking-page)
- [Barq Meet vs Microsoft Bookings: Google or Outlook?](https://meet.barq.dev/compare/barq-meet-vs-microsoft-bookings)
- [Booking API and webhooks for your own application](https://meet.barq.dev/features/api-and-webhooks)
- [What is a calendar invite?](https://meet.barq.dev/glossary/calendar-invite)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
