Office 365 Service Communications API reference

最新推荐文章于 2019-10-02 10:24:28 发布

beixing_xuan

最新推荐文章于 2019-10-02 10:24:28 发布

阅读量670

点赞数

分类专栏： Office 365 文章标签： Office 365 api

Office 365 专栏收录该内容

6 篇文章 0 订阅

订阅专栏

You can use the Office 365 Service Communications API V2 to access the following data:

Get Services : Get the list of subscribed services.
Get Current Status : Get a real-time view of current and ongoing service incidents and maintenance events
Get Historical Status : Get a historical view of service health, including service incidents and maintenance events.
Get Messages : Find Incident, Planned Maintenance, and Message Center communications.

Currently, the Office 365 Service Communications API contains data for the following services: Dynamics CRM, Dynamics Marketing, Exchange Online, Exchange Online Protection, Identity Service, Mobile Device Management, Office 365 Partner Admin Center, OneDrive for Business, Parature, OneDrive for Business, Power BI for Office 365, Rights Management Service, SharePoint Online, SHD Admin, Skype for Business, Social Engagement, and Yammer Enterprise.

The Fundamentals

The root URL of the API includes a tenant identifier that scopes the operations to a single tenant:

The Office 365 Service Communications API is a REST service that allows you to develop solutions using any web language and hosting environment that supports HTTPS and X.509 certificates. The API relies on Microsoft Azure Active Directory and the OAuth2 protocol for authentication and authorization. To access the API from your application, you'll need to first register it in Azure AD and configure it with permissions at the appropriate scope. This will enable your application to request OAuth2 access tokens necessary for calling the API. You can find more information about registering and configuring an application in Azure AD at Office 365 Management APIs getting started.

All API requests require an Authorization HTTP header that has a valid OAuth2 JWT access token obtained from Azure AD that contains theServiceHealth.Read claim; and the tenant identifier must match the tenant identifier in the root URL.