Mobile Application Management
Mobile application management (MAM) is a subset of enterprise mobility management that controls which applications are deployed to employee devices, what data those applications can access, and how applications are updated or remotely wiped — without necessarily managing the device itself.
How it works
MAM operates through an enrollment profile pushed to managed applications. The profile enforces policies: data cannot be copied from a managed app to an unmanaged one, screenshots may be blocked, and the application can be wiped remotely if a device is lost or an employee leaves. This is distinct from MDM (mobile device management), which controls the device rather than the application.
Selection criteria
| Criterion | What to evaluate |
|---|---|
| Platform coverage | iOS and Android parity is the baseline. Check whether the MAM solution covers your ERP vendor's mobile client specifically. |
| Conditional access integration | The MAM policy should integrate with your identity provider (Entra ID, Okta) so access is denied if device compliance lapses. |
| App wrapping vs SDK | App wrapping adds a management layer to existing apps without code changes. SDK integration offers deeper control but requires vendor support. |
| Selective wipe | Confirm the solution can wipe managed app data only — not the full device — to limit liability on personal devices. |
| Reporting | Audit logs of app installs, policy violations, and wipe events are required for SOX and HIPAA device-management controls. |
Frequently asked questions
What is the difference between MAM and MDM?+
Do I need MAM if my ERP is browser-based?+
Which ERP platforms support MAM natively?+
Ready to assess your ERP managed services options?
Our specialists work with IT directors and finance leads at organisations managing one or more ERP platforms. An assessment takes 45 minutes and produces a written summary you can share with your steering committee.