The future of EMM: AirWatch’s roadmap for 2025 and beyond
Enterprise mobility management (EMM) has grown from a tool for enrolling phones and pushing email into a central control plane for access, applications and endpoint risk. The future of EMM centres on context: who is requesting access, which device they use, what data the request may expose and whether conditions justify granting it. For Australian teams, that shift matters as hybrid work, bring-your-own-device programs and mobile-first operations become routine rather than exceptions.
AirWatch now sits within VMware’s endpoint and digital workspace ecosystem, where its administration strengths connect with identity, access and device posture capabilities. This gives organisations a practical base for unified endpoint management, yet it also makes roadmaps and commercial boundaries harder to read. The useful AirWatch roadmap for 2025 and beyond is therefore less a list of dated features than a set of outcomes: fewer manual tasks, clearer risk decisions and a consistent experience across corporate and personal devices.
From device administration to context-aware mobility
Traditional EMM focused on enrolment, configuration, compliance and application distribution. Those controls remain essential, but mature deployments now expect the console to explain why a device is noncompliant, which business service is affected and which remedy is safe. That turns administration into operational decision-making, particularly where a device can be both a productivity tool and a route into sensitive company data.
Context changes with each request. A Sydney accountant may use a managed laptop at the office and an approved personal phone in the evening. A Melbourne courier may switch from a rugged company handset to a web session over mobile data. A contractor in Perth may join a project workspace for only eight weeks. Each situation calls for policies based on identity, application sensitivity, network and device state rather than a single corporate-versus-personal rule.
The platform direction points toward automated remediation, contextual access and simpler self-service. AirWatch can feed a wider workspace view while organisations retain familiar mobile administration. The roadmap test is whether fewer alerts reach service desks and users can resolve routine issues without waiting for a technician.
Security convergence with an Australian compliance lens
Security is becoming inseparable from mobility management. Device posture, user identity, application permissions and data classification need to travel together in an access decision. Encryption, remote lock or wipe and compliant configuration remain useful controls, but their value rises when they trigger a defined response: block a session, limit an application, require reauthentication or revoke an access token.
Australian organisations must also account for how mobile administration affects personal information. Under the Privacy Act 1988 and the Australian Privacy Principles, organisations subject to the Act must be transparent about collection and use, protect personal information and restrict it to permitted purposes. Device inventory, location metadata and application activity can reveal more than an IT administrator needs. The Notifiable Data Breaches scheme adds another layer by requiring eligible organisations to assess and notify affected people when serious harm is likely.
For critical infrastructure operators, the Security of Critical Assets Act 2018 and the Australian Signals Directorate’s Essential Eight provide additional security context. AirWatch can supply device-state evidence and enforce configured controls, while local incident-response procedures determine what happens next. Australian mining, logistics and government customers should test those integrations against actual operational systems rather than assuming a compliant console guarantees a compliant environment.
Platform consolidation and the cloud operating model
Following Broadcom’s acquisition of VMware, AirWatch forms part of a broader portfolio that customers increasingly encounter through Workspace ONE. This consolidation favours connected endpoint management: mobile administration, identity, access policy and security signals can appear within a shared operating model. It also changes how buyers interpret product roadmaps, since some AirWatch capabilities may evolve as parts of a wider suite, an ecosystem integration or a revised commercial package.
The technical direction is increasingly cloud-first and automation-led. Routine configuration, application deployment and compliance evaluation can run through centrally managed workflows, while intelligent analysis may help teams prioritise incidents or identify risky device states. Human approval remains important where a mistaken remediation could interrupt a worker’s only route to payroll, dispatch systems or clinical information.
Interoperability will determine how quickly organisations can adopt that direction. Identity providers, Microsoft 365, service-management platforms and collaboration tools need reliable data exchange without creating conflicting policies. Australian enterprise and public-sector buyers should also assess support hours, data residency options, migration effort and contractual service levels, particularly when operations span Sydney, Melbourne, Brisbane and Perth.
A staged roadmap for Australian mobility teams
A staged approach reduces the risk of replacing a working mobile environment with a larger but underused platform. Start with an inventory of devices, applications, owners and data access. Segment the estate by risk and work pattern, then introduce identity-based and conditional access policies. Automated remediation should follow, supported by clear exceptions for shared devices, field equipment and operational systems that cannot tolerate the same enforcement rules as office endpoints.
The pilot should include both everyday office users and mobile-heavy teams. Hybrid employees checking messages and calendars on personal phones create a different environment from logistics staff in Brisbane using rugged devices, or field crews in Western Australia relying on intermittent connectivity. Include those differences in support models, application choices and success measures before expanding the program across the business.
The commercial case should be tested alongside the technical one. A fully functional 30-day free trial can expose administration and support effort before a broad rollout, while customer stories and package comparisons help teams model adoption. Before renewing or consolidating, a current AirWatch pricing and licensing review can clarify tier boundaries and optional add-ons; Australian buyers should also check data residency terms, support hours and total cost over the contract term.
Turning the roadmap into operational value
Roadmaps should be judged by outcomes rather than feature volume. Useful measures include the time required to enrol a device, the percentage of issues resolved without help-desk intervention, the number of high-risk sessions blocked and the reduction in manual compliance work. These indicators connect platform investment with service quality and operational resilience.
The appropriate operating model also depends on the existing endpoint estate, internal skills and expected growth. These approaches can be compared across their principal benefits and trade-offs.
| Operating approach | Primary emphasis | Best fit | Main trade-off |
|---|---|---|---|
| AirWatch-led mobile estate | Device enrolment, applications, profiles and compliance | Focused mobile or wearable programs | A narrower management scope than a full workspace platform |
| Workspace ONE with AirWatch | Endpoint management, identity, access and digital experience | Hybrid workforces with mixed corporate and personal devices | Integration and commercial validation require careful planning |
| Microsoft-centric with AirWatch | Microsoft management for productivity and Windows, AirWatch for mobile | Organisations already standardised on Microsoft 365 and Intune | Overlapping controls can create administrative boundaries |
| Partner-managed service | Platform deployment, monitoring and operational support | Lean internal IT teams needing extended coverage | Response times and outcomes depend on clear service agreements |
Begin the next stage with a representative pilot and measurable acceptance criteria. Select one high-value mobile workflow, document the current support burden, and establish the compliance and access outcomes the deployment must achieve. Use the 30-day trial to test enrolment, application access, conditional policy, reporting and remote support with real users in the intended environment.
Request a tailored sales consultation with those findings attached, then compare the available packages against the agreed pilot results. A focused deployment will reveal whether AirWatch and VMware’s broader ecosystem can meet Australian security obligations, support everyday mobile work and deliver a clear return on investment before a wider rollout.