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 running "Start-HawkTenantInvestigation" after the connection to Microsoft Graph is made, the script throws up;
Select-MgProfile : The term 'Select-MgProfile' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:31 char:9
+ Select-MgProfile -Name "v1.0"
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Select-MgProfile:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Tested on a new Windows 10 Install.
To Reproduce
Steps to reproduce the behavior:
Run "Start-HawkTenantInvestigation"
Make connection to MS-Graph
Expected behavior
No Error ?
Screenshots
If applicable, add screenshots to help explain your problem.
I ran into the same error and ended up downgrading some of my modules. I also fully reinstalled HAWK. You also need to be careful to connect the modules in the exact order they are in the documentation.
Try to downgrade below modules to the provided versions:
AzureAD - 2.0.2.180
Microsoft.Graph - 1.28.0
Sucks you need to be running outdated modules, but just a sacrifice that needs to be made I suppose.
When running "Start-HawkTenantInvestigation" after the connection to Microsoft Graph is made, the script throws up;
Tested on a new Windows 10 Install.
To Reproduce
Steps to reproduce the behavior:
Run "Start-HawkTenantInvestigation"
Make connection to MS-Graph
Expected behavior
No Error ?
Screenshots
If applicable, add screenshots to help explain your problem.
File (please complete the following information):
Additional context
3.4.0 ExchangeOnlineManagement
3.1.0 Hawk
2.18.0 Microsoft.Graph
1.1.183.66 MSOnline
1.10.318 PSFramework
2.1.0 RobustCloudCommand
0.9.6 PSAppInsights
2.0.2.182 AzureAD
The text was updated successfully, but these errors were encountered: