MS.SHAREPOINT.4.2v1 functional test fails in SPO mode for GCC high test tenant about scubagear HOT 3 CLOSED

Suggest changing [0] index in testplan commands for Set-SPOSite to [1] after verifying across all test tenants, that this index is a site (in all cases) that accepts the -DenyAddAndCustomizePages property option.

from scubagear.

I believe this is the same issue that Crutch previously posted about: #622

• I am not sure that we can hard code the index to [1]. If I remember correctly, we need to get the configuration information for the top level Sharepoint site which follows the convention https://tenantName-admin.sharepoint.com. We cannot assume any order in the sites listed by Get-SPOSite.
• Below is some code that we can use for the functional test based on what Crutch recommended and it worked for me. The part that is different from the existing functional test is the tailored Get-SPOSite command to get the top level site.

$Site=[System.Uri]((Get-SPOSite -Limit All | Where-Object {($_.Url -NotLike '*-my*') -And ($_.Url -Like '*/') }).Url);Set-SPOSite -Identity "$($Site.Scheme)://$($Site.Authority)" -DenyAddAndCustomizePages:$false

• Although we can fix the functional test case now, we should discuss the long-term impacts of Microsoft's changes to custom script settings 4.2 and 4.1 with @ahuynhMITRE via #977 so that we know how to modify Scuba + ScubaGear if needed.

from scubagear.

Closing as duplicate of #622

from scubagear.