MDM in the UAE: the technology is the easy part, getting staff to accept it is not.

This is the single most common reason device management rollouts stall in the UAE, and it is entirely avoidable. It is a scoping error rather than a technical one, and it usually comes from applying a corporate-device policy to a personal device because it was simpler to configure one way.

• Full enrolment on a personal phone gives the employer the ability to wipe the entire device, see the installed application inventory, and in some configurations enforce restrictions across the whole handset. Staff are right to object to that on a phone they paid for, and in a market where many employees also hold personal and family data on that device, the objection is strong and reasonable.
• The correct answer is application-level protection instead. Company data lives inside company applications with its own PIN, copy and save restrictions, and a selective wipe that removes only the company side. The employer cannot see personal apps, cannot locate the device, and cannot erase it. Most staff accept that readily once it is explained clearly.
• Reserve full supervision for hardware the company owns, where the argument is straightforward: it is company property holding company data. The two models should be genuinely different policy sets rather than one policy with exceptions, because exceptions drift.
• Explain it in writing before enrolment rather than after. The rollouts that go smoothly are the ones where staff were told exactly what IT can and cannot see, in plain language, before being asked to enrol anything. The ones that stall are the ones where somebody discovered a capability afterwards and told everyone else.