Windows Integration Errors

Fix PowerShell TLS and SSL Errors in Matter Center Deployment

Rana GarciaRana Garcia Nov 20, 2026 869 views

Question details

Resolve an SSL or TLS connection error when running the Matter Center deployment script on an Azure virtual machine.

Fix PowerShell TLS and SSL Errors During Matter Center Deployment
Product
Matter Center deployment script, Windows PowerShell, and SharePoint
Device & OS
Azure virtual machine; operating system not provided
Scenario
The user is deploying Matter Center with deploy.ps1 and connecting to a SharePoint HTTPS site.
Observed behavior
The script reports an SSL or TLS connection error even though the SharePoint site has a valid certificate and TLS 1.2 was enabled.
Before you start

Identify the exact HTTPS URL and error message reported by deploy.ps1, since the failing connection may not be to the SharePoint site. Check which PowerShell edition and version are running with $PSVersionTable.

Solution 1Recommended

Check certificate trust and network access from the Azure VM

Use these checks when the endpoint has a valid certificate but the deployment script cannot establish a secure connection.

1
Inspect the certificate chain

On the Azure VM, open the failing HTTPS URL in a browser and inspect its certificate. Verify that the certificate name matches the URL and that the chain includes trusted root and intermediate certificates.

2
Check the VM certificate stores

Open certlm.msc and inspect Trusted Root Certification Authorities and Intermediate Certification Authorities. If a required certificate is missing, obtain it from a trusted administrator or certificate authority before importing it into the appropriate store.

3
Test DNS and connectivity

In PowerShell, run Resolve-DnsName <hostname> and Test-NetConnection <hostname> -Port 443 using the failing URL's hostname. Investigate incorrect DNS results or blocked outbound HTTPS traffic.

4
Review proxy and time settings

Run netsh winhttp show proxy to inspect the WinHTTP proxy configuration, and check any proxy settings used by the deployment environment. Run Get-Date and correct the VM's date, time, or time zone if necessary.

Check certificate trust and network access from the Azure VM
Check the actual endpoint: A deployment script may connect to more than one service. A valid SharePoint certificate does not confirm that every endpoint used by the script is trusted.
Free Microsoft Office alternative

Work with Office files in WPS Office

WPS Office is a free, lightweight alternative for working with Office documents in a familiar interface. Its Microsoft Office format support can help make moving everyday files straightforward. It does not repair Matter Center deployment or PowerShell TLS errors.

Open and edit documents, spreadsheets, and presentations in a familiar interface.Compatible with common Microsoft Office formats, including DOCX, XLSX, and PPTX.Review Office-format deployment documentation without relying on Microsoft Office.Free and lightweight for everyday productivity.
microsoft office alternative - wps office

Frequently Asked Questions

Why can a valid SharePoint certificate still produce a TLS error?

The VM may not trust the complete certificate chain, the hostname may not match, or the script may be connecting to a different endpoint. Inspect the certificate for the exact URL named in the error.

How can I check whether the VM can reach the HTTPS endpoint?

Run Resolve-DnsName <hostname> to check DNS, then Test-NetConnection <hostname> -Port 443 to test TCP connectivity. A successful TCP test alone does not prove that the TLS handshake will succeed.

Does setting SecurityProtocol to TLS 1.2 change Windows globally?

No. In Windows PowerShell, the ServicePointManager setting applies to supported .NET requests in the current process. Set it again in a new session if the script needs it.

Where should I get help if the deployment still fails?

Contact Microsoft or SharePoint support with the exact error, failing endpoint, PowerShell version, and sanitized logs. Environment-specific proxy, certificate, or TLS policies may require further investigation.