• Products
  • Get started
  • Documentation
  • Resources

Integrate Opsgenie with Microsoft Azure Service Health

Azure service health logo

Overview

Azure Service Health alerts you and your teams via targeted and flexible notifications. Opsgenie is an alert and notification management solution highly complementary to Azure Service Health's alerting mechanism.

What does the integration offer?

Use the Azure Service Health integration to forward Azure Service Health alerts to Opsgenie. Opsgenie determines the right people to notify based on on-call schedules- using email, text messages (SMS), phone calls, iOS & Android push notifications, and escalates alerts until the alert is acknowledged or closed.

How does the integration work?

When an Azure Service Health alert is created in Azure, an alert is automatically created in Opsgenie.

Set up the integration

Azure Service Health is an API-based integration. Setting it up involves the following steps:

  • Add an Azure Service Health integration in Opsgenie

  • Configure the integration in Azure Service Health

Add an Azure Service Health integration

If you're using Opsgenie's Free or Essentials plan or if you’re using Opsgenie with Jira Service Management's Standard plan, you can add this integration from your team dashboard only. The Integrations page under Settings is not available in your plan.

  1. Go to Teams and select your team.

  2. Select Integrations on the left navigation and then select Add integration.

Adding the integration from your team dashboard will make your team the owner of the integration. This means Opsgenie will assign the alerts received through this integration to your team only. Follow the rest of the steps in this section to set up the integration.

To add an Azure Service Health integration in Opsgenie:

  1. Go to Settings > Integrations.

  2. Select Add integration.

  3. Run a search and select “Azure Service Health”.

  4. On the next screen, enter a name for the integration.

  5. Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.

  6. Select Continue.
    The integration is saved at this point.

  7. Expand the Steps to configure the integration section and copy the URL generated for your account.
    You will use this URL while configuring the integration in Azure later.

  8. Select Turn on integration.
    The rules you create for the integration will work only if you turn on the integration.

Configure the integration in Azure Service Health

  1. In the Azure Portal, select Browse.

  2. Select Service Health.

  3. In the Alerts section, select Health Alerts.

  4. Select the Add service health alert button.

  5. Add conditions for filtering the alerts.

  6. Go to the Actions tab.

  7. Select Create Action Group to create an action group.
    While adding actions, select Webhook for the action type.

  8. Paste the URL you copied while adding the integration in Opsgenie into URI.

  9. Enable the common alert schema if required.

  10. Save the changes for the new action group.

  11. Save the changes for the alert.

Sample payload sent from Azure Service Health

(in JSON format)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 { "schemaId": "Microsoft.Insights/activityLogs", "data": { "status": "Activated", "context": { "activityLog": { "channels": "Admin", "correlationId": "bbac944f-ddc0-4b4c-aa85-cc7dc5d5c1a6", "description": "Active: Virtual Machines - Australia East", "eventSource": "ServiceHealth", "eventTimestamp": "2017-10-18T23:49:25.3736084+00:00", "eventDataId": "6fa98c0f-334a-b066-1934-1a4b3d929856", "level": "Informational", "operationName": "Microsoft.ServiceHealth/incident/action", "operationId": "bbac944f-ddc0-4b4c-aa85-cc7dc5d5c1a6", "properties": { "title": "Virtual Machines - Australia East", "service": "Virtual Machines", "region": "Australia East", "communication": "Starting at 02:48 UTC on 18 Oct 2017 you have been identified as a customer using Virtual Machines in Australia East who may receive errors starting Dv2 Promo and DSv2 Promo Virtual Machines which are in a stopped "deallocated" or suspended state. Customers can still provision Dv1 and Dv2 series Virtual Machines or try deploying Virtual Machines in other regions, as a possible workaround. Engineers have identified a possible fix for the underlying cause, and are exploring implementation options. The next update will be provided as events warrant.", "incidentType": "Incident", "trackingId": "0NIH-U2O", "impactStartTime": "2017-10-18T02:48:00.0000000Z", "impactedServices": "[{\"ImpactedRegions\":[{\"RegionName\":\"Australia East\"}],\"ServiceName\":\"Virtual Machines\"}]", "defaultLanguageTitle": "Virtual Machines - Australia East", "defaultLanguageContent": "Starting at 02:48 UTC on 18 Oct 2017 you have been identified as a customer using Virtual Machines in Australia East who may receive errors starting Dv2 Promo and DSv2 Promo Virtual Machines which are in a stopped "deallocated" or suspended state. Customers can still provision Dv1 and Dv2 series Virtual Machines or try deploying Virtual Machines in other regions, as a possible workaround. Engineers have identified a possible fix for the underlying cause, and are exploring implementation options. The next update will be provided as events warrant.", "stage": "Active", "communicationId": "636439673646212912", "version": "0.1.1" }, "status": "Active", "subscriptionId": "4970d23e-ed41-4670-9c19-02a1d2808ff9", "submissionTimestamp": "2017-10-18T23:49:28.7864349+00:00" } }, "properties": {} } }

Additional Help