Last Seen is not displaying latest last seen across any connected app

%3CLINGO-SUB%20id%3D%22lingo-sub-1208612%22%20slang%3D%22en-US%22%3ELast%20Seen%20is%20not%20displaying%20latest%20last%20seen%20across%20any%20connected%20app%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1208612%22%20slang%3D%22en-US%22%3E%3CP%3Ewhen%20viewing%20the%20accounts%20tab%20of%20azure%3B%20i'm%20seeing%20last%20seen%20column%20dates%20that%20are%20not%20reflective%20of%20actual%20login%3C%2FP%3E%3CP%3Ewhen%20i%20expand%20the%20account%20-%20it%20shows%20three%20dates%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20default%20column%20should%20show%20the%20latest%20date%20of%20last%20seen%20for%20any%20app%3B%20and%20not%20the%20first%20one%20found..%20(see%20attached)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1208612%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECloud%20App%20Security%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1241891%22%20slang%3D%22en-US%22%3ERe%3A%20Last%20Seen%20is%20not%20displaying%20latest%20last%20seen%20across%20any%20connected%20app%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1241891%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F85990%22%20target%3D%22_blank%22%3E%40Michael%20Baker%3C%2FA%3E%26nbsp%3Bthank%20you%20for%20the%20comment.%20This%20is%20a%20known%20issue%20and%20our%20engineers%20are%20working%20to%20resolve%20the%20problem.%20Unfortunately%2C%20we%20do%20not%20have%20an%20ETA%20at%20this%20time.%20Sorry%20for%20the%20inconvenience.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

when viewing the accounts tab of azure; i'm seeing last seen column dates that are not reflective of actual login

when i expand the account - it shows three dates;  

the default column should show the latest date of last seen for any app; and not the first one found.. (see attached)

1 Reply

@Michael Baker thank you for the comment. This is a known issue and our engineers are working to resolve the problem. Unfortunately, we do not have an ETA at this time. Sorry for the inconvenience.