AWS quicksuite documentation change
Summary
Updated authentication steps: added email requirement for all identity providers, added Okta support, reordered SCIM setup instructions, and removed Entra ID exclusivity note.
Security assessment
Enhances security documentation by mandating email associations and SCIM identity propagation. These changes promote secure identity management but don't remediate any known security flaws.
Diff
diff --git a/quicksuite/latest/userguide/teams-extension.md b/quicksuite/latest/userguide/teams-extension.md index 74c658fa5..5720d041e 100644 --- a//quicksuite/latest/userguide/teams-extension.md +++ b//quicksuite/latest/userguide/teams-extension.md @@ -57 +57 @@ If you configured the authentication to connect to Amazon Quick Suite with IAM I - 2. Use Microsoft Entra ID as your identity provider. + 2. Ensure that every user under your Entra ID or Okta provider configuration has an email associated with them. @@ -59 +59 @@ If you configured the authentication to connect to Amazon Quick Suite with IAM I - 3. Ensure that every user under your Entra ID provider configuration has an email associated with them. + 3. If using Entra ID, set up SCIM identity propagation between the Microsoft Entra ID instance and IAM Identity Center. For detailed steps, see [Configure SAML and SCIM with Microsoft Entra ID and IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/azure-ad-idp.html). @@ -61 +60,0 @@ If you configured the authentication to connect to Amazon Quick Suite with IAM I - 4. Set up SCIM identity propagation between the Microsoft Entra ID instance and IAM Identity Center. For detailed steps, see [Configure SAML and SCIM with Microsoft Entra ID and IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/azure-ad-idp.html). @@ -65,5 +63,0 @@ If you configured the authentication to connect to Amazon Quick Suite with IAM I - -###### Note - -The Microsoft Teams extension supports only Entra ID authentication with IAM Identity Center. -