Misleading graphs in the Admin Center Usage Reports

%3CLINGO-SUB%20id%3D%22lingo-sub-118163%22%20slang%3D%22en-US%22%3EMisleading%20graphs%20in%20the%20Admin%20Center%20Usage%20Reports%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-118163%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20look%20at%20our%20usage%20reports%2C%20it%20visually%20appears%20that%20Exchange%20and%20Yammer%20usage%20are%20roughly%20the%20same%20for%20my%20organization%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F22459i49A1B72B11719040%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22UsageGraphpng.png%22%20title%3D%22UsageGraphpng.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20our%20actual%20Exchange%20number%20is%2050%2C734%20while%20Yammer%20(blue)%20is%2013%2C640.%26nbsp%3B%20The%20problem%20is%20the%20scale%20--%20the%20distance%20from%201%20to%2010%20is%20the%20same%20distance%20as%2010k%20to%20100k%3F%26nbsp%3B%20For%20me%2C%20that%20makes%20this%20graph%20misleading%20at%20best%2C%20and%20unusable%20at%20worst.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-118163%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%20center%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EReporting%20Portal%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-799275%22%20slang%3D%22en-US%22%3ERe%3A%20Misleading%20graphs%20in%20the%20Admin%20Center%20Usage%20Reports%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-799275%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1273%22%20target%3D%22_blank%22%3E%40Kelly%20Jones%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20would%20you%20correct%20this%20data%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-118803%22%20slang%3D%22en-US%22%3ERe%3A%20Misleading%20graphs%20in%20the%20Admin%20Center%20Usage%20Reports%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-118803%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20taking%20time%20to%20provide%20feedback.%20Feedback%20noted.%20Will%20look%20into%20addressing%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-118467%22%20slang%3D%22en-US%22%3ERe%3A%20Misleading%20graphs%20in%20the%20Admin%20Center%20Usage%20Reports%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-118467%22%20slang%3D%22en-US%22%3ETotally%20agree.%20I%20never%2C%20ever%20show%20these%20logarithmic%20scale%20charts%20to%20anyone.%20They%20would%20be%20horribly%20misinterpreted.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-118459%22%20slang%3D%22en-US%22%3ERe%3A%20Misleading%20graphs%20in%20the%20Admin%20Center%20Usage%20Reports%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-118459%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20a%20logarithmic%20scale%2C%20but%20I%20guess%20that's%20a%20valid%20feedback.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F210%22%20target%3D%22_blank%22%3E%40Anne%20Michels%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-799356%22%20slang%3D%22en-US%22%3ERe%3A%20Misleading%20graphs%20in%20the%20Admin%20Center%20Usage%20Reports%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-799356%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390585%22%20target%3D%22_blank%22%3E%40RAYSHON0323%3C%2FA%3E%26nbsp%3BWe%20use%20the%20Adoption%20pack%20for%20Power%20BI%20that%20Microsoft%20released%20a%20few%20years%20ago%20to%20display%20adoption%20stats%20between%20the%20workloads.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F126570i1026F060F40FC940%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22AdoptionGraph.png%22%20title%3D%22AdoptionGraph.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

When I look at our usage reports, it visually appears that Exchange and Yammer usage are roughly the same for my organization:

UsageGraphpng.png

 

However, our actual Exchange number is 50,734 while Yammer (blue) is 13,640.  The problem is the scale -- the distance from 1 to 10 is the same distance as 10k to 100k?  For me, that makes this graph misleading at best, and unusable at worst. 

5 Replies
Highlighted

It's a logarithmic scale, but I guess that's a valid feedback. @Anne Michels

Highlighted
Totally agree. I never, ever show these logarithmic scale charts to anyone. They would be horribly misinterpreted.
Highlighted

Thanks for taking time to provide feedback. Feedback noted. Will look into addressing it.

Highlighted

@Deleted 

How would you correct this data?

Highlighted

@RAYSHON0323 We use the Adoption pack for Power BI that Microsoft released a few years ago to display adoption stats between the workloads.AdoptionGraph.png