When you try to authenticate to a Microsoft a cloud service such as Office 365, Microsoft Azure, or Microsoft Intune by using a federated account, the authentication is unsuccessful, and one or more of the following issues occur:
If these issues only occur for some user accounts, this indicates that those user accounts are likely set up incorrectly in the on-premises Active Directory environment. In this scenario, one or more of the following items may be set up incorrectly:
- The wrong user principal name (UPN) and password are being used.
- The UPN isn't updated for user accounts.
In this case, the UPN suffix for each identity-federated account must be updated to reflect the federated domain name. To verify a user account UPN, follow these steps:
- On the local Active Directory domain controller, click Start, point to All Programs, click Administrative Tools, and then click Active Directory Users and Computers.
- Right-click the user account that you want to change, and then click Properties.
- On the Account tab, make sure that the UPN suffix of the federated namespace is listed in the list in the upper-left corner, and then click OK.
- Office 365 user account isn't licensed for the Office 365 resource
Access to Office 365 resources for which the user account doesn't have a license is restricted. To check the license status for a user account, follow these steps:
- Sign in to the Office 365 portal (https://portal.office.com
) by using an Office 365 admin user account. You can use a managed account if it's required.
- Click Admin, click Office 365, and then in the left navigation pane, click users and groups.
- In the list of users, locate the user accounts that you want to test, and then select Display Name. Check that each user account has the required licensing for the Office 365 resource.
- Select the Select all items check box.
If a user account that you want to test isn't listed, Active Directory synchronization may be syncing the account to Azure Active Directory (Azure AD).
Note If the user account has an on-premises mailbox, an Office 365 mailbox isn't created. This specific resource remains unavailable, even when the user account is licensed for Exchange Online.
- Subdomain doesn't inherit parent domain's federation settings
When a subdomain, such as subdomain.contoso.com, is added before its parent domain, for example contoso.com, the subdomain automatically inherits the parent domain’s federation status. To determine the inheritance status, follow these steps:
- Sign in to Office 365 (https://portal.office.com
) by using an Office 365 admin user account. You can use a managed account if this is required.
- Click Admin, and then in the left navigation pane, click Domains.
- In the list of domains, locate the federated subdomain name, and then determine whether the Domain type setting is set to Single Sign-On.
- Repeat step 1 to step 3 for the parent domain. If the Domain type setting differs from the subdomain setting, the subdomain has been orphaned from its parent.
- Directory synchronization issues are preventing proper user account configuration on-premises from syncing to Azure AD.
Single sign-on (SSO) relies on identical user accounts being represented in both the on-premises Active Directory and in Azure AD. Directory synchronization is responsible for making sure that the same Office 365 user account is created for each on-premises user account. Sign in may fail when directory synchronization doesn't sync correct account settings from the on-premises Active Directory to Azure AD.
To resolve this issue, use one or more of the following methods:
- Make sure that the correct UPN and password are used for sign in.
- The UPN isn't updated for federated accounts.
For more info about how to resolve this issue, see the following Microsoft Knowledge Base article:
Troubleshoot user name issues that occur for federated users when they sign in to Office 365, Azure, or Intune
- The Office 365 user account isn't licensed for Office 365 resources.
To resolve this issue, use the Office 365 portal to assign the appropriate licenses to the user accounts that require a license.
- Office 365 subdomain doesn't inherit parent domain's federation settings.
To resolve this issue, remove the subdomain from the Office 365 portal. For more info about how to remove a domain, go to the following Microsoft website: After the domain is removed, you have to re-create the domain. For more info, go to the following Microsoft website: When the domain is re-created, the subdomain inherits the parent domain’s Domain type setting.
Note Domain verification by using DNS TXT records or MX records isn't required for subdomain re-creation because the subdomain is recognized as part of the already-verified parent domain.
- Directory synchronization issues prevent the on-premises user account configuration from syncing properly to Windows Azure AD.
To determine whether an account mismatch has occurred, follow these steps:
- Make a minor (arbitrary) change to the on-premises Active Directory user account.
- Force directory synchronization. For more info about how to force synchronization, go to the following Microsoft website:For info about how to determine whether synchronization was successful, go to the following Microsoft website: If minor changes are not synced to the Office 365 user account, a directory synchronization problem may cause this issue.
Note Directory synchronization may sync successfully without updating the user’s UPN to the appropriate value if the user account is already licensed.
For more info about how to update the UPN in this case, see the following Microsoft Knowledge Base article:
User names in Office 365, Azure, or Intune don't match the on-premises UPN or alternate login ID
Still need help? Go to the Office 365 Community
website or the Azure Active Directory Forums
Article ID: 2530590 - Last Review: May 14, 2015 - Revision: 37.0
- Microsoft Azure Active Directory
- Microsoft Office 365
- Microsoft Intune
- CRM Online via Office 365 E Plans
- Microsoft Azure Recovery Services
- Office 365 Identity Management
|o365 o365a o365e o365022013 o365m KB2530590||