None of the Microsoft.Graph.Beta cmdlets work in GCC High about scubagear HOT 5 CLOSED

ScubaGear version 1.2.0. I'll give this ago again Monday. I'll remove and reinstall the Microsoft Beta modules again. Are you running Scuba from an admin or non admin powershell? Thanks.

Non-admin PowerShell.
ScubaGear has not required an admin PowerShell since before v1.0 .
Security and Compliance PowerShell (Defender) made the transition over to REST cmdlets summer 2023 which allowed us to drop the requirement for an admin PowerShell to run ScubaGear.

from scubagear.

Which version of ScubaGear and the Microsft Graph Beta modules are installed on your client?

For ScubaGear, ensure that you're also running Invoke-SCuBA with the -M365Environment parameter so that ScubaGear will authenticate to GCC High properly.
Invoke-SCuBA -M365Environment gcchigh

Tests against our GCC High tenant are still passing and I just confirmed the beta commands are still working on my end as well with GCC High.

Since this seems to be a MS Graph specific issue try opening an issue over at their repo as well to see if they can help.

from scubagear.

ScubaGear version 1.2.0. I'll give this ago again Monday. I'll remove and reinstall the Microsoft Beta modules again. Are you running Scuba from an admin or non admin powershell? Thanks.

from scubagear.

Invoke-SCuBA -M365Environment gcchigh

Well it looks like the device I was using actually didn't have all the beta modules installed. Thanks for pointing me in the right direction. :-) I got a pretty clean run this time. The report showed 6 Exchange errors. Get-ScubaSpfRecord, Get-ScubaDkimRecord and 4 Get-ScubaDmarcRecord did not execute successfully.

from scubagear.

Feel free to file a separate issue for the failures with errors and we can take a look. We'll go ahead and close this one.

Sometimes we get errors on those in organizations using split horizon DNS, especially if certain fallbacks are blocked.

from scubagear.