# Azure Container Registry adds proactive Service Health alerts > Registry incidents can now trigger Azure Service Health notifications based on push, pull, and authentication service indicators. Canonical URL: https://www.devobs.io/news/news-azure-container-registry-proactive-service-health/ By: Claire Dubois Published: 2026-09-06T11:58:54.637Z Updated: 2026-09-06T11:58:54.637Z Event date: 2026-03-12 Section: Infrastructure Azure Container Registry introduced proactive monitoring and automatic Service Health communication. The [announcement](https://techcommunity.microsoft.com/blog/appsonazureblog/proactive-health-monitoring-and-auto-communication-now-available-for-azure-conta/4501378) says Azure evaluates indicators for authentication, image pushes, and image pulls, then notifies affected customers about qualifying degradation. Operators can route notices through Service Health alert rules and action groups. ## A provider signal joins workload telemetry Registry trouble is often first noticed by a deployment job that cannot pull an image. A provider-generated event gives responders a separate signal for distinguishing a service incident from an expired credential, missing tag, or broken network path. It complements metrics, diagnostic logs, and synthetic pulls; it cannot replace them. The operational gain is earlier, automatic incident context. Teams do not need to rely only on a manual status-page check after failures have spread through release queues. Detection thresholds and incident scope may still differ from an application's experience. ## Build an actionable route Confirm that subscriptions containing production registries have Service Health rules filtered to Container Registry and the intended regions. Test the action group, verify who owns its destination, and document how responders correlate the event with failed operations. Preserve pipeline alerts and bounded retries. For multi-region delivery, map registry endpoints and deployment environments to escalation routes. A provider notice should accelerate diagnosis, while immutable image references, cached layers, and controlled rollout pauses limit impact. Avoid retry storms: pause launches when authentication or pull failures cross a threshold, then resume only after both Service Health and application probes recover. ## Source references -