Share via

Entra App Proxy setup "Private Network settings - Application operation failed"

Mendez,Agustin 5 Reputation points
2024-05-14T16:50:22.59+00:00

Good day community,
I'm reaching out to you since I would like to understand if there is a limitation with Entra App Proxy (EAP, aka Azure App Proxy) when creating new EAPs with too many '.' (dots) in the internal URL or '-' (minus) in them as well.
eg: https://place-governance-service.instance.environment.domain.com

I've been trying to setup a new EAP for an internal URL like so and this has proven to be impossible since EntraID always gives me the same message "Private Network settings - Application operation failed". Don't know exactly if it's a limitation with its internal URL (this only happens with this kind of URLs and need to setup new Wildcards for them) or there is another configuration that needs to happen in our EntraID Tenant.

Thank you for your time.
Regards,

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,910 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. James Hamil 22,431 Reputation points Microsoft Employee
    2024-05-16T19:31:07.0266667+00:00

    Hi @Mendez,Agustin , there is no known limitation with Entra App Proxy (EAP) when creating new EAPs with too many dots or dashes in the internal URL. However, there are some limitations on the characters that can be used in the internal URL.

    The internal URL should be a fully qualified domain name (FQDN) that uses only letters, numbers, and hyphens. It should not start or end with a hyphen, and it should not contain consecutive hyphens. The maximum length of the internal URL is 255 characters.

    If you are using a valid FQDN for the internal URL and still getting the "Private Network settings - Application operation failed" error, there may be other configuration issues that need to be addressed. Here are some things you can check (I'm sure you've done this, but just in case):

    1. Make sure that the application is configured correctly in the Azure portal. Check that the internal URL and external URL are correct, and that the application is enabled.
    2. Check that the connector is installed and running correctly. You can check the connector status in the Azure portal.
    3. Check that the firewall settings are configured correctly. Make sure that the required ports are open and that the firewall is not blocking traffic to the application.
    4. Check that the DNS settings are configured correctly. Make sure that the DNS records are pointing to the correct IP address and that the DNS cache is up to date.

    If you've confirmed the above and are still having issues please let me know and we can open a ticket for you.

    Please let me know if you have any questions and I can help you further.

    If this answer helps you please mark "Accept Answer" so other users can reference it.

    Thank you,

    James

    0 comments