Cookies on this site

We would like to use cookies to understand how the site is used and to measure our campaigns. Nothing is set until you choose, and you can change your mind at any time from “Cookie settings” at the foot of every page. Privacy policy

Contact UsContact Us

Resources / Blogs

Microsoft 365 & Azure

Offboarding Devices in Intune — Retire vs. Wipe vs. Delete, and Why the Order Matters

Learn the correct Intune offboarding process. Compare Retire, Wipe, and Delete actions to protect company data and manage devices securely.

· · 3 min read

Summary:

Microsoft Intune provides three different ways to remove a device—Retire, Wipe, and Delete—and they are not interchangeable. Choosing the wrong option can leave corporate data on a personal device or trigger a factory reset when you only intended to remove management. This guide explains how Intune device management handles each action and the correct offboarding sequence for secure endpoint management and device lifecycle management.

Device offboarding looks like a one-click task until you open the Microsoft Intune action menu and see three options that all appear to remove a device: Retire, Wipe, and Delete. They behave very differently, and choosing the wrong one can either leave corporate data exposed or wipe a device that was never meant to be reset. Understanding these actions before processing an employee departure or responding to a lost-device incident helps create a reliable Intune offboarding process.

Retire is the action you want for most offboarding scenarios, especially in BYOD device management environments. It removes only the company footprint—the Intune management profile, security policies, and corporate data—while leaving personal apps, photos, and accounts untouched. For a personal phone enrolled through Microsoft Intune, Retire is the correct approach because it protects business information without affecting the employee’s personal content. This is a key best practice in mobile device management (MDM).

Wipe is the heavier option. It performs a full factory reset, erasing everything on the device and returning it to an out-of-box state. This action is appropriate for corporate-owned devices that will be reassigned, as well as lost or stolen devices where organizational data may be at risk. For corporate device management, Wipe helps maintain strong endpoint security by ensuring sensitive information is removed completely. However, using a Wipe action on a personal BYOD device would erase personal data along with company information, making it unsuitable for most employee-owned devices.

Delete is the option that often creates confusion in Microsoft Intune management. Deleting a device record only removes it from the Intune admin center; it does not remove management, policies, or company data from the actual device. If administrators choose Delete Device from Intune before a Retire or Wipe action has been processed, the device can become orphaned. The device disappears from the console but may still contain corporate data and active management profiles. In other words, Delete is a cleanup action, not a device removal action.

A safe offboarding order

  • Identify the ownership type first—personal (BYOD) or corporate-owned—because it determines whether you should use Intune Retire Device or Intune Wipe Device.
  • For BYOD devices, run Retire to remove the company profile, policies, and corporate data while preserving the user’s personal information.
  • For corporate-owned, lost, or stolen devices, run Wipe to perform a complete factory reset and protect organizational data.
  • Confirm that the device has checked in and that the action completed successfully. Both Retire and Wipe require the device to be online before the requested action can be processed.
  • Only after the action has completed should you Delete Device from Intune to remove the stale record from the console. Delete should always be the final cleanup step.

The most common mistake in Intune device lifecycle management is performing the actions in the wrong order. Deleting a device record before Retire or Wipe has completed can leave a managed device containing corporate data without any practical way to remove it remotely. Another common issue is assuming that Retire or Wipe happens immediately. If the device is offline, the action remains queued until the next check-in, making verification an essential part of the Intune offboarding process.

The takeaway is simple: match the action to the device and follow the correct sequence. Use Retire for personal devices, Wipe for corporate-owned or compromised devices, and Delete only after the removal process has been completed. By incorporating these steps into your device lifecycle management and endpoint management procedures, organizations can securely remove corporate data, respect employee privacy, and maintain a clean Microsoft Intune environment every time.

← All articles

Case studies

Microsoft Consulting in practice

Client names are withheld. We are happy to share details on a call.

All case studies
  • Delivered

    600k files, < 3 days

    Document management

    Microsoft

    600,000 documents moved from ImageRight to SharePoint in under three days

    A one-file-at-a-time script would have needed about 22 days of continuous running. We rebuilt the migration around a SQL work queue with parallel uploads, automatic retries and crash recovery, and it finished unattended in under three days.

    • 1,125 → 8,314 files per hour
    • Under 3 days instead of about 22
  • Product

    Every prompt screened

    Any industry on Microsoft 365

    Microsoft

    AI activity and data posture for Microsoft 365

    Sentinel watches Copilot and Copilot Studio agents in a Microsoft 365 tenant. It logs prompts and tool calls, scores each agent's risk, flags oversharing and stale access, and screens prompts for injection attempts with a classifier that runs locally at no per-call cost.

    • Every agent prompt screened
    • Runs inside the customer's own Azure tenant
  • In production

    Hours → minutes

    Food manufacturing

    AI Consulting

    Document intake agent for a national food cooperative

    A Copilot Studio agent reads certificates of analysis as they arrive in the quality team's inbox, extracts 14 fields with AI Builder, checks them, files the PDF in SharePoint and posts a summary in Teams. Fields it is unsure about go to a person instead of being guessed.

    • Hours of daily filing down to minutes
    • 14 fields per document, validated

Keep reading

All Microsoft 365 & Azure articles

Planning something on Microsoft 365 or Azure?

Talk to the engineers who write these articles. We will look at your tenant and tell you what to do first.