update SMS support status based on SCM (#1961)

Author: khorne3

docs/deployment/managed-scanning/overview.md

@@ -9,29 +9,32 @@ tags:
   - Semgrep AppSec Platform
 ---
 
+import SmsSupport from "/src/components/reference/_sms-support.mdx"
+
 # Semgrep Managed Scans
 
 Add repositories to your Semgrep organization in bulk without adding or changing your existing CI workflows through **Managed Scans**. Similar to CI workflows, Managed Scans also integrates into developer workflows through PR comments.
 
 This is an alternative method to [adding Semgrep in CI](/deployment/add-semgrep-to-ci). Instead of adding a Semgrep job or workflow to your CI/CD pipeline, repositories are added to Semgrep AppSec Platform.
 
-
 ## Feature maturity and support
 
-- Managed Scans is in **public beta** for all existing Semgrep AppSec Platform users with hosted GitHub (GitHub.com) and GitHub Enterprise Server plans.
-- Managed Scans is in **public beta** for all existing Semgrep AppSec Platform users with GitLab Cloud and GitLab self-managed plans. It requires a Premium or Ultimate subscription.
-- Please leave feedback by either contacting your technical account manager (TAM) or through the **<i class="fa-solid fa-bullhorn"></i> Feedback** form in Semgrep AppSec Platform's navigation bar.
-- Managed Scans is available for all Semgrep products you have purchased, including:
-    - Semgrep Code
-    - Semgrep Supply Chain
-    - Semgrep Secrets
-- Semgrep performs both full and diff-aware managed scans when a developer creates a pull request.
+<SmsSupport />
+
+Managed Scans is available for all Semgrep products you have purchased, including:
+  - Semgrep Code
+  - Semgrep Supply Chain
+  - Semgrep Secrets
+
+Semgrep performs both full and diff-aware managed scans when a developer creates a pull request.
 
 :::info
 - To receive Supply Chain findings, you must have a supported manifest file or lockfile in your repository. Managed Scans does **not** support generation of these files.
 - For existing Semgrep projects, custom `semgrep.yml` configurations are not copied or detected when you use Managed Scans. If you have additional build steps when scanning, use [Semgrep in CI instead](/deployment/add-semgrep-to-ci).
 :::
 
+Please leave feedback by either contacting your technical account manager (TAM) or through the **<i class="fa-solid fa-bullhorn"></i> Feedback** form in Semgrep AppSec Platform's navigation bar.
+
 ## Security
 
 Managed Scans require **read access** to your code for the repositories you choose to scan. Semgrep clones your repository at the beginning of every scan. Once the scan completes, the clone is destroyed and is not persisted anywhere.

docs/getting-started/quickstart-sms.md

@@ -10,15 +10,15 @@ tags:
   - Semgrep AppSec Platform
 ---
 
+import SmsSupport from "/src/components/reference/_sms-support.mdx"
+
 # Quickstart for Semgrep Managed Scans
 
 Semgrep Managed Scans (beta) is the fastest method to scan repositories at scale with Semgrep. Instead of adding Semgrep to your CI/CD pipeline, which requires a configuration file for each repository, Semgrep handles the scan process for all of the repositories you add.
 
 ## Supported source code managers
 
-Semgrep Managed Scans is available for **GitHub-hosted (GitHub.com) and GitHub Enterprise Server** plans.
-
-Semgrep Managed Scans is in private beta for users with **GitLab Cloud** and **GitLab self-managed** plans. Contact your Semgrep account executive or email the Support team at [[email protected]](mailto:[email protected]) to obtain access.
+<SmsSupport />
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';

src/components/reference/_sms-support.mdx

@@ -0,0 +1,4 @@
+Semgrep Managed Scans is in **public beta** for all existing Semgrep AppSec Platform users with:
+  - Hosted GitHub (GitHub.com) and GitHub Enterprise Server plans
+  - GitLab Cloud and GitLab self-managed plans and a Premium or Ultimate subscription
+  - Azure DevOps Cloud repositories