How to use AirWatch to wipe only corporate data from personal phones

AirWatch, now associated with VMware, gives organisations one console for provisioning apps, profiles, security policies and support across managed endpoints. During BYOD offboarding, the aim is usually not to erase the handset: it is to remove the managed work layer while leaving personal photos, contacts, messages and unrelated apps alone.

That outcome depends on how the device was enrolled and which remote action is selected. AirWatch can remove managed apps and their associated corporate information, yet it cannot reliably delete material copied into personal accounts or unmanaged apps. A safe process therefore combines the right console command with identity controls, record retention and post-action checks.

Separate managed work data from personal content

Begin by defining what counts as corporate data in your deployment. Usually this means apps installed through device ownership, managed app data, work-profile content, corporate email and documents exposed through managed apps, SSO tokens, certificates, VPN profiles and enrolment settings. On iOS and Android, the exact effect varies by platform and app, so some actions remove a managed app entirely while others clear only its managed content. Personal camera rolls, contacts and messages normally remain when they sit outside the managed boundary.

AirWatch cannot reliably remove a screenshot saved to personal Photos, a document exported to a personal mailbox, or a file uploaded to an unmanaged cloud account. Prevent this spread with managed app permissions, policy controls and user training rather than treating a remote command as complete data deletion. For Australian organisations subject to the Privacy Act 1988 and the Australian Privacy Principles, governance of access, security and disposal is equally important. Document the wipe and any retained record rather than assuming a technical reset satisfies every legal obligation.

Prepare the device and offboarding policy

Confirm whether the handset is enrolled as BYOD or corporate owned before opening the action menu. For a personal phone, verify that it has an active work profile and that the organisation has not set it up for full device management. If the device belongs to the business and is being returned, a full wipe may be appropriate. If it is BYOD, agree the offboarding outcome with the user and explain what will be removed.

Australian deployments often mix office teams in Sydney, Melbourne and Brisbane with field crews in regional Queensland and Western Australia. Handsets may switch between Telstra, Optus and Vodafone Australia services, carry dual-SIM plans, or use 5G for tethering. Set expectations in writing so a user knows which work profile, authenticator and company app will disappear and which personal services remain.

Before sending a command, preserve required corporate records through an approved repository and make sure the user has backed up any personal material they want to keep. Check battery, connectivity and the current enrolment status. A remote command needs a reachable device; it may remain queued while a phone is offline, travelling or using a congested mobile network. Record the planned action and approval before proceeding.

Run the selective wipe in the console

Sign in to the AirWatch console, or the equivalent VMware Workspace ONE area in a current deployment, and open the device record. Filter by the departing user, enrolment ID or corporate email address, then check ownership and compliance. Under Device Actions, Remote Actions or an equivalent menu, look for Selective Wipe, Enterprise Wipe or a documented BYOD data-removal action. Product labels and available options can differ by release and device platform.

Choose the selective or enterprise option rather than Device Wipe, Factory Reset or Erase All Content and Settings. Read the action summary before confirmation: a warning that all application data will be removed may mean the selected command is too broad. Some managed apps store personal and work material together, so no remote command can preserve that app’s local content while removing all corporate files. Use the product documentation for your exact configuration.

Add a reason or case reference if your workflow requires one, then start the action. Monitor the status rather than treating submission as completion. The handset may display a management notification, and an online device should return a success or failure event. If it fails, check enrolment state, network access, battery and operating-system restrictions before retrying. Do not escalate to a full wipe without confirming ownership and approval.

Compare the available wipe actions

The right choice depends on ownership and the desired result. Compare the console labels before execution because platform and VMware release differences can alter their scope.

Action Typical scope Effect on personal content Suitable use
Selective or enterprise wipe Removes managed apps and data, the work profile and company credentials; scope varies by platform Usually retained outside the managed work area BYOD offboarding
App removal Removes selected managed apps and their associated data Usually retained Narrow app cleanup
Remote lock Locks the device and protects access without deleting data Retained Temporary containment
Device or factory wipe Restores or erases the entire handset Erased Company-owned returns or approved lost-device resets

For a BYOD departure, the selective or enterprise wipe is normally the closest match because it targets the managed work layer. App removal may leave credentials or other corporate artefacts behind, while a remote lock protects access without deleting anything. Export the relevant audit record before wiping because the managed app may disappear with its local history. Test the chosen action on each supported platform before using it for live offboarding.

Preserve records and handle exceptions

Before wiping, decide which records must survive and export them through an approved repository. If an authorised archive check involves encrypted PDFs created in LibreOffice, the technical note on LibreOffice PDF decryption can help assess recoverability; decrypt or export only under company and legal authority, then retain the material according to policy.

Cross-border travel needs separate treatment. Staff travelling from Australia may pass through Australian Border Force checks with a personal handset, while a company-owned device may need to appear in travel, insurance or export records. If customs, insurance or a legal hold depends on the device’s state, obtain approval before changing it. Complete the wipe at a controlled point rather than assuming the command will work without connectivity.

Handle exceptions explicitly. For a lost or stolen phone, revoke directory, VPN and application access in parallel with locking and wiping; the mobile command is not a substitute for account containment. Shared devices, legal holds, regulated records and disputed ownership need review by IT, privacy and legal owners. Record the decision so the wipe remains auditable and proportionate.

Verify the result and complete offboarding

After the command, confirm that its status is successful and check that managed apps, work profiles, certificates and enrolment access are gone. Save the console event, timestamp, operator and affected user in the offboarding record. In a mixed estate, align the handset process with Windows endpoint guidance so departures and asset returns do not follow conflicting retention rules.

Validate the result with the user where possible: work email, intranet and managed documents should be inaccessible, while personal messages and photos should remain. Then complete offboarding in the connected systems, disabling the directory account, SSO sessions, SaaS access, VPN profiles and separately issued tokens. A successful mobile wipe does not disable those accounts, and it cannot remove corporate material the user copied into a personal mailbox or cloud drive.


Standardise BYOD offboarding by reviewing AirWatch customer stories, comparing pricing and package options, and using the fully functional 30-day free trial to rehearse the selective wipe on representative iOS and Android devices before production rollout. Contact the sales team for deployment advice, then document the approved action names, retention rules, support ownership and escalation path for your organisation.