Ted Kolovos

@mitchelbaker-cisa You can lump this with the quick fix in #1220.

You can probably take care of this one at the same time as well to maximize pull request resources: #1268 If you agree, you can self-assign.

Via hands-on testing, I verified that the MS.SHAREPOINT.4.1v1 (custom scripts for personal OneDrive sites) has been removed from the MS Sharepoint admin portal so @ahuynhMITRE we should remove it from...

Via hands-on testing, I verified that Microsoft changed the way that MS.SHAREPOINT.4.2v1 (custom scripts for self-service (aka Sharepoint sites) is implemented in the admin portal. This impacts our baseline and...

I set the Custom Scripts setting to Allowed at the site level for the following three sites on 7/17. According to Microsoft they were supposed be automatically reverted back to...

Update the status of #622 once we determine if we are keeping or removing Sharepoint policy 4.2. We are currently in back and forth discussions and hands-on testing with Microsoft.

Thank you! - I am good with the action plan to change the Rego to produce an N/A for 4.2 as a short-term implementation. - I am good with updating...

Reassigning to Kraken to balance other bugs and items we have to fix in the short term.

I believe the scope of changes for this issue are going to be to add new code to the Get-PrivilegedUser function to get the list of service principals assigned to...

This is the part of the AAD provider code we would need to augment. The Get-MgBetaDirectoryRoleMember returns a list of items and for service principals the type returned would be...