This might be completely wide of the mark, but we use ADFS to authenticate our logins to Office365/SharePoint. We had problems trying to use synthetic transactions, as it is out to a web application, using adfs.
In the end, we are looking at Office365mon, a 3rd party company. We can install probes on our on-premise servers which test the logins to office365 sharepoint. By extension, this also checks that ADFS is functional as, without it, the probes could not connect to the sharepoint sites.
Another way around this which you could try is to use System Centre Orchestrator to attempt the login and then get it to raise a SCOM alert on the failure. A runbook will just need to be created for this to work, and once created you can set to run on a set time frame.
This seems like it would suit your needs, and be the answer to your question. It would just require a bit of time to set-up.
I haven’t done this personally; however I do use SCOM and SCOR together for some self healing tasks albeit basic ones
That was good links but not exactly what I was looking for. We have probably >50.000 ADFS logins per day and a lot of them goes wrong due to wrong passwords. So monitoring the logs wont help that much. I need to do a correct login with a test account and verify that the login works and alert if it does not.
Ah, okay. That makes life a little easier. You’ll need to create a synthetic transaction in SCOM. This will essentially test the login process at a regular interval.