Missing CMDlets about 365inspect HOT 20 CLOSED

OK, think I figured it out.. my account has MFA enforced

from 365inspect.

That would certainly do it. If your session wasn't authed to the Security and Compliance module you wouldn't see some of those commands.
Thanks for hanging in there!

from 365inspect.

Hi there!
Thank you for using 365Inspect!
These cmdlets all rely on the user running the scripts having the proper permissions, and connecting to the Security and Compliance Center via PowerShell. The script handles these session connections, but cannot determine if the user running them has the correct permissions to run each command - in the case of these particular cmdlets, ATP/Defender licensing and permissions. If you could validate that those licenses and permissions are correct, we can begin to look further into this issue.

I can confirm that the cmdlets are still present in the Exchange PowerShell module version 2.0.5

The cmdlets listed with tmp_* as the source, are imported functions from the Exchange Online module
Get-SafeLinksPolicy
Get-DlpCompliancePolicy

from 365inspect.

from 365inspect.

Your license structure looks correct - both the RIGHTSMANAGEMENT_ADHOC and O365_BUSINESS_PREMIUM licenses should grant you access to these cmdlets if you have the appropriate roles. Due to the use of the two Graph modules and the requirement of admin consent, we recommend Global Admin role (we are actively working towards reducing the required permissions as much as possible), but for those specific cmdlets Security Reader or Global Reader roles should be sufficient to return the results of inspectors. Security and Compliance Permissions
If you are able to retrieve the results when running the tool, and hold the appropriate roles, then the error messages are just odd. Unfortunately, we cannot troubleshoot the modules themselves, but we're always happy to try to help as much as possible to get you into a good spot while using our tool!

from 365inspect.

from 365inspect.

Interesting.
What results do you get when you run this?

$Username = Read-Host -Prompt "Enter your UserPrincipalName (eg [email protected] or user @mycompany.onmicrosoft.com)"
Connect-ExchangeOnline -UserPrincipalName $Username -ShowBanner:$false
Connect-IPPSSession

$cmdlets = @("Get-DlpCompliancePolicy","Get-DlpSensitiveInformationType","Get-SafeLinksPolicy","Get-SafeAttachmentPolicy")

Foreach ($cmdlet in $cmdlets){
    Try{
        Get-Command $cmdlet
    }
    Catch{
        Write-Warning "$cmdlet not found."
    }
}

I would expect something like this (source names will likely be different)

from 365inspect.

from 365inspect.

Unfortunately, it looks like reply by email drops the attachments. Could you paste it into the Issue?

from 365inspect.

from 365inspect.

Can you try the following?

Disconnect-ExchangeOnline 

$Username = Read-Host -Prompt "Enter your UserPrincipalName (eg ***@***.*** or user @mycompany.onmicrosoft.com)"

Connect-ExchangeOnline -UserPrincipalName $Username -ShowBanner:$false

Connect-IPPSSession

Import-Module ExchangeOnlineManagement -Force

$cmdlets = @("Get-DlpCompliancePolicy","Get-DlpSensitiveInformationType","Get-SafeLinksPolicy","Get-SafeAttachmentPolicy")

Foreach ($cmdlet in $cmdlets){
    Try{
        Get-Command $cmdlet
    }
    Catch{
        Write-Warning "$cmdlet not found."
    }
}

from 365inspect.

from 365inspect.

Ok, how about running Disconnect-ExchangeOnline by itself, and then the above commands?

from 365inspect.

same error I'm affraid

from 365inspect.

maybe I should uninstall Powershell and start again. Up early tomorrow so got to go to bed, sorry. Thanks for you help so far

from 365inspect.

No problem.
You can also try installing the modules system-wide as an admin if you haven't already. The script prompt installs for the current user only.

from 365inspect.

Morning. After re-installing Powershell (rebooting in between) I installed ExchangeOnlineManagement and ran the set of commands you sent over. This was the result:

from 365inspect.

from 365inspect.

Hi there!

This seems like an authentication issue to the Security and Compliance center.
This may be due to a difference in your connection URI. Please see Microsoft's documentation about the differences in parameters.

from 365inspect.

Unable to replicate the issue and no response since October. Will reopen in the future if the issue is not resolved.

from 365inspect.