This should be fixed in the next hour. Sorry for the any inconvenience and thank you for your patience
Azure AD Application Proxy SSL Certificate for custom domain
I'm setting up what is now our 3rd Azure AD App Proxy, and having an issue with the SSL certificate that I didn't have the first two times. It was already set to use the same certificate, being the same custom domain... but instead has been presenting clients with the *.msappproxy.net certificate, instead of the uploaded one.
So, I've uploaded it again to the app proxy, I've switched to a different cert and back... and still nothing.
But now where I'm at, I have some clients receiving the cert I switched to (which was a cert issued from an internal CA), and some receiving the *.msappproxy.net cert. But none are receiving the publicly issued wildcard cert, that is still working fine on the first 2 app proxies I made.
So... did Microsoft change something on their back end? Is there a bug going on right now with SSL certs and Azure AD App Proxies? Does anyone know anything else to try?
Microsoft Security Microsoft Entra Microsoft Entra ID
2 answers
Sort by: Most helpful
-
-
Řádek Vít 0 Reputation points
2024-01-23T17:01:07.9766667+00:00 Years later, the system still has problems.
I've discovered the process for fixing the configuration.
I have configured Enterprise application for specific URL including proper certificate.
Page access started operating as intended.I have removed specific configuration (changed to another URL).
The page is still functional; perhaps it is utilizing a wildcard configuration.