The security token we received didn't contain the expected claim: '{0}'. This isn't something you can fix yourself. Contact your administrator for help; Here's some information about UPN issues that may help your admin to solve this problem: {1}.
The secure URL and storage account key are used in the tools for importing files either by shipping them or by uploading ...
The security settings required by your email account are stricter than the Microsoft account security settings of at least ...
The security settings required by your email account are stricter than the settings for your Microsoft account. This device ...
The security token we received didn't contain the expected claim: '{0}'. It appears that your Active Directory federation ...
The security token we received didn't contain the expected claim: '{0}'. This isn't something you can fix yourself. Contact ...
The security token we received didn't contain the expected URN '{0}' at '{1}'. It appears that your Active Directory federation ...
The security token we received from your identity provider did not contain a NameID value in the Subject element. This may ...
The security token we received from your identity provider doesn't specify a signature method. This is a potential security ...
The security token we received from your identity provider is not signed with the SHA-1 or SHA-256 algorithm. This is a potential ...