Article ID: 128225, created on Feb 3, 2016, last review on Feb 3, 2016

  • Applies to:
  • Operations Automation 6.0

Symptoms

"Unable to authenticate your credentials" error when you try to connect to Azure Active Directory. Attempt to execute Connect-MsolService cmdlet with correct credentials fails with:

PS C:\> $cred=get-Credential
PS C:\> Connect-MsolService -Credential $cred
Connect-MsolService : Unable to authenticate your credentials. Make sure that your user name is in the format: <username>@<domain>. If this issue persists, contact Support.
At line:1 char:1
+ Connect-MsolService -Credential $cred
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [Connect-MsolService], Mic
   rosoftOnlineException
    + FullyQualifiedErrorId : 0x80048862,Microsoft.Online.Administration.Autom
   ation.ConnectMsolService

Cause

Besides conditions described in Microsoft KB article an error may also occur when Microsoft Online Services Sign-In Assistant on the machine where the cmdlet is being executed cannot establish secure communication channel with Microsoft Cloud.

To make sure that affected machine can communicate with Microsoft cloud you can open https://login.microsoftonline.com/ in any browser installed on the machine and verify that there are no security warnings related to untrusted SSL certificates. One of the possible reasons of security warning is absence of one of the CA certificates which is used by Microsoft cloud in Trusted Root Certification Authorities container on the affected machine.

Resolution

Make sure that all CA certificates which are used by Microsoft cloud are installed on the machine.

See also: https://support.microsoft.com/en-us/kb/2929554

Search Words

Unable to authenticate your credentials. Make sure that your user name is in the format: <username>@<domain>

Unable to authenticate your credentials

<username>@<domain>

Connect-MsolService

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF