How AirWatch Integrates with Okta for Identity Management
Identity and endpoint management meet at a critical security boundary: the moment a person signs in and requests access to corporate data. AirWatch, now associated with VMware, manages the devices, applications and compliance controls that hold that data. Okta manages users, authentication and application entitlements. Connecting both platforms creates a stronger identity-based access model than either system provides independently.
For Australian organisations, this combination can support hybrid workers, BYOD programmes and regulated environments without adding unnecessary administration. It also gives IT teams a more complete view of who accessed a resource, which device they used and whether that device met security requirements.
Responsibilities that reinforce each other
Okta serves as the identity layer. It can authenticate employees and contractors, apply multifactor authentication, manage group membership and control access to cloud applications. Okta also records sign-in events and evaluates risk signals such as location, device status and user behaviour.
AirWatch operates as the endpoint layer. It enrolls devices, installs managed applications, configures security settings and reports whether hardware meets organisational standards. These controls can cover encryption, screen locks, operating-system versions, application permissions and restrictions on device functions.
The integration links these responsibilities through shared identity and device information. A user authenticated in Okta can be associated with a correctly enrolled AirWatch device. Access decisions can then consider both the person's account status and the endpoint's compliance. This gives security teams separate control over identity and device posture while producing a consistent decision for the user.
Common technical methods include SAML 2.0 or OpenID Connect federation for single sign-on, directory synchronisation and, where supported, SCIM provisioning. APIs can also exchange enrollment, user and compliance information. The exact method depends on the deployed editions, licensing and architecture.
Authentication, access and device posture
Okta can protect access to AirWatch administrative services through federated single sign-on. Instead of maintaining a separate password for every management portal, administrators can use Okta's authentication policies, including multifactor authentication. Local emergency accounts should remain securely controlled for recovery when the identity service or corporate network is unavailable.
End-user access requires a clear division between application assignment and endpoint deployment. Okta can determine whether a person is entitled to an application, while AirWatch determines how a corporate application is installed, configured and protected on a particular device. Keeping those roles separate prevents conflicting policies, particularly when the same application can be accessed from a managed phone, browser or company desktop.
Conditional access brings identity and posture together. In supported configurations, Okta can use device signals to decide whether a session should proceed, require an additional factor or be blocked. AirWatch can independently enforce the underlying endpoint controls. For example, Okta may refuse a risky sign-in, while AirWatch can quarantine an app or deny access to corporate data on a non-compliant device.
This combined approach is particularly useful for BYOD. Access can depend on device enrollment, required security settings and the user's assigned role. The organisation can permit flexibility for personal devices without treating every enrolled device as fully trusted.
Security outcomes and operational trade-offs
A sound deployment assigns each control to the platform best equipped to enforce it. The division should also identify where automation connects one platform to the other.
| Area | AirWatch | Okta | Combined approach |
|---|---|---|---|
| User identity | Maintains user and enrollment records | Acts as the identity authority and manages groups | One user identity supports device enrollment and application access |
| Authentication | Supports federated access to management services | Provides single sign-on, multifactor authentication and risk policies | Users authenticate centrally while endpoint policies remain in force |
| Device posture | Checks encryption, configuration, OS and app compliance | Uses device context in supported conditional-access policies | Access decisions consider both account risk and device compliance |
| Offboarding | Removes apps, unenrolls devices and can wipe corporate data | Disables accounts, revokes sessions and changes entitlements | Automated workflows reduce the delay between departure and revocation |
| Audit events | Records enrollment, configuration and endpoint actions | Records sign-ins, authentication attempts and identity changes | Logs can be correlated in a SIEM for a fuller investigation trail |
The integrated model improves visibility, but it does not remove implementation work. Device signals must be mapped carefully to Okta policies, and endpoint restrictions must support the business workflow. If compliance data is stale, a valid identity could still receive access through a device that no longer meets policy.
Shared responsibility also affects incident response. Disabling an Okta account stops future authentication, yet an already issued session or offline device may retain limited access. A robust offboarding process coordinates account suspension, session revocation, application removal, device unenrollment and, where appropriate, remote wipe. These actions should be tested against both managed phones and shared tablets.
Deployment and identity lifecycle
Most implementations begin with Okta as the authoritative identity source. Employee or contractor records are synchronised with the AirWatch directory, while Okta groups can inform application assignment and AirWatch policies. Newly hired staff receive an identity, the required multifactor method and an enrolled endpoint through separate but coordinated workflows.
Lifecycle automation is critical. Where the installed product supports SCIM, it can reduce manual user creation and updates. API-driven provisioning can cover other requirements. Deactivated accounts, contractors reaching their end date and transferred employees should trigger prompt updates to both systems, including removal from privileged groups and access to sensitive apps.
Australian organisations should connect these workflows to their broader governance obligations. Commonwealth and state government agencies commonly align identity controls with the Australian Signals Directorate's Essential Eight. Private-sector organisations in finance, health and critical infrastructure may also reference the Australian Privacy Act and the Australian Privacy Principles when defining access, auditability and data-handling requirements.
A staged deployment reduces operational risk. A representative pilot can test directory matching, single sign-on, conditional access and offboarding before expansion. Break-glass procedures, local break-glass accounts and recovery documentation should be included from the outset, particularly where field users may be offline for extended periods.
An operating model for Australian teams
Many Australian businesses now coordinate staff across Sydney, Melbourne, Brisbane and regional offices. Hybrid work increases the volume of unmanaged access points, yet endpoint and identity controls must remain consistent. AirWatch can enforce standards on company-managed devices, while Okta applies account policies across office networks, home connections and mobile networks.
Field operations create a different access pattern. Mining teams in the Pilbara, transport operators and agricultural businesses in regional Queensland may use shared tablets, intermittent connections and worksite-specific applications. AirWatch can preconfigure those endpoints and set sensible offline periods. Okta can restrict each shift to authorised users, while carefully defined offline access prevents connectivity gaps from becoming uncontrolled data exposure.
Identity events and endpoint records should flow into the security team's existing monitoring environment. Relevant alerts can include impossible travel, repeated MFA failures, unusual application use and access from a newly enrolled device. Correlation between systems helps analysts distinguish a credential problem from a compromised endpoint.
Australia's geography also affects support coverage. Teams spanning Perth, Darwin, Brisbane, Sydney and Melbourne operate across several time zones and extended service windows. Runbooks should use straightforward Australian English, with terms such as “authorised”, “organisation” and “enrolment” used consistently. Clear ownership and escalation times are essential when identity, device and application support need to work together.
Build a unified access model
A successful Okta and AirWatch integration starts with clear ownership. Okta should remain the primary authority for users, authentication and application entitlements, while AirWatch manages devices, application configuration and endpoint compliance. Integration workflows should connect onboarding, role changes and offboarding rather than leaving each system to operate independently.
Australian organisations can begin by reviewing their user lifecycle, BYOD exposure and conditional-access requirements. A well-scoped pilot can validate the technical connection, provide measurable security outcomes and reveal where policy exceptions are needed.
Explore AirWatch pricing and package comparisons, review customer stories, and contact the sales team to plan an Okta-connected deployment. Request a fully functional 30-day free trial to assess identity-aware endpoint management against Australian security, workforce and device requirements.