-
Notifications
You must be signed in to change notification settings - Fork 553
No remote wipe for BYOD iPhones #22882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
A couple of things for us to think through. Our current BYOD solution is not really BYOD otherwise this would not be a problem. Our current BYOD solution is user-initiated enrollment with full MDM capabilities. This is supposed to be used for companies that have devices that aren't being automatically managed by ABM/DEP. The issue around admins have pervasive permissions and capabilities would be address if we supported User Enrollment (true BYOD). I am concerned that just hiding Wipe from the UI would not address the potential issue being raised since the profile being enrollment profile being installed in this method would still have the rights to wipe the device. We would likely have to change the rights management of the enrollment profile that gets installed to fully block wipe capabilities which would mean a re-enrollment of the device. It also means that the customers that want user-initiated enrollment with full MDM capabilities would lose this ability without creating some UI to have multiple user-initiated enrollment workflows. |
ProblemMike: I want to be able to disable remote wipe for a given team (eg byod devices. Could even call it “BYOD mode”— but simplest step is to be able to; as an admin, disable this one particular feature that could wipe your pictures of your kids What have you tried?Potential solutionsWhat is the expected workflow as a result of your proposal? |
Hey @Sampfluger88, we decided to drop #23242 because none of our customers requested this feature. We're planning to bring #27390 into the sprint starting on May 5. |
User stories
The text was updated successfully, but these errors were encountered: