Delegate365 changelog version 4.5.3-AllRequestOutOfPolicy

Delegate365 will be updated to version 4.5.3 this Friday. In this version resource mailboxes receive a new feature for controlling the AllRequestOutOfPolicy property (a feature the Office 365 portal does not provide).

• The AllRequestOutOfPolicy setting: When using resources like a room, there can be an issue with reservation: “Office 365 users can reserve a meeting room even though it's already reserved for another meeting”.
  Microsoft describes this issue in https://support.microsoft.com/en-us/kb/3066068.
  This resource mailbox property cannot be set in the Office 365 portal, just with PowerShell – and with Delegate365 for portal admins and scope admins as well.
• What this property means: If the AllRequestOutOfPolicy property of the room mailbox is set to “Yes”, Office 365 users can reserve a meeting room even though it's already reserved for another meeting. To resolve this issue, set the AllRequestOutOfPolicy property of the room mailbox to “No”  in D365.
• How it works in D365: Open resources, select a resource item and click Edit resource.
  
  In the mailbox settings there is now a new region named "all request out of policy".
  The switch “Ignore conflicting meeting requests” can be set to Yes or No.
  Yes - means that this resource can be reserved even though it's already reserved for another meeting – so maybe you don’t want this behavior in your organization.
  No - means that this resource cannot be double booked – so usually you want to set this switch to No in your organization.
  Click Save for making this switch active for this resource.
  

Delegate365 version 4.5.3 will be rolled out this Friday, on 13th November in the morning (CET).
Thanks to Henry K. for giving this D365 feature feedback.

For a list of all D365 changes pls. check out http://bit.ly/d365blognews or http://bit.ly/d365changelog.