virtual network

Author: katarzyna-koltun-mx

content/en/docs/deployment/mx-azure/mx-azure-installation.md

@@ -78,6 +78,32 @@ The following diagram shows one potential solution to the access issue. Bi-direc
 
 {{< figure src="/attachments/deployment/mx-azure/virtual-network-peerings.png" class="no-border" >}}
 
+To enable virtual network peering for your Mendix on Azure app, perform the following steps:
+
+1. In the Microsoft Azure portal, add a new bi-directional virtual peering.
+
+    {{< figure src="/attachments/deployment/mx-azure/virtual-network-peerings-add.png" class="no-border" >}}
+
+2. Create an [Azure Private DNS zone](https://learn.microsoft.com/en-us/azure/dns/private-dns-privatednszone).
+3. In the **Instance details** section, in the **Name** field, enter the domain of your Mendix app, for example, *azure.mendixapps.io*.
+
+    {{< figure src="/attachments/deployment/mx-azure/virtual-network-peerings-name.png" class="no-border" >}}
+
+4. Create a [DNS record](https://learn.microsoft.com/en-us/azure/dns/dns-operations-recordsets-portal) for the Mendix application.
+5. In the **Name** field, enter the name of our Mendix app, for example, *myapp*.
+6. In the **IP** field, enter the IP address of the internal load balancer.
+7. Create a [virtual network link](https://learn.microsoft.com/en-us/azure/dns/private-dns-virtual-network-links) and link it with your custom virtual network.
+
+    Users in the other virtual network can now connect to your Mendix app.
+
+8. If you want to enable connections from your Mendix app to a virtual back-end machine in the other network, perform the following additional steps:
+    
+    1. In the Azure portal, create another private DNS zone for the virtual machine, with auto-registration enabled.
+    2. In the **Environment Details** page of your Mendix environment, go to [Model Options](/developerportal/deploy/environments-details/#model-options).
+    3. In the [Constants](/developerportal/deploy/environments-details/#constants) section, find and edit the **RestClient.RestServiceUrl** constant.
+    4. In the **New value** field, enter the URL and port of your back-end machine, and then click **Save and Apply**.
+    5. In the Azure portal, configure the virtual network link to link the private DNS zone with the virtual network of your managed Mendix application.
+
 #### Potential Solution 2: Private Endpoints
 
 Another possible solution can be achieved by using [private endpoints](https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-overview). In the following diagram, a private endpoint has been added to each resource group. The private endpoint connects to a private link in the other resource group, which in turn connects to an internal load balancer.