Device management is not uniform across a fleet. Brands, models and operating-system versions expose different management capabilities, and a restriction that works on one device may be unavailable on another. MDM.Plus configures policies according to four inputs: device platform, OS version, supervision status and enrolment method.
What determines availability
- Platform and OS version define which management APIs and policy keys exist.
- Supervision status affects whether stronger restrictions can be applied at all.
- Enrolment method determines which commands the device can receive once managed.
- Vendor interfaces and connectivity matter for some functions: certain restrictions require prior enrolment, an online device, or a manufacturer's interface conditions to be met.
Verify before deployment
Because these conditions vary, run a check on a test device that matches your target model and OS build before a formal rollout. Confirm two things, not one: that the intended policy applies successfully, and that the device can be recovered — through unlock, profile removal or wipe — if the policy needs to be reversed. A passing result applies only to the tested combination.
Scope of this description
This article covers policy configuration within the tested range. It is not a claim of exclusive market position, nor a promise of protection beyond what was tested. Compatibility here means that a given model and version were verified under specific permissions and deployment conditions; it is not official authorisation, endorsement or a commercial partnership. The definitive list of supported platforms, versions and functions is in the product documentation and compatibility list. Final scope is subject to the confirmed product specification and service agreement.
