Standard preset always appears disabled

[mrapoc]

I have checked across multiple tenants using Standard Preset and they all appear as disabled in the report.

[cammurray]

Hi @mrapoc confirming here, in tenants that have "Standard Preset" applied to both EOP/MDO, those policies are appearing disabled?

[mrapoc]

Hi Correct yes showing as a disabled policy

…

________________________________ From: Cam Murray ***@***.***> Sent: Thursday, November 16, 2023 3:13:08 AM To: cammurray/orca ***@***.***> Cc: mrapoc ***@***.***>; Mention ***@***.***> Subject: Re: [cammurray/orca] Standard preset always appears disabled (Issue #269) Hi @mrapoc<https://github.com/mrapoc> confirming here, in tenants that have "Standard Preset" applied to both EOP/MDO, those policies are appearing disabled? — Reply to this email directly, view it on GitHub<#269 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABWD4OZSIBZSPYLI62OE6C3YEWAEJAVCNFSM6AAAAAA7K6GPQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTG4ZDGOBSGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[CW-RKR]

I can confirm this too. There is a screenshot in my issue (#265) where you can see it. The round red dot with the number 1.

[cammurray]

Thanks @CW-RKR @mrapoc

Would either of you be willing to share with me a report by sending me an email [email protected]. I can then look in to this a bit further.

[cammurray]

@CW-RKR @mrapoc

Turns out this is due to a consistency issue with how the preset policies are applied and normal policies.

I believe this is fixed now - and looking at the report you sent me @CW-RKR, certainly appears that's the case - in that report you sent, Standard policy is appearing correctly as applied and Strict is not.

Can I get some confirmation on the behaviour you see in 2.7.1?

[mrapoc]

Hey Cam I still get disabled next to the Standard Preset Security Policy on 2.7.1

…

On Mon, 20 Nov 2023 at 04:00, Cam Murray ***@***.***> wrote: @CW-RKR <https://github.com/CW-RKR> @mrapoc <https://github.com/mrapoc> Turns out this is due to a consistency issue with how the preset policies are applied and normal policies. I believe this is fixed now - and looking at the report you sent me @CW-RKR <https://github.com/CW-RKR>, certainly appears that's the case - in that report you sent, Standard policy is appearing correctly as applied and Strict is not. Can I get some confirmation on the behaviour you see in 2.7.1? — Reply to this email directly, view it on GitHub <#269 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWD4O4GBI3U5BHBEECKXB3YFLIWDAVCNFSM6AAAAAA7K6GPQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJYGE4TANRZHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[CW-RKR]

Sorry. Still shown as 'Disabled'

[cammurray]

Re-opening this for investigation..