Home

Get Outlook versions

%3CLINGO-SUB%20id%3D%22lingo-sub-15983%22%20slang%3D%22en-US%22%3EGet%20Outlook%20versions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15983%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20do%20I%20get%20a%20report%2Fetc%20of%20Outlook%20versions%20connecting%20to%20EO%3F%20I%20presume%20on-prem%20I%20would%20use%26nbsp%3BGet-LogonStatistics%20which%20isn't%20available%20on%20EO.%20I%20can't%20see%20a%20suitable%20report%20in%20new%20or%20old%20admin%20portal.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20ask%20as%20we%20got%20this%20Message%20in%20one%20of%20our%20client%20tenants.%20Maybe%20a%20Mac%20Office%20version%20issue%3F%3C%2FP%3E%3CP%3E%5B%5B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%3CSPAN%3EUpdated%20Feature%3A%20Web%20support%20for%20Outlook%202007%20and%202010%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%2F!%5C%26nbsp%3B%3CSPAN%3EAction%20required%20by%20Oct%2025%2C%202016%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%5B...%5D%20You%20are%20receiving%20this%20message%20because%20our%20reporting%20indicates%20you%20have%20at%20least%20one%20user%20in%20your%20organization%20connecting%20to%20Office%20365%2C%20using%20either%20Outlook%202007%20or%20Outlook%202010.%20%5B...%5D%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%5D%5D%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-15983%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16262%22%20slang%3D%22en-US%22%3ERe%3A%20Get%20Outlook%20versions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16262%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Vasil.%20I%20turned%20on%20the%20auditing%20last%20night%20and%20will%20see%20what%20today's%20logging%20brings.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYup%2C%20had%20tried%20that.%20But%20not%20even%20client%20name%20(never%20mind%20version)%20AFAICS.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16139%22%20slang%3D%22en-US%22%3ERe%3A%20Get%20Outlook%20versions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16139%22%20slang%3D%22en-US%22%3E%3CP%3EYup%2C%20you%20need%20auditing%20enabled%20on%20each%20mailbox%20for%20the%20events%20to%20be%20gathered.%20Otherwise%20you%20can%20rely%20on%20the%20Logon%20events%2C%20but%20in%20my%20experience%20they're%20not%20that%20reliable%20client%20version-wise.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20option%20is%20to%20try%20Get-ConnectionByClientTypeReport%2C%20though%20it%20only%20lists%20the%20protocol%20(OWA%2FEWS%2FEAS%2Fetc).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20are%20running%20AD%20FS%2C%20you%20can%20also%20get%20the%20client%20info%20from%20the%20event%20logs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16120%22%20slang%3D%22en-US%22%3ERe%3A%20Get%20Outlook%20versions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16120%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Vasil.%20I'll%20look%20at%20that%20again%20then.%20I%20didn't%20have%20it%20enabled%20on%20the%20respective%20tenant%20but%20it%20is%20now!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20another%20tenant%20I%20looked%20and%20there%20were%20no%20useful%26nbsp%3Bentries.%20I%20wonder%20why%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAhh%20needs%20turned%20on%20for%20all%20individual%20mailboxes%3F%20%26nbsp%3BYeh%3F%20%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-gb%2Farticle%2FSearch-the-audit-log-in-the-Office-365-Security-Compliance-Center-0d4d0f35-390b-4518-800e-0c7ec95e946c%3Fui%3Den-US%26amp%3Brs%3Den-GB%26amp%3Bad%3DGB%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-gb%2Farticle%2FSearch-the-audit-log-in-the-Office-365-Security-Compliance-Center-0d4d0f35-390b-4518-800e-0c7ec95e946c%3Fui%3Den-US%26amp%3Brs%3Den-GB%26amp%3Bad%3DGB%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16092%22%20slang%3D%22en-US%22%3ERe%3A%20Get%20Outlook%20versions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16092%22%20slang%3D%22en-US%22%3E%3CP%3EAhh%20-%20didn't%20even%20think%20about%20that.%20Sorry%2C%20early%20morning%20brain%20fart%2C%20ha.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16090%22%20slang%3D%22en-US%22%3ERe%3A%20Get%20Outlook%20versions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16090%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3188%22%20target%3D%22_blank%22%3E%40Paul%20Bridges%3C%2FA%3E%26nbsp%3Bno%2C%20this%20will%20not%20work%20against%20EO%2C%20as%20we%20dont%20have%20access%20to%20the%20logs.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16089%22%20slang%3D%22en-US%22%3ERe%3A%20Get%20Outlook%20versions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16089%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20check%20the%20Activity%20logs%20in%20the%20SCC%20(%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2F%23%2Funifiedauditlog%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fprotection.office.com%2F%23%2Funifiedauditlog%3C%2FA%3E).%20For%20example%2C%20filter%20by%20%22Created%20or%20received%20message%22%20then%20export%20the%20logs%20to%20CSV%2C%20the%20client%20information%20will%20be%20visible%20there.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16059%22%20slang%3D%22en-US%22%3ERe%3A%20Get%20Outlook%20versions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16059%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20100%25%20sure%20this%20will%20work%20against%20EXO%2C%20but%20used%20this%20in%20an%20on%20prem%20version%20last%20week%20and%20it%20worked%20great%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fmikefrobbins.com%2F2014%2F09%2F18%2Fuse-powershell-to-determine-what-outlook-client-versions-are-accessing-your-exchange-servers%2F%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fmikefrobbins.com%2F2014%2F09%2F18%2Fuse-powershell-to-determine-what-outlook-client-versions-are-accessing-your-exchange-servers%2F%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Alan McFarlane
Contributor

How do I get a report/etc of Outlook versions connecting to EO? I presume on-prem I would use Get-LogonStatistics which isn't available on EO. I can't see a suitable report in new or old admin portal.

 

I ask as we got this Message in one of our client tenants. Maybe a Mac Office version issue?

[[

    Updated Feature: Web support for Outlook 2007 and 2010

    /!\ Action required by Oct 25, 2016

    [...] You are receiving this message because our reporting indicates you have at least one user in your organization connecting to Office 365, using either Outlook 2007 or Outlook 2010. [...]

]]

7 Replies

Not 100% sure this will work against EXO, but used this in an on prem version last week and it worked great: 

 

http://mikefrobbins.com/2014/09/18/use-powershell-to-determine-what-outlook-client-versions-are-acce...

You can check the Activity logs in the SCC (https://protection.office.com/#/unifiedauditlog). For example, filter by "Created or received message" then export the logs to CSV, the client information will be visible there.

@Paul Bridges no, this will not work against EO, as we dont have access to the logs.

Ahh - didn't even think about that. Sorry, early morning brain fart, ha. 

Thanks Vasil. I'll look at that again then. I didn't have it enabled on the respective tenant but it is now!

 

On another tenant I looked and there were no useful entries. I wonder why??

 

Ahh needs turned on for all individual mailboxes?  Yeh?  https://support.office.com/en-gb/article/Search-the-audit-log-in-the-Office-365-Security-Compliance-...

Yup, you need auditing enabled on each mailbox for the events to be gathered. Otherwise you can rely on the Logon events, but in my experience they're not that reliable client version-wise.

 

Another option is to try Get-ConnectionByClientTypeReport, though it only lists the protocol (OWA/EWS/EAS/etc).

 

If you are running AD FS, you can also get the client info from the event logs.

 

Thanks Vasil. I turned on the auditing last night and will see what today's logging brings.

 

Yup, had tried that. But not even client name (never mind version) AFAICS.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Discussion - Updating our interface with Fluent touches
Elliot Kirk in Discussions on
102 Replies