You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run Get-ORCAReport, I get an error related to Get-ProtectionAlert: "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."
I find that I need to first run Connect-IPPSSession -UserPrincipalName User@someplace.some before I can use Get-ProtectionAlert interactively, otherwise I get the same error.
I'm running ExchangeOnlineManagement 3.2.0 and running the report from PowerShell 7.3.5.
The text was updated successfully, but these errors were encountered:
Hi @cammurray,
I have tested again from a VM so I can isolate other logins. I do get 2 login prompts, and if I log in to both, the report runs fine.
I think I must have missed the second login prompt, or maybe it used another credential. Most likely I missed it because on my main machine, it pops up in the background for some reason.
Some feedback on the tool and report. We use it to review our configs every 3 months. It provides a great way to keep on top of config drift changes made by some team members, and helps us stay on top of the latest recommendations. THANKS!
When I run Get-ORCAReport, I get an error related to Get-ProtectionAlert:
"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."
I find that I need to first run Connect-IPPSSession -UserPrincipalName User@someplace.some before I can use Get-ProtectionAlert interactively, otherwise I get the same error.
I'm running ExchangeOnlineManagement 3.2.0 and running the report from PowerShell 7.3.5.
The text was updated successfully, but these errors were encountered: