Integrate with Azure Service Health

1 Overview
- 1.1 What does the integration offer?
- 1.2 How does the integration work?
2 Set up the integration
- 2.1 Add Azure Service Health integration
- 2.2 Configure the integration in Azure Service Health

Overview

Azure Service Health alerts you and your teams via targeted and flexible notifications. Jira Service Management 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 Jira Service Management. Jira Service Management 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 a Service Health alert is created in Azure, an alert is automatically created in Jira Service Management.

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 Jira Service Management
Configure the integration in Azure Service Health

Add Azure Service Health integration

If you're using the Free or Standard plan in Jira Service Management, you can only add this integration from your team’s operations page. To access the feature through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be on Premium or Enterprise plan.

Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management only assigns the alerts received through this integration to your team.

To add an Azure Service Health integration in Jira Service Management:

Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “Azure Service Health”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.
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.
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

In the Azure Portal, select Browse.
Select Service Health.
In the Alerts section, select Health Alerts.
Select the Add service health alert button.
Add conditions for filtering the alerts.
Go to the Actions tab.
Select Create Action Group to create an action group.
While adding actions, select Webhook for the action type.
Paste the URL you copied while adding the integration in Jira Service Management into URI.
Enable the common alert schema if required.
Save the changes for the new action group.
Save the changes for the alert.

Sample payload sent from Azure Service Health

{
  "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 &quot;deallocated&quot; 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 &quot;deallocated&quot; 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": {}
  }
}

Operations Help