Hi @Alen Cappelletti,
It is a bug in the SSMS 20 and 20.1
It is documented in the SSMS 20 release notes: https://learn.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-ver16#known-issues-201
It better to stay with SSMS 19. Many people got burned by the SSMS 20
Check it out here: https://learn.microsoft.com/en-us/answers/questions/1652988/sql-server-2022-certificate-error-when-creating-a