Organizations increasingly distribute Azure service ownership across multiple teams. Azure Service Health provides crucial updates, but notifications often go to a central mailbox, requiring manual forwarding. This manual process becomes inefficient with growing Azure services and teams, impacting response times.A proposed automated solution uses Azure Service Health, Azure Monitor Action Groups, and an Autonomous Agent Logic App for intelligent notification routing. The Logic App acts as the intelligent routing layer, determining who should receive each Service Health notification. It maintains a service-to-owner mapping, stored as a CSV in Azure Blob Storage in this example, which can be replaced by other data sources like SharePoint or a database. An autonomous agent simplifies routing logic by analyzing events, identifying services, retrieving ownership, and delivering notifications.The solution involves three steps: building the Logic App, configuring the Azure Monitor Action Group, and creating the Service Health Alert. The Logic App, built as a Consumption (Multi-Tenant) Logic App with an Autonomous Agent workflow, includes tools for reading trigger input, looking up service owners, sending alert emails, and failure notifications. The Azure Monitor Action Group invokes the Logic App when a matching Service Health event occurs, using an HTTP trigger. Finally, a Service Health Alert is configured to use this Action Group.After deployment, Office 365 authorization is required for email notifications. Validation and testing of Logic App execution, routing accuracy, and email delivery are recommended. The solution's cost is generally low, based on consumption, as Service Health events are infrequent. It helps organizations streamline alert management by automating notification routing to responsible teams, reducing manual effort, and improving response times.