Loading...

Action required: Retirement of EWS-based Personal Bookings controls (Microsoft Bookings)

Action required: Retirement of EWS-based Personal Bookings controls (Microsoft Bookings)

Microsoft is retiring EWS-based controls for Personal Bookings in Microsoft Bookings on August 5, 2026. After that, access will be managed only via OWA Mailbox Policy settings. Administrators must migrate existing EWS configurations to OWA policies before this date to maintain control. Introduction We’re retiring the Exchange Web Services (EWS)–based controls used to enable or disable Personal Bookings (Bookings with me) in Microsoft Bookings. Beginning August 5, 2026, access to Personal Bookings will be managed exclusively through OWA Mailbox Policy settings. This change aligns with Microsoft’s Exchange Online management and security principles, while providing a single, consistent administrative experience. When this will happen Now: The OWA Mailbox Policy setting for Personal Bookings is available. August 5, 2026: EWS‑based Personal Bookings controls will be retired. How this affects your organization Who is affected Microsoft 365 administrators managing Microsoft Bookings and Exchange Online Organizations currently using EWS organization configuration or per‑user CAS mailbox settings to control Personal Bookings What will happen After August 5, 2026, admins will no longer be able to manage Personal Bookings access using: Set-OrganizationConfig (EWS settings) EWS‑related parameters in Set-CASMailbox The default OWA Mailbox Policy is tenant‑configurable and may already include customized Personal Bookings settings. Any existing EWS‑based Personal Bookings configuration will be ignored. Access to Personal Bookings will be determined only by the OWA Mailbox Policy assigned to the user. If no custom OWA Mailbox Policy is assigned to a user, Personal Bookings availability will follow the settings configured in the tenant’s default OWA Mailbox Policy (OwaMailboxPolicy-Default). If your default OWA Mailbox Policy already reflects your intended Personal Bookings access state, no additional changes are required. What you can do to prepare Administrators should complete migration of any existing EWS‑based Personal Bookings controls to OWA Mailbox Policy before August 5, 2026, to avoid unintended changes to user access. The following steps require Exchange Online PowerShell. There is no change to the Personal Bookings user experience. This change affects only how administrators manage access. Migrate your existing EWS‑based Personal Bookings controls to the new OWA Mailbox Policy Review your current EWS‑based configuration Organization‑wide: Get-OrganizationConfig | Select-Object EwsEnabled,EwsApplicationAccessPolicy,EwsBlockList,EwsAllowList Per […]

The post Action required: Retirement of EWS-based Personal Bookings controls (Microsoft Bookings) appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Action required: Retirement of EWS-based Personal Bookings controls (Microsoft Bookings)

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

M365 Admin
M365 Admin

by João Ferreira

Share post:

Related posts

Microsoft Teams: Hide organizer names in calendar view on Teams Panels

Microsoft Teams Panels will add an admin setting to show or hide organizer names in Calendar View, configurable via the Teams Rooms Pro Manage...

19 hours ago

Microsoft Defender for Office 365: New email submissions data in Advanced Hunting

Microsoft Defender for Office 365 will add two new Advanced Hunting tables, SubmissionEvents and SubmissionResults, providing security teams e...

19 hours ago

Microsoft Copilot: Introducing the Microsoft plugin registry for Microsoft Copilot experiences

Microsoft is introducing a Microsoft plugin registry for Copilot experiences and Microsoft 365 apps, centralizing discovery, publishing, and g...

19 hours ago

Action Required: Upgrade ExchangeOnlineManagement PowerShell Module to Version 3.10.1 or Later

Upgrade the ExchangeOnlineManagement PowerShell module to version 3.10.1 or later by March 31, 2027, to avoid authentication failures due to n...

19 hours ago

Microsoft PowerPoint: Brand Guidelines and Style removed from new Brand Kit creation

Microsoft PowerPoint no longer includes Brand Guidelines and Style when creating new Brand Kits to simplify the process. Existing Brand Kits r...

19 hours ago

Updates available for Microsoft 365 Apps for Current Channel

We’ve released updates to the following update channel for Microsoft 365 Apps: Current Channel When this will happen: We’ll be gra...

19 hours ago

Windows settings backup is now enabled by default for eligible devices

With the release of Windows 11, version 26H2, the Windows settings backup policy is now enabled by default for eligible devices (see the Impac...

19 hours ago

Dynamics 365 and Power Platform– Information about storage validation for Dataverse-only tenants

Beginning November 9, 2026, we are introducing staged storage validation for supported Dynamics 365 applications. The change gives administrat...

19 hours ago

Business Skills in Work IQ – Default On

We are announcing the ability to use Business Applications in Work IQ to search and query Dataverse business data, Semantic Modeling, Business...

19 hours ago

Dynamics 365 Contact Center – Let representatives set next presence to handle routing of work items

We are announcing the ability to let customer service representatives set their next presence to handle routing of work items in Dynamics 365 ...

19 hours ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.