Should we focus on Viva / Syntex commands?

[appieschot]

There now is a set of REST api's avialable for working with Syntex (and related to that some of the viva parts as well). More on those here. There might be a somewhat narrow userbase due to licensing requirements, but do we feel we should invest in some CLI commands for those scenarios?

This discussion is both to measure the interests before speccing the commands, as well as to gather any insights. Let us know!

[pschaeflein]

NOT UNTIL THEY ARE ON GRAPH.MICROSOFT.COM!

Releasing APIs only on the sharepoint.com domain is a disservice to devs who have embraced the "the API for Microsoft 365."

[waldekmastykarz]

In the context of CLI for Microsoft 365 it's not relevant to users where the particular API is hosted, so we shouldn't use this as an argument whether to add specific commands or not.

[kevmcdonk]

On the Viva side, I would wait until there are more available. There's been little info recently on when the Topics APIs will be available, no plans on Insights or Learning and Conmections will be mostly SharePoint page related.

Some of the Topics stuff for including external systems will be related to the ExternalConnections in the Graph related to Search and I'm hoping to get that PR in this week (may have a couple of questions @garrytrinder...).

The Syntex ones may be useful but most people who have used them with PnP PowerShell have used them for the sample content to test things out so not sure there would be a massive demand beyond that. Would be very happy to be proved wrong on that though.

[jansenbe]

This is the support we've added for SharePoint Syntex in PnP Core SDK: https://pnp.github.io/pnpcore/using-the-sdk/syntex-intro.html

[kevmcdonk]

Just out of interest Bert, are there any stats on how much the Syntex commands are used?

[jansenbe]

@kevmcdonk : given Syntex is an add-on license the usage is not expected to be very high, but the ones using Syntex are often large companies and they can benefit from automation options.