On the management page, use the toggle to enable that certificate version.ĭescription: The associated certificate has been deleted from Key Vault.Select the required certificate name, and then select the disabled version.Resolution: Re-enable the certificate version that is currently in use for Application Gateway. Error code: SecretDisabledĭescription: The associated certificate has been disabled in Key Vault. You can accomplish it by using ARM template, CLI, or PowerShell.

Portal support for adding a new key vault-based certificate is currently not available when using Azure role-based access control. Members: select the user-assigned managed identity that you've associated with your application gateway.įor more information, see Azure role-based access control in Key Vault. Add role assignment for your managed identity by choosing the followingĬ.Navigate to Access Control (IAM) blade to configure permissions.For Permission model, select Azure role-based access control.Under Secret Management Operations, select the Get permission.įor more information, see Assign a Key Vault access policy by using the Azure portal.For Permission model, select Vault access policy.Go to the linked key vault in the Azure portal.You may do so in any of the following ways: Resolution: Configure the access policies of your key vault to grant the user-assigned managed identity permission on secrets. Error code: UserAssignedIdentityDoesNotHaveGetPermissionOnKeyVaultĭescription: The associated user-assigned managed identity doesn't have the required permission. If the diagnostic continues to show the error after you have fixed the configuration, you might have to wait for the logs to be refreshed. Azure Application Gateway generates logs for key vault diagnostics every four hours.

Keyvault validator