Exercise 5 – exploring Azure Service Health
In this section, you’ll learn how to interact with Azure Service Health in the Azure portal:
Task – accessing the Azure portal
- Log in to the Azure portal by going to https://portal.azure.com. Alternatively, you can use the Azure desktop app: https://portal.azure.com/App/Download.
Task – exploring Azure Service Health
- From the search box at the top of the portal, enter Service Health and click on Service Health from the results.
- On the Service Health page, there is a left-hand navigation menu. Here, you can view ACTIVE EVENTS, HISTORY, RESOURCE HEALTH, and ALERTS.
- From Service issues, under the ACTIVE EVENTS section, you can launch a guided tour and view the current service issues or issues that have been resolved in the past 7 days that may be impacting your resources; the map will show color status dots for each region you have resources in. This can be seen in the following screenshot:
Figure 6.37 – Service Health
- In the ACTIVE EVENTS section, you can also click through to see any Planned maintenance events that may impact your resources, Health advisories, and Security advisories; for each, there is a click-through link to see all past issues in the Health history section
- In the Health History section, you can click on a service issue, find out more information about the impact, any updates, and download a summary report and a Root Cause Analysis (RCA) report.
- In the Resource health section, you can view the health of any individual resource you have created within your subscription(s) so that you know if everything is running as expected. If any problems are impacting its running, you will be told and actions you can take will be provided. For example, if a VPN gateway is not running normally, a hyperlink will be provided so that you can reset it.
- In the Health alerts section, you can add a service health alert rule so that a notification is sent based on a set of service health criteria.
With that, we’ve covered the hands-on exercises for this chapter. Now, let’s summarize what we’ve learned.