Hi,
Some more context could help (PowerShell 7.x maybe?) but for now it seems related to https://techcommunity.microsoft.com/t5/sql-server-blog/released-general-availability-of-microsoft-data-sqlclient-4-0/ba-p/2983346 ie :
- a short term fix is to use Encrypt=false in the connection string as you are not using yet a trusted certificate
- the long term fix is to start using trusted certificates on SQL Server so that the communication is encrypted (much like at some point we have gone from http to https)
If part of a company see rather with SQL Server/IT admins. If an individual you could consider to give it a try with a free certificate provider such as https://www.naturalborncoder.com/sql/2019/08/30/how-to-configure-sql-server-to-use-lets-encrypt-certificates/