fix links

Author: ceperezb

learn-pr/wwl-sci/design-solutions-identity-access-management/includes/3-design-solution-external-identities.md

@@ -1,7 +1,7 @@
 
 Microsoft Entra External ID combines powerful solutions for working with people outside of your organization. With External ID capabilities, you can allow external identities to securely access your apps and resources. Whether you’re working with external partners, consumers, or business customers, users can bring their own identities. These identities can range from corporate or government-issued accounts to social identity providers like Google or Facebook.
 
-:::image type="content" source="../media/external-identities-overview.png" lightbox="../media/nexternal-identities-overview.png" alt-text="Diagram showing an overview of Microsoft Entra External ID.":::
+:::image type="content" source="../media/external-identities-overview.png" lightbox="../media/external-identities-overview.png" alt-text="Diagram showing an overview of Microsoft Entra External ID.":::
 
 These scenarios fall within the scope of Microsoft Entra External ID:
 
@@ -67,11 +67,11 @@ The following table compares the scenarios you can enable with External ID.
 | ---- | --- |   --- |
 | **Primary scenario**  | Allow your workforce to collaborate with business guests. Let guests use their preferred identities to sign in to resources in your Microsoft Entra organization. Provides access to Microsoft applications or your own applications (SaaS apps, custom-developed apps, and so on). <br><br> *Example:* Invite a guest to sign in to your Microsoft apps or become a guest member in Teams. |  Publish apps to external consumers and business customers using External ID for identity experiences. Provides identity and access management for modern SaaS or custom-developed applications (not first-party Microsoft apps). <br><br> *Example:* Create a customized sign-in experience for users of your consumer mobile app and monitor app usage. |
 | **Intended for**  | Collaborating with business partners from external organizations like suppliers, partners, vendors. These users might or might not have Microsoft Entra ID or managed IT.   |   Consumers and business customers of your app. These users are managed in a Microsoft Entra tenant that is configured for external apps and users. |
-| **User management**  | B2B collaboration users are managed in the same workforce tenant as employees but are typically annotated as guest users. Guest users can be managed the same way as employees, added to the same groups, and so on. [Cross-tenant access settings](cross-tenant-access-overview.md) can be used to determine which users have access to B2B collaboration.   |   App users are managed in an external tenant that you create for consumers of your application. Users in an external tenant have different [default permissions](customers/reference-user-permissions.md) than users in a workforce tenant. They're managed in the external tenant, separate from the organization's employee directory. |
+| **User management**  | B2B collaboration users are managed in the same workforce tenant as employees but are typically annotated as guest users. Guest users can be managed the same way as employees, added to the same groups, and so on. [Cross-tenant access settings](/entra/external-id/cross-tenant-access-overview) can be used to determine which users have access to B2B collaboration.   |   App users are managed in an external tenant that you create for consumers of your application. Users in an external tenant have different [default permissions](/entra/external-id/customers/reference-user-permissions) than users in a workforce tenant. They're managed in the external tenant, separate from the organization's employee directory. |
 | **Single sign-on (SSO)**  | SSO to all Microsoft Entra connected apps is supported. For example, you can provide access to Microsoft 365 or on-premises apps, and to other SaaS apps such as Salesforce or Workday.  | SSO to apps registered in the external tenant is supported. SSO to Microsoft 365 or to other Microsoft SaaS apps isn't supported. |
-|   **Company branding**    |  The default state for the authentication experience is a Microsoft look and feel. Administrators can customize the guest sign-in experience with their company branding.    |  The default branding for the external tenant is neutral and doesn't include any existing Microsoft branding. Administrators can customize the branding for the organization or per application.  [Learn more](customers/concept-branding-customers.md).    |  
-| **Microsoft cloud settings**  | [Supported.](cross-cloud-settings.md)  |  Not applicable.  |
-| **Entitlement management**  | [Supported.](~/id-governance/entitlement-management-overview.md)  | Not applicable. |
+|   **Company branding**    |  The default state for the authentication experience is a Microsoft look and feel. Administrators can customize the guest sign-in experience with their company branding.    |  The default branding for the external tenant is neutral and doesn't include any existing Microsoft branding. Administrators can customize the branding for the organization or per application.  [Learn more](/entra/external-id/customers/concept-branding-customers).    |  
+| **Microsoft cloud settings**  | [Supported.](/entra/external-id/cross-cloud-settings)  |  Not applicable.  |
+| **Entitlement management**  | [Supported.](/entra/id-governance/entitlement-management-overview)  | Not applicable. |
 
 
 #### Related technologies