Skip to content

Commit 27a7df3

Browse files
authored
Merge pull request #93988 from ThomasWeiss/release-ignite-cosmosdb
Formatting changes in Cosmos DB / PE tutorial
2 parents 4383c88 + abb2ea8 commit 27a7df3

File tree

1 file changed

+9
-12
lines changed

1 file changed

+9
-12
lines changed

articles/private-link/create-private-endpoint-cosmosdb-portal.md

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,17 @@ ms.author: sngun
1212

1313
Azure Private Endpoint is the fundamental building block for Private Link in Azure. It enables Azure resources, like virtual machines (VMs), to communicate privately with Private Link resources.
1414

15-
In this article, you will learn how to create a VM on an Azure virtual network, an Azure Cosmos account with a Private Endpoint using Azure portal. Then, you can securely access the Azure Cosmos account from the VM.
15+
In this article, you will learn how to create a VM on an Azure virtual network and an Azure Cosmos account with a Private Endpoint using the Azure portal. Then, you can securely access the Azure Cosmos account from the VM.
1616

1717
## Sign in to Azure
1818

1919
Sign in to the [Azure portal.](https://portal.azure.com)
2020

2121
## Create a VM
2222

23-
In this section, you will create virtual network and the subnet to host the VM that is used to access your Private Link Resource (an Azure Cosmos account in this example).
24-
2523
### Create the virtual network
2624

27-
In this section, you will create virtual network and the subnet to host the VM that is used to access your Private Link resource.
25+
In this section, you will create a virtual network and the subnet to host the VM that is used to access your Private Link resource (an Azure Cosmos account in this example).
2826

2927
1. On the upper-left side of the screen, select **Create a resource** > **Networking** > **Virtual network**.
3028

@@ -43,7 +41,7 @@ In this section, you will create virtual network and the subnet to host the VM t
4341

4442
1. Leave the rest as default and select **Create**.
4543

46-
### Create virtual machine
44+
### Create the virtual machine
4745

4846
1. On the upper-left side of the screen in the Azure portal, select **Create a resource** > **Compute** > **Virtual machine**.
4947

@@ -96,7 +94,7 @@ Create an [Azure Cosmos SQL API account](../cosmos-db/create-cosmosdb-resources-
9694

9795
## Create a Private Endpoint for your Azure Cosmos account
9896

99-
Create a Private Link for your Azure Cosmos account as described in the [Create a Private Link using the Azure portal](../cosmos-db/how-to-configure-private-endpoints.md#create-a-private-link-using-the-azure-portal) section of the linked article.
97+
Create a Private Link for your Azure Cosmos account as described in the [Create a Private Link using the Azure portal](../cosmos-db/how-to-configure-private-endpoints.md#create-a-private-link-using-the-azure-portal) section of the linked article.
10098

10199
## Connect to a VM from the internet
102100

@@ -108,7 +106,7 @@ Connect to the VM *myVm* from the internet as follows:
108106

109107
1. Select **Download RDP File**. Azure creates a Remote Desktop Protocol (*.rdp*) file and downloads it to your computer.
110108

111-
1. Open the downloaded.rdp* file.
109+
1. Open the downloaded *.rdp* file.
112110

113111
1. If prompted, select **Connect**.
114112

@@ -128,11 +126,11 @@ Connect to the VM *myVm* from the internet as follows:
128126
In this section, you will connect privately to the Azure Cosmos account using the Private Endpoint.
129127

130128
> [!IMPORTANT]
131-
> The DNS configuration for the Azure Cosmos account needs a manual modification on the hosts file to include the FQDN of the specific account. In production scenarios you will configure the DNS server to use the private IP addresses. However for the demo purpose, you can use administrator permissions on the VM and modify the `c:\Windows\System32\Drivers\etc\hosts` file or `/etc/hosts` file on Linux to include the IP address and DNS mapping.
129+
> The DNS configuration for the Azure Cosmos account needs a manual modification on the hosts file to include the FQDN of the specific account. In production scenarios you will configure the DNS server to use the private IP addresses. However for the demo purpose, you can use administrator permissions on the VM and modify the `c:\Windows\System32\Drivers\etc\hosts` file (on Windows) or `/etc/hosts` file (on Linux) to include the IP address and DNS mapping.
132130
133131
1. To include the IP address and DNS mapping, sign into your Virtual machine *myVM*, open the `c:\Windows\System32\Drivers\etc\hosts` file and include the DNS information from previous step in the following format:
134132

135-
[Private IP Address] myaccount.blob.core.windows.net
133+
[Private IP Address] [Account endpoint].documents.azure.com
136134

137135
**Example:**
138136

@@ -173,9 +171,8 @@ When you're done using the Private Endpoint, Azure Cosmos account and the VM, de
173171

174172
## Next steps
175173

176-
In this article, you created a VM on a virtual network and Azure Cosmos account and a Private Endpoint. You connected to one VM from the internet and securely communicated to the Azure Cosmos account using Private Link.
174+
In this article, you created a VM on a virtual network, an Azure Cosmos account and a Private Endpoint. You connected to the VM from the internet and securely communicated to the Azure Cosmos account using Private Link.
177175

178176
* To learn more about Private Endpoint, see [What is Azure Private Endpoint?](private-endpoint-overview.md).
179177

180-
* To learn more about limitation of Private Endpoint when using with Azure Cosmos DB, see [Azure Private Link with Azure Cosmos DB](../cosmos-db/how-to-configure-private-endpoints.md) article.
181-
178+
* To learn more about limitation of Private Endpoint when using with Azure Cosmos DB, see [Azure Private Link with Azure Cosmos DB](../cosmos-db/how-to-configure-private-endpoints.md) article.

0 commit comments

Comments
 (0)