• Products
  • Get started
  • Documentation
  • Resources

Integrate with Microsoft Azure Resource Health

This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.

Azure Service Health Logo

What does the integration offer?

Use the Azure Resource Health Integration to forward Azure Resource 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 Resource Health alert is created in Azure, an alert is automatically created in Jira Service Management. The alert is closed in Jira Service Management if the Resource Health alert is closed in Azure.

Set up the integration

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

  • Add an Azure Resource Health integration in Jira Service Management

  • Configure the integration in Azure Resource Health

Add an Azure Resource Health integration

Bidirectional integrations aren’t supported in Free and Standard plans. All the other integrations are supported at a team level in Free and Standard; however, for their outgoing part to work, you need to upgrade to a higher plan. To add any integration at a site level through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be either on Premium or Enterprise.

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 Resource Health integration in Jira Service Management, complete the following steps:

  1. Go to your team’s operations page.

  2. On the left navigation panel, select Integrations and then Add integration.

  3. Run a search and select “Azure Resource 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 integration 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 Resource Health

To configure the integration in Azure Resource Health, complete the following steps:

  1. In the Azure Portal, select Browse.

  2. Select Service Health.

  3. In the Resource Health section, select Resource Health.

  4. Open Add resource health alert.

  5. Add conditions for filtering alerts.

  6. Go to the Actions tab.

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

  8. Paste the integration URL copied from Jira Service Management 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

(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 { "schemaId": "Microsoft.Insights/activityLogs", "data": { "status": "Activated", "context": { "activityLog": { "channels": "Admin, Operation", "correlationId": "a1be61fd-37ur-ba05-b827-cb874708babf", "eventSource": "ResourceHealth", "eventTimestamp": "2018-09-04T23:09:03.343+00:00", "eventDataId": "2b37e2d0-7bda-4de7-ur8c6-1447d02265b2", "level": "Informational", "operationName": "Microsoft.Resourcehealth/healthevent/Activated/action", "operationId": "2b37e2d0-7bda-489f-81c6-1447d02265b2", "properties": { "title": "Virtual Machine health status changed to unavailable", "details": "Virtual machine has experienced an unexpected event", "currentHealthStatus": "Unavailable", "previousHealthStatus": "Available", "type": "Downtime", "cause": "PlatformInitiated" }, "resourceId": "/subscriptions/<subscription Id>/resourceGroups/<resource group>/providers/Microsoft.Compute/virtualMachines/<resource name>", "resourceGroupName": "<resource group>", "resourceProviderName": "Microsoft.Resourcehealth/healthevent/action", "status": "Active", "subscriptionId": "<subscription Id>", "submissionTimestamp": "2018-09-04T23:11:06.1607287+00:00", "resourceType": "Microsoft.Compute/virtualMachines" } } } }


Still need help?

The Atlassian Community is here for you.