Configure the access policies for your Key Vault

Question

Ref: [Configure the access policies for your Key Vault][1] The save button is disable after I did complete the 6 steps. 1. On the Key Vault properties pages, select Access policies. 2. Select + Add Access Policy. 3. Click on the Certificate Permissions dropdown and check the boxes for Get and List under Certificate Management Operations. 4. Click on the Secret Permissions dropdown and check the boxes for Get and List under Secret Management Operations. 5. Click on Select Principal, search for the user you are granting access to, and click Select. 6. Click Add. 7. Make sure to save your changes by clicking Save. (Failed) Due to that failure I'm not able to Select a Certificate from Azure key Vault form VS2022 - after I pressed View Metadata. ![212633-image.png][2] ![212711-image.png][3] [1]: https://learn.microsoft.com/en-us/windows/msix/desktop/sign-with-akv-cert#configure-the-access-policies-for-your-key-vault [2]: /api/attachments/212633-image.png?platform=QnA [3]: /api/attachments/212711-image.png?platform=QnA

Answer 1

Hello anonymous user

Thanks for posting your query

Are you trying to add yourself to the Access Policies?

For that you will need appropriate rights on Key Vault

Can you let me know what access do you currently have on Key Vault

Else you can try requesting the Admin to add an Access Policy for you, as the steps you mentioned seems right way to add an access policy

Answer 2

There was already one Access Policy but assign to this strange email ![212630-image.png][1] Did delete this one and recreate a new one. This time, I was able to click on the save button. But the email still the same. I was not able to view Metadata in VS2022 due to that email which is different of my login email ("Micropsoft Personal Account") from Azure. Yesterday did create another Azure account with a professional Microsoft account this time. I was able to view the key vault created in this account with VS2022. ![212761-image.png][2] Do you know how can I fix the problem with the email ![212630-image.png][3] [1]: /api/attachments/212630-image.png?platform=QnA [2]: /api/attachments/212761-image.png?platform=QnA [3]: /api/attachments/212630-image.png?platform=QnA