From 151c1f4e01e5688f42421be4571198a9f685032c Mon Sep 17 00:00:00 2001
From: hc-github-team-secure-vault-core
 <82990506+hc-github-team-secure-vault-core@users.noreply.github.com>
Date: Tue, 21 Nov 2023 11:06:56 -0500
Subject: [PATCH] backport of commit 66b3e439d80c7cb991ec31cd84d652c1001aa3f6
 (#24216)

Co-authored-by: Scott Miller <smiller@hashicorp.com>
---
 website/content/docs/enterprise/fips/fips1402.mdx | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/enterprise/fips/fips1402.mdx b/website/content/docs/enterprise/fips/fips1402.mdx
index 817dcd82a02c..58745a6864f9 100644
--- a/website/content/docs/enterprise/fips/fips1402.mdx
+++ b/website/content/docs/enterprise/fips/fips1402.mdx
@@ -88,8 +88,12 @@ reasons:
    of say, a Root CA involves a concerted, non-Vault effort to accomplish
    and must be done thoughtfully.
 
-Combined, we suggest leaving the existing cluster in place, and carefully
-consider migration of specific workloads to the FIPS-backed cluster.
+As such Hashicorp cannot provide support for workloads that are affected
+either technically or via non-compliance that results from converting
+existing cluster workloads to the FIPS 140-2 Inside binary.
+
+Instead, we suggest leaving the existing cluster in place, and carefully
+consider migration of specific workloads to the FIPS-backed cluster.  
 
 #### Entropy Augmentation Restrictions