One of the most overlooked—but critical—steps in the IT asset disposition (ITAD) process is ensuring that devices are fully and properly decommissioned. While data security, asset tracking, and inventory audits may seem straightforward, modern device management platforms introduce new complexities that can expose your organization to unexpected risks.

Why Are Devices Still Connecting After Disposition?

You followed all the right steps:

• Assets tracked and inventoried
• Drives wiped or destroyed
• Licenses reviewed with your software asset manager
• Devices marked as processed

So why are disposed devices still reconnecting to your network or management tools?

The answer lies in features like Hardware ID Enrollment, Persistent Enrollment, and Automatic Re-Enrollment. These capabilities, built into modern MDM solutions such as Microsoft Intune, Azure AD, Jamf, VMware Workspace ONE, and IBM MaaS360, bind devices to your environment even after a wipe or hardware audit.

With Windows 11, this issue has become even more apparent. After reinstalling the OS—even on wiped or refurbished devices—some units reconnect to the corporate domain, display your organization’s name, and enforce lockout credentials. This not only renders the device unusable for resale or donation, but also poses significant risks:

• Brand exposure: Your company name and security policies appear on public-facing hardware.
• Compliance violations: You may still be paying for licenses or remain linked to assets no longer in your control.
• Security concerns: Residual management profiles create backdoor access and potential breach vectors.

Why Most ITAD Vendors Miss This

Few ITAD vendors reinstall the OS as part of their quality control process. Without this check, devices may pass all audit criteria—yet still be enrolled in your environment. These assets are then resold globally, inadvertently broadcasting your organization’s identity and creating future legal or financial risk.

What You Need to Do Now

To ensure true disposition and mitigate exposure, review and strengthen your decommissioning protocols:

• Remove Microsoft Account ties
• Unlink or disassociate devices from Intune, Azure AD, or any MDM tool
• Wipe or destroy drives using NIST-compliant methods
• Reset and clear BIOS/UEFI settings
• Reinstall OS for final validation if needed

The Bottom Line

With today’s evolving device management technologies, it’s not enough to wipe a drive and mark an asset as complete. You must actively decouple the device from your organization’s digital identity. Take the time to audit, update, and automate your decommissioning process—ensuring security, compliance, and sustainability while maximizing ROI on every asset lifecycle.