How to configure Priority Booking action in Web Portal for Office 365 environment

Granting additional roles using PowerShell commands

IMPORTANT: According to the Microsoft Community article, the RBAC Application Impersonation role in Exchange Online will be retired in the fall of 2024. In light of this, you will need to assign the Calendars.ReadWrite.Shared permission in the Microsoft Graph API to your Cayosoft connection account, rather than using the Application Impersonation role, to continue using the Priority Booking web action. Learn more in: Entra ID application permissions required by Cayosoft Administrator Service.

If you are using a version of Cayosoft Administrator older than v11.4.0, simply add the Calendars.ReadWrite.Shared permission won't be enough. You must upgrade to v11.4.0 in order for the action to work without the Application Impersonation role.

To grant additional roles using PowerShell commands:

Open the PowerShell console on the machine where Cayosoft Administrator is installed. This machine must have all prerequisites installed to allow connection to Office 365.

When running these PowerShell commands, replace user@yourtenant.onmicrosoft.com with your Cayosoft Administrator Microsoft 365 Service Account:

$credential = (Get-Credential)
Connect-ExchangeOnline -Credential $credential
New-ManagementRoleAssignment -Name "CayoAccountImp" -Role ApplicationImpersonation -User "user@yourtenant.onmicrosoft.com"

Adding the Priority Booking action to a Web Query

1. In the Cayosoft Administrator console, navigate to Configuration > Web Portal > Virtual Admin Units > Active Directory.

2. Open the AD Users web query.

3. In the AD Users query dialog, switch to the Web Actions tab.

4. Scroll down or search for the Priority Booking action.

5. Click the Add button to add a web action.

6. Expand the Active Directory web actions and select Priority Booking.

7. Click Save Changes.

   

    

NOTE: Global Administrators will see this command in the web interface when the browser refreshes. Other users must have this action added to their Web Role delegation. See Role-based delegation for more information.

Use attribute policies to set default messages. Refer to the following article for additional information: Attribute policies .