Share via

Having Certificate issue on Application Gateway

Mahto, Ashok (-a) 0 Reputation points
2026-02-09T18:17:18.5333333+00:00

Having Certificate issue on Application Gateway

RG-ENMAX-EDM-UW1-001-P

ENMAXEDMSB001P

Azure Application Gateway
Azure Application Gateway

An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.

0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Vallepu Venkateswarlu 6,045 Reputation points Microsoft External Staff Moderator
    2026-02-09T18:39:46.4133333+00:00

    Hi @ Mahto, Ashok (-a)

    Welcome to Microsoft Q&A Platform.

    When configuring end-to-end TLS (HTTPS from client to Application Gateway and HTTPS from Application Gateway to backend), Azure Application Gateway requires separate certificates for the frontend and backend.

    Application Gateway (Frontend) Certificate:

    • Must be provided in PFX format
    • Must include the private key

    If the PFX is missing the private key or is invalid, frontend HTTPS listeners will fail.

    Backend Server Certificate:

    • Application Gateway does not automatically trust backend certificates
    • The backend certificate private key remains on the backend server
    • Application Gateway requires the public certificate of the issuing CA (Root or Intermediate)

    Make sure to follow the below steps to configure the certificate.

    • Export the Root CA or Intermediate CA that issued the backend server certificate
    • Upload it to Application Gateway as a Trusted Root Certificate
    • Do not upload a PFX or leaf certificate

    This ensures Application Gateway only communicates with explicitly trusted backend servers.
    For Application Gateway ENMAXEDMSB001P in resource group RG-ENMAX-EDM-UW1-001-P, please validate the following:

    • Verify the backend health status under Application Gateway → Backend Health
    • Ensure the backend certificate chain (Root/Intermediate CA) is uploaded as Trusted Root Certificate (public .cer format, not PFX)
    • Confirm the backend certificate Common Name or SAN matches the backend pool FQDN Validate certificate expiry
    • If using Key Vault, confirm Managed Identity access to the certificate.

    Follow the Create certificates to allow the backend with Azure Application Gateway and Configure end to end TLS by using Application Gateway with PowerShell for more details.

    If still facing an error, please share the error screenshot and other relevant details via private message for further troubleshooting.

    Please210246-screenshot-2021-12-10-121802.pngand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.