How do you connect a Windows 10 profile to an Office 365 account?

[Dos_Box]

As above, how do you do this with an existing profile or do you have to add a new profile and set the login details with that (tried that but didn't work)? Edited October 3, 2014 by Dos_Box

[FN-GM]

Are you talking about the login account for the computer? If so you can't these are Microsoft accounts not Office 365 accounts. They are 2 separate set of credentials.

[Dos_Box]

That's what I'm asking. I'm sure that it was mentioned that you would have the ability to connect a 365 account to a profile (only tried the other method to see if it worked ). Edited October 3, 2014 by Dos_Box

[FN-GM]

Last I heard it wasn't possible. Although it would make sense to do that.

[JRowley]

Still isn't possible to my knowledge, which is a shame as it was basically the one thing I was expecting.

[gshaw]

Looks like we'll have to wait until the next release of the preview for it, was rather disappointed when the Windows 8.x first run wizard appeared with only a Microsoft Account option

[Dos_Box]

Still isn't possible to my knowledge, which is a shame as it was basically the one thing I was expecting.

 

Thats what it looks like. There was so much chat about it going to have this feature I expected it to already be in there.

[Arthur]

Here's a better link, MS blog post that confirms it is coming...

It's already possible to login to a Windows 10 PC joined to Azure AD (as of build 9926).

 

https://cloudpuzzles.net/2015/02/joining-windows-10-device-azure-active-directory

 

http://a.pomf.se/cenccu.png

[SLS_]

So, after eventually getting my test laptop upgraded to 9926, I found that I could indeed sign in with an Office365 address!

Buut, I had to use the whole email address to do it, which isn't great, but my tester is on a Workgroup atm, so may be able to get around that by joining it to a domain with the UPN Suffix the same as our email domain?

 

Unfortunately once in, I found again dependency on Microsoft Accounts! I'm hoping this is because MS are going for the same Outlook Express vs Outlook kind of model with Mail and Office2013, i.e. Mail & builtin Onedrive are meant for home users and Office2013 Mail & Onedrive will work with Office365, or, maybe they've just not got that far with the AzureAD compatibility?

 

I'll kick off a copy of Office2013 on this tester when I get a mo and see if I get any joy.

[Jesper]

Hi all. I'm Jesper who wrote the blog referenced here. I just wanted to clarify some things about the cloud domain join feature.

 

So, after eventually getting my test laptop upgraded to 9926, I found that I could indeed sign in with an Office365 address!

Buut, I had to use the whole email address to do it, which isn't great, but my tester is on a Workgroup atm, so may be able to get around that by joining it to a domain with the UPN Suffix the same as our email domain?

Azure AD logins - the UPN - is required to have a public domain to determine where the authentication is happening. By default when you create an Azure AD (AAD) the UPN will be *.onmicrosoft.com where the wildcard is the name of your AAD. If you want to use a custom domain, cloudpuzzles.net as in the screenshot above, you have to add that domain to AAD and verify it. That way AAD can forward login requests for *@cloudpuzzles.net to AAD, and if I want to, I can also have it forward these requests to my ADFS server. If you're syncing users from your own AD you should add the UPN.

Also, a computer cannot be both cloud domain joined and joined to a normal AD, so yes, a workgroup for the computer.

 

And yes, there is no doubt still a lot of work going on behind the scenes.

[gshaw]

The newer build of Windows 10 seems to have this built into the first run screen

 

 

Might need to spool up another O365 trial to play around with it

Edited April 4, 2015 by gshaw