You can link a Microsoft account to a Windows digital license in about two minutes—sign in with that account and the license attaches automatically. The catch matters more than the method: only retail and some promotional licenses can move to new hardware this way. OEM licenses that ship with a PC stay locked to that motherboard no matter which account you sign in with.
The linking step itself is the easy part. Most people searching this phrase want to know whether the license follows them to a new build, a repaired machine, or a second PC. That question has a different answer depending on which license type sits in your firmware or on your receipt, so the account link is really a label on a package you already own. Attach the label correctly and the package becomes portable; attach it to an OEM license and you've labeled something that can't travel.
Microsoft's activation servers read two things when you sign in: the license type recorded against your hardware hash and the account now claiming it. Get the hardware side wrong—swapping a motherboard before signing in, for instance—and the link has nothing valid to attach to. Do it in the right order and the same account can reactivate a fresh build through the Activation troubleshooter in under five minutes.
Why Linking an Account Is Not the Same as Buying a Portable License
A digital license is a record held on Microsoft's activation servers, keyed to a 50-character hardware hash that Windows generates from your motherboard, CPU, and other fixed components. Signing in with a Microsoft account adds a second key to that record: your identity. The account doesn't create portability. It only tells Microsoft whom to offer reactivation to when the hardware hash no longer matches.
Retail licenses bought from the Microsoft Store, a boxed copy, or an authorized reseller carry transfer rights under Microsoft's Software License Terms. OEM licenses preinstalled on a Dell, HP, or Lenovo machine do not. Those are bound to the original hardware for the life of that machine, and Microsoft's documentation states plainly that OEM licenses can't be transferred to another device.
A third category confuses people: upgrade licenses from the free Windows 10 upgrade era, or promotional licenses from education programs. Some of these behave like retail, some like OEM, and Microsoft has handled them inconsistently over the years. If your license came from a $20 "key" on a marketplace site, treat it as suspect until the activation settings page shows the channel.
Here's the practical distinction. Linking is a convenience that unlocks the Activation troubleshooter. Owning a retail license is what makes that troubleshooter useful. If you have an OEM license on a laptop that you'll keep until it dies, linking costs nothing and harms nothing—it just doesn't buy you hardware freedom.
Checking Your Edition and Channel Before You Sign In
Before linking anything, confirm what you're working with. Open Settings > System > Activation. The page shows "Activation state: Active" and, below it, "Edition: Windows 11 Pro" (or Home). That's the half most people check and stop.
The half that matters is the channel. On Windows 11, scroll to the bottom of the Activation page and look for "Your Microsoft account" if you're already signed in, or click "Add an account" to link. If you're unsure whether the license is retail or OEM, open Command Prompt and run slmgr /dli. The dialog that pops up names the license "Product Key Channel"—you'll see "Retail," "OEM:DM," "OEM:NONSLP," or "Volume:MAK." Retail and OEM:DM are the two you'll encounter on consumer machines.
Run the same command on a machine that has been through a motherboard replacement and you may see "Notification" mode instead of "Licensed," which means Windows 11 is running unactivated. Linking the account first, then running the troubleshooter, is the correct order. Reversing it—swapping hardware, then signing in—often leaves the troubleshooter unable to find a prior activation to transfer.
One edge case worth naming: Windows 10 machines upgraded to Windows 11 retain their original channel. A Windows 10 Home OEM license upgraded to Windows 11 Home still shows OEM:DM. The upgrade didn't convert it to retail. Plenty of guides imply otherwise.
Step-by-Step: Attaching the License to Your Microsoft Account
Do this before any hardware change, and do it once per device. The whole sequence takes under three minutes on a normal connection.
1: Sign in to Windows with an administrator account. Open Settings > Accounts > Your info and confirm you're signed in with the Microsoft account you want the license tied to. A local account won't work here. 2: Open Settings > System > Activation. If the license is active and you're signed in, you'll see "Windows is activated with a digital license linked to your Microsoft account." 3: If the screen shows only "Windows is activated with a digital license" without the account line, click Add an account under the "Your Microsoft account" section and sign in. 4: Open Settings > Accounts > Email & accounts and verify the same address appears under "Accounts used by other apps" as a Microsoft account—not a work or school account. Work accounts cause the troubleshooter to fail with error 0x803F7001. 5: Restart the PC and return to the Activation page. The linked-account line should now display your email address.
If step 3 shows no "Add an account" option, the device is likely on a local account or a domain-joined profile. Switch to a Microsoft account under Settings > Accounts > Your info first, then repeat.
If activation fails with error 0x800704CF after linking, the Microsoft account service isn't reachable—check that the PC isn't behind a corporate proxy that blocks login.live.com. Error 0xC004F034 on the troubleshooter means the account you signed in with has never held a license for that edition, usually because the license is OEM and you've already swapped the board.
Moving the License to New Hardware: The Activation Troubleshooter in Detail
Once the account is linked, hardware changes become recoverable—for retail licenses. The path runs through Settings > System > Activation > Troubleshooting. Sign in with the same Microsoft account, and the troubleshooter lists devices that hold a license for your edition. Pick the one you're building on, confirm "This is the device I'm using right now," and click Activate.
The troubleshooter only works when the PC is not already active. If your new build has a fresh Windows 11 install in the grace period, you're fine. If it's running unactivated, the option appears. If it's already active with a different license—say, a leftover OEM key in a donor motherboard—the troubleshooter refuses, and you must remove the existing key first with slmgr /upk before retrying.
Microsoft's support documentation states that the troubleshooter requires the linked account to own the license, and that it can be used only a limited number of times per year (Microsoft's published limit is five reactivations per year for retail licenses, per the Windows activation FAQ). Reaching that cap means calling Microsoft Support. There's no self-service override.
Time check: a clean motherboard swap plus activation typically runs 20–40 minutes, with the activation portion under five. If the troubleshooter fails twice, stop retrying. Repeated attempts with the same account can lock out further tries for 24 hours, and each failed attempt logs an error in Event Viewer under Applications and Services Logs > Microsoft > Windows > Security-SPP.
OEM vs. Retail vs. Volume: What Actually Transfers
| License type | Slmgr channel label | Transfers to new hardware? | Links to Microsoft account? | Typical source |
|---|---|---|---|---|
| Retail | Retail | Yes, under Software License Terms | Yes | Microsoft Store, boxed copy, authorized reseller |
| OEM (preinstalled) | OEM:DM | No | Login works, but reactivation fails on new board | Prebuilt PC (Dell, HP, Lenovo) |
| OEM (System Builder) | OEM:NONSLP | No, bound to first activation | Login works, reactivation fails | Hand-built PCs using OEM keys |
| Volume (business) | Volume:MAK or KMS | No, tied to organization | No, requires domain or M365 tenant | Corporate/enterprise deployments |
| Upgrade from Win 10 | Same as original channel | Inherits original rules | Yes (if retail-origin) | Free upgrade 2015–2016 era |
The verdict is split. Buyers on a prebuilt laptop should link the account anyway—it costs nothing and future Microsoft account features use it—but they should not expect it to move to a new motherboard. Buyers who built their own PC with a retail key and later upgrade the board will find the troubleshooter works cleanly, usually on the first try. People running a volume-licensed machine from work are in the wrong article; their license is managed by the organization and never travels.
One drawback worth naming for the recommended pick: retail licenses reactivate, but they reactivate as Windows 11 Home or Pro at the version currently installed, not at whatever version the original purchase shipped. If your retail key came from Windows 7, you'll get Windows 11—the version history doesn't carry over, only the entitlement.
Failure Cases That Trip Up the Troubleshooter
The Activation troubleshooter's error messages are terse and misleading. The most common one, 0xC004C008, means the key has been used on more than one device simultaneously, not that the key is invalid. This usually happens after a motherboard swap when the old board was reactivated in another build, or after a virtual machine used the same account. Signing out of the VM and waiting for the grace period to reseed fixes it.
Error 0xC004F034 means the license can't be found for the account's edition. Common cause: someone linked the account on a Windows 11 Pro machine but the account's record holds a Windows 11 Home license from an earlier laptop. The troubleshooter compares edition, not just key. You can't upgrade or downgrade through it.
Error 0x803F7001 frequently appears on machines with a work or school account also signed in. Windows chooses the last-used identity, and the work account has no license. Remove the work account under Settings > Accounts > Email & accounts, restart, and sign in with the personal account alone. The same error appears if the Microsoft account's region doesn't match the license's activation region—Microsoft's support notes region locking, though it's rarely enforced for retail.
A less obvious failure case involves virtual machines. A Windows 11 Pro retail license linked to an account can activate one VM as long as the VM uses a different virtual hardware hash. Clone that VM, and the second instance triggers 0xC004C008. Shut down the original, restart the clone, and the clone activates on the next check. Running both at once violates the one-device rule in the license terms.
When the Account Link Won't Appear, and How to Fix It
Sometimes the Activation page never shows the "Add an account" option, or shows it but the account fields are greyed out. Start by confirming you're on a Microsoft account, not a local one—Settings > Accounts > Your info displays "Local account" if not. Click "Sign in with a Microsoft account instead" and complete the switch.
If the option is present but disabled, the account may be a child account under Family Safety with restrictions, or a work account pushed by your organization. Adult personal accounts don't have this issue. Sign out of any school or work email in Settings > Accounts > Access work or school, restart, and check again.
Windows 11 24H2 introduced a wrinkle some users hit: after the 24H2 update, the Activation page moved the account link below a "Related support" section and it can be missed. Scroll the entire page. On Windows 10, the link remains under Settings > Update & Security > Activation, and the account section shows above "Go to Store."
If the account still won't show after all that, the pairing may be corrupted server-side. Sign in to account.microsoft.com on a browser and check Devices. If your PC appears there, the link exists; the settings page is just failing to display it. Sign out of Windows entirely (Settings > Accounts > Your info > Sign out), restart, and sign back in. That forces Windows to re-read the account-link state from Microsoft's servers.
Removing the Link Without Losing the License
Unlinking is not the same as deactivating. You can remove the Microsoft account from Windows and the digital license stays on the hardware—it just stops being portable until you re-link. To remove: Settings > Accounts > Your info > "Sign out" or "Stop signing in to all Microsoft apps automatically." Windows reverts to a local account, and the Activation page shows "Windows is activated with a digital license" without the account line.
The license stays activated because activation is keyed to the hardware hash, not to the account. This is worth knowing when selling a laptop—remove the account link, factory reset, and the buyer gets an activated OEM machine (if OEM) or an unactivated retail machine (if retail and you'll reuse the license elsewhere).
If you need to sever the account-to-license association at Microsoft's server level—say, an old account you're abandoning—visit account.microsoft.com > Devices, find the PC, and click "Remove device." Microsoft's support documentation confirms this detaches the license record from the account without deactivating the current installation. The link can be re-added later.
Timing matters when selling. If you remove the device while it's still signed in, the account-side record detaches immediately. If you remove it while the PC is offline, the local Windows install thinks it's still linked until the next sign-in, which can confuse a buyer seeing a stale account email on the Activation page.
Reading Activation Errors and When to Call Support
Microsoft's activation error pages list roughly 30 codes. Five cover 90% of what you'll see after linking. 0xC004F034 (license not found for account) and 0xC004F074 (KMS volume server unreachable) account for most non-activation reports on retail devices. 0x803F7001 (license not found at all) and 0x8007232B (DNS resolution failure during activation) both resolve with a network check. 0xC004C008 (key in use) is the mother-board-swap classic.
Most error pages advise running the troubleshooter, which is correct but incomplete. If the troubleshooter returns 0xC004F034 three times, no amount of retrying fixes it—the account genuinely doesn't hold a matching license. At that point, call Microsoft Support at the regional number listed on support.microsoft.com (Microsoft's consumer support line for activation issues is free even on non-Store purchases). The support agent can see server-side records that the client cannot, and can manually transfer the license once every 12 months if you're outside the five-per-year self-service cap.
For a volume-licensed machine, don't call Microsoft—call your IT department. They control the KMS server and can reactivate you in seconds. For a machine that shows "Notification" mode after swapping boards on an OEM license, you're on your own: Microsoft won't transfer OEM, and buying a new retail key is the only path. That's a fact I'd rather state bluntly than let you discover after two hours of retrying.
FAQ
Can I link a Windows 7 or Windows 8 upgrade license to a Microsoft account?
Yes, but it behaves inconsistently. If the upgrade ran on hardware that later upgraded to Windows 10 or 11 through the free upgrade path, the license usually inherits retail-style transfer rights. If the original Windows 7 license was OEM, the resulting Windows 11 license stays OEM. Microsoft's support docs don't explicitly categorize upgrade licenses, so verify the channel with slmgr /dli before relying on portability.
Does signing in with a Microsoft account move my license to that account forever?
No. The link is a record, not a migration. If you later remove the device from your Microsoft account or sign in with a different account, the original account loses its association but the license remains on the hardware. Re-linking to a second account is possible only after unlinking from the first and reactivating.
Will the troubleshooter work if I already replaced the motherboard?
Sometimes, and the order matters. Sign in with the linked account on the fresh Windows install before running the troubleshooter. If Windows is already activated with a leftover OEM key from the donor board, remove it with slmgr /upk and restart first. If the troubleshooter lists the machine as "currently in use" on another device, remove that entry at account.microsoft.com > Devices, then retry.
Can I link the same Microsoft account to more than one Windows PC?
Yes, and the account can hold multiple device licenses at once. That's how Microsoft's device list works at account.microsoft.com > Devices. But each device must hold its own license. The account doesn't act as a shared license pool—transferring a retail license from PC A to PC B deactivates PC A, unless you've exceeded the five-reactivation yearly limit, in which case Support must intervene.
Why does the Activation page say "Windows is activated with a digital license" but not show my account?
Two reasons are common. You may be signed in with a local account, which prevents the account line from appearing; switch to a Microsoft account first. Or the machine is running Windows 11 24H2 and the account section is below the fold—scroll the entire page. If neither applies, sign out and back in to force Windows to re-read the account record from the server.
Is linking my Microsoft account required to use Windows 11?
No. Windows 11 Home's out-of-box setup pushes Microsoft account sign-in hard in recent versions, but you can switch to a local account after setup under Settings > Accounts > Your info. Retail activation works without an account link. The link is only needed if you want the portability features through the Activation troubleshooter, or if you plan a hardware change on a retail license.
What happens if I try to activate a second PC with the same retail license?
Microsoft's activation servers flag it as 0xC004C008 on the second device, and the first device's activation remains intact until you remove it manually or Windows detects the conflict at the next validation. The license terms allow one device at a time. Reactivation on a new PC only works after the license has been released from the old one, which the troubleshooter does automatically when it transfers.