on installing the latest windows 10 preview on our Microsoft surface pro 3, we ignored the option in the setup wizard to use our AAD tenant. Rather, we made a local account and then, as shown below, promoted it to a Microsoft account.
Now we wish to augment all this with the firstname.lastname@example.org AAD-based account – which happens to be 2-factor enabled.
On the settings tab we see
we learn quickly to ignore the connect option in favor of the join AAD:
we could not use our federated account (email@example.com), so we used an account built into the the AAD tenant.
second time around