Does running an OEM Recovery Tool automatically transfer a claimed bundled Office license to a new Microsoft Account?

Question

Hi Microsoft Engineering team and experts,

I am an IT technician at a very large, well-established, and highly reputable computer and hardware retail chain with numerous stores all across Vietnam. My job gives me the opportunity to attend various training sessions from brands like HP, Dell, Asus, Microsoft, Lenovo, etc.

Recently, during an offline training session hosted by HP, I was completely surprised and confused when the HP trainer told us the following:

"When Customer A buys an HP laptop bundled with an Office License Key and claims it using their Microsoft Account (MSA A). If, for some reason, Customer A returns the laptop, our store takes it back and uses the 'HP Cloud Recovery Tool' app from the Microsoft Store to restore the machine to its factory state. When the laptop is then sold to Customer B, and Customer B logs in with their new Microsoft Account (MSA B), the Office License Key will automatically detach from Customer A's account and transfer to Customer B's account. This means no matter how many customers the laptop goes through, simply running the Recovery tool will retrieve the Office License Key for that machine."

My Real-World Test: I decided to test this myself with a real case. A customer bought an HP OmniBook 15. A few days after the customer claimed the bundled Office 2024 license into their Microsoft Account (MSA), the laptop had a touchscreen defect, so we replaced the machine for them.

After sending that returned HP OmniBook 15 to the HP service center for a screen replacement and getting it back to our store, I recovered the machine using the "HP Cloud Recovery Tool" app. I then logged in with my second Microsoft Account (which doesn't have any Office licenses attached to it). As a result, my account did not receive any Office license, and the Office license was simply no longer available on the machine.

My Question: Based on your knowledge of Microsoft's licensing architecture, is the claim made by the HP trainer correct? Can a local OEM recovery tool actually detach a digital license from a cloud MSA?

Thank you!

PS: I would highly appreciate it if a Microsoft Licensing Engineer or a Microsoft MVP could weigh in on this architectural design and help clarify the facts for our technical team.

Answer 1

The claim from the HP trainer is not correct based on how Microsoft Office/Microsoft 365 licensing works in the provided material.

Key points from the licensing architecture:

1. Consumer Office licenses are bound to a Microsoft account, not to the device image
   • For one-time-purchase products (Office Home & Student, Home & Business, Professional, etc.), the license is associated with the Microsoft account used to redeem/activate it. Reinstallation is done by signing in to that same account at the Services & Subscriptions page and installing from there, not by reading a key from the device.
   • Guidance for reinstalling or moving these products consistently directs users to sign in to the account that already owns the license and install from there, confirming that the entitlement is stored in the cloud against the account, not “inside” the PC image.
2. Microsoft 365 Apps subscriptions are user-based or device-based, but still controlled by cloud licensing services
   • User-based Microsoft 365 Apps licenses allow a user to install on multiple devices and are activated and kept activated automatically by the Office Licensing Service. The entitlement is managed in the Microsoft 365 tenant and tied to the user’s account, not to an OEM recovery image.
   • Device-based licensing for Microsoft 365 Apps for enterprise is controlled via Microsoft Entra ID and license assignment to device groups. Activation requires the device to contact the Office Licensing Service and is validated against cloud license assignments. Resetting or reimaging the device does not “move” a license between Microsoft accounts; it only affects the local activation state.
3. Local reset/recovery affects only the local installation and activation state
   • Articles on device-based licensing explicitly state that to transition licensing modes, the activation state on the device must be reset. This is a local operation; the actual license assignment remains in the cloud (tenant/device group or user account).
   • Recovery or reimaging (whether via OEM tools or other means) can remove or reset the locally installed Office and its activation tokens, but it does not reach into Microsoft’s cloud licensing system to detach a license from one Microsoft account and attach it to another.
4. License checks and renewals are cloud-based and tied to existing assignments
   • Microsoft 365 Apps regularly contact the Office Licensing Service and Activation & Validation Service to confirm subscription status and activation. These services use identifiers such as tenant ID and machine key to validate an existing entitlement; they do not automatically reassign ownership of a license to a different Microsoft account simply because a different user signs in after a recovery.
5. Real-world behavior in the test aligns with the architecture
   • In the described test, after OEM recovery and signing in with a different Microsoft account, no Office license appeared for the new account and Office was not licensed. This matches the documented model: the original customer’s account still owns the license in the cloud, and a recovery image cannot transfer that ownership.

Conclusion:

An OEM recovery tool (such as HP Cloud Recovery Tool) can:

• Restore the factory OS and preinstalled Office image.
• Reset or remove the local activation state.

It cannot:

• Detach a claimed Office license from the original customer’s Microsoft account in Microsoft’s licensing service.
• Automatically transfer that license to a new Microsoft account just because a different user signs in after recovery.

Any transfer of entitlement for one-time-purchase Office products or reassignment of Microsoft 365 licenses must follow the documented account/tenant-based processes, not OEM recovery.

---

References:

• Overview of licensing and activation in Microsoft 365 Apps
• Troubleshooting device-based licensing for Microsoft 365 Apps
• Licensing and activation data sent to Office 365 by Microsoft 365 Apps
• Understand subscriptions and licenses in Microsoft 365 for business
• Why do I need an account to sign in to Microsoft 365 or Office?
• How to reinstall Office & Student 2019 - Microsoft Q&A
• Move my Home and Student 2016 to a new computer - Microsoft Q&A
• Transfer your Office license to another device or another person