Skip to content

Commit 264bf24

Browse files
authored
fixing alt text
1 parent 1d58c93 commit 264bf24

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/hybrid/connect/tshoot-connect-sso.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,17 +41,17 @@ This article helps you find troubleshooting information about common problems re
4141

4242
Ensure that the Seamless SSO feature is still **Enabled** on your tenant. You can check the status by going to the **Azure Active Directory** > **Azure AD Connect** pane in the [[Microsoft Entra admin center](https://entra.microsoft.com)](https://portal.azure.com/).
4343

44-
![Microsoft Entra admin center: Azure AD Connect pane](./media/tshoot-connect-sso/sso10.png)
44+
![Screenshot of the Microsoft Entra admin center: Azure AD Connect pane.](./media/tshoot-connect-sso/sso10.png)
4545

4646
Click through to see all the AD forests that have been enabled for Seamless SSO.
4747

48-
![Microsoft Entra admin center: Seamless SSO pane](./media/tshoot-connect-sso/sso13.png)
48+
![Screenshot of the Microsoft Entra admin center: Seamless SSO pane.](./media/tshoot-connect-sso/sso13.png)
4949

5050
## Sign-in failure reasons in the [Microsoft Entra admin center](https://entra.microsoft.com) (needs a Premium license)
5151

5252
If your tenant has an Azure AD Premium license associated with it, you can also look at the [sign-in activity report](../../reports-monitoring/concept-sign-ins.md) inside of Azure Active Directory in the [Microsoft Entra admin center](https://entra.microsoft.com).
5353

54-
![Microsoft Entra admin centerhttps://entra.microsoft.com: Sign-ins report](media/tshoot-connect-sso/sso9.png)
54+
![Screenshot of the Microsoft Entra admin center: Sign-ins report.](media/tshoot-connect-sso/sso9.png)
5555

5656
Browse to **Azure Active Directory** > **Sign-ins** in the [[Microsoft Entra admin center](https://entra.microsoft.com)](https://portal.azure.com/), and then select a specific user's sign-in activity. Look for the **SIGN-IN ERROR CODE** field. Map the value of that field to a failure reason and resolution by using the following table:
5757

0 commit comments

Comments
 (0)