user10998602
user10998602

Reputation: 127

Accessing Azure Log Analytics from Portal via AMPLS

I'm trying to restrict access to our Azure Monitor resources (Log Analytics Workspace and Application Insights) with an Azure Monitor Private Link Scope that has both "Accept data ingestion from public networks not connected through a Private Link Scope" and "Accept queries from public networks not connected through a Private Link Scope" set to "No", while still being able to access them the Azure Portal while connected to an Azure VPN peered with the main virtual network.

In the main resource group, I have the following:

In the VPN resource group, I have the following:

On my own computer, I have the DNS records for the Private Endpoints in the Windows hosts file.

What I've tried:

What happened:

What I want to be able to do:

Upvotes: 1

Views: 251

Answers (2)

hip9k
hip9k

Reputation: 1

If you are using Azure custom DNS servers (eg VMs configured in your VNET DNS settings) or Azure DNS resolver you can also configure conditional forwarding for these FQDNs from local/on-prem to your Azure custom DNS servers and your Azure custom DNS servers should forward them to Azure provided DNS (168.63.129.16). Also your private DNS zones in Azure should be linked to VNET where DNS servers reside and all other VNETS (if any) should be peered for proper DNS resolution.

I've encountered this issue too, shame that MS docs doesn't provide this information on AMPLS configuration guide (api.loganalytics.io and api.applicationinsights.azure.com are not mentioned at all).

Upvotes: 0

user10998602
user10998602

Reputation: 127

I don't know if there's a better solution, but manually adding hosts file entries for api.loganalytics.io and api.applicationinsights.azure.com pointing to the same private IP as api.monitor.azure.com allowed me to access Log Analytics and Application Insights from the Azure Portal over the VPN.

I also removed the NSG and "Private endpoint network policy" for the subnet.

Upvotes: 0

Related Questions