Cli-microsoft365: Discussion: Office 365 users and Skype For Business Reports

[plamber]

Hello guys,
We are already at a good point with the integration of the usage reports of Office 365 services. Before proceeding with the residual command requests I wanted to have a short alignment with you.

The structure and implementation of Yammer's usage commands will be a no brainer. But on the other hand, we have two other categories that do not necessarily fit in our current setup.

• Office 365 users reports: Link
• Office 365 activation reports: Link
  These are reports that are not necessarily associable with an individual product. Where do we want to place them and how should we call these commands?

Last but not least, there are still many Skype for Business reports. The question is if we still want to invest here considering that Skype will be replaced in near future. Link

Thank you for your feedback.

Patrick

[garrytrinder]

Thanks for raising this issue and starting a discussion, it is much appreciated.

My initial thoughts are that the two Office 365 reports you have mentioned should go under the 'tenant' group which at the moment only contains a single command id, this returns the ID of the Office 365 tenant. The full command path is o365 tenant id so your proposed reports could be implemented as o365 tenant report activeusers and o365 tenant report activations respectively.

For the Skype for Business reports, these could still be useful as Teams uses the Skype for Business architecture behind the scenes to handle calls, messaging etc and as they are present in the Graph I think it will be safe to implement. We should implement these under a new command group like sfb.

As you've mentioned Skype for Business will be replaced by Teams as the communications tool of choice for Office 365 in the future, but I don't think all of the architecture will be replaced anytime soon.

[garrytrinder]

@VelinGeorgiev @waldekmastykarz do you agree with the above approach?

[waldekmastykarz]

I like the proposal for the naming convention of tenant-level reports tenant report xyz.

As for Skype reports, it's hard for me to judge the need for them. I think the community would be a better judge of that. That said, I'm not against implementing them. One suggestion I'd like to make is regarding the commands' prefix. Since we use onedrive for OneDrive for Business, I'd like to propose using skype for Skype for Business to keep things consistent and more user-friendly.

[plamber]

@waldekmastykarz and @garrytrinder

I am going to open the issues for these commands beginning of next year

[waldekmastykarz]

Excellent! Shall we close this issue then and keep the command-specific issues open for tracking?