Fix Microsoft Bookings 403 Forbidden Errors for Customers
Question details
Customers need to open a Microsoft Bookings page without receiving a 403 Forbidden error.

- Product
- Microsoft Bookings
- Device & OS
- not provided
- Scenario
- A booking page owner shares a link with customers, including customers using Chrome.
- Observed behavior
- Some customers receive a 403 Forbidden error even though the link works for the owner or in another browser.
Sign in to Microsoft Bookings with an account that can manage the affected booking page. Have the customer-facing booking link ready for testing, and confirm that the page is intended to accept external bookings.
Allow customers without an organization account to book
Use this approach when external customers should be able to book without signing in to an organization account.
Sign in to Microsoft 365, open Bookings, select the affected shared booking calendar, and choose Booking page.
Find the booking page access control setting and clear the option that requires customers to have a Microsoft 365 or Office account from your organization. The wording may vary.
Select Save, then copy the public booking page link and ask an affected customer to open it again.

Test the booking link in a private browser window
Use a private window to check whether a browser session or cached data is contributing to the error.
Work with booking-related documents in WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility, making it easy to move existing documents and spreadsheets. It does not fix Microsoft Bookings access errors or replace the Bookings service.

Frequently Asked Questions
Why can I open my booking page when customers get a 403 error?
You may be signed in with an account that is allowed to access the page. In Bookings, open the affected calendar's Booking page settings and check whether customers must have an account in your organization.
Can customers book without a Microsoft 365 account?
They may be able to if the booking page allows external access. In Booking page settings, clear the requirement for an organization account, save the change, and test the public link. Organization policies can still apply.
What should I do if the link works in Chrome Incognito?
Compare the result with a regular Chrome window. If only the regular window fails, review the site's stored data and enabled extensions in Chrome Settings before testing again.
What if customers still receive a 403 after I change the setting?
Confirm that you saved the booking page settings and shared the correct public link. If the error persists in multiple browsers, ask your Microsoft 365 administrator to review organization-level Bookings access policies.




