Mar 03 2023 11:57 AM
I have noticed something, only because some users raised it as an issue, but it seems to be widespread in Exchange Online. With Set-CalendarProcessing we have -AllRequestInPolicy, -AllRequestOutofPolicy, and -AllBookInPolicy. Each of these is a boolean and only one should be set to $true. Each of these has a corresponding multi-valued property - RequestInPolicy, RequestOutofPolicy, and BookInPolicy. The entries in these multi-valued properties are recipients whose meeting requests will be deemed In or Out of policy, or automatically accepted.
When AllRequestInPolicy is set to $true, and the other two All***Policy settings are set to false, it is expected that all requests are "In-Policy". However in Exchange Online, no matter what, the forwarded approval request that goes to delegates always says "
This out-of-policy resource request was forwarded to you for your approval.
This request was forwarded to you for approval because the organizer doesn't have permission to book this resource."
In Exchange (on-premises) server, these forwarded requests would say "This in-policy resource request was forwarded to you for approval." and it shows the same reason (organizer doesn't have permission to book).
I'm just wondering - has anyone else observed this issue? If so, any insights or additional info to share, maybe from Microsoft Support?
Mar 03 2023 12:46 PM
Mar 20 2023 07:35 AM
SolutionFYI, MS Support has confirmed that this is a known issue in EXO and the "PG" are aware of it. It's on a list of things to be fixed, with no ETA or info regarding the priority of this compared to other things that are broken.
I was initially told that this behavior is the design of the product, but I refuted that and supplied all the information I could about the true design of the product, which is:
There are many settings the dictate ‘in or out of policy’. In addition, there are 3 pairs of settings that involve who is allowed to make in-policy or out-of-policy requests. These and their definitions can be found online and confirm what I’m saying (Set-CalendarProcessing:(
Of the 3 All***Policy true/false settings, only one is supposed to be set to True, and the other two set to False. By default AllBookInPolicy is true while AllRequestInPolicy and AllRequestOutOfPolicy are False.
Whether a meeting request is in or out of policy is determined by things like the following:
A meeting is not deemed out-of-policy simply because the requestor isn’t named in the ***InPolicy settings and/or the All***InPolicy settings are not set to True. The privilege to book or request to book are completely decoupled from the in-or-out-of-policy decision.
In Exchange Online, while this issue is still unresolved, all forwarded meeting requests (going to the resource delegates for approval) erroneously have the text in the message body stating the request is "out-of-policy", no matter if the request is truly in or out of policy.
Jun 02 2023 12:16 PM
Aug 18 2023 05:05 AM
Mar 09 2024 08:50 AM
@Jeremy Bradshaw Looks like the issue is back
again. We are facing the exact same issue. If delegate books the conference room who is in RequestOutOfpolicy, all delegates get an approval email. Though there is no way to approve it, the meeting itself is appearing as Tentative on the Conference room. What was the fix for you?
Mar 11 2024 04:34 AM
Mar 11 2024 10:35 AM
@Jeremy Bradshaw Thank you for your response. The issue is when somebody including delegate submits for requestoutofpolicy meeting, the organizer gets pending approval email and delegates get the meeting invite to accept/decline. If they accept, the organizer does not get any update that his requestoutofpolicy meeting is accepted nor calendar changes to busy from tentative not they get any update if the meeting is declined by the delegate.
if I add a delegate to bookinpolicy, they will be auto approved if the meeting is only within the bookin window.
Mar 11 2024 01:44 PM
Mar 20 2023 07:35 AM
SolutionFYI, MS Support has confirmed that this is a known issue in EXO and the "PG" are aware of it. It's on a list of things to be fixed, with no ETA or info regarding the priority of this compared to other things that are broken.
I was initially told that this behavior is the design of the product, but I refuted that and supplied all the information I could about the true design of the product, which is:
There are many settings the dictate ‘in or out of policy’. In addition, there are 3 pairs of settings that involve who is allowed to make in-policy or out-of-policy requests. These and their definitions can be found online and confirm what I’m saying (Set-CalendarProcessing:(
Of the 3 All***Policy true/false settings, only one is supposed to be set to True, and the other two set to False. By default AllBookInPolicy is true while AllRequestInPolicy and AllRequestOutOfPolicy are False.
Whether a meeting request is in or out of policy is determined by things like the following:
A meeting is not deemed out-of-policy simply because the requestor isn’t named in the ***InPolicy settings and/or the All***InPolicy settings are not set to True. The privilege to book or request to book are completely decoupled from the in-or-out-of-policy decision.
In Exchange Online, while this issue is still unresolved, all forwarded meeting requests (going to the resource delegates for approval) erroneously have the text in the message body stating the request is "out-of-policy", no matter if the request is truly in or out of policy.