1. LandOffer
  2. Blog
  3. All articles
  4. New Job Uses Microsoft Intune on Your Personal Device: Confirm What IT Can See

Job search

New Job Uses Microsoft Intune on Your Personal Device: Confirm What IT Can See

Separate app protection, work profiles, device enrollment and employer policies before agreeing to Intune setup on a personal phone or laptop.

10 min readLandOffer team

Before agreeing to Intune setup on your personal device, ask IT to identify the operating system, enrollment or app-management method, visible information and available controls. “We use Intune” does not answer those questions. App protection, a separate work profile and device management can expose different information and support different actions.

This guide uses current Microsoft and Android public documentation checked October 23, 2026. We read public guidance, not an employer's tenant, your device settings or a private onboarding policy. Both completed cases are fictional. LandOffer publishes this guide; recent tech roles can support a separate job shortlist while you clarify the equipment arrangement for this offer.

Classic editorial illustration of a new employee comparing a personal phone and onboarding notes with separate work and personal trays

Identify the operation before interpreting the privacy promise

Start with a plain description: personal Android phone for Outlook, personal Windows laptop for development, or company-issued iPhone. Then ask IT for the named enrollment or app-management method. Ownership and management method are separate fields. A device you bought can be enrolled in management; a work app can also be protected without full device enrollment.

Microsoft's app-protection overview describes controls such as an app PIN, restrictions on copying work data into personal apps and limits on saving corporate files. These policies can operate with or without mobile-device management. A blocked copy action describes a restriction on moving work data. It does not establish access to your camera roll; a work app can remain restricted without device enrollment.

On Android, Company Portal is required for app protection, and Microsoft 365 MAM also requires Microsoft Entra device registration. Seeing that app or a registration prompt does not, by itself, prove an Android work profile exists. Device registration, app protection and device enrollment should not be treated as interchangeable labels.

For Windows, Microsoft's account-registration explanation separates signing into one app, adding an account to the device and accepting device management. The public page explains the choices; it does not establish which enrollment, if any, your employer requires or whether app-only access will be permitted. Ask which step the onboarding instructions require rather than selecting a smaller scope as a way around an access policy.

Read the general visibility list with its platform qualifications

Microsoft's enrolled-device visibility guidance says enrollment does not give the organization access to personal call or browsing history, messages, photos, passwords or the contents of personal documents. It describes device fields such as owner, name, model, manufacturer and OS version, alongside potentially visible app inventory, storage and network details. Identifier availability needs the enrollment-method qualification below. This is guidance about that management capability, not a statement about every service your employer operates.

For example, it does not establish that work email stored in the employer's service is private from the employer. A separate work VPN, security product or remote-support session has its own scope. Ask about those tools explicitly; the Intune product name cannot settle their collection rules or your company's retention policy.

The same generic page lists identifiers such as serial number and IMEI, but a method-specific exception is important. Microsoft's Apple User Enrollment overview says this BYOD method does not collect persistent identifiers such as serial number, phone number or IMEI, nor app inventory outside the managed volume. It separates work data and has a limited management scope without supervision.

That Apple page now says Company Portal-based User Enrollment is deprecated for new enrollments and recommends account-driven User Enrollment. This does not mean all Apple enrollment is retired, or that every personal iPhone uses User Enrollment. Ask which Apple method the employer actually supports. Do not convert a generic identifier list into a promise about a specific enrollment you have not identified.

Separate app names, app data, location and remote control

Use four questions instead of the single question “Can IT see my phone?”

Information or action Public-document boundary Employer-specific question
Installed applications Personal-device managed inventory is visible; Microsoft notes some configurations expose more Which inventory is collected for this OS and method?
Personal content Intune enrollment is not general access to personal photos, messages or document contents What other agents, services or support tools are required?
Location Microsoft distinguishes locating a lost corporate device from a personal device Can work apps collect location with their permissions?
Control and removal Available actions depend on platform and configuration What can IT change, remove or reset in this exact setup?

A personal device's physical location and a work app's location data are different questions. Android's work-profile guidance says organizations can see work-profile network activity and location information from work apps. It also explains that a VPN configured within that profile does not route personal-profile app traffic. That does not describe every VPN or establish the permissions of your employer's particular app.

Keep the operating-system qualifier attached to permission statements. Microsoft's general visibility page labels its description of administrators granting work-app permissions as applying to Android 11 and earlier. It should not be copied as an explanation of every permission prompt on a newer phone.

Worked Android review: Lena separates three data questions

Lena is a fictional new analyst with a personally owned Android 14 phone. In this example, her supplied onboarding sheet explicitly names an Android Enterprise personally-owned work profile, work Outlook and a work scheduling app. It also says the scheduling app may request location for site check-in. No actual employer policy, app permission or tenant configuration has been inspected.

Her completed diagnostic record is:

Item in the fictional packet Conclusion supported by public guidance Remaining decision
Personal ownership plus named work-profile method Android separates personal and work profiles; the profile is managed Confirm IT records that exact ownership and method
Work Outlook and scheduling app These belong to the proposed managed work scope Ask which app details and work data are collected
Personal photo library and personal banking app Work-profile guidance does not give IT general visibility into personal apps and their data Do not supply personal photos or banking screenshots for setup
Scheduling app location request Work-app location can be visible even though this is a personal phone Ask when location is collected, why and how long it is retained
Copying a work attachment into a personal app Cross-profile sharing can be restricted Use the approved work destination; do not work around the restriction
End of employment Removing work-profile company data removes its apps, settings and data Obtain the offboarding process before treating the setup as reversible

Lena records two separate findings: the named work-profile method documents separation of personal content, while the scheduling app's location collection and retention still need an employer answer. The presence of a personal banking app is not proof IT can see it, and the personal ownership label is not proof that work-app location is absent.

Her completed decision is to pause the optional phone setup pending the location answer and ask whether a company device or another approved access arrangement is available. She does not assume either alternative is offered. If the job requires site check-in, she needs a workable approved arrangement rather than a promise to deny a permission and hope the app still works.

This record deliberately contains no real serial number, account email, photos or permission screenshots. An actual IT question generally needs the OS, ownership and method first. If support later needs a screenshot, review what it contains and use the employer's approved support channel.

Classic editorial illustration of a new employee and IT colleague reviewing a personal laptop and a separately identified company equipment option

Ask about offboarding before using removal as a test

Visibility and control are different. A system can enforce an access rule or remove managed data without giving an administrator the contents of your personal messages. It is also possible to lose work access without erasing personal files.

Microsoft's Retire documentation describes removing managed company data and settings while preserving personal data. For Android personally owned work-profile devices, that includes the work profile's data, apps and settings. Its Wipe documentation describes factory-reset actions with platform-specific prerequisites and options. Retire and Wipe describe different actions; identify the specific operation and its effects instead of treating either name as a generic disconnect.

Do not assume every listed action is available on every personal device. Equally, do not assume “personal” prevents all destructive actions under every enrollment method. Ask which operations apply to your actual platform, which are restricted by the employer and what happens if the device is lost or you leave.

Microsoft's Company Portal removal guidance warns that unenrollment can remove access to protected work files, apps and email. Coordinate offboarding with IT rather than deleting a profile to test privacy. Preserve personal backups using your ordinary safe process, without exporting company files into personal storage. We did not remove a device or verify a wipe, retire or recovery operation.

Worked Windows decision: Darius needs an equipment answer

Darius is an independent fictional case. He starts a development job next week and owns a Windows 11 laptop used for personal projects. His invented onboarding note says “sign into Outlook and allow management,” but does not name the management policy, inventory scope or required security agents. The equipment form lists a company laptop option with delivery unconfirmed. No promise of shipment or employer approval is represented.

He completes a three-route comparison using Microsoft's public Windows explanation:

Route described in public documentation Meaning for this review Darius's decision
One-app sign-in The account is not added to Windows and that flow does not register the device in the organization directory Do not assume this satisfies development access requirements
Account added to the device Directory registration exposes fields such as name, OS, owner and compliance information Registration alone does not answer the management-policy question
Device-management enrollment IT can apply device settings, apps and security policies Obtain the actual scope before agreeing on a personal laptop

His completed gap list contains six unresolved fields: required enrollment method, recorded ownership, inventory and diagnostic collection, additional agents or VPN, applicable reset/removal actions, and offboarding assistance. He marks all six unresolved. None becomes “not collected” merely because the onboarding note omitted it.

His unsent request reads:

Hi IT team, I start the development role next week and would be using my personally owned Windows 11 laptop. The onboarding note asks me to allow management. Could you confirm the exact enrollment method and personal-ownership classification, the inventory and diagnostic information collected, and any required security agents, VPN or remote-support tools? Please identify the settings and removal or reset actions available in this setup, plus the approved offboarding process. The equipment form also lists a company laptop: is that option available for my start, and what approved interim access should I use if delivery is later? I have not enrolled the personal laptop or assumed that app-only access meets the role's requirements.

Darius chooses to keep personal enrollment pending and request the company-equipment decision plus an approved start-day arrangement. This is a completed review outcome, not a claim he can refuse every requirement without affecting access. He also keeps family and personal-project data out of the support request; IT can identify the policy without receiving those files.

Keep the answer tied to the device you will actually use

Save the employer's dated response with its enrollment instructions and privacy notice. Record the OS, method, ownership classification, tools, visible information and removal process in the same place. Ask for a separate answer for each device you intend to use. Android work-profile instructions do not resolve a Windows laptop request, and a colleague may have a different assigned policy.

If already enrolled, Microsoft's visibility guide points to Company Portal Device Details for the ownership type. Use an approved support discussion to resolve a mismatch rather than changing ownership or security settings yourself. We did not inspect any enrolled device or organizational account.

The useful answer is specific enough to decide whether this equipment arrangement works for you. Ask IT for missing fields and an approved alternative where needed. Keep recent LandOffer roles as a separate shortlist; Intune clarification is an onboarding decision, not evidence about another employer's policy or a guarantee of continued access.

Sources and Further Reading