SMSMC Blog

Company data on personal phones: a BYOD setup that protects the business without owning the phone

How to protect company email and files on employee-owned phones with app protection, Apple User Enrollment and Android work profiles, without taking over the phone.

By Jim Venuto

What NIST says about personal phones at work

In May 2023 NIST published Revision 2 of SP 800-124, its guidelines for managing the security of mobile devices in the enterprise. The update explicitly covers personally owned devices alongside company-issued ones, and it is frank about the tension. A bring-your-own-device (BYOD) model, NIST writes, raises concerns that company information can leak from the phone to untrustworthy third-party services that other apps on the device talk to. It also notes that the organization usually knows nothing about where a personal phone came from, whether it has been rooted or jailbroken, or whether it already carries malware.

NIST’s suggested middle ground is mobile application management (MAM): control the work apps rather than the whole device. The guidance says that MAM does not require the owner to enroll the device or accept an enterprise profile, and that using it instead of full device management may help with employees’ privacy concerns about their own phones.

That is the practical answer for most small and mid-sized organizations. Employees already read work email on their own phones. The question is whether you protect that data deliberately or leave it to chance.

The problem in plain terms

Without any controls, a personal phone that reads company email can copy an attachment into a personal cloud drive, paste client details into any app, and keep everything after the employee leaves. If the phone is lost, the company has no way to remove its data. If you go to the other extreme and require full device management, many employees will refuse, or they will comply and resent IT having power over their personal photos and messages.

The good news is that the major platforms now support a split: the company manages its own apps and data, and the rest of the phone stays the employee’s.

Three ways to separate work from personal

ApproachWhat the company managesWhat the company can removeWho it fits
Microsoft Intune app protection policies, no enrollmentMicrosoft 365 apps and other protected apps, at the app levelWork data inside protected apps onlyOrganizations on Microsoft 365 whose staff mostly need email, Teams and files
Apple account-driven User EnrollmentWork accounts, settings and managed apps on an iPhone or iPadManaged data only, not the whole deviceOrganizations that need some device-level settings on personal iPhones
Android Enterprise work profileA separate work profile on the phoneThe work profile onlyOrganizations that want a clearly separated work space on personal Android phones

App protection policies without enrollment

Microsoft documents that Intune app protection policies can be used independently of any device management, including on employee-owned devices that are not enrolled at all. Policy applies only when the app is used with a work account. Typical settings include requiring a PIN or biometric to open work data, blocking copy and paste from work apps into personal apps, preventing work files from being saved to personal storage, and encrypting work data inside the app. Microsoft’s own framework starts at a basic level (app PIN, encryption, selective wipe) and steps up to stronger data-leak controls and minimum operating system versions.

There are limits. Microsoft notes that without enrollment, apps are not pushed to the phone (the employee installs them from the store), and Wi-Fi, VPN and certificate profiles are not delivered. On Android, the Intune Company Portal app must be installed for app protection to work, even though the device is not enrolled.

Apple User Enrollment

Apple describes account-driven User Enrollment as the option for BYOD. The employee signs in with a work account, and IT manages only the organization’s accounts, settings and data, never the user’s personal account. Apple’s enrollment comparison lists what the organization cannot do under User Enrollment, including querying the serial number or phone number, seeing the full list of apps, querying the device location, viewing personal mail, messages, call logs or browser history, and remotely erasing all content and settings. It can remotely erase managed data.

Android work profile

Google describes the work profile as a separate container where the organization manages work apps and data while personal apps, data and usage stay private. Google states that a remote wipe on a personal phone with a work profile removes the work profile without affecting the employee’s personal profile.

Make the controls stick with Conditional Access

App protection only helps if people cannot sidestep it by using an unprotected mail app. Microsoft’s guidance is to pair app protection policies with a Conditional Access policy in Microsoft Entra ID that, for iOS and Android, grants access only to apps that meet the app protection requirement. Microsoft recommends starting the policy in report-only mode to see the impact first, excluding at least one emergency account so administrators cannot lock themselves out, and also blocking unknown or unsupported device platforms. Phones must register with Entra ID for this to work.

One change to note: Microsoft has retired the older “Require approved client app” grant. Its migration page says that since June 30, 2026, that control and any policies using it are read-only, and that new policies should use only “Require app protection policy”. If your Conditional Access policies were written a few years ago, check them.

Selective wipe versus full wipe

This is the point that matters most to employees.

  • Full wipe returns the phone to factory settings and removes everything, personal and work. Microsoft notes that full device wipe is only available on devices enrolled in Intune device management. Do not use it on personal phones.
  • Selective wipe removes only company data. With Intune app protection, it removes work data from protected apps without removing the apps. Apple User Enrollment erases only managed data. An Android work profile wipe removes only the work profile.

Write this into your policy so employees know, in advance, that leaving the company or losing the phone means the company removes its data, not their photos.

What the company can and cannot see

Microsoft publishes a plain-language list for enrolled devices. The organization cannot see calling and browsing history, email and text messages, contacts, calendar, passwords, pictures, or the content of user-created documents. It can always see the device owner, name, serial number, model, manufacturer, operating system version and IMEI. On personal devices it sees only the last four digits of the phone number, cannot view the device location, and sees the managed (work) app inventory. Apple and Google describe similar boundaries for User Enrollment and the work profile.

Share the vendor’s own page with employees. It answers the question most of them are actually asking.

NIST also cautions that monitoring which is reasonable on a company-owned phone, such as location tracking, may be unacceptable on a personally owned device and can conflict with privacy law.

A short BYOD policy checklist

  1. State which data and apps may be used on personal phones (for example, email, Teams and OneDrive, but not the client database).
  2. Name the technical approach: app protection only, User Enrollment, or work profile.
  3. Require a device screen lock and an app PIN or biometric for work apps.
  4. Require supported, updated operating systems, and block rooted or jailbroken devices.
  5. Block copying or saving work data into personal apps and storage.
  6. Enforce access through Conditional Access so unprotected apps cannot connect.
  7. Explain in writing what the company can and cannot see, with links to the vendor pages.
  8. Commit to selective wipe only, and say when it will happen: loss, theft, or departure.
  9. Require prompt reporting of a lost or stolen phone, and say who to call.
  10. Have employees acknowledge the policy before access is granted, and review it yearly.

Who does what

The owner or manager decides which data is allowed on personal phones and approves the policy. IT or your managed service provider builds the app protection and Conditional Access policies and tests them in report-only mode. Employees install the required apps, accept the policy, and report losses quickly.

When to get help

If you are not sure which of these models fits your licenses and your people, or your Conditional Access policies predate the current guidance, an outside review can sort that out before something goes missing.

Want to talk it through? Book a free 30-minute call with Security Medic Consulting.

Sources