Microsoft 365 MP - connection state - M365 Connection State monitor

Stephen Morrison 71 Reputation points
2022-01-04T19:51:01.413+00:00

Yesterday the conneciton state monitor triggered in our production instance of SCOM. We are on 2019 U3 and have the 10.1.100.0 Microsoft 365 MP in place. this has been working for a couple of weeks now.

Going back into the wizard to setup the watcher running the synthetic test shows successful. I also see event ID 910 which shows PortalLogin
Success: Connected.

but the alert has this context
Authentication message:
Endpoint message: Connection to EndPoint Service failed

How can I troubleshoot this?

running this from the watcher is successful
PS P:\> curl -v https://graph.microsoft.com/v1.0
VERBOSE: GET https://graph.microsoft.com/v1.0 with 0-byte payload
VERBOSE: received -1-byte response of content type application/json

StatusCode : 200
StatusDescription : OK

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,417 questions
0 comments No comments
{count} votes

Accepted answer
  1. Ingerson, Terry 76 Reputation points
    2022-01-20T13:19:36.413+00:00

    We deployed over the top but redid the subscription part.

    We added a new subscription using the "auto created service principal" option (worth noting this wasn't working with the old MP), edited the watcher node to use the newly configured subscription, and then removed the old subscription.

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Ingerson, Terry 76 Reputation points
    2022-01-06T16:39:49.207+00:00

    We are seeing the same error. All other parts of the MP are working correctly. All I can find searching is references to to the old MP which looks like it used the URL https://office365servicehealthcommunications.cloudapp.net/ for the check but that URL no longer functions. Looks like it may have been deprecated. Not sure if that is what this monitor is trying to connect to.


  2. Ingerson, Terry 76 Reputation points
    2022-01-06T17:21:48.24+00:00

    Same time frame for us. I submitted a ticket.


  3. Stephen Morrison 71 Reputation points
    2022-01-07T17:18:23.73+00:00

    I heard back from one of the developers of the MP, this was his response. No answer yet but they are looking into it.

    • I am looking into this for you. We have not seen this error in our QA or Dev labs, but continue to hunt it down.
      FWIW: This monitor is certainly not critical (any more). It used to be there to check the ability to read the old Message Center API, but now that everything is going through the Graph API, this monitor no longer really adds much value. But we’ll see what we can do to find the issue and fix it. *