Teams policies 2.2, 2.3, and 3.1 are not applicable for gcc tenants - update results report.

[nanda-katikaneni]

Prerequisites

• This issue has an informative and human-readable title.

ScubaGear Version

v1.5.0

Operating System

Windows 10

PowerShell Version

5.1

M365 Environment and License(s)

M365 Environment: gcc, gcc high, dod
License: GCC E5, GCC E3

🐛 Summary

MS.TEAMS.2.2v1, MS.TEAMS.2.3v1, and MS.TEAMS.3.1v1 policies are not applicable to GCC, GCC High, or DoD regions. Currently ScubaGear results report for gcc/gcchigh regions show these policies as passed. Update ScubaGear logic to make it context/region specific and not test these policies when the tenant is of gcc, gcc high or dod regions; and grey out respective policy results in the report with a note that they are not applicable.

Note that configuration options for these policies on gcc, gcchigh and dod regions are not available and there is no real effect. But these policy results should be updated as N/A based on the tenant type.

Steps to reproduce

1. Run ScubaGear v1.5.0 on a gcc or gcc high tenant for the Teams product.
2. Check the results report to note that policies 2.2, 2.3 and 3.1 have results as passed with green

Expected behavior

1. Run ScubaGear on a gcc or gcc high tenant for the Teams product.
2. Check the results report to note that policies 2.2, 2.3 and 3.1 are greyed out with a note saying that they are not applicable for gcc, gcc high or dod regions (similar to policy 4.1).

Output from Initialize-SCuBA (optional)

No response

[schrolla]

Related to #1548 which changes how N/A results are listed in HTML reports.

[mitchelbaker-cisa]

As it stands right now TEAMS2.2 does not check for the environment type. Only the removal of the note specifying that the policy is not applicable should be removed.

Moving this to Orca as a future baseline update, this issue will act as the implementation after #1692 is complete.