Mobile devices

Mobile device management for Apple and Android

Manage iPhones, iPads, Macs and Android devices through the workspace MDM area. Apple and Google use separate enrollment and policy paths. Current deployment evidence confirms a managed Mac; Android requires a Google connection and device verification before customer rollout.

Mobile device management enrollment and policiesMobile device management enrollment and policiesMobile device management enrollment and policies

What it does

Enroll, apply policy, act when a device is lost.

Status

Where each platform stands today.

How it works

From an email to a managed device.

01

Create the enrollment

Choose the customer and platform, with an optional policy. Apple devices can inherit that customer; Android imports need an explicit customer assignment after sync.

02

Send it

Email the user an enrollment link, or hand them a QR code. The landing page walks them through it.

03

Verify enrollment and policy

Apple queues its selected configuration profile after push-token enrollment. Android receives the selected Google policy, or the default reporting policy when none is selected. Verify the device outcome rather than assuming every starter template applies automatically.

04

It appears where it should

Check inventory, customer assignment and portal visibility. An enrollment link, sent email or locally stored policy is not proof that setup completed.

Limits

What it does not do yet.

Enrollment and offboarding boundaries

  • Windows and Linux use the desktop agent; there is no Windows/Linux MDM enrollment provider in this screen. Separately, the Microsoft hub can request actions on devices already managed by external Microsoft Intune, including Windows.
  • Apple MDM and the Mac agent are separate enrollments. Screen Recording still needs local approval.
  • Retire changes local state and blocks the Apple command channel while Retired; it does not remove management or profiles from the device.
  • Local enrollment revocation does not revoke a Google-issued token and can stop existing Apple management communication. Verify offboarding separately.

Not in the product today: one connected asset record across agent, network, mobile and manual sources, and verified offboarding.

See the roadmap →

Questions

Good to know.

Your APNs MDM push certificate, matching private key and topic. RMM accepts the existing PEM material; it does not generate or sign the push certificate request. Configuration acceptance still needs verification on the device.

An authorized Google service account and bound enterprise. Enrollment requires a real Google-issued code; stored settings alone do not verify the connection or device setup.

The current active-workspace check found no Google binding or Android devices. Runtime source is deployed, but a Google-backed customer path was not verified. Talk to us before relying on it for a fleet.

The App requests Apple lock/erase and Android lock/reboot/wipe. Delivery requires the configured provider and a reachable, compatible enrolled device. Confirm the actual outcome; a sent or queued message is not completion.

Assigned, non-retired MDM devices appear read-only under Mobile devices. Explicitly assign the customer after Android sync; the import does not inherit it from the enrollment.

Keep exploring

Limits, checked daily

Not in the product today.

Each line below is a gap recorded against this capability in the product's own feature record. A line leaves this page by itself on the next daily run once that record says the gap is closed, so the list cannot fall behind what we ship. The rest of this page is written by hand.

  • There is no lost mode that tracks the location of a missing device.
  • Apple devices enroll, take profiles and can be locked, wiped and erased; automated device enrollment, managed app purchasing, disk encryption through management and kiosk modes are not built yet.
  • Android devices take policies and can be locked, restarted and wiped; kiosk mode, location and remote viewing are not built yet.

Next step

Tell us about your customers' device mix.

Half an hour on a call. We will walk through enrollment and management for the devices you actually support.