The term 'Get-ProtectionAlert' is not recognized

[SamErde]

I ran this with the Exchange Online Management 3.3.0 module in PowerShell 7.3.6 and Windows PowerShell 5.1, and got the following error:

Get-ProtectionAlert: The term 'Get-ProtectionAlert' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Per the docs article for that cmdlet, "This cmdlet is available only in Security & Compliance PowerShell. For more information, see Security & Compliance PowerShell."

It looks like the SCC module should be listed in the pre-requisites and installation section of the README unless I'm missing that detail somewhere already.

[SamErde]

It has been a while since I've used the Security and Compliance module, but it looks like that functionality has been [mostly?] rolled into the Exchange Online Management module along with the Connect-IPPSSession cmdlet.

[SamErde]

Will chip away at this as I find time. A search for that cmdlet only shows up one time in the repo: currently line 644 in the Get-ORCACollection function.

[cammurray]

Hey @SamErde, we run Get-ProtectionAlert since 2.4 for the purpose of ensuring the default alerts (which can trigger AIR, ZAP, etc) are not disabled. You can add -NoSCC to the Get-ORCAReport in order to bypass these checks.

SCC should be inside the Exchange Online Managemement module though?

Can you run Get-Command Connect-IPPSSession?

Do you get any errors (other than the missing command) when running Get-ORCAReport?

[SamErde]

I no longer have access to the environment where I experience this, but will continue to use and update if I see it happen elsewhere. Thanks!