AWS Security ChangesHomeSearch

AWS quicksuite documentation change

Service: quicksuite · 2025-10-13 · Documentation low

File: quicksuite/latest/userguide/sharepoint-integration.md

Summary

Removed specific pricing details from subscription requirements and maintained organizational consent guidance

Security assessment

The changes remove monetary values from subscription tiers but retain security-relevant information about Microsoft admin consent requirements. No direct security vulnerability or mitigation is addressed.

Diff

diff --git a/quicksuite/latest/userguide/sharepoint-integration.md b/quicksuite/latest/userguide/sharepoint-integration.md
index e936fb8ab..76443a685 100644
--- a//quicksuite/latest/userguide/sharepoint-integration.md
+++ b//quicksuite/latest/userguide/sharepoint-integration.md
@@ -21 +21 @@ Make sure you have the following before you set up SharePoint integration.
-  * For action connectors: Amazon Quick Suite Enterprise subscription ($40 per user per month)
+  * For action connectors: Amazon Quick Suite Enterprise subscription
@@ -23 +23 @@ Make sure you have the following before you set up SharePoint integration.
-  * For data access: Amazon Quick Suite Professional subscription ($20 per user per month) or higher – As a one-time step from the admin, your Microsoft admin may need to grant organizational consent first before users can create a SharePoint integration to bring data. This is because Microsoft requires admin approval when using new applications (in our case the managed OAuth application), unless your user consent setting allows bypassing the admin approval. Admins can grant organization-wide consent by signing in and checking "Consent on behalf of your organization" during an integration creation for SharePoint.
+  * For data access: Amazon Quick Suite Professional subscription or higher – As a one-time step from the admin, your Microsoft admin may need to grant organizational consent first before users can create a SharePoint integration to bring data. This is because Microsoft requires admin approval when using new applications (in our case the managed OAuth application), unless your user consent setting allows bypassing the admin approval. Admins can grant organization-wide consent by signing in and checking "Consent on behalf of your organization" during an integration creation for SharePoint.