Shared Booking Page invitations

Hi @Jason Rezac, 

I hope you have a good day. 

Based on your description, you are seeking clarification on whether it is possible to hide attendee email addresses in personal booking confirmations and if shared booking page links can be configured to expire after they have been distributed. 

Regarding your first inquiry, the current architecture of the booking platform captures attendee data to facilitate seamless communication between the organizer and the participant. Therefore, there is no built-in administrative setting to suppress or hide the email address within the confirmation view or the automated notification emails sent to either party.  

Similarly, for shared booking pages, the system is designed with persistent URLs. While there are options to restrict visibility or disable search indexing, a dedicated feature to assign a specific expiration date to an invitation link is not currently supported. 

As a workaround for managing link longevity, you may utilize the following approach by custom availability. Instead of relying on a link that disappears, you can make the service itself inaccessible after a certain date: 

1. Access the Shared Booking Page. 
2. Navigate to Services and edit the specific service associated with the link. 
3. In the Availability tab, change "General availability" to "Not bookable." 
4. Under "Set different availability for a date range," define a specific window (only for the current week). 

Note: once this date range passes, the link remains active, but the calendar will display "No availability," preventing further bookings. However, a significant limitation of this method is that the link remains functional; it simply fails to offer open slots, which may lead to confusion for recipients attempting to schedule a meeting after the window has closed.

I know these workarounds do not fully meet your operational requirements, so I highly recommend submitting a feature feedback via Bookings · Community. Providing direct feedback is essential, as it allows the development team to prioritize privacy enhancements and more granular link management tools in future updates. 

As a forum moderator, the most I can do here is confirm the behavior and explain why it happens. Since this is a product‑side limitation, I’m not able to recover the transcript or intervene at the service level.   

Thank you for your understanding and contribution. I hope the information above address your concerns and should you have any further questions, please feel free to reach out. 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

For the scenarios described, the available documentation only supports the following behaviors and controls:

1. Hiding end‑user email addresses in confirmations
   • Shared Bookings offers a tenant-level control to block sharing staff details with customers, but there is no documented granular control to hide customer email addresses in confirmation messages.
   • The granular controls that can be configured for Shared Bookings are:
     • Block shared bookings from outside your organization
     • Block social sharing options
     • Block sharing staff details with customers
     • Require staff approvals before sharing free/busy information
     • Allow Microsoft to send SMS messages
     • Disable direct search engine indexing
     • Enforce naming policy for shared booking pages alias
     • Restrict collection of customer data
   • “Restrict collection of customer data” allows preventing collection of specific customer fields on forms, but the documentation does not describe a setting that both allows collecting email for scheduling and simultaneously hides it in confirmations.
   Based on the documented controls, there is no supported setting exposed in Shared Bookings to hide end‑user email addresses in confirmation messages while still using them for booking.
2. Expiration of personal or shared booking page links
   • Personal Bookings and Shared Bookings are designed around a persistent booking page URL that can be widely shared (email, chat, social media, email signatures) so that people can book whenever slots are available.
   • The documentation describes:
     • Sharing personal booking page links via copy link, email, or email signature.
     • Tenant-level controls to block shared bookings from outside your organization and disable direct search engine indexing.
   • There is no documented feature to set an expiration time or one‑time use limit on a personal or shared booking page link. Control is instead achieved by:
     • Adjusting scheduling policy (minimum/maximum lead time) to limit when future bookings can be made.
     • Restricting who can access the page (for shared bookings, for example, blocking external users at the tenant level).
   Therefore, there is no supported configuration to make an individual invitation link expire; links remain valid as long as the booking page itself is published and accessible under the tenant’s policies and scheduling rules.

To tighten behavior as much as possible with current capabilities:

• Use Restrict collection of customer data if certain customer fields should not be collected at all.
• Use Block shared bookings from outside your organization and Disable direct search engine indexing to limit who can discover and use shared booking pages.
• Use Maximum lead time and Minimum lead time in scheduling policy to limit how far into the future bookings can be made, even if someone retains an old link.

References:

• Manage granular controls for Shared Bookings
• Shared Bookings Frequently Asked Questions (FAQ)
• Preview and share your personal booking page
• Microsoft Bookings
• Create a new meeting type in Bookings