Since I don't know Go, and I don't think you generally can expect knowledge about Go and this specific driver here, I post an Answer with some advices for troubleshooting.
- First make sure that you can retrieve an unencrypted string column, using the same code. (To make sure that you are not doing some basic silly mistake.)
- Then run a query against an AE column for which the encryption is in your local certificate store. You can easily achieve this by using the AE wizard in SSMS. If this works, you know that the issue is the access to Azure Key Value. If it does not work, we can rule out AKV from the suspects.
- Also run the program with the local key from a different machine which does not have access to the encryption key, so that you understand what the behaviour is when the encryption key is not available.
These steps may not lead to the answer, but you will be in better position to open an Issue on the Github site, if you first conduct your own troubleshooting.
It occurs to me a little funny that you specify in the code all the details about AKV. I was under the impression that such information was stored in the database together with the key. But I have never used AE with Azure Key Vault. And certainly not from Go.