Image Pull and Auth Errors
Use this query to isolate registry pull failures and authentication errors during revision provisioning.
Data Source
| Table | Schema Note |
ContainerAppSystemLogs_CL | Legacy schema. If empty, try ContainerAppSystemLogs (non-_CL). |
Query Pipeline
flowchart LR
A[Filter by app] --> B[Filter pull and auth terms] --> C[Project revision and reason] --> D[Sort by time]
Query
let AppName = "my-container-app";
ContainerAppSystemLogs_CL
| where ContainerAppName_s == AppName
| where Log_s has_any ("ImagePull", "pull", "manifest", "unauthorized", "denied")
| project TimeGenerated, RevisionName_s, Reason_s, Log_s
| order by TimeGenerated desc
Example Output
| TimeGenerated | RevisionName_s | Reason_s | Log_s |
| 2026-04-04T12:54:11.477Z | ca-myapp--0000001 | PulledImage | Successfully pulled image in 2.42s (58720256 bytes) |
| 2026-04-04T12:54:11.477Z | ca-myapp--0000001 | PullingImage | Pulling image '.azurecr.io/myapp-job:v1.0.0' |
| 2026-04-04T11:12:03.208Z | ca-myapp--0000002 | RevisionUpdate | Failed to pull image: unauthorized: authentication required |
Interpretation Notes
manifest unknown usually means bad repository or tag. unauthorized or denied points to registry auth/identity scope issues. - If no console logs exist, this query is often your primary evidence.
Limitations
- Text-matching query; custom log messages may vary by platform updates.
- Does not validate ACR role assignments directly.
See Also