Removing specific finding names from Cloud and SaaS Remediation (#28418)

Cloud and SaaS Findings Remediation actions currently support several vendors and actions. These lists will grow in time. To ensure the documentation is up-to-date, this commit removes specific call outs of which vendors and finding types are supported. Instead, customers should reference the Cloudflare Dash directly.

Author: mleslie-cf

src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx

@@ -114,17 +114,6 @@ The instance will be moved from **Active** to **Hidden** within the finding. If
 
 In addition to detecting and surfacing misconfigurations or issues with SaaS and cloud applications, CASB can also remediate findings directly in applications.
 
-CASB supports remediation for findings from the [Microsoft 365 integration](/cloudflare-one/integrations/cloud-and-saas/microsoft-365/):
-
-<Details header="Supported CASB findings for remediation">
-
-- Microsoft: File publicly accessible with edit access
-- Microsoft: File publicly accessible with view access
-- Microsoft: File publicly accessible with edit access with DLP Profile match
-- Microsoft: File publicly accessible with view access with DLP Profile match
-
-</Details>
-
 ### Configure remediation permissions
 
 Before you can remediate findings, [add a new integration](/cloudflare-one/integrations/cloud-and-saas/#add-an-integration) and choose _Read-Write mode_ during setup. Alternatively, you can update an existing integration: