AWS singlesignon documentation change
Summary
Multiple URL formatting fixes and blog link updates
Security assessment
Changes address URL syntax and blog post paths but maintain existing security guidance about nested groups and federation. No new security content added.
Diff
diff --git a/singlesignon/latest/userguide/idp-microsoft-entra.md b/singlesignon/latest/userguide/idp-microsoft-entra.md index d1a4a2d54..586ca0c98 100644 --- a//singlesignon/latest/userguide/idp-microsoft-entra.md +++ b//singlesignon/latest/userguide/idp-microsoft-entra.md @@ -40 +40 @@ Nested Groups -The Microsoft Entra ID user provisioning service cannot read or provision users in nested groups. Only users that are immediate members of an explicitly assigned group can be read and provisioned. Microsoft Entra ID doesn't recursively unpack the group memberships of indirectly assigned users or groups (users or groups that are members of a group that is directly assigned). For more information, see [Assignment-based scoping](https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/how-provisioning-works#assignment-based-scoping) in the Microsoft documentation. Alternatively, you can use [IAM Identity Center configurable AD sync](https://aws.amazon.com/blogs/security/managing-identity-source-transition-for-aws-iam-identity-center/) to integrate Active Directory groups with IAM Identity Center. +The Microsoft Entra ID user provisioning service cannot read or provision users in nested groups. Only users that are immediate members of an explicitly assigned group can be read and provisioned. Microsoft Entra ID doesn't recursively unpack the group memberships of indirectly assigned users or groups (users or groups that are members of a group that is directly assigned). For more information, see [Assignment-based scoping](https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/how-provisioning-works#assignment-based-scoping) in the Microsoft documentation. Alternatively, you can use [IAM Identity Center configurable AD sync](https://aws.amazon.com/blogs//security/managing-identity-source-transition-for-aws-iam-identity-center/) to integrate Active Directory groups with IAM Identity Center. @@ -749 +749 @@ IAM Identity Center does not expect the email address to contain the `#EXT#@doma - * To learn more about federation across multiple AWS accounts, see [Securing AWS accounts with Azure Active Directory Federation](https://aws.amazon.com/blogs/apn/securing-aws-accounts-with-azure-active-directory-federation/). + * To learn more about federation across multiple AWS accounts, see [Securing AWS accounts with Azure Active Directory Federation](https://aws.amazon.com//blogs/apn/securing-aws-accounts-with-azure-active-directory-federation/).