Office 365 Service Health - Depreciated API

nglynn  wrote: So we leverage a whole host of the Office 365 SAM monitors for pulling down Service Health status information.  We've recently gotten word from MS that the older service API that all of the SolarWinds Office365 Service Health monitors are leveraging today are going away in Q1.  Is SolarWinds already working on new monitors leveraging the newer API to replace this functionality?  Has anyone else started working on these?

We are working on enabling more authentications in the simplified API pollers so customers can react quickly to changes in API even if there hasn't been an official release of SolarWinds.

the first version of the API poller is :SAM 2019.4 Release Notes

Which of our  Microsoft Office 365  templates are you worried about in particular nick?

All of the Office 365 templates that pull the Service Health information from the Office 365 Admin portals that are configured to use the https://api.admin.microsoftonline.com/shdtenantcommunications.svc such as: Microsoft Office 365 Exchange Online   I currently am using the Exchange, Portal, SharePoint and OneDrive templates.  Per MS the following legacy APIs are going away Feb 17th.

These legacy API endpoints include:

• http://office365servicehealthcommunications.cloudapp.net/
• http://ctpoffice365servicehealthcommunications.cloudapp.net/
• https://api.admin.microsoftonline.com/shdtenantcommunications.svc
• Microsoft.Exchange.ServiceStatus.TenantCommunications.Data

All of the Office 365 templates that pull the Service Health information from the Office 365 Admin portals that are configured to use the https://api.admin.microsoftonline.com/shdtenantcommunications.svc such as: Microsoft Office 365 Exchange Online   I currently am using the Exchange, Portal, SharePoint and OneDrive templates.  Per MS the following legacy APIs are going away Feb 17th.

These legacy API endpoints include:

• http://office365servicehealthcommunications.cloudapp.net/
• http://ctpoffice365servicehealthcommunications.cloudapp.net/
• https://api.admin.microsoftonline.com/shdtenantcommunications.svc
• Microsoft.Exchange.ServiceStatus.TenantCommunications.Data

nglynn- where did you end up with your monitoring after MS retired the "legacy" APIs?  I'm about to embark on monitoring our 365 environment in the next week or two.

BWB8771 , nglynn 

SAM 2020.2.1 has dedicated Microsoft 365 API Poller templates that capture the data that was available in depreciated API: https://documentation.solarwinds.com/en/Success_Center/sam/Content/Release_Notes/sam_2020-2-1_release_notes.htm

Using https://manage.office.com/api/v1.0/

jan for the service account, can I use Global Reader instead of Global Admin? 

itengineer As mentioned here: https://documentation.solarwinds.com/en/Success_Center/sam/Content/SAM-API-Poller-Microsoft-365-Admin-Center.htm and https://docs.microsoft.com/en-us/office/office-365-management-api/office-365-service-communications-api-reference ServiceHealth.Read permission should be used.