Skip to content

Commit db1be9d

Browse files
committed
update screenshots
1 parent 3bded2a commit db1be9d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/iot-central/core/howto-create-private-endpoint.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To create a private endpoint on an existing IoT Central application:
3737

3838
1. Select the **Private endpoint connections** tab, and then select **+ Private endpoint**.
3939

40-
1. On the **Basics** tab, enter add a name and select a region for your private endpoint. Then select **Next: Resource**.
40+
1. On the **Basics** tab, enter a name and select a region for your private endpoint. Then select **Next: Resource**.
4141

4242
1. The **Resource** tab is auto-populated for you. Select **Next: Virtual Network**.
4343

@@ -129,14 +129,14 @@ In some situations, you may not be able to integrate with the private DNS zone o
129129
130130
1. In the Azure portal, navigate to your private endpoint, and select **DNS configuration**. On this page, you can find the required information for the IP address mapping to the DNS name.
131131
132-
:::image type="content" source="media/howto-create-private-endpoint/private-dns-configuration.png" alt-text="Screenshot from the Azure portal that show the private D N S configuration.":::
132+
:::image type="content" source="media/howto-create-private-endpoint/private-dns-configuration.png" alt-text="Screenshot from the Azure portal that shows the private D N S configuration.":::
133133
134134
> [!WARNING]
135135
> This information lets you populate your custom DNS server with the necessary records. If at all possible, you should integrate with the private DNS Zones of the virtual network and not configure your own custom DNS server. Private endpoints for IoT Central applications differ from other Azure PaaS services. In some situations, such as IoT Central autoscaling, IoT Central scales out the number of IoT Hubs accessible through the private endpoint. If you choose to populate your own custom DNS server, it's your responsibility to update the DNS records whenever IoT Central autoscales, and later remove records when the number of IoT hubs scales in.
136136
137137
## Restrict public access
138138
139-
To restrict public access for your devices to IoT Central, turn off access from public endpoints. After you turn off public access, devices can't connect to IoT Central from public networks and must use a private endpoint:
139+
To restrict public access for your devices to IoT Central, turn off access from public endpoints. After you turn off public access, devices can't connect to IoT Central from public networks, and must use a private endpoint:
140140
141141
1. In the Azure portal, navigate to your IoT Central application and then select **Networking**.
142142

0 commit comments

Comments
 (0)