Monitoring Microsoft Azure

You can monitor your Microsoft Azure services using IncidentHub's integration that fetches health data using official Microsoft APIs. The access is read-only and works by fetching your service health data and status directly from your Microsoft Azure subscription.

Available on the Business and Multi-Client plans. You need an Azure Subscription Owner (or User Access Administrator) plus Microsoft Entra rights to create a service principal - typically a Global Administrator.

IncidentHub reads:

1. Service Health events for the subscription (service issues, planned maintenance, health advisories, emerging issues)

2. Resource Health availability for resources in the subscription (unavailable and degraded)

Before You Start

Note down two GUIDs from your Azure portal:

Value	Where to find it
Tenant ID	Microsoft Entra ID → Overview → Tenant ID
Subscription ID	Subscriptions → the subscription → Subscription ID

Both must be in the UUID format (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

In Your IncidentHub Account

1. Login to your IncidentHub dashboard

2. In "My Services", click on "Add"

3. Select Microsoft Azure (Resource Health Integration)

This is different from adding the "Microsoft Azure" from the dropdown - which monitors the public status page only. Do not select that.

Paste the Azure tenant ID and Azure subscription ID and click Continue.

You will get a script which you can paste into your Azure Cloud Shell in bash mode (not Powershell). This is a one-time setup.

What the Script Does

1. Registers the Microsoft.ResourceHealth resource provider on the subscription

2. Creates the IncidentHub service principal in the tenant if it does not already exist

3. Creates a custom role named IncidentHub Resource Health Reader (read-only Resource Health permissions)

4. Assigns that role on the subscription

After running the script, wait for a few minutes so that the changes propagate and click on "Verify Access" on the same screen in IncidentHub. If verification fails because the role is still propagating, wait a few minutes and try again.

RBAC changes can take a few minutes to propagate. After the script succeeds, wait before you click Verify Access.

Permissions granted to IncidentHub are read-only:

• Microsoft.ResourceHealth/events/read

• Microsoft.ResourceHealth/availabilityStatuses/read

• Microsoft.ResourceHealth/emergingissues/read

• Microsoft.ResourceHealth/operations/read

• Microsoft.ResourceHealth/metadata/read

IncidentHub cannot create, change, or delete Azure resources.

Complete Your Setup

If the RBAC permissions were granted correctly, IncidentHub will show you a screen where you can give a unique name to this integration. You can also choose which components in Microsoft Azure you wish to monitor, or choose "Monitor all components" to monitor everything.

Click on Save to save your integration.

You can edit the components at any time just like any other service - by clicking on the Edit icon next to your Microsoft Azure integration in the IncidentHub dashboard.

Which Events are Ingested

Source	Included
Service issues (outages and degradation)	Yes
Planned maintenance	Yes, as maintenance events. You only get maintenance alerts if you tick that checkbox during setup (or tick it later).
Health advisories and emerging issues	Yes
Per-resource unavailable / degraded	Yes (not filtered by selected Azure services yet)
Security advisories	No

This integration uses the Azure Resource Health REST API to poll Service Health events and resource availability for the connected subscription.

IncidentHub is not affiliated with Microsoft or any of the services mentioned in this article. IncidentHub uses standard Microsoft APIs and authentication mechanisms to fetch health data.