Hi @ Binod Maharjan,
Yes. I carefully compared the success and failure entries in IIS logs. As you said, the identifier indicating success is not as clear as failure.
So I checked some other login logs and found a more suitable identifier for the trigger in the httpproxy logs.
You can find the httpproxy logs related to OWA at this location: C:\Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\Owa
Failed entry:
2023-06-16T05:38:27.264Z,14e1b06a-1fa2-47ee-afc8-95142913eeab,15,1,2507,6,,Owa,e16a,/owa/auth.owa,,FBA,false,,,,Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML like Gecko) Chrome/109.0.0.0 Safari/537.36 Edg/109.0.1518.100,192.168.2.52,E16A,302,,,POST,,,,,,,,,132,,,,,,,,,,,,,,,28,,,,,,,,,,,,,,28,,28,28,,,,ClientId=B89D36EBF04F4812AB9456267F870051;BeginRequest=2023-06-16T05:38:27.236Z;CorrelationID=<empty>;SharedCacheGuard=0;NoCookies=302 - GET/E14AuthPost;EndRequest=2023-06-16T05:38:27.264Z;,,,,,,
Success Entry:
2023-06-16T05:35:41.342Z,d2eae339-b0e7-4f72-ae5f-de9e74e21f1b,15,1,2507,6,,Owa,e16a,/owa/auth.owa,,FBA,true,DOMAIN1\Administrator,,Sid~S-1-5-21-960715358-4216514951-3559177506-500,Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML like Gecko) Chrome/109.0.0.0 Safari/537.36 Edg/109.0.1518.100,192.168.2.52,E16A,302,,,POST,,,,,WindowsIdentity,Database~67a251b9-031b-4160-8d98-86bbef4165da~~
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.