• Products
  • Get started
  • Documentation
  • Resources

Integrate Opsgenie with Microsoft Azure Service Health

Azure service health logo

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

What does Opsgenie offer Azure Service Health users?

Use Opsgenie’s 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.

Functionality of the integration

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

Add Azure Service Health Integration in Opsgenie

  1. Go to Opsgenie's Azure Service Health Integration page.

Under the Free and Essentials plans, the tabs under the Team dashboard are limited to Main, Integrations, Members, and Activity Stream.

2. Specify who is notified of Azure Service Health alerts using the Teams field. Autocomplete suggestions will be provided as you type.

Did you know that you can also add this integration from your team dashboard? 

If you want your team to be the owner of this integration, add it from your team dashboard. Opsgenie will assign the alerts received through this integration to your team only.

To do that;

  1. Go to Teams

  2. Find your team and select it to go to your team dashboard,

  3. From your team navigation, select Integrations,

  4. Select Add integration.

3. Copy the URL.

4. Click Save Integration.

Azure Service Health integration

Configuration in Azure Service Health

  1. In the portal, select Monitor.

Azure Service Health portal monitor

2. In the "Activity log" section, select Alerts.

Azure Service Health Monitor Alerts

3. Select Add activity log alert, and fill in the fields.

Azure Service Health Log Alert

4. In the "Event category" box, select Service Health.

5. Under Alert via, select New action group. Enter a name in the Action group name box, and enter a name in the short name box. The short name is referenced in the notifications that are sent when this alert fires.

6. Under "Actions", Select Webhook as "ACTION TYPE".

7. Paste the URL copied previously into the "DETAILS" field.

Azure Service Health actions

8. Click OK.

Sample payload sent from Azure Service Health

JSON

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": {} } }

 

Last modified on Jan 27, 2021
Cached at 6:20 AM on Jul 27, 2021 |

Additional Help

Ask the Community