Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Personal Bookings and Bookings share the same licensing model. However, Bookings doesn't have to be turned on for the organization using tenant settings for users to access Personal Bookings. The Bookings app must be enabled for users to have access to Personal Bookings.
To turn on Personal Bookings without access to Bookings, block access to Microsoft Bookings using the OWA Mailbox policy PowerShell command or follow the instructions here: Turn Microsoft Bookings on or off.
Turn Personal Bookings on or off
Personal Bookings can be turned on or off for your entire organization or specific users. When Personal Bookings is turned on, users can create a Personal Bookings page and share links with others inside or outside your organization.
Note
Tenant admins won't be able to control Personal Bookings access via EWS organization configuration (Set-OrganizationConfig) or per-user CAS Mailbox settings (Set-CASMailbox) anymore. Instead, they will need to use the OWA Mailbox Policy (Set-OwaMailboxPolicy) to control Personal bookings access within the organization.
Organization level: To identify if personal bookings is enabled/ disabled for your organization, admins can run the following PowerShell command:
Get-OrganizationConfig | Select-Object EwsEnabled, EwsApplicationAccessPolicy, EwsBlockList, EwsAllowList
Only these two configuration responses ensure that the BWM is ENABLED for an Organization:
Note: All other configuration responses indicate that BWM is DISABLED for the organization.
Per user settings:
Get-CASMailbox -Identity <smtp> | Select EwsEnabled, EwsApplicationAccessPolicy, EwsBlockList, EwsAllowList
Only these two configuration responses ensure that the BWM is ENABLED for a user:
Note: All other configuration responses indicate that BWM is DISABLED for the user.
To DISABLE Personal Bookings for your entire organization:
Admin should run following PowerShell commands:
Set-OwaMailboxPolicy -Identity "OwaMailboxPolicy-Default" -PersonalBookingsDisabled $trueVerification:
Get-OwaMailboxPolicy -Identity "OwaMailboxPolicy-Default" | Select PersonalBookingsDisabledExpected Output:
Result:
To ENABLE Personal Bookings only for specific users (all others blocked):
a. First, disable org-wide: Perform above steps.
b. Next, enable for specific users by assigning a separate policy: Creating a new custom policy:
New-OwaMailboxPolicy -Name "BwmEnablePolicy"Output:
Set User to this policy:
Set-CASMailbox -Identity <smtp> -OwaMailboxPolicy "BwmEnablePolicy"Verification:
Get-OwaMailboxPolicy -Identity "BwmEnablePolicy" | Select PersonalBookingsDisabledOutput:
Result:
To DISABLE Personal Bookings only for specific users (all others are enabled):
a. First, enable org-wide: It is a default feature, or admin can reset by using command:
Set-OwaMailboxPolicy -Identity "OwaMailboxPolicy-Default" -PersonalBookingsDisabled $falseb. Next, Disable for specific users by assigning a separate policy: Creating a new custom policy:
New-OwaMailboxPolicy -Name "BwmDisablePolicy"Set PersonalBookingsDisabled true for this policy:
Set-OwaMailboxPolicy -Identity "BwmDisablePolicy" -PersonalBookingsDisabled $trueVerification:
Get-OwaMailboxPolicy -Identity "BwmDisablePolicy" | Select PersonalBookingsDisabledOutput:
Set User to this policy:
Set-CASMailbox -Identity <smtp> -OwaMailboxPolicy "BwmDisablePolicy"Verification:
Results: