The major incident was most likely caused by the Audittrail Service overloading the server, which also hosted the Gatekeeper Service responsible for authorization. The increased load from the Audittrail Service led to significant performance issues, including service logging errors, slow response times, and login failures. The root cause is believed to be the shared resource constraint between the Audittrail Service and Gatekeeper Service on the same machine. The incident was resolved as the load on the server most likely balanced itself. To prevent future occurrences, the plan involves separating the databases by leveraging Azure infrastructure, an ongoing process with high priority.