Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Get-ProtectionAlert' is not recognized as a name of a cmdlet #312

Open
hanneschu1z opened this issue Apr 29, 2024 · 2 comments
Open

'Get-ProtectionAlert' is not recognized as a name of a cmdlet #312

hanneschu1z opened this issue Apr 29, 2024 · 2 comments

Comments

@hanneschu1z
Copy link

When you run: Get-ORCAReport, the Protection Alert Check fails with the following error:

04/29/2024 11:47:57 Getting Protection Alerts
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.

@BohrenAn
Copy link

@hanneschu1z
This happens if you are connected with Exchange Online
Connect-ExchangeOnline
but not with SSC (Security & Compliance PowerShell )
Connect-IPPSSession

If you're not connected with Exchange Online Orca will ask you twice for a login:
Connect-ExchangeOnline
Connect-IPPSSession
Then it works

image

Kind Regards
Andres

@hanneschu1z
Copy link
Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants