Introduction
The Status Service lets you
- monitor the health of your applications, and
- keep your users informed of an application’s status.
For our purposes:
- Application health is defined by pinging a developer-supplied URL every minute or so, and based on the response is either healthy or unhealthy.
- Application status is set by developers to inform end-users about planned (or otherwise) service outages.
In addition, the Status Service
- sends notifications to developers when an application’s health changes,
- sends notifications to developers and end-users when an application’s status changes,
- lets you customize notification messages (email or text),
- provides a public, static status page for your tenant that can be used to inform end users about an Application’s Status.
Notices and Notifications
Notices are used to inform end-users about an Application’s Status. They may include
- reasons for the outage
- a time-frame for planned outages
Notices are displayed on a public, static webpage that applications can link to, so users can quickly determine their status.
Notifications are triggered when an application’s health or status changes. Developers can subscribe to be notified about health changes, while end-users can subscribe to be notified when the status changes. The latter is a self-serve operation available through the public status page mentioned above, and is delivered by email. Developers can be notified by either text or email.
Learn More
Learn how to
- monitor your application’s health.
- use status codes to keep users informed about application health.
- provide notices about application status to end users.
- get notified about changes in application health and status.