sme review

Author: katarzyna-koltun-mx

content/en/docs/deployment/mx-azure/mx-azure-getting-started.md

@@ -57,4 +57,4 @@ To adopt Mendix on Azure, you need to have the following:
 
 Mendix on Azure is available for purchase from the the [Azure Marketplace](https://azuremarketplace.microsoft.com/). Connecting to Azure services may also include additional cost. For more information, refer to Azure documentation.
 
-For production environments, you also need a license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/).
+For production environments, you also need a runtime license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/). The Operator license is applied automatically when using Mendix on Azure.

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

@@ -104,12 +104,62 @@ To enable virtual network peering for your Mendix on Azure app, perform the foll
     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.
 
+    Your Mendix app can now connect to a back-end server in the other virtual network.
+
 #### 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.
 
 {{< figure src="/attachments/deployment/mx-azure/private-endpoints.png" class="no-border" >}}
 
+To enable private endpoints for your Mendix on Azure app, perform the following steps:
+
+1. In the Microsoft Azure portal, add a new [private link](https://learn.microsoft.com/en-us/azure/private-link/private-link-overview) for the Mendix AKS load balancer.
+
+    {{< figure src="/attachments/deployment/mx-azure/private-link.png" class="no-border" >}}
+
+2. Create a private endpoint in your custom resource group.
+3. In the **Resource** tab, specify the following settings:
+
+    * **Resource type** - **privateLinkServices**
+    * **Resource** - the private link that you created in step 1 above
+
+4. In the **Virtual Network** tab, specify the following settings:
+
+    * **Virtual network** - the virtual network where the user's machine is located
+
+5. Configure other settings as needed.
+6. Create an [Azure Private DNS zone](https://learn.microsoft.com/en-us/azure/dns/private-dns-privatednszone).
+7. 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" >}}
+
+8. Create a [DNS record](https://learn.microsoft.com/en-us/azure/dns/dns-operations-recordsets-portal) for the Mendix application.
+9. In the **Name** field, enter the name of our Mendix app, for example, *myapp*.
+10. In the **IP** field, enter the IP address of the private endpoint.
+11. Create a [virtual network link](https://learn.microsoft.com/en-us/azure/dns/private-dns-virtual-network-links) and link it with your Mendix managed virtual network.
+
+    Users in the other virtual network can now connect to your Mendix app.
+
+12. 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. Create a load balancer that points to the back-end machine.
+    2. Add a new [private link](https://learn.microsoft.com/en-us/azure/private-link/private-link-overview) for the back-end load balancer.
+
+        Make sure to select the back-end load balancer in the **Load balancer** field of the **Outbound settings** tab.
+
+    3. Configure other settings as needed.
+    4. Create a private endpoint in your Mendix managed resource group.
+    5. In the **Resource** tab, specify the following settings:
+
+    * **Resource type** - **privateLinkServices**
+    * **Resource** - the private link that you created in step 12-b above.
+
+    6. In the **Virtual Network** tab, specify the following settings:
+
+    * **Virtual network** - the virtual network managed by Mendix
+
+
 ## Deploying an App to an Azure Cluster
 
 After creating your cluster in Microsoft Azure, you can deploy now deploy your applications to the cluster. The deployment process is the same as with Mendix for Private Cloud. For more information, see [Deploying a Mendix App to a Private Cloud Cluster](/developerportal/deploy/private-cloud-deploy/).