From: V@nguard.LH
Paul wrote:
> As I don't dabble in doing things like this, and the Google gets
> quite carried away with irrelevant answers, let's try this instead.
>
> CoPilot question
>
> I have a Windows 11 installation with a local account.
> What interface do I use to add a Microsoft Account MSA ?
> The purpose of the MSA is to add to the setup capability
> rather than create an additional user as such.
>
> *************** Begin CoPilot answer **************
>
> Windows 11 actually supports two different ways of “adding” a Microsoft
Account,
> and only one of them creates a new user profile. The other simply **attaches
an MSA
> to your existing local account** to unlock sync, Store access, device
registration,
> and other cloud‑backed features.
>
> Here’s the clean, correct interface for what you want.
>
> # Add an MSA *to your existing local account* (without creating a new user)
>
> ### Use **Settings -> Accounts -> Your info**
>
> This is the only interface that *links* an MSA to the currently signed‑in
local account.
>
> **Path:**
> **Settings -> Accounts -> Your info -> "Sign in with a Microsoft account
instead"**
>
> This does **not** create a new user.
> It converts your local account into a connected account (or partially
connects it, depending on your choices).
>
> ### What this interface does:
> - Links your local profile SID to an MSA
> - Enables Store, OneDrive, sync, device backup, BitLocker recovery key
upload, etc.
> - Keeps all your files, registry hive, and profile folder intact
> - Does *not* create a second user account
> - Does *not* require switching to a PIN unless you choose to enable Windows
Hello
>
> ---
>
> # What **not** to use
>
> ### Settings -> Accounts -> Family & other users -> Add account
> This creates a **new user profile**, which is *not* what you want.
>
> ### netplwiz
> This only manages local users and cannot attach an MSA.
>
> ### Control Panel -> User Accounts
> Legacy interface; cannot attach an MSA to a local account.
>
> ---
>
> # Optional: Add an MSA *for apps only* (without converting the account)
>
> If you want to keep your Windows sign‑in local but still use an MSA for
Store, Mail, etc.:
>
> **Settings -> Accounts -> Email & accounts -> Add a Microsoft account**
>
> This:
> - Adds the MSA to the “Accounts used by other apps” list
> - Does *not* convert your local account
> - Does *not* affect login
> - Still enables Store, Mail, Calendar, etc.
>
> This is often used on corporate or lab machines where the sign‑in must
remain local.
>
> ---
>
> # Summary
>
>| Goal | Correct Interfac
| Creates New User? |
>|--------------------------------------|-----------------------
----------------------|-------------------|
>| Attach MSA to existing local account | **Settings -> Accounts -> Your
info** | No |
>| Use MSA only for apps (Store, Mail) | **Settings -> Accounts -> Email &
accounts** | No |
>| Create a new MSA-based user | Settings -> Accounts -> Family &
other users | Yes |
>
> ---
>
> If you want, I can walk you through the exact screens or help you decide
whether to fully connect the account or use the “apps only” method.
>
> *************** End CoPilot answer **************
Thanks for the as-always detailed response. Looks like signing into an
MSA from an existing and logged in local Windows account keeps that
local account, and just links the MSA account to it. That's what I
want.
Perhaps missed is that I'm testing Win11 inside a Virtualbox virtual
machine. So, I can save a Vbox snapshot, have my local Windows account
sign into my MSA account, see what happens, and if I find a new Windows
account and its profile folder got created then I could restore to the
snapshot saved before the change. I could similar on my real hardware
(not inside a VM) by saving an image restore before testing what
happens, and restore if I didn't like the change.
The only residual effect from the testing is my MSA account would get a
record of and track my Win11 license.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
