Application Insights on private site "This url is not supported."

Question

I'm trying to configure availability test for a private website that is exposed with HTTPS on another port different than 443. https://<some_url>:50002/Launcher/production/#login. I've tried with Classic Test and Standard Test.
The application is behind an Application Gateway, and the resolved IP is the private IP of the AppGateway.
Public DNS does resolve to the private IP but I get the message "This url is not supported." I have not found anything on the docs related to this. Am I missing something? Thanks for your help.

Answer 1

Hello @Christian Fabián !

Thanks for the message !

I think it is very clear for Private Testing , as per documentation , and i have read it over and over

https://learn.microsoft.com/en-us/azure/azure-monitor/app/availability-private-test

You scenario is not the first one , it states clearly you need to be Public Visible

Your scenario is the disconnected One

Thats why you get the error

So kindly change your approach and you will get results :

To use this method, your test server must have outgoing access to the Application Insights ingestion endpoint. This is a much lower security risk than the alternative of permitting incoming requests. The results will appear in the availability web tests tab with a simplified experience from what is available for tests created via the Azure portal. Custom availability tests will also appear as availability results in Analytics, Search, and Metrics.

1. Connect your Application Insights resource and disconnected environment by using Azure Private Link.
2. Write custom code to periodically test your internal server or endpoints. You can run the code by using Azure Functions or a background process on a test server behind your firewall. Your test process can send its results to Application Insights by using the TrackAvailability() API in the core SDK package.

---

I hope this helps!

Kindly mark the answer as Accepted and Upvote in case it helped!

Regards

Answer 2

Hello @Christian Fabián !

For Standard and Classic Tests as we can read :

https://learn.microsoft.com/en-us/azure/azure-monitor/app/availability-standard-tests

URL	The URL can be any webpage you want to test, but it must be visible from the public internet. The URL can include a query string. So, for example, you can exercise your database a little. If the URL resolves to a redirect, we follow it up to 10 redirects.

You mayfind this ti fit your case ;

If you want to use availability tests on internal servers that run behind a firewall, you have two possible solutions: public availability test enablement and disconnected/no ingress scenarios.

https://learn.microsoft.com/en-us/azure/azure-monitor/app/availability-private-test

---

I hope this helps!

Kindly mark the answer as Accepted and Upvote in case it helped!

Regards

Answer 3

Hello @Christian Fabián !

Thank you for your post

I think there is a misundestanding here

You have to enter on your Public DNS , the Public IP that exposes your service!

From : https://learn.microsoft.com/en-us/azure/cloud-services/cloud-services-custom-domain-name-portal#add-an-a-record-for-your-custom-domain

To create an A record, you must first find the virtual IP address of your cloud service. Then add a new entry in the DNS table for your custom domain by using the tools provided by your registrar. Each registrar has a similar but slightly different method of specifying an A record, but the concepts are the same.

Thats why you get that error !

Find the Public IP that your service is accessed from outside otherwise it is futile to add a Private record on Public DNS !

---

I hope this helps!

Kindly mark the answer as Accepted and Upvote in case it helped!

Regards