cisagov/ScubaGear

Prerequisites This issue has an informative and human-readable title. Assignee should meet with issue author before starting work. 💡 Summary We only have instructions for users to install ScubaGear from PS Gallery or download the official release bundle from GitHub. Often times we have to direct users to download and run ScubaGear code from the main branch or specific fix branches. Currently there is no central documentation page to direct users to so we end up re-creating the documentation on the fly each time. Motivation and context It is more efficient to have central documentation and send users a link to it than recreating the wheel every time. Implementation notes Create a new /docs/installation page named activedevbranch.md The title of the page should be "Download and Execute Latest ScubaGear Development Branch". Under the page change the instructions to the steps I have below. Feel free to enhance this. Go to https://github.com/cisagov/ScubaGear Download the zip file of

Prerequisites This issue has an informative and human-readable title. Assignee should meet with issue author before starting work. 💡 Summary Currently the tenant domain name is only displayed on the ScubaGear report overview page. It would be helpful to have the domain name included on individual reports such as for Entra, Sharepoint, etc. Here is the overview page. Here is the product report page (notice there is no tenant domain name). Motivation and context Many organizations, including our dev team, work with multiple tenants and having the domain name information handy when viewing a product report helps to better track which specific tenant was assessed. Implementation notes Implement the domain name as described above. Acceptance criteria Developer has implemented the actions above and conducted proper testing

Prerequisites This issue has an informative and human-readable title. Assignee should meet with issue author before starting work. 💡 Summary Review all implementation steps to ensure they match the current UI and that we're giving incorrect instructions Motivation and context The implementation steps of the Teams baseline should be checked against the UI to ensure that the implementation directions are accurate. Implementation notes See some of the comments on #1974 for examples of where there are some discrepancies in the implementation steps. Acceptance criteria Verify that the implementations steps match the current UI Update any implementation steps which with current UI

Prerequisites This issue has an informative and human-readable title. 💡 Summary Add some discussion so that users understand that there are two different places where the settings are configured: the Entra portal and the Entra admin center. Review all implementation steps to ensure they match the current UI and that we're not mixing up the two places Motivation and context The implementation steps of the Entra ID baseline use both the Entra portal and the Entra admin center, depending on the baseline policy. It is easy to confuse the two locations. Some of the implementation steps we give actually confuse the two, as in we say to use the Entra portal but our instructions more closely resemble that Entra admin center. Implementation notes See some of the comments on #1974 for examples of where there are some discrepancies in the implementation steps. Acceptance criteria The fact that there are two different locations where the settings are configured is highlighted Verify tha