Rewinding back to before adding the connection string to the vault, did that work if you add the hub connection string direct in local.settings.json?
Try to add like this first and hit F5 to make sure you can first make work like this and be sure the value you will add to the vault is correct
Once you are sure it works without the vault:
1. make sure you are logged in in Visual Studio with the same login you use to access azure (will use different account for test/prod in the cloud)
2. go to the vault , create the secret and add the connection string to the value
3. in the left menu in the vault, click access policies
4. select a template. we are only reading secrets:
5.We are just reading, so get and list should be enough
6. step 2 we add the same user we have in Visual studio, I login in VS as myself, so I grant the permission to myself. Different story when you deploy to test or prod in the cloud. there you can use a proper service account
7.skipp all to way to the last step and create. You should now have a policy that will allow you to use the vault reference
make sure you are using the correct sintax for vault reference: https://learn.microsoft.com/en-us/azure/app-service/app-service-key-vault-references?tabs=azure-cli#reference-syntax
This worked for me:
Case that information helps, don't forget to vote or mark as Answer to help the community. Cheers!