This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 92%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVL%3C/text%3E%3C/svg%3E)
Hi, i'm experiencing this behavior, when the device is personal and enrolled with Work Profile and there is a device restriction policy enforcing or not a password for the work profile, it is not possible to have a samsung phone unlocked through Samsung Find My Mobile.
After some tests, the only way i can unlock (thus deleting any pin, pattern, password) the device with Find My Mobile is when i remove the restriction policy.
It's a Android 11 device enrolled with Android Enterprise Work Profile.
Am i missing something? is this the expected behavior?
Thank you!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 30%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
@Anonymous , Thanks for posting on Q&A. From your description, it seems the Samsung find my mobile is not working when a device restriction policy is assigned. If there's any misunderstanding, please let us know.
To check on the issue, could you let us know what is the device restriction policy we set? Then I can research more to help you find if others have the similar issue on Samsung device.
@Anonymous ,Hope things are going well. I am writing to see If there's any opportunity to provide the information to go further. If there's any question, feel free to let us know.
Hi @Crystal-MSFT , everything's fine!
Yes, it's correct, no misunderstanding.
It was first reported by another party and i was able to replicate the behavior, this is the configuration profile detail:
Android Enterprise > Personally-Owned Work Profile > Device Restrictions
Tried with some combinations but Find My Mobile only seems to work again when i unassign the profile.
Please let me know if you need any further information.
@Anonymous , Thanks for the reply.
I have tested on one device. I try the setting from your device restriction policy Remove them one by one to find the affected setting. After i remove all the settings, I find VPN client is default configured and unlock my phone is with error "Something went wrong". Then I try to un-assgin the policy. And find it can unlock now.
For our issue, it seems to be a known issue. I will try to feedback. If I can get any update, I will update here. But I can't guarantee it. As a quick method, I suggest to open case which is free to get more help.
https://learn.microsoft.com/en-us/mem/get-support
Thanks for your understanding and have a nice day!
Could you point me to any documentation where this is stated as a known issue?
Thanks for your time and effort!
@Anonymous , Thanks for the reply. Currently, I didn't find other customers report this. And there's no official document mentioned it. But I can test and find the same result. So i guess this can be a known issue. To double confirm this, you can open a case to get more help.
Thanks for the understanding.