App Service Certificate (Azure issued from GoDaddy) will not import into Azure Key Vault

Bryan Farrell 5 Reputation points
2025-04-30T16:22:09.1333333+00:00

I went through the process in Azure Portal to purchase an App Service Certificate (Azure issued from GoDaddy). This is a wildcard certificate and I've been charged the $299 USD fee for the 1-year cert so I need to get my issue resolved in Azure Portal of via CLI if possible. I will describe my issue below:

All of the following steps were done in the same subscription.

  • Created a Resource Group in East US region, 'companyname-eus-vnet-global-rg'
    • Created a Virtual Network in East US region, in the Resource Group and named it 'companyname-eus-vnet-global' and assigned 'default' subnet address space: '10.1.2.0/24'
    • Created a Private DNS zone named 'privatelink.vaultcore.azure.net'
      • Location: Global
      • Recordsets: 2
        • Recordset 1
          • Name: @
          • Type: SOA
          • TTL: 3600
          • Value: Email: azureprivatedns-host.microsoft.com Host: azureprivatedns.net Refresh: 3600 Retry: 300 Expire: 2419200 Minimum TTL: 10 Serial number: 1
          • Auto registered: false
        • Recordset 2
          • Name: companyname-eus-kv-global
          • Type: A
          • TTL: 10
          • Value: 10.1.2.4
          • Auto registered: false
      • Virtual Network Links: 1
        • Link Name: 4gjadbqlc5kx7
        • Link Status: Completed
        • Virtual Network: companyname-eus-vnet-global
        • Auto-Registration: Disabled
        • Fallback to Internet: Disabled
      • Virtual Network Links With Registration: 0
  • Created a Resource Group in East US region, 'companyname-eus-kv-global-rg'
    • Created a Key Vault in East US region in the Resource Group and named it 'companyname-eus-kv-global'.
      • I selected Premium, with Soft-delete and Purge Protection Enabled.
      • Originally it was created with permission model Azure RBAC but during trouble shooting I changed it to Key Vault access policy as was suggested by Copilot as well as in articles.
      • Originally all three resource access options were disabled, though I have tried turning them all on during trouble shooting.
      • Originally under Networking, for Firewall and Virtual Networks, selected Disable public access and Allow trusted Microsoft service to bypass this firewall was disabled.
        • During trouble shooting, I selected Allow public access from all networks and enabled Allow trusted Microsoft service to bypass this firewall. I also tried selecting Allow public access from specific virtual networks and IP addresses and added virtual network 'companyname-eus-vnet-global' and subnet 'default'.
    • Created a Private Endpoint named 'companyname-eus-kv-global-pe'
      • Virtual network/subnet: 'companyname-eus-vnet-global/default'
      • Network interface: 'companyname-eus-kv-global-pe-nic'
      • Private link resource: 'companyname-eus-kv-global'
      • Target sub-resource: vault
      • Connection status: Approved
      • Request/Response: -
      • Provisioning State: Succeeded
    • Created a Network Interface named 'companyname-eus-kv-global-pe-nic'
      • Private IPv4 address: 10.1.2.4
      • Attached to: 'companyname-eus-kv-global-pe (Private endpoint)'
      • Type: Regular
      • Accelerated networking: Disabled
      • Virtual network/subnet: 'companyname-eus-vnet-global/default'
      • Under Settings - DNS configuration - Customer Visible FQDNs
        • Network Interface: 'companyname-eus-kv-global-pe-nic'
          • IP Addresses: 10.1.2.4
            • FQDN: companyname-eus-kv-global.vault.azure.net
        • Configuration name: privatelink-vaultcore-azure-net
          • Private DNS zone: privatelink.vaultcore.azure.net
          • DNS zone group: default
            • FQDN: companyname-eus-kv-global.privatelink.vaultcore.azure.net
            • IP Address: 10.1.2.4
    • Created and purchased the App Service Certificate and named the resource 'companyname-eus-kv-global-sitename-com-wildcard-cert'
      • Distinguished Name: CN=*.sitename.com
      • Product Type: Wild Card
      • Validity Period: 1 Year(s)
      • Certificate Status: Issued
    • In App Service Certificate, a warning showed "Configured required Key Vault store -->". Clicking on this goes to 'Certificate Status'
      • Step 1: Store - No Green Check and says "Import certificate into Key Vault for secure administration."
        • Step 1 is what keeps throwing an error.
      • Step 2: Verify - Shows Green Check and says "Domain ownership verified"
      • Step 3: Assign - Shows Green Check and says "Certificate ready to use in App Service"

With all of the different troubleshooting steps I've tried, I always have the same issues:

  • Every time I click on 'Configured required Key Vault store -->' and it opens the 'Certificate Status' page, and I then click on Step 1: Store, I get two success notifications:
    • Get certificate service principal - Successfully obtained service principal object ID.
    • Get web app service principal - Successfully obtained service principal object ID.
  • If I then go and click on 'Select from Key Vault', my Subscription is selected by default and then I click on 'companyname-eus-kv-global' under the resource group 'companyname-eus-kv-global-rg' and then I click on the blue Select button.
    • Every time I do this, I get an error notification:
      • Save Key Vault Settings - Failed to link certificate with the selected Key Vault. Check below errors for more detail.: The parameter name has an invalid value.

I have tried every suggestion that Copilot has given me and looked into every article it referenced or that I could find with a web search. Those results always mention the Key Vault security, so under Access policies, I gave the Applications "Microsoft Azure App Service" and "Microsoft.Azure.CertificateRegistration" All permissions to Certificate Permissions. I additionally gave "Microsoft.Azure.CertificateRegistration" All permissions to Key and Secret as well. I additionally gave my admin user I'm logged in with All permissions for Key, Secret and Certificate as well, which I believe should rule out permissions on the Key Vault, based on what I could find online.

At this point I am dead in the water. I have a $300 cert I cannot import into Azure so I can start using it and all self-help troubleshooting has failed to resolve the issue.

The only thing I think that may possibly be something to try is to consolidate my resource groups. I had made a separate resource group for my Virtual Network, as ideally, I'd like to manage all global vnets for the tenant from one resource group as I do intend to add more vnets for other purposes. That is the only thing I can think of that might be preventing this from working but before I go through the process of tearing down most of what I setup already and reconfiguring everything, I wanted to get some input from an Azure expert to see if there is something else I am missing that we can change to get this working.

I greatly appreciate anyone's help in this matter.

Thank you,

Bryan

Azure Key Vault
Azure Key Vault
An Azure service that is used to manage and protect cryptographic keys and other secrets used by cloud apps and services.
1,416 questions
{count} votes

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.