EMM vs MDM: What Does a Business Mobile Management Plan Need?

Two purple phones: one beside a cog, the other with app tiles and a shield.

A supplier says you need EMM. Your IT team asks for MDM. Meanwhile, someone needs to decide whether staff can read work email on their own phones — and what happens to that email when they leave.

The useful distinction in EMM vs MDM is scope. Mobile device management focuses on enrolled devices and their settings. Enterprise mobility management is the broader category, bringing together device, application and data management, often with identity and access integration. MDM is usually part of EMM, rather than a competing alternative. IBM’s overview of EMM sets out these components.

For a business buyer, the next step is to document the controls, responsibilities and evidence you need. Start with ownership and enrolment, then work through apps, identity, updates, loss and offboarding. That gives you a brief a supplier can answer properly.

EMM vs MDM: What Do the Terms Cover?

Term Main Focus Question to Ask
MDM: Mobile Device Management Enrolment, device configuration, inventory and supported remote actions. Which settings can we apply to each device and enrolment type?
MAM: Mobile Application Management Work applications and the business data they handle. Which apps support the protection rules we need?
EMM: Enterprise Mobility Management A broader combination of device, app, data and identity capabilities. How do those controls work together in our environment?
UEM: Unified Endpoint Management Management extending across mobile and other endpoints, such as desktops. Does the proposed service cover our wider device estate?

These are category descriptions, not a feature list for every product. IBM describes MDM as a foundation of EMM and explains the wider scope of UEM. The NCSC’s MDM guidance also warns that device types, security features and management options differ between services.

Ask suppliers to translate the acronym into a written scope: supported devices, operating systems, enrolment methods, applications, licences and support responsibilities. “We provide EMM” is the start of that conversation.

Mobile Device Management for Business Starts With Ownership

A company phone used only for work has different requirements from an employee’s personal phone. A company phone that permits personal use needs its own rules too. Shared tablets and devices dedicated to one task belong in separate groups.

For each group, record who owns the hardware, who uses it, what business data it can access and whether personal use is allowed. Then explain what administrators can see or change, and what happens when management is removed.

Enrolment is a material part of that decision. Apple’s enrolment comparison shows that available controls and administrator visibility vary by method; it also says not every management service offers every option. On Android, a Work Profile separates work apps and data from personal use, while company-owned devices can allow additional policies.

For bring your own device (BYOD), write an employee-facing explanation before rollout. A clear answer to “Can IT erase my photos?” is more useful than a vague assurance about privacy. Base the answer on the actual enrolment method and configured actions.

Write the App and Identity Requirements Together

Make an application list that reflects how people work: email, messaging, documents, CRM, field-service software and any specialist tools. Identify where business data is stored, downloaded or shared. For each app, decide which actions should be allowed and which need a restriction.

App management and device management can be combined. Microsoft documents Intune app protection with or without MDM enrolment, but it applies to supported applications and has dependencies and limitations. App protection without enrolment does not provision company Wi-Fi, VPN or certificate profiles. Verify the exact apps and access paths instead of assuming that every app receives the same protection.

Next, specify who can sign in, how they authenticate and what should happen when a device or app fails your policy. In Microsoft’s model, Intune supplies device compliance information to Microsoft Entra Conditional Access. That is an example of the integration to check, not a promise that every EMM service includes the same identity controls.

Include the awkward cases: a replacement phone, an unavailable authentication method, a contractor and a shared device. Assign someone to approve exceptions, with an expiry date and a record of the decision.

A Business Mobile Management Requirements Matrix

Use this matrix to prepare your supplier brief. The evidence column tells you what to request or demonstrate; the source links explain the relevant platform or guidance. It is a planning tool assembled from public documentation, not a product certification or a hands-on comparison.

Requirement Decision to Document Evidence to Request
Ownership and Privacy Separate personal, company-owned, shared and dedicated devices. Define permitted personal use. Visibility and removal rules for each group, checked against Apple enrolment or Android Work Profile documentation.
Enrolment Choose the setup route, authentication and recovery process for each group. A supported-method list and a representative setup demonstration. See NCSC MDM preparation.
Applications and Data Name approved apps and define download, sharing and removal rules. An app-by-app support assessment and test of required restrictions. See Microsoft app protection.
Identity and Access Define authentication, access conditions and exceptions. Licence and integration requirements; demonstrations of allowed and blocked access. See Microsoft’s identity integration example.
Updates Set supported OS and app versions, update deadlines and replacement rules. Version reports, overdue-device handling and an exception workflow. See NCSC monitoring guidance.
Loss or Theft Name the reporting contact, action approver and recovery route. A rehearsal covering identity access, SIM service and supported device actions; record command status. See NCSC remote erasure guidance.
Offboarding Set the order for access removal, business-data handling, SIM decisions and hardware return. A completed test leaver record, including pending actions and wipe scope. See Microsoft’s wipe documentation.
Support and Administration Assign policy ownership, administrator permissions, support hours and escalation. A written division of responsibilities, administrator-access review and pilot results. See NCSC service-selection guidance.

Give each row an owner and an acceptance criterion. Replace “supports remote management”, for example, with a defined action on a named device and enrolment type, plus the result you expect to see in the management record.

If your management plan includes cellular profile deployment, use our business eSIM deployment guide to check device, enrolment and provider requirements and rehearse replacement support.

Plan for Loss and Offboarding Before Rollout

A lost-phone procedure needs more than a button labelled “wipe”. Staff need a reporting route they can use without the missing phone. Your support team needs to know who may authorise actions, which accounts and SIM services to address, and how to track unfinished work.

Remote erasure depends on the device being reachable. NCSC guidance says an MDM remote wipe requires the device to be turned on and have a data connection. Record whether an action was requested, remains pending or has completed. Do not treat a submitted command as proof of erasure.

For leavers, distinguish removing business app data from resetting the whole phone. Microsoft’s Intune Wipe action removes personal and organisational data, apps and configurations, with platform-specific behaviour. Approve the appropriate action for the ownership model before using it.

A hypothetical sales employee using a personal phone might need work access removed and supported business app data cleared. A returned company phone might need approved data preserved, then a reset before reassignment. Write separate procedures and test them on representative devices.

If you are changing mobile provider as well as reviewing device management, use our business SIM-only switching checklist to coordinate contract dates, number transfers, device checks and authentication testing.

What to Take Into a Supplier Consultation

Bring the completed matrix, your device and application lists, ownership rules, identity requirements and the results you expect from a pilot. Ask for gaps and dependencies to be marked explicitly, including anything that requires another licence, a different enrolment method or replacement hardware.

Vertu Connect has an enterprise mobility management service page alongside its business mobiles options. Use the consultation to confirm how a proposed service would meet your documented requirements.

If business eSIMs form part of your setup, include provisioning, transfer and cancellation responsibilities in the same requirements brief. Assign an owner for both the mobile service and device-management tasks.

Talk to Vertu Connect to review your completed policy and platform requirements, including device ownership, apps, identity, support and connectivity.

Frequently Asked Questions

Is EMM Better Than MDM?

EMM describes a broader scope, while MDM handles device management. Compare the controls your business needs with the proposed service’s documented support, dependencies and pilot results.

Can We Protect Work Apps Without Enrolling the Whole Phone?

There are options. Microsoft documents app protection without MDM enrolment for supported apps, subject to its requirements and limitations. Check your application list and identity setup before choosing that approach.

Does Mobile Management Guarantee Compliance?

A management product is not evidence that your organisation meets every obligation. Define the relevant requirements, assign responsibility and retain records of the controls you configure and verify.

How Often Should We Review the Plan?

Use a quarterly review, with an earlier check after material OS or platform guidance changes. Also revisit the affected requirements when apps, ownership models, identity services or support needs change.

Ready to Review Your Business Mobile Management Plan?

Bring your completed policy checklist and platform requirements to a consultation with Vertu Connect. Discuss device ownership, apps, identity and support needs before choosing an approach.

Discuss Your Mobile Management Plan

Join The Conversation

  1. Jamie Walsh says:

    Should we enrol a remote starter's phone into MDM before sorting the eSIM, or does the order not really matter?

    1. Drew Clarke says:

      The order can matter. Enrolment, eSIM installation and any number transfer are separate jobs with different owners, but if your MDM service pushes the profile, enrolment must come first. The phone also needs Wi-Fi before it can download anything, so rehearse the whole sequence — getting online, enrolling, receiving activation material, installing the profile — before the starter's first day.

  2. Alex Lane says:

    When a leaver returns a company phone, should we remove the eSIM profile before wiping it, or does the reset sort that as well?

    1. Casey Lane says:

      Don't rely on the reset. Whether a wipe removes the eSIM depends on the erase method and preservation settings, so decide first whether the profile should be kept (phone being reassigned) or removed, then test that exact action on a spare. Either way, treat the provider subscription separately — deleting the profile doesn't end the airtime contract.

Leave A Comment

Your email address will not be published. Required fields are marked *