Skip to content

Adding more clarity around resource-specific DNS entries #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion articles/azure-monitor/logs/private-link-configure.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,8 @@ This article reviews how configuration is done through the Azure portal. It prov

1. From the menu for your AMPLS, select **Azure Monitor Resources** and then **Add**.

1. Select the component and select **Apply** to add it to your scope. Only Azure Monitor resources including Log Analytics workspaces, Application Insights components, and data collection endpoints (DCEs) are available.
1. Select the component and select **Apply** to add it to your scope. Only Azure Monitor resources including Log Analytics workspaces, Application Insights components, and data collection endpoints (DCEs) are available. <br>
Connecting the Azure Monitor resources to the AMPLS is vital, as this process automatically creates the specific DNS entries required for each resource.

:::image type="content" source="media/private-link-security/ampls-select-2.png" lightbox="media/private-link-security/ampls-select-2.png" alt-text="Screenshot that shows selecting a scope.":::

Expand Down