The requirements are not exactly clear, but this is a general summary of what is available:
- Cell-level encryption. Has been around since SQL 2005. You can encrypt columns inside stored procedures or in clent code that submits SQL statements. Keys are stored in SQL Server, so the DBA can always get to the data.
- Transperant Data Encryption. Available since SQL 2008, and starting with SQL 2019 also in Standard Edition. The entire database is encrypted, but if you are connected you will never notice. The aim is to protect data at test.
- Always Encrypted, introduced in SQL 2016. Encryption occurs client-side, and SQL Server only knows where the keys are stored, but the DBA cannot get to the data. In your case, you would distribute the encryption keys to the users who want to see it.
Overall, there are many wet dreams about encryption being transperant, but in the end, security often means a lot of hassle. And for a good reason.