PnP can only provide capabilities which have native APIs. There's no bypassing of the native APIs using PnP channels. If there's external API, PnP can though faster provide for example a cmdlet for the capability... but in this case, challenge is simply the lack of existing API to call.
VesaJuvonenhave any changes been made to the APIs that would provide this capability?
MicrosoftNot aware of any programmatic way to control these. Are not at least exposed through the CSOM APIs or through PowerShell.
Thanks for the confirmation. How do they decide which settings can be accessed programmatically? it seems sort of random, some settings can only be configured through code and others can only be configured manually.
MicrosoftThanks Dean for the input. I'm also part of "they", but anyway. There are internal plans always for the specific capabilities and then additional APIs are prioritized based on UserVoice entries or other demand from the field.
are there any plans to expand the scope of the PnP powershell cmdlets to include other services like Delve? It would be great if PnP could fill in the gaps like this.
