Hi @Paul Green
I understand that you are experiencing issues with their Application Gateway when trying to use a certificate from Azure Key Vault. when they import the .pfx file directly into the Gateway, it works fine. However, when they upload the same file to the Vault, it doesn't work and there are no error message found.
After checking with internal networking team, this is an expected behavior because once the Application Gateway is configured to use Key Vault certificates, it retrieves the certificate from Key Vault and installs it locally for TLS termination. The instances poll Key Vault every four hours to check for a renewed version of the certificate. If an updated certificate is found, the TLS/SSL certificate associated with the HTTPS listener is automatically rotated. This ensures that the Application Gateway always uses the most up-to-date certificate for secure communication.
I understand Immediate polling after a change to the gateway would provide a more transparent and reassuring experience for users, rather than waiting for up to four hours. It can be difficult to wait for the next polling interval to confirm that the changes have been applied successfully. Since this is a product limitation, I suggest you to shar your feedback on this in our feedback forum which is closely monitored by our Product team.
Reference document TLS termination with Key Vault Supported certificates
Hope this helps. Do let us know if you any further queries by responding in the comments section.