Enforce PS 5.1 limitation in tool in some configurations

[gdasher]

💡 Summary

Some dependencies (at least SPO related modules) require PS 5.1. We should create a more understandable error message in these scenarios by checking the powershell version up front. We could implement this for all invocations, or, for extra credit, determine which baselines work in PS 7 and limit the checks to when the tool is being run for unsupported baselines.

In the later case, we would need to ensure some selection of the automated test suite is run in PS 7 mode.

Motivation and context

Users are confused by current errors when running tool with PS 7,

This would be useful because...

Implementation notes

Acceptance criteria

How do we know when this work is done?

• [ ] Tool runs without error under supported versions of PS and notifies user with a helpful error for unsupported versions of PS.

[schrolla]

This appears to be related to our platform support epic #97 . Recommend adding to it.

[twneale]

I can confirm the AAD baseline works with no problems using certificate auth on PS 7 (on Ubuntu!). The Sharepoint baseline seems to work on PS 7 as well. It has issues with MITRE's http proxy depending on where it's run from, but I don't think that's related to PS version.

[schrolla]

Good to know! I do believe the SharePoint limitations on PS7 are only wrt user auth, not cert auth. The reason being that we had to use different modules to do cert auth as the existing SharePoint libraries we used did not support it at the time and those were the ones with PS7 issues.

[schrolla]

@gdasher Do we still need this issue with the larger multi-platform support epic? I don't recall seeing issues with users running in PS7 as much as we had in the past. May want to instead focus on moving forward on PS7 support?

[schrolla]

Maybe create an exploratory issue to identify all the PS7 technical difficulties and then this focuses on annotating to warn the user appropriately.