DOC-136 Document feature Azure Implementation for Cloud GA (#353)

micheleRP · web-flow · commit 1ab60ba6ca30 · 2025-07-30T14:42:31.000-06:00
* DOC-136 Document feature Azure Implementation for Cloud GA

* update admonition

* minor edits for consistency

* add missing beta features

* remove beta from BYOVPC on AWS, consistency updates

* update text for What's New

* BYOVNet back to beta, Dedicated back to LA

* move BYOVPC on AWS back to beta

* typo

* revert back feature flag partial

* minor edits, just reverting back to original text

* minor edits

* add Iceberg GA to What's New

* remove beta admonition for Iceberg
diff --git a/modules/get-started/pages/cloud-overview.adoc b/modules/get-started/pages/cloud-overview.adoc
@@ -264,8 +264,7 @@ Features in limited availability are production-ready and are covered by Redpand
 The following features are currently in limited availability in Redpanda Cloud:
 
 * Serverless
-* Dedicated and BYOC for Azure
-* BYOVPC for GCP
+* Dedicated for Azure
 
 == Features in beta
 
@@ -275,8 +274,11 @@ The following features are currently in beta in Redpanda Cloud:
 
 * BYOVPC for AWS  
 * BYOVNet for Azure
+* Secrets Management for BYOVPC on GCP and AWS
 * Integration with Apache Iceberg
 * Remote Read Replicas for AWS and GCP
+* AI agents
+* Several Redpanda Connect components 
 
 == Next steps
 * xref:manage:maintenance.adoc[Learn about upgrades and maintenance]
diff --git a/modules/get-started/pages/cluster-types/byoc/aws/vpc-byo-aws.adoc b/modules/get-started/pages/cluster-types/byoc/aws/vpc-byo-aws.adoc
@@ -6,11 +6,9 @@
 
 include::shared:partial$feature-flag-rpcn.adoc[]
 
-This topic explains how to create a Bring Your Own Virtual Private Cloud (BYOVPC) cluster. This setup allows you to deploy the Redpanda glossterm:data plane[] into your existing VPC and take full control of managing the networking lifecycle. See also: xref:get-started:byoc-arch.adoc[BYOC architecture]. 
+A Bring Your Own Virtual Private Cloud (BYOVPC) cluster allows you to deploy the Redpanda glossterm:data plane[] into your existing VPC and manage the networking lifecycle. Compared to a standard Bring Your Own Cloud (BYOC) setup, where Redpanda manages the networking lifecycle for you, BYOVPC provides more control. See also: xref:get-started:byoc-arch.adoc[BYOC architecture]. 
 
-Compared to a standard Bring Your Own Cloud (BYOC) setup, where Redpanda manages the networking lifecycle for you, BYOVPC provides more security.
-
-When you create a BYOCVPC cluster, you specify your VPC and service account. The Redpanda Cloud agent doesn't create any new resources or alter any settings in your account. With BYOVPC: 
+When you create a BYOVPC cluster, you specify your VPC and the IAM role (instance profile) that the Redpanda agent will assume. The Redpanda Cloud agent doesn't create any new resources or alter any settings in your account. With BYOVPC: 
 
 * You provide your own VPC in your AWS account.
 * You maintain more control over your account, because Redpanda requires fewer permissions than standard BYOC clusters.
diff --git a/modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc b/modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc
@@ -2,7 +2,6 @@
 :description: Use the Redpanda Cloud UI to create a BYOC cluster on Azure.
 :page-aliases: deploy:deployment-option/cloud/create-byoc-cluster-azure.adoc, get-started:cluster-types/byoc/create-byoc-cluster-azure.adoc
 
-include::shared:partial$feature-flag.adoc[]
 
 To create a Redpanda cluster in your virtual network (VNet), follow the instructions in the Redpanda Cloud UI. The UI contains the parameters necessary to successfully run `rpk cloud byoc apply`. See also: xref:get-started:byoc-arch.adoc[BYOC architecture].
 
diff --git a/modules/get-started/pages/cluster-types/byoc/azure/index.adoc b/modules/get-started/pages/cluster-types/byoc/azure/index.adoc
@@ -1,3 +1,3 @@
 = BYOC: Azure
-:description: Learn how to create a BYOC or BYOVPC cluster on Azure.
+:description: Learn how to create a BYOC or BYOVNet cluster on Azure.
 :page-layout: index
diff --git a/modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc b/modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc
@@ -4,9 +4,7 @@
 
 include::shared:partial$feature-flag-rpcn.adoc[]
 
-This topic explains how to create a Bring Your Own Virtual Network (BYOVNet) cluster. This setup allows you to deploy the Redpanda glossterm:data plane[] into your existing VNet and take full control of managing the networking lifecycle. See also: xref:get-started:byoc-arch.adoc[BYOC architecture]. 
-
-Compared to a standard Bring Your Own Cloud (BYOC) setup, where Redpanda manages the networking lifecycle for you, BYOVNet provides more security.
+A Bring Your Own Virtual Network (BYOVNet) cluster allows you to deploy the Redpanda glossterm:data plane[] into your existing VNet and manage the networking lifecycle. Compared to a standard Bring Your Own Cloud (BYOC) setup, where Redpanda manages the networking lifecycle for you, BYOVNet provides more control. See also: xref:get-started:byoc-arch.adoc[BYOC architecture].
 
 When you create a BYOVNet cluster, you specify your VNet and managed identities. The Redpanda Cloud agent doesn't create any new resources or alter any settings in your account. With a customer-managed VNet: 
 
diff --git a/modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc b/modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc
@@ -4,9 +4,7 @@
 
 include::shared:partial$feature-flag-rpcn.adoc[]
 
-This topic explains how to create a Bring Your Own Virtual Private Cloud (BYOVPC) cluster. This setup allows you to deploy the Redpanda glossterm:data plane[] into your existing VPC and take full control of managing the networking lifecycle. See also: xref:get-started:byoc-arch.adoc[BYOC architecture]. 
-
-Compared to a standard Bring Your Own Cloud (BYOC) setup, where Redpanda manages the networking lifecycle for you, BYOVPC provides more security.
+A Bring Your Own Virtual Private Cloud (BYOVPC) cluster allows you to deploy the Redpanda glossterm:data plane[] into your existing VPC and manage the networking lifecycle. Compared to a standard Bring Your Own Cloud (BYOC) setup, where Redpanda manages the networking lifecycle for you, BYOVPC provides more control. See also: xref:get-started:byoc-arch.adoc[BYOC architecture].
 
 When you create a BYOVPC cluster, you specify your VPC and service account. The Redpanda Cloud agent doesn't create any new resources or alter any settings in your account. With BYOVPC: 
 
diff --git a/modules/get-started/pages/cluster-types/create-dedicated-cloud-cluster.adoc b/modules/get-started/pages/cluster-types/create-dedicated-cloud-cluster.adoc
@@ -9,18 +9,12 @@ After you log in to https://cloud.redpanda.com[Redpanda Cloud^], you land on the
 . On the Clusters page, click *Create cluster*, then click *Create Dedicated cluster*.
 +
 Enter a cluster name, then select the resource group, cloud provider (AWS, GCP, or Azure), xref:reference:tiers/dedicated-tiers.adoc[region, tier], availability, and Redpanda version.
-
 +
 [NOTE]
 ====
 * If you plan to create a private network in your own VPC, select the region where your VPC is located.
 * Three availability zones provide two backups in case one availability zone goes down.
 ====
-+
-[IMPORTANT]
-====
-To unlock this feature for Azure, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda support^]. 
-====
 
 . Click *Next*.
 . On the Network page, enter the connection type: *Public* or *Private*. For private networks:
@@ -30,7 +24,7 @@ To unlock this feature for Azure, contact https://support.redpanda.com/hc/en-us/
 Private networks require either a VPC peering connection or a private connectivity service, such as xref:networking:configure-privatelink-in-cloud-ui.adoc[AWS PrivateLink], xref:networking:configure-private-service-connect-in-cloud-ui.adoc[GCP Private Service Connect], or xref:networking:azure-private-link.adoc[Azure Private Link]. 
 
 . Click *Create*.
-
++
 After the cluster is created, you can select the cluster on the *Clusters* page to see the overview for it.
 
 include::shared:partial$kafka-connect.adoc[]
diff --git a/modules/get-started/pages/whats-new-cloud.adoc b/modules/get-started/pages/whats-new-cloud.adoc
@@ -9,6 +9,14 @@ This page lists new features added to Redpanda Cloud.
 
 == July 2025
 
+=== Iceberg topics in Redpanda Cloud: GA
+
+xref:manage:iceberg/about-iceberg-topics.adoc[Iceberg topics] are now generally available (GA) in Redpanda Cloud. 
+
+=== BYOC on Azure: GA
+
+xref:get-started:cluster-types/byoc/azure/create-byoc-cluster-azure.adoc[BYOC for Azure] is now generally available (GA). 
+
 === mTLS and SASL authentication for Kafka API on AWS
 
 You can now enable mTLS and SASL authentication simultaneously for the Kafka API on AWS clusters. If you enable both mTLS and SASL on AWS clusters, Redpanda creates two distinct listeners: an mTLS listener operating on one port and a SASL listener operating on a different port.
diff --git a/modules/manage/pages/iceberg/about-iceberg-topics.adoc b/modules/manage/pages/iceberg/about-iceberg-topics.adoc
@@ -1,6 +1,4 @@
 = About Iceberg Topics
 :description: Learn how Redpanda can integrate topics with Apache Iceberg.
 
-NOTE: The Iceberg integration for Redpanda Cloud is a beta feature. It is not supported for production deployments.
-
 include::ROOT:manage:partial$iceberg/about-iceberg-topics.adoc[]
diff --git a/modules/networking/pages/azure-private-link.adoc b/modules/networking/pages/azure-private-link.adoc
@@ -1,7 +1,7 @@
 = Configure Azure Private Link with the Cloud API
 :description: Set up Azure Private Link with the Cloud API.
 
-NOTE: For UI-based configuration of Azure Private Link, see xref:networking:azure-private-link-in-ui.adoc[Configure Azure Private Link in the Cloud UI].
+NOTE: For UI-based configuration of Azure Private Link on new clusters, see xref:networking:azure-private-link-in-ui.adoc[Configure Azure Private Link in the Cloud UI].
 
 The Redpanda Azure Private Link service provides secure access to Redpanda Cloud from your own virtual network. Traffic over Azure Private Link does not go through the public internet, but instead through Microsoft's backbone network. While clients can initiate connections against the Redpanda Cloud cluster endpoints, Redpanda Cloud services cannot access your virtual networks directly.
 
diff --git a/modules/shared/partials/feature-flag-rpcn.adoc b/modules/shared/partials/feature-flag-rpcn.adoc
@@ -1,5 +1,4 @@
 [IMPORTANT]
 ====
-
 BYOVPC/BYOVNet is an add-on feature that may require an additional purchase. To unlock this feature for your account, contact your Redpanda account team or https://www.redpanda.com/price-estimator[Redpanda Sales^]. 
-==== 
+==== 
