Windows 10: Why can I not use my MS 365 credentials to be added to a computer log in?

I cannot add a user to a computer. When I attempt to add another account, it says "That Microsoft account doesn't exist. Enter a different account or get a new one." I am trying to use my MS265 credentials, but it says I have no account.

:)

 

Logging into Windows 10 Pro using Office 365 credentials


If we are talking about O365 Business or Enterprise accounts, you cannot use these email addresses when creating new users to your computer if the computer has not been joined to Azure AD. If an O365 Business / Enterprise user so wishes, he/she can create a new MS account using the O365 email address as a third party email, but in that case using that account to create a user it would be just a normal MS account.

A new user must be either a local account or a Microsoft account, O365 Business / Enterprise accounts will not be recognized.

You don't even have to create user accounts for your coworkers. Here's the correct way to this:

Sign in to your own admin account. Open Settings > Accounts, select Work access, select Join or leave Azure AD:




Click Join Azure AD:




Enter your own O365 / Azure AD account credentials, click Sign in:





Confirm by clicking Join:




Your PC has now joined Azure AD:




Sign out. Sign in with your own O365 credentials by selecting Other user and entering your O365 / Azure AD credentials and let Windows go through the account initializing process:




Sign out. As this PC now belongs to an Azure AD domain, your coworkers can sign in without a need to first create user accounts to them. First time they use their O365 credentials, Windows creates the accounts:

 

Logging into Windows 10 Pro using Office 365 credentials

I would do it like this:

• Create a local administrator account, let's say you name it Admin. Be sure it's an administrator account! Give this account a strong password
• Sign in to that account once to let Windows to initialize the user profile
• Sign out
• Use your existing MS account to sign in to Windows 10, join Azure AD
• Sign out from the MS account
• Sign in once using your personal O365 / Azure AD credentials, let Windows to initialize the user profile
• Sign out
• Sign in to your new local admin account Admin, remove your original MS account
• Now the machine has for you the local admin account plus your O365 account
• Let your coworkers sign in with their O365 credentials. Accounts will be created when they sign in first time
• Anyone wth your organization's O365 credentials can sign in to that PC; when a new user signs in first time the account will be created
• Notice that these new organisational user accounts are not shown in Welcome screen. A user from your organization wanting to sign in must always first select Other user and then enter full credentials

No. If the Office suite is installed from your available 5 seats, whoever uses it has full access to your data.

 

Scheduled tasks run with elevated privileges can't access stored Windows credentials

It seems that after Creators update scheduled tasks run with elevated privileges ('run with highest privileges' option) can't access stored Windows credentials. Is that a bug or an intentional change and is there a recommended workaround?

Here's one way to reproduce the behaviour:

• Start Credential Manger and add some Windows share credentials.
• In a console window type 'cmdkey /list', which should list the added credentials
• Create a task in a task manager:
  • Trigger: on user logon
  • Action: run cmd.exe
  • Tick the 'run with highest privileges' option
• Reboot the machine and log in
• In the console window (let's call it 'console 1') opened from the scheduled task type 'cmdkey /list'. This most likely won't display the credentials added in step 1 and properly listed in step 2. ->
  This looks like a bug
• Now, without closing 'console 1' open another console window as an administrator (let's call it 'console 2') and type 'cmdkey /list'. This will properly list credentials added in step 1.
• Switch to 'console 1' and type 'cmdkey /list' again. This time the credentials are listed properly, unlike in step 5. It looks like an access to Windows credentials was somehow 'unlocked' by step 6.