We are unable to persist CA Certificates in our API Management instance

Corey Stewart 0 Reputation points
2025-04-28T21:44:56.0433333+00:00

We have attempted to upload both self-signed and publicly signed certificates under CA Certificates manually via the Azure Portal and programmatically via AZ CLI. The upload appears successful initially; however, the certificates disappear from the APIM instance within minutes after upload without visible error.

This issue is isolated to one particular instance in our Staging subscription. In contrast, our Development APIM instance (in a different subscription) accepts the same certificates without issue, and they persist as expected.

We have verified:

Certificates are properly structured (valid KeyUsage, ExtendedKeyUsage, SANs, and expiration times)

Correct password protection on PFX bundles (where applicable)

Azure Activity Logs show no failure events, only success

No relevant Resource Health warnings

Please advise on possible configuration or service issues preventing CA Certificate persistence. Both instances are using the Developer SKU.

Further details of the APIM instance with this issue:

westus2 region

Multiple APIs (Microsoft.ApiManagement/service/apis)
Backends for container app and on-premise APIs

API Version Sets for version management

Network Security Group + Private DNS Zone for Azure Container Apps integration

NAT Gateway to fix the outbound IP address

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
2,387 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff Moderator
    2025-04-30T04:47:07.5066667+00:00

    Hi Corey Stewart,

    Thanks for the update. Glad to hear that recreating the resources resolved the issue.

    It seems that the issue with CA Certificates disappearing without errors in your API Management instance may have been related to the specific configuration or state of that instance. Since recreating the resources resolved the problem, it suggests that there may have been an underlying issue with the previous configuration.

    For future reference, if similar issues arise, consider checking the following:

    • Ensure all configurations are correct and consistent across instances.
    • Monitor Azure Activity Logs for any hidden errors or warnings.
    • Validate that the Key Vault permissions and access policies are correctly set.

    If the problem reoccurs, further investigation into the specific instance's settings and configurations may be necessary.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.