From 0e07035130b5df74669ea40798764d9f75008179 Mon Sep 17 00:00:00 2001
From: martin-tournier <martin.tournier@datadoghq.com>
Date: Thu, 16 Apr 2026 09:43:24 +0200
Subject: [PATCH] removing-preview.md

---
 .../logs/log_configuration/forwarding_custom_destinations.md  | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/content/en/logs/log_configuration/forwarding_custom_destinations.md b/content/en/logs/log_configuration/forwarding_custom_destinations.md
index 4b23450a25b..c3777d2e1ac 100644
--- a/content/en/logs/log_configuration/forwarding_custom_destinations.md
+++ b/content/en/logs/log_configuration/forwarding_custom_destinations.md
@@ -110,10 +110,6 @@ Due to security protocols for the US1-FED site, only port 443 and 8088 are open
 
 {{% tab "Google SecOps (Chronicle)" %}}
 
-<div class="alert alert-info">
-<b>Preview available</b>: You can send logs to Google SecOps (Chronicle) from Datadog  <a href="https://www.datadoghq.com/product-preview/log-forwarding-to-google-chronicle/">Register for the Preview</a>.
-</div>
-
 7. Enter a name for the destination.
 8. Authentication for the Google Chronicle Forwarder requires using a GCP Service Account with Chronicle write access.
 9. In the **Configure Destination** section, enter the following details: