This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 64%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
Hi,
I have been using the following to upload policies in my pipeline: https://learn.microsoft.com/en-us/azure/active-directory-b2c/deploy-custom-policies-devops
A few weeks ago this all stopped working, I traced it to the call for Invoke-RestMethod failing with the following error:
System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
I can see for https://graph.microsoft.com/ the certificate was updated around the time I started to see issues.
Anyone else with this issue or know how to get it working again.
Thanks
I tried this on my end and works. Can you try one more time?
I tried again but still failed, has been since around the 11th.
The only fix to work is some code to ignore validating the certificate.
Has the CA change for this certificate and its not known in our DevOps.
I'm reaching within the product team and will come back to you.
The issue is most likely an Azure-wide issuer change that is described here: https://learn.microsoft.com/en-us/azure/security/fundamentals/tls-certificate-changes. Ensuring the latest issuer / root certificates are on the VM running the tasks in Azure DevOps is the correct way to mitigate this issue -- ignoring TLS failures is of course extremely dangerous.