Merge pull request #229128 from miwithro/patch-218

Update workload-identity-migrate-from-pod-identity.md

Author: prmerger-automator[bot]

articles/aks/workload-identity-migrate-from-pod-identity.md

@@ -6,12 +6,10 @@ ms.custom: devx-track-azurecli
 ms.date: 03/14/2023
 ---
 
-# Migrate from pod managed-identity to workload identity (preview)
+# Migrate from pod managed-identity to workload identity
 
 This article focuses on migrating from a pod-managed identity to Azure Active Directory (Azure AD) workload identity (preview) for your Azure Kubernetes Service (AKS) cluster. It also provides guidance depending on the version of the [Azure Identity][azure-identity-supported-versions] client library used by your container-based application.
 
-[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
-
 ## Before you begin
 
 - The Azure CLI version 2.40.0 or later. Run `az --version` to find the version, and run `az upgrade` to upgrade the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
@@ -116,6 +114,9 @@ az identity federated-credential create --name federatedIdentityName --identity-
 
 ## Deploy the workload with migration sidecar
 
+> [!NOTE]
+> The migration sidecar is **not supported for production usage**.  This feature was designed to give customers time to migrate there application SDK's to a supported version and not be a long running process.
+
 If your application is using managed identity and still relies on IMDS to get an access token, you can use the workload identity migration sidecar to start migrating to workload identity. This sidecar is a migration solution and in the long-term applications, you should modify their code to use the latest Azure Identity SDKs that support client assertion.
 
 To update or deploy the workload, add these pod annotations only if you want to use the migration sidecar. You inject the following [annotation][pod-annotations] values to use the sidecar in your pod specification: