redpanda-data · micheleRP · Jun 23, 2025 · Jun 18, 2025 · Jun 23, 2025 · kbatuigas
@@ -50,9 +50,9 @@ contained in your own environment. This provides an additional layer of security
 
 NOTE: With standard BYOC clusters, Redpanda manages security policies and resources for your VPC or VNet, including subnetworks, IAM roles, and storage buckets/accounts. 
 
-==== Bring Your Own Virtual Private Cloud (BYOVPC) 
+==== Bring Your Own Network (BYOVPC/BYOVNet) 
 
-BYOVPC clusters allow you to deploy the Redpanda glossterm:data plane[] into your existing VPC/VNet and take full control of managing the networking lifecycle. Compared to standard BYOC, BYOVPC provides more security, but the configuration is more complex. See <<Shared responsibility model>>.
+BYOVPC or BYOVNet clusters allow you to deploy the Redpanda glossterm:data plane[] into your existing VPC (for AWS or GCP) or VNet (for Azure) and take full control of managing the networking lifecycle. Compared to standard BYOC, BYOVPC/BYOVNet provides more security, but the configuration is more complex. See <<Shared responsibility model>>.
 
 The BYOC infrastructure that Redpanda manages should not be used to deploy any other workloads.
 
@@ -148,7 +148,7 @@ BYOC::
 |===
 
 --
-BYOVPC::
+BYOVPC/BYOVNet::
 +
 --
 |===
@@ -263,7 +263,7 @@ Features in limited availability are production-ready and are covered by Redpand
 
 The following features are currently in limited availability in Redpanda Cloud:
 
-* Redpanda Connect for Dedicated and BYOC (excluding BYOVPC on Azure)
+* Redpanda Connect for Dedicated and BYOC (excluding BYOVNet on Azure)
 * Serverless
 * Dedicated and BYOC for Azure
 * BYOVPC for GCP
@@ -275,10 +275,10 @@ Features in beta are available for testing and feedback. They are not covered by
 
 The following features are currently in beta in Redpanda Cloud:
 
-* Redpanda Connect on Serverless and BYOVPC
-* BYOVPC for AWS and Azure
+* Redpanda Connect on Serverless and BYOVPC/BYOVNet
+* BYOVPC for AWS  
+* BYOVNet for Azure
 * Integration with Apache Iceberg
-
 * Remote Read Replicas for AWS and GCP
 
 == Next steps

@@ -6,7 +6,7 @@ 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].
 
-NOTE: With standard BYOC clusters, Redpanda manages security policies and resources for your virtual network (VNet), including subnetworks, managed identities, IAM roles, security groups, and storage accounts. For the most security, you can manage these resources yourself with a xref:get-started:cluster-types/byoc/azure/vnet-azure.adoc[BYOVPC cluster on Azure].
+NOTE: With standard BYOC clusters, Redpanda manages security policies and resources for your virtual network (VNet), including subnetworks, managed identities, IAM roles, security groups, and storage accounts. For the most security, you can manage these resources yourself with a xref:get-started:cluster-types/byoc/azure/vnet-azure.adoc[BYOVNet cluster on Azure].
 
 == Prerequisites
 

@@ -1,20 +1,20 @@
-= Create a BYOVPC Cluster on Azure
+= Create a BYOVNet Cluster on Azure
 :description: Connect Redpanda Cloud to your existing VNet for additional security.
 :page-beta: true
 
 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 virtual network (VNet) and take full control of managing the networking lifecycle. See also: xref:get-started:byoc-arch.adoc[BYOC architecture]. 
+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, BYOVPC provides more security.
+Compared to a standard Bring Your Own Cloud (BYOC) setup, where Redpanda manages the networking lifecycle for you, BYOVNet provides more security.
 
-When you create a BYOVPC 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: 
+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: 
 
 * You provide your own VNet in your Azure account.
 * You maintain more control over your account, because Redpanda requires fewer permissions than standard BYOC clusters.
 * You control your security resources and policies, including subnets, user-assigned identities, IAM roles and assignments, security groups, storage accounts, and key vaults.
 
-The https://github.com/redpanda-data/cloud-examples/tree/main/customer-managed/azure/README.md[Redpanda Cloud Examples repository^] contains https://developer.hashicorp.com/terraform[Terraform^] code that deploys the resources required for a BYOVPC cluster on Azure. You'll need to create these resources in advance and give them to Redpanda during cluster creation. Variables are provided in the code so you can exclude resources that already exist in your environment, such as the VNet.
+The https://github.com/redpanda-data/cloud-examples/tree/main/customer-managed/azure/README.md[Redpanda Cloud Examples repository^] contains https://developer.hashicorp.com/terraform[Terraform^] code that deploys the resources required for a BYOVNet cluster on Azure. You'll need to create these resources in advance and give them to Redpanda during cluster creation. Variables are provided in the code so you can exclude resources that already exist in your environment, such as the VNet.
 
 See the code for the complete list of resources required to create and deploy Redpanda cluster. Customer-managed resources can be broken down into the following groups:
 
@@ -36,8 +36,8 @@ See the code for the complete list of resources required to create and deploy Re
 
 == Limitations
 
-* Existing clusters cannot be moved to a BYOVPC cluster.
-* After creating a BYOVPC cluster, you cannot change to a different VNet.
+* Existing clusters cannot be moved to a BYOVNet cluster.
+* After creating a BYOVNet cluster, you cannot change to a different VNet.
 * Only primary CIDR ranges are supported for the VNet.
 
 == Set environment variables

@@ -1,6 +1,6 @@
 [IMPORTANT]
 ====
 
-* BYOVPC 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^]. 
+* 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^]. 
 * Redpanda Connect is in beta for BYOVPC clusters.
 ====