Hello KN,
Thank you for posting your question in the Microsoft Q&A forum.
When enabling TLS inspection in Azure Firewall Premium, the certificate auto-generation process should create both a managed identity and Key Vault resource, but the absence of the certificate in Key Vault suggests a deployment hiccup. First, verify the Azure Firewall’s managed identity has Key Vault Certificate Contributor and Secrets Officer roles, as portal-based permissions may not propagate correctly.
Check Activity Logs in both the Firewall and Key Vault resources for errors during certificate creation. Common issues include regional mismatches (ensure Key Vault and Firewall reside in the same region) or DNS resolution failures. If logs show success but the certificate remains missing, manually trigger a Firewall policy sync or recreate the TLS inspection configuration.
As a fallback, manually upload a CA certificate to Key Vault and link it to the Firewall policy. Ensure the certificate meets Azure’s requirements (root CA, RSA 2048+, and proper key usage flags). If problems persist, engage Microsoft Support with correlation IDs from the activity logs for deeper diagnostics.
If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated.