Why this matters for revenue teams
Before reissuing a rep device, check passcode erasure, recovery attempts, FileVault access, daily wipe caps, bulk eligibility, and shared wipe counts. A wipe limit decides whether a wipe does what you expect, and when.
When a sales rep leaves, the laptop and phone they carried usually go back into a pool. IT wipes them, someone labels them, and they go to the next person. That routine works until someone asks what the old device held. The answer is often more than anyone expected: customer lists in a notes app, saved proposals, a chat thread with a pricing contact, a forecast spreadsheet, or a session still signed in to a shared account.
Revenue leaders care for two reasons. The first is exposure. A device that leaves with customer data on it is a risk even if nobody meant harm. The second is continuity. The deals, contact history, and forecast notes that lived on the device need to land somewhere the team can still reach before the next rep opens it. A reissue that loses either one has failed, even if the wipe itself ran without errors.
This post covers six wipe limits to check before you reissue a rep device. Some come from the device itself, such as how many passcode attempts a phone allows. Others come from the management tool your company uses to wipe devices remotely. Each one can stop a wipe from doing what you expected, or make it finish in a way nobody planned for. The numbers below come from vendor documentation at the time of writing. Those pages change, so check them before you build a process around any figure.
Deleting is not the same as wiping
Start with the point every offboarding checklist should open with. The UK National Cyber Security Centre's guidance on erasing devices says that, because of the way data storage works, simply deleting files is often not enough to prevent that data from being recovered (NCSC, Erasing devices). The same guidance adds that these methods do not guarantee complete removal, and that a determined expert using specialist techniques may be able to recover some of it in some circumstances.
For a sales team, the practical reading is plain. "I cleared the customer folder" is not the same as "the device no longer holds customer data." If a rep kept sensitive files on a laptop, the reissue should rely on a proper wipe run by IT, not a manual clean-up by the rep on the way out. The sections below cover the limits on that wipe, because a wipe that hits one of them can leave you unsure what happened to the device.
Ownership matters too. When several people touch a departing device, each can assume someone else checked it. Name one owner for the wipe, one for the record, and one for exceptions, and write those names into the offboarding process.
Limit 1: Erase Data after ten wrong passcodes
Apple's platform security guide describes an Erase Data option. If it is turned on for an iPad or iPhone, then after 10 consecutive incorrect attempts to enter the passcode, all content and settings are removed from storage (Apple, Passcodes and passwords).
This cuts two ways. With Erase Data turned on, ten consecutive wrong guesses on a lost phone remove its content and settings. It also works against you during a reissue. If a departing rep's phone is locked and the passcode is unknown, repeated guesses can trigger erasure when Erase Data is on, and the customer data you hoped to recover goes with it.
Before a phone leaves the rep, check whether Erase Data is on, and do not assume the answer. Get the business data off the phone first, through a sanctioned route such as a managed account or a synced app, while the rep can still unlock it. Do not count on recovering anything from a phone that is already locked. If the device has no known passcode, treat it as a device that needs a deliberate, supervised recovery plan, not a guessing game.
Limit 2: Ten more attempts after a restart into recoveryOS
The same page also describes a recovery sequence. If its initial 10 attempts are exhausted, 10 more attempts are available after restarting into recoveryOS. This is a recovery-attempt allowance, not a promise that data survives passcode erasure. It still matters for a reissue, because someone usually tries to recover a locked device before anyone wipes it.
Do not treat the recovery sequence as extra guesses for an iPhone or iPad with Erase Data enabled. Someone following the recovery sequence has a second set of attempts, but that does not undo the erasure described above. For a reissue, identify which device and recovery path you are dealing with. Settle the recovery path before the device is handed over: who on the IT side may attempt recovery, and what they do if the attempts run out.
Limit 3: FileVault recovery adds 10 attempts within the 30-attempt maximum
The sequence carries on. If those attempts are also used up, then 10 additional attempts are available for the configured FileVault recovery mechanism, which can be iCloud recovery, a FileVault recovery key, or an institutional key. The guide states a maximum of 30 additional attempts across the recovery sequence.
For a Mac, the recovery mechanism your IT team set up decides who can still get in. A laptop whose FileVault recovery depends on a key nobody holds is a laptop that may never be reissued cleanly. Before a Mac goes back into the pool, confirm which recovery mechanism is configured, and make sure the person or system that holds it is still on the team.
Read the page itself for how the counts add up. A summary such as this one can get the arithmetic wrong, and in a real recovery the exact numbers matter. Treat the guide as the reference, and this post as a checklist to start from.
Limit 4: 500 wipe actions per day for the whole tenant
Microsoft's documentation for wiping devices with Intune says a tenant can submit up to 500 Wipe actions per day (Microsoft Learn, Wipe devices with Microsoft Intune). A tenant is your organization's Intune environment, so the cap belongs to the company, not to any one admin.
For one rep, this cap will almost never bite. It matters when a reorg, a layoff, or a seasonal cleanup puts a large batch of devices into the queue at once. Spread a large batch across days rather than leaving it to the last afternoon of a busy quarter. Check the day's count before you queue more, and remember that the same count covers every wipe path, as the last limit below explains.
Limit 5: 100 devices in a bulk wipe
The same documentation says to use a bulk device action to wipe up to 100 corporate-owned fully managed (COBO), corporate-owned dedicated (COSU), or corporate-owned work profile (COPE) devices. For Android Enterprise devices, it adds that you can select up to 100 supported corporate-owned devices on the Devices page.
A batch of eligible departing reps' devices therefore has to be split into groups of no more than 100. Run two checks first. Confirm that each device falls in one of the corporate-owned categories the bulk action covers, because a device outside those categories needs a different plan. Then confirm that each Android device is a supported Android Enterprise type if you select it from the Devices page. A group that looks like one batch on a spreadsheet may need two or more actions in the console.
Limit 6: One shared count across every wipe path
The documentation adds the detail that matters most for busy teams. The tenant-wide limit on wipe actions is cumulative across individual device actions, bulk device actions, and Microsoft Graph API requests.
In practice, a wipe from the admin console, a bulk action, and a script that calls the Graph API all draw from the same count. If an automation runs offboarding wipes overnight, it also uses up the room your admin needs for a manual wipe the next morning. Ask who runs scripts against the tenant, and agree how wipes are scheduled. Keep a simple log of the wipes you submit each day, with the device, the reason, and the time, so you can see the count before you queue more.
Walking through one reissue
Consider an illustrative case built from the limits above. A regional account executive leaves on a Friday.
On Monday, the revenue operations lead asks IT to reissue both devices. Before anything is wiped, the team writes down what each device held. The spreadsheet has already been copied to a shared drive, so the laptop is ready for a wipe. The phone is different. It holds a handful of customer contacts that were never saved to the CRM, so they need to be transferred first. That is a transfer step, not a clean-up step.
IT then checks the phone's settings. Erase Data is on. The account executive never shared the passcode, so the phone is locked and nobody on the team knows the code. This is the case the first limit warns about. The team stops guessing, marks the phone as a locked exception, and hands it to a named person who will run a supervised recovery plan. It does not go into the batch.
The laptop goes into a bulk action with the other devices from the same reorganization. The team then checks the day's wipe count, because a nightly script calls the Graph API and draws from the same tenant-wide count. They schedule the batch so the script does not use up the room they need.
At the end, the team records which device went to which new owner and what the wipe result was. The sales lead receives a transfer record that lists the contacts moved to the CRM and the status of each device. The lead does not receive a blanket statement that the devices are clean.
When a limit stops a wipe
A limit can stop a wipe in the middle of a batch, or leave a device in a state nobody expected. A few habits make these moments easier to handle.
Read the message before you retry. A wipe that failed because of a count limit is not the same as one that failed because the device was offline, and the fix is different. Retrying blindly wastes time and makes the count harder to track.
Check the count before any retry. Look at the day's wipe actions across all paths, including scripts, and note the time of each attempt. That record tells you whether a retry fits inside the limit or needs to wait for the next day.
Keep exceptions on their own list. A device that cannot be wiped in the normal path should have an owner, a reason, and a next step. Exceptions that sit in a general backlog are easy to forget, and a forgotten locked phone is a risk in its own right.
Be plain with the business about what is still open. If a device is locked, say so and name the person handling it. Do not report it as finished until the wipe result is confirmed.
Build the limits into your reissue checklist
The limits only help if they change the process. Here is a checklist a revenue operations lead can hand to IT.
- Record what the device held. List the apps with customer data, the accounts signed in, and any synced folders. Ask the rep's manager to confirm the list. The list tells you what needs to move. It does not replace the wipe.
- Move business records off the device first. Deal notes, contacts, proposals, and forecast inputs should live in systems the team can reach without the laptop or phone. If a record exists only on the device, move it before the device goes back into the pool.
- Confirm the device category. Corporate-owned devices can use the bulk path if the category and the daily count allow it. Personal devices used for work need their own process, and the bulk limits above do not describe them.
- Check the passcode and recovery state. For iPhones and iPads, know whether Erase Data is on. For Macs, know which FileVault recovery mechanism is set and who holds it.
- Queue wipes against the caps. Count the day's wipe actions across all paths, split eligible batches into groups of 100 or fewer, and spread large batches across days.
- Confirm the outcome. A wipe that was queued is not the same as a wipe that finished. Check the device record for each one, and note in your log which device went to which new owner.
- Escalate the exceptions. A device that is lost, locked, or unresponsive goes to a named person rather than into the batch. Do not promise the business that its data can be recovered from a locked device.
- Keep one record. Store the transfer list, the wipe results, and the exception list in the same place, so the next audit does not start from memory.
What to tell the rest of the team
After a reissue, sales leaders tend to get two questions: did we lose anything, and is the old data still on the device? Answer the first with the transfer record. Answer the second with the wipe record, and be honest about its limits. Say what was done, with which tool, and what the result was. That is more useful than a blanket reassurance.
Over time, the simplest protection is to keep less on devices in the first place. When deal history, contacts, and forecast inputs live in shared systems, a reissue carries less risk and less lost context. That is a process decision as much as a technical one, so raise it with your sales operations lead before the next departure rather than after it.
The six limits at a glance
Here are the six limits in one table, so you can check each before a reissue.
| Limit | Figure or rule | What to check before a reissue |
|---|---|---|
| Erase Data on iPhone or iPad | 10 consecutive incorrect attempts to enter the passcode | Whether Erase Data is on, and whether business data is already off the phone |
| Attempts after recoveryOS | 10 more attempts are available after restarting into recoveryOS | Which recovery sequence applies, who may attempt recovery, and what happens when attempts run out |
| FileVault recovery | 10 additional attempts; maximum of 30 additional attempts | Which recovery mechanism is configured, and who holds it |
| Tenant wipe actions | up to 500 Wipe actions per day | The day's count across the whole tenant before queuing more |
| Bulk wipe | up to 100 corporate-owned fully managed (COBO), corporate-owned dedicated (COSU), or corporate-owned work profile (COPE) devices; up to 100 supported corporate-owned Android Enterprise devices | Device category, Android Enterprise type, and batch size |
| Shared wipe count | cumulative across individual device actions, bulk device actions, and Microsoft Graph API requests | Which scripts and admins draw from the same count |
Final check before you reissue
A reissue is the point where a departing rep's device changes hands. The six limits above can change how you plan the wipe, and they are easy to miss when the process runs on habit. Put them on the checklist, confirm the current vendor pages before you finalize it, and keep a record of what happened to each device.