Share via

MS Bookings

Cain, Joshua 0 Reputation points
2026-04-07T20:20:17.9833333+00:00

How do I restrict a MS bookings to 1 external company only with multiple staff members on my side?

Outlook | Web | Outlook on the web for business | Email
0 comments No comments

2 answers

Sort by: Most helpful
  1. Chris Duong 8,050 Reputation points Microsoft External Staff Moderator
    2026-04-07T21:12:23.12+00:00

    Hi @Cain, Joshua

    I hope you’re having a great day. I appreciate your patience and the details you provided. 

    A - What's happening 

    I’d like to clarify one important point up front so expectations are aligned: Microsoft Bookings does not currently offer a native feature to restrict a public booking page to only one external company or domain. Booking access is generally controlled at two levels either the page is accessible to anyone who has the link, or access is limited to authenticated users within your Microsoft 365 tenant.  

    B - Recommended workarounds 

    That said, there are a few practical approaches you can use, depending on how strict the restriction needs to be. 

    Option 1: Strict access control using Guest accounts (Recommended for strong enforcement) 

    If you require strict control so that only that external company can book appointments, the most reliable option is to require sign-in and onboard that company as guest users in your tenant. By enabling the “Require a Microsoft 365 account from my organization to book” option on the booking page, only users who can authenticate against your tenant will be able to access and book.  

    To do this, please go to Microsoft Bookings > select your shared booking page > Booking page > Configure booking page > set availability to “Available to people in your organization” 

    With this setting enabled, only users who can authenticate against your tenant will be able to access and book the page. You can then invite users from the external company as Entra ID (Azure AD) guest users. Once they accept the invitation and sign in, they will be able to book appointments, while all other external (public) users will be blocked. 

    This approach effectively creates a controlled “whitelist” limited to that partner company, although it does require onboarding and managing Guest user accounts. 

    Option 2: Public booking page with reduced exposure (No hard restriction) 

    If you prefer to keep the booking page public and avoid creating guest accounts, it’s important to note that Microsoft Bookings cannot technically enforce a “single external company only” rule. In this case, you can reduce exposure by disabling direct search engine indexing of the booking page, limiting social sharing options at the tenant level, and sharing the link only through tightly controlled channels such as direct emails to named contacts.  

    This approach helps reduce risk but does not provide hard enforcement anyone who obtains the link could still attempt to book. 

    About configuring appointments with multiple internal staff members 

    Regarding your requirement to include multiple staff members from your side in each appointment, Microsoft Bookings does support this. You can configure the service to use a multiple-staff setup by assigning all required staff members to the service. With this configuration, Bookings will only show time slots where all selected staff are available.  

    If you ever need more flexibility, such as one staff member being mandatory while others are optional, the usual workaround is to create separate services for each required staff combination. 

    For additional information, you can refer to these articles: 

    C - Submit Feedback to Microsoft 

    As a forum moderator, I hope you understand that I don’t have the ability to modify or escalate product issues directly. However, I strongly recommend submitting your feedback through the Bookings · Community. This is the most effective way to ensure your voice reaches the product team and can be considered for future improvements.  

    Once you've submitted your feedback, feel free to share the link here in the comments. I’ll be happy to upvote it to help bring more visibility.   

    If you are unable to submit feedback from your side, please let me know and I will be happy to submit it on your behalf.      

    Additionally, since many other users have expressed similar concerns but may not know where to submit feedback, if my response has helped you better understand the situation and guided you toward a possible next step, please mark it as the "Accepted Answer". Your action will help pin this post to the top, making it easier for others in the community who are experiencing the same issue to find your feedback and support it.    

    I hope this information is helpful. Should you have any further questions or need additional assistance, feel free to reach out. 

    Thank you again for your time and for raising this important usability concern.   


    If you have any extra questions about this answer, please click "Comment".  

    Note: Follow the steps in our documentation to enable email notifications if you want to receive email notifications related to this topic.     

    0 comments No comments

  2. Q&A Assist
    2026-04-07T20:20:29.82+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To restrict a Microsoft Bookings page so that only one external company can book, while allowing multiple staff members from the organization to attend, configure both access control and service/staff settings.

    1. Restrict who can access the booking page
      • In the Bookings web app, go to the Booking page tab.
      • Use these options as needed:
        • Require a Microsoft 365 or Office 365 account from my organization to book: If the external company has accounts in the tenant (for example, guest accounts), enabling this will restrict booking to authenticated users in the tenant only.
        • Additionally, in the Microsoft 365 admin center under Settings > Org settings > Bookings, use granular controls such as:
          • Block shared bookings from outside your organization if only authenticated/guest users in the tenant should book.
          • Disable direct search engine indexing so the page is not discoverable via search engines.
          • Optionally Block social sharing options so the link is not easily spread.
      • Then share the booking page URL only with the specific external company. Bookings does not natively restrict to a single external domain; control is achieved by tenant-level restrictions plus controlling who receives the link.
    2. Configure the service as a multi‑staff service
      • In the Bookings web app, go to Services.
      • Either create a new service or edit an existing one.
      • On the Assign staff page:
        • Select Multiple staff so the booking is scheduled with all assigned staff members (N:1 service).
        • Under Select staff, choose all internal staff who must attend each appointment.
        • Optionally enable Allow customers to choose a particular staff for booking only if the external company should be able to pick specific staff; otherwise leave it off so all assigned staff are booked together.
    3. (Optional) Use attendee limits and custom fields
      • In the service settings, configure Maximum number of attendees if only a limited number of people from that company should join each slot.
      • Use Custom fields to capture information that identifies the external company (for example, company name or contract ID) on every booking.

    Operationally, the restriction to “one external company” is enforced by:

    • Tenant-level controls that block general external access where appropriate.
    • Not publishing or broadly sharing the booking link.
    • Optionally requiring authenticated/guest accounts for that company only.

    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.