How to set up SQL Server 2017 as a service
Revoking that one view was never a good way to protect your instance.  The most straightforward way to do this is to make the user the owner of their database, but have no other rights on the instance, even to list the other databases.  EG:

use master 
create database a 
create login a_user with password='P@sssword*****'
alter authorization on database::a to a_user

revoke view any database to public


Now a_user will be able to connect (with SSMS or otherwise) and will see only one database.