Sometimes you have use a specific TLS/SSL certificate or thumbprint for outgoing HTTPS connections because of endpoint restrictions. To test these connections you can use PowerShell, but how do you get the required certificate from your certificate store?
In this post you’ll learn how to use a specific TLS certificate or thumbprint for outgoing HTTPS connections because of endpoint restrictions. All with PowerShell of course.
If an endpoint has restricted HTTPS connections based on security certificates or certificate thumbprints, you must be able to pull that certificate from your Windows Certificate Store and use it in your request. This is not a big issue if the certificate is stored in the CurrentUser store, but it gets harder when it’s in LocalComputer.
How to use an SSL certificate from CurrentUser certificate store in PowerShell Invoke-WebRequest

Use certmgr.msc on your command line to open up the CurrentUser certificate store in Managment Console.
If you need to use a personal TLS/SSL certificate you can pull it up using PowerShell:
$certStorePath = "Cert:\CurrentUser\My"
# Must return one result:
$certhash = (
Get-ChildItem -Path $certStorePath | Where-Object {
$_.Subject -like "CN=Part_of_Common_Name*"
}
).Thumbprint
Because Invoke-WebRequest will only look in the CurrentUser certificate store, this will suffice for your HTTPS request. Try:
Invoke-WebRequest -Uri https://example.com -CertificateThumbprint $certThumbPrint
If you need a LocalMachine certificate, then it becomes a (small) bit harder.
Install SSL/TLS certificates in Windows Server using PowerShell
LocalMachine SSL certificate to use in PowerShell Invoke-WebRequest HTTPS requests

Start LocalMachine certificate store management console directly with certlm.msc.
Invoke-WebRequests only looks at the CurrentUser certificate store, you need a second approach for SSL certificates stored in LocalMachine:
Use Get-ChildItem to get the certificate itself, and pass that to Invoke-WebRequest instead of a thumbprint:
$certStorePath = "Cert:\LocalMachine\My"
# Must return one result:
$certificate = Get-ChildItem -Path $certStorePath | Where-Object {
$_.Subject -like "CN=Part_of_Common_Name*"
}
Invoke-WebRequest -Uri https://example.com -Certificate $certificate
Conclusion
In this post you learned how you can use PowerShell to retrieve specific TLS certificates from your certificate store for outgoing HTTPS connections. Sometimes this is required, for example when the remote endpoint is secured using client authentication certificates.
If needed you can substitute Invoke-WebRequest with Invoke-RestMethod for APIs.
Summary
- Learn how to use a specific TLS certificate for outgoing HTTPS connections with PowerShell.
- Access the CurrentUser certificate store using certmgr.msc and use it with Invoke-WebRequest.
- For LocalMachine certificates, use certlm.msc and Get-ChildItem to retrieve the certificate.
- This process is crucial when endpoints require specific security credentials, especially in client authentication situations.
- You can use Invoke-RestMethod as an alternative to Invoke-WebRequest for API interactions.






