Skip to content

Commit 8dfbd55

Browse files
Update read-replica-database-access.md
1 parent 2aac9a3 commit 8dfbd55

1 file changed

Lines changed: 5 additions & 3 deletions

File tree

content/en/docs/deployment/mx-azure/read-replica-database-access.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,14 +44,16 @@ By default, the read replica for Postgres database is disabled. To enable it, pe
4444

4545
4. Add the users who should be able to access the replica database by performing the following steps:
4646

47-
1. In Azure portal, Go to Resource group where managed app is created. Under the resource group, go to managed resource group and click on the replica database resource. Go to **Security > Authentication**
48-
2. Add the required users.
47+
1. In the Azure portal, go to the resource group where you created the managed app.
48+
2. Under the resource group, go to the managed resource group and click on the replica database resource.
49+
3. Go to **Security > Authentication**
50+
4. Add the required users.
4951

5052
{{< figure src="/attachments/deployment/mx-azure/adduser.png" class="no-border" >}}
5153

5254
## Enabling Virtual Network Peering
5355

54-
VNet peering to the Mendix on Azure vNet is required to access the database and should be setup if it hasn’t been already. This allows to connect two virtual networks (VNets) so resources can talk to each other using private IPs.
56+
VNet peering to the Mendix on Azure vNet is required to access the database. It enables connections between two virtual networks (VNets) so resources can talk to each other using private IPs. If you have not already configured VNet peering, you should do it now.
5557

5658
The following diagram shows one potential solution to the access issue. Bi-directional [virtual network peering](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-peering-overview) has been configured between the two resource groups.
5759

0 commit comments

Comments
 (0)