Azure Web App for Containers与ACR的CI集成故障及升级问题求助

Let’s work through your problems step by step — I’ve helped many users untangle similar ACR/Web App CI integration headaches, so let’s start with the most impactful fixes:

1. Fix the "Unmanaged Container Registry" Error When Creating ACR Webhooks #

That error almost always links to your ACR’s SKU or deployment model:

• Check your ACR pricing tier: The Basic SKU doesn’t support webhooks at all. You’ll need to upgrade to Standard or Premium. If you don’t see an upgrade option in the Azure portal, your registry might be using the outdated classic deployment model (instead of Resource Manager). In that case, migrate it first via Azure CLI with az acr update --name <your-acr-name> --sku Standard — just be sure to back up your images before making changes.
• Verify permissions: Make sure you have Owner or Contributor access to the ACR resource; without that, you won’t see upgrade or webhook creation options.

2. Resolve Failed CI Enablement in Web App’s Docker Settings #

When enabling CI directly from the Web App’s Docker tab fails, it’s typically a permissions or network issue:

• Grant your Web App access to ACR: Use a system-assigned managed identity for the cleanest setup:
  1. Go to your Web App > Identity > System assigned > Toggle to On and save.
  2. Navigate to your ACR > Access control (IAM) > Add role assignment.
  3. Select the AcrPull role, then under Members, choose Managed identity and pick your Web App’s identity.
• Manually set up the CI webhook: If automatic setup fails, do it manually:
  1. Grab your Web App’s CI hook URL: https://<your-webapp-name>.scm.azurewebsites.net/docker/hook
  2. Go to your ACR > Webhooks > Add.
  3. Paste the URL, name the webhook, select push as the trigger event, and enable it.
• Test the webhook: After creation, use the Test button in the ACR webhook menu. A 200 OK response means the connection works; if not, check the webhook logs for errors (common culprits: blocked IPs or invalid resource permissions).

3. Troubleshoot Existing Failed Webhooks #

If your old webhook stopped working, run through these checks:

• Check webhook status: In ACR’s webhook list, confirm it’s not disabled and review its delivery history for failure patterns.
• Validate the hook URL: Ensure the URL hasn’t changed (e.g., if you renamed your Web App). Test it by sending a blank POST request (use curl or Postman) — a 200 response means it’s reachable.
• Check network restrictions: If your Web App uses VNet integration or your ACR has firewall rules:
  • Add your Web App’s outbound IPs to ACR’s allowed list, or enable the "Allow trusted Azure services to access this container registry" setting.
  • Confirm your Web App’s SCM site (https://<your-webapp-name>.scm.azurewebsites.net) isn’t blocked by NSGs or private endpoints.

内容的提问来源于stack exchange，提问作者Jordan Finneran