diff --git a/app/_data/docs_nav_konnect.yml b/app/_data/docs_nav_konnect.yml
index a2b894f1e92a..93977c1b5790 100644
--- a/app/_data/docs_nav_konnect.yml
+++ b/app/_data/docs_nav_konnect.yml
@@ -60,6 +60,8 @@
url: /gateway-manager/data-plane-nodes/custom-dp-labels
- text: Transit Gateways
url: /gateway-manager/data-plane-nodes/transit-gateways
+ - text: Azure VNET Peering
+ url: /gateway-manager/data-plane-nodes/azure-peering
- text: Provision a Dedicated Cloud Gateway
url: /gateway-manager/provision-cloud-gateway/
- text: Control Plane Groups
diff --git a/app/_includes/md/konnect/azure-peering.md b/app/_includes/md/konnect/azure-peering.md
new file mode 100644
index 000000000000..0557ed81b434
--- /dev/null
+++ b/app/_includes/md/konnect/azure-peering.md
@@ -0,0 +1,45 @@
+
+{% mermaid %}
+flowchart LR
+
+A(API or service)
+B(API or service)
+C(API or service)
+
+G(
Konnect \n#40;fully-managed \ndata plane#41;)
+H(Konnect \n#40;fully-managed \ndata plane#41;)
+J(fa:fa-wifi \n Internet)
+
+subgraph 1 [User Azure Cloud]
+ subgraph 2 [Region]
+ subgraph 3 [Virtual Network #40;VNET#41;]
+ A
+ B
+ C
+ end
+ end
+end
+3 <--VNET Peering \n Private API Access--> 6
+
+subgraph 4 [Kong Azure Cloud]
+ subgraph 5 [Region]
+ subgraph 6 [Virtual Network #40;VNET#41;]
+ G
+ H
+ end
+ end
+end
+
+G & H <--public API \n access--> J
+
+style A stroke:#e07113
+style B stroke:#e07113
+style C stroke:#e07113
+style 2 stroke:#167eba,color:#167eba,stroke-dasharray:3
+style 5 stroke:#167eba,color:#167eba,stroke-dasharray:3
+style 3 stroke:#238813,color:#238813,stroke-dasharray:3
+style 6 stroke:#238813,color:#238813,stroke-dasharray:3
+
+
+{% endmermaid %}
+
\ No newline at end of file
diff --git a/app/konnect/gateway-manager/data-plane-nodes/azure-peering.md b/app/konnect/gateway-manager/data-plane-nodes/azure-peering.md
new file mode 100644
index 000000000000..b4264a79de06
--- /dev/null
+++ b/app/konnect/gateway-manager/data-plane-nodes/azure-peering.md
@@ -0,0 +1,89 @@
+---
+title: How to configure Azure Virtual Network Peering
+---
+
+{{site.konnect_short_name}} can leverage [Azure Virtual Network Peering](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-peering-overview) to create virtual networks, and ingest data from your Azure services and expose them to the internet via {{site.konnect_short_name}}.
+
+## How virtual network peering works
+
+{% include_cached /md/konnect/azure-peering.md %}
+> _**Figure 1:** In this diagram, the "User Azure Cloud", represents the Azure infrastructure that runs your microservices. The "Kong Azure Cloud", powers your Kong data planes. Using virtual network peering, you can ingest traffic from your Azure environment and expose it to the internet._
+
+## Prerequisites
+
+* A {{site.konnect_short_name}} control plane
+* An Azure Tenant account with administrative privileges to create resources and manage peering, including the following information:
+ * Azure tenant ID
+ * Azure VNET subscription ID
+ * Azure VNET resource group name
+ * Azure VNET name
+
+## Configure VNET Peering
+
+### Configure Azure
+
+Grant access to your Azure AD Tenant:
+
+1. Navigate to the following URL making sure to replace `` with your own Azure tenant ID and approve the `kong-cgw-azure-vnet-peering-app`.
+
+ `https://login.microsoftonline.com//adminconsent?client_id=207b296f-cf25-4d23-9eba-9a2c41dc62ca`
+
+1. Input the following command into the Azure CLI making sure to replace `` with your Azure VNET subscription ID:
+
+ ```bash
+ az role definition create --output none --role-definition '{
+ "Name": "Kong Cloud Gateway Peering Creator - Kong",
+ "Description": "Perform cross-tenant network peering.",
+ "Actions": [
+ "Microsoft.Network/virtualNetworks/read",
+ "Microsoft.Network/virtualNetworks/virtualNetworkPeerings/read",
+ "Microsoft.Network/virtualNetworks/virtualNetworkPeerings/write",
+ "Microsoft.Network/virtualNetworks/virtualNetworkPeerings/delete",
+ "Microsoft.Network/virtualNetworks/peer/action"
+ ],
+ "AssignableScopes": [
+ "/subscriptions/",
+ ]
+ }'
+ ```
+1. Run the following command with your Azure VNET Subscription ID ``, Azure VNET resource group name ``, and Azure VNET Name `` specified to assign the role to the service principal:
+
+ ```bash
+ az role assignment create \
+ --role "Kong Cloud Gateway Peering Creator" \
+ --assignee "$(az ad sp list --filter "appId eq '207b296f-cf25-4d23-9eba-9a2c41dc62ca'" \
+ --output tsv --query '[0].id')" \
+ --scope "/subscriptions//resourceGroups//providers/Microsoft.Network/virtualNetworks/"
+ ```
+
+
+### Configure {{site.konnect_short_name}}
+
+1. From {{site.konnect_short_name}}, navigate to the **Gateway Manager**.
+1. On the **Networks** tab, select the desired network, then select **Configure VNET Peering**.
+1. In the form that appears, enter the following values:
+ * Azure Tenant ID
+ * Azure VNET Subscription ID
+ * Azure VNET Resource Group Name
+ * Azure VNET Name
+1. For DNS configuration, add the IP addresses of DNS servers that will resolve to your private domains, along with any domains you want associated with your DNS. {{site.konnect_short_name}} supports the following mappings:
+
+ * 1-1 Mapping
+ * Each domain is mapped to a unique IP address.
+ * For example: `example.com` -> `192.168.1.1`
+ * N-1 Mapping
+ * Multiple domains are mapped to a single IP address.
+ * For example: `example.com`, `example2.com` -> `192.168.1.1`
+ * M-N Mapping
+ * Multiple domains are mapped to multiple IP addresses, not necessarily in a one-to-one relationship.
+ * For example: `example.com`, `example2.com` -> `192.168.1.1`, `192.168.1.2`
+ * For example: `example3.com` -> `192.168.1.1`
+
+ {:.note}
+ > **Note**: You will need to create an inbound endpoint for private DNS zone within your tenant. The IP of the inbound endpoint should the IP of the DNS server.
+
+1. Click **Next** and move on to configuring Azure in the next section.
+
+
+After VNET Peering is successfully established you will be able to configure a [route](/konnect/api/control-plane-configuration/latest/#/Routes/list-route) for the upstream service and forward all traffic through the virtual network to the data plane. This guarantees that traffic from the {{site.konnect_short_name}} data plane reaches the services and that response packets are routed back properly.
+