Configuration - Admin Portal Status

Monitoring Benefit

The Configuration Admin Portal status test reports whether ENow's connection to the Microsoft 365 administrative interface is healthy.

This test depends entirely on the PowerShell test. It does not make its own connection to Microsoft 365. It reports on the result recorded by the Configuration - PowerShell Status test, which always runs first.

What to do first

Check the PowerShell status test before investigating anything here.

• PowerShell is also failing. This is the normal case. There is one underlying problem, and it is the PowerShell connection. Resolve that, and the Admin Portal check will clear on the next monitoring cycle. Nothing needs to be done to the Admin Portal check itself.
• PowerShell is healthy but Admin Portal is not. This is the unusual case. Because Admin Portal is reporting on a stored result rather than testing anything itself, the problem is usually that the result it is reading is not current — see below.

How do we verify the monitoring test results?

First, validate the underlying connection using the steps in the Configuration - PowerShell Status article.

If that connection succeeds by hand and ENow still reports Admin Portal as failing, the two checks are disagreeing about the same stored result. Check:

• When the PowerShell test last completed. Compare its last run time against the monitoring interval configured for the check. A PowerShell test that is starting but never finishing leaves the last successful result in place and going stale, which shows up here before it shows up there.
• That ENow can reach its database. Test results are stored in SQL. If the ENow services cannot write to or read from the database, checks that report on stored results go stale or blank while the underlying connection is perfectly healthy. Confirm the SQL Server is reachable from the ENow web server and that the ENow service account can still authenticate to it.
• The ENow service logs on the web server, for an unhandled error during the PowerShell test.

Common warning or error results, and potential solutions

• Both checks red at the same time. Expected behaviour, not two faults. Work the PowerShell check.
• Both checks went red immediately after a Conditional Access change. The monitoring account has most likely been brought into the scope of a policy it was previously excluded from. See Service Accounts: What Each ENow Component Needs, and Rotating Credentials and Conditional Access and ENow: Why Device-Based Policies Block Monitoring.
• Several unrelated checks went stale at the same moment. That pattern points at the database rather than at any one test. A SQL outage, a failed-over instance, or an expired service account password affects everything that stores results at once.
• Admin Portal red, PowerShell green, and the PowerShell result is current. Contact ENow Support with both results, as the two checks are reading the same data and should agree.