Ah. Yeah, that’s feedback we’ve had before. At this time there are not any plans to fix it, but I am not gong to mark this as declined. I moved it from Issues to Suggestions, and I changed the title to match the bug we have internally. I won’t promise that getting a lot of feedback on this will change our plans, but I will say that getting a lot of feedback would help us have a better discussion about whether we should fix it. More data is helpful.
An error occurred while saving the commentJahan Ahmed commented
Thanks for the prompt reply however maybe I didn't explain my issue clearly as its definitely an issue and not a suggestion. Let me try again.
Device needs to be encrypted? Defined as 'NO'
My understanding is this means that if a device is not encrypted it will conform the encryption setting as I have selected 'NO'
Settings on the device:
I decided I want to keep my phone encrypted
Now the issue:
The compliance policy states that any device which is not encrypted will confirm the encryption policy because I have selected 'NO' devices do not have to be encrypted to be compliant.
Why does it matter if I decide I want my device encrypted?
Why do I have to turn the encryption 'off' on my DEVICE to be compliant?
(This test is based on a Windows 10 mobile phone)
I do appreciate what you said about the slider bit, if the option was there so we don't have to select yes or no would mean the setting is disabled totally, but that still doesn't answer my issue.
JahanJahan Ahmed shared this idea ·