This is due to that Microsoft have changed the defaults for encryption in their drivers, and the more applications that are using the new drivers, the more you will see this error.
What it is about is that preferably the communication between SQL Server and the client should be encrypted, so that no one can tap the communication line and steal data.
One way to encrypt the communication is that SQL Server itself creates a certificate which the client downloads as part of the login process. This is not that secure, because a man-in-the-middle could play SQL Server and send you the certificate. And steal the data.
A better option is to install a certificate from a trusted certificate authority.
The default in the past was to not require any trusted certificate, and this is what has been changed.
The best way to address this is to ask your DBA to install a trusted certificate on the SQL Server instance you are using.
The other option would be to request the communication not to be encrypted. This is an item on the connection string, but I can't seem to find any such option exposed in Excel.