Managing meetings and events using Outlook on the web for business
This behavior points to a time zone mismatch in the settings that control Bookings internally, especially after a regional time zone change or daylight saving time change.
For Microsoft Bookings, there are two separate time zone settings that must be aligned:
- Booking calendar time zone
This uses the logged-in user’s Outlook on the web language and time zone settings. - Booking page time zone
This controls the self-service booking page that customers use.
Because bookings made from the public booking page land correctly, the booking page time zone is likely already correct. The issue is more likely with the booking calendar / Outlook on the web time zone used when creating bookings from the back end.
Use this path to correct it:
- Sign in to Microsoft 365 and open Outlook.
- Select the gear icon in the upper-right.
- Search for time zone in Settings.
- Verify and update the account’s Language and Current time zone.
- Select Save.
- Let Outlook on the web restart so the new setting is applied.
Then verify the Bookings page setting as well:
- Open Microsoft 365 > Bookings.
- Go to Booking page.
- Select Change language and time zone settings.
- Confirm the correct language and current time zone.
- Keep Always show time slots in business time zone enabled if the goal is to show business-time-based slots.
A few important points from the documented behavior:
- Bookings uses the business time zone by default.
- The self-service page can show appointment times in the visitor’s local time zone unless Always show time slots in business time zone is enabled.
- There is no provision to set a separate time zone for staff in Bookings. Staff time zone and business hours are in the business time zone.
- If the problem started when the region changed its time zone rules, the one-hour offset strongly matches daylight saving time or regional time zone rule changes.
If front-end bookings are correct but back-end-created bookings still send invitations using the old time zone after both settings are updated, only the supported next step is to have the Microsoft 365 admin open a support case for a deeper service-side review.