The issue you're experiencing — where the "Scan" option is not visible and
Start-Scan
doesn’t start the job (status remainsIdle
) — is related to an authentication failure in the Microsoft Information Protection (MIP) Scanner.
Based on your logs: MsalUiRequiredException: ErrorCode: no_prompt_failed
This indicates that the scanner attempted silent authentication, but it failed because user interaction was required and not permitted in the current mode.
According to this MS documentation: Resolve issues with MIP Scanner deployment
Please follow these steps to resolve the issue:
Run the scanner in interactive mode - You need to perform an interactive login once to allow the scanner to acquire and cache the necessary authentication token.
Run the following command from an elevated PowerShell session:
Start-Process "msip.scan.exe" -ArgumentList "-interactive"
Re-run the scan - After signing in successfully, you can try to start the scan again:
Start-Scan
Get-ScanStatus
You should now see the scan status changing from Idle
to Running
.
Confirm required permissions - Ensure that the account you're using has the appropriate permissions assigned in Microsoft Entra ID (formerly Azure Active Directory). This includes roles like Compliance Administrator or Security Reader/Administrator.
Review Scanner Configuration:
The content scan job is configured properly
The scanner profile is assigned and enabled
The repositories have valid paths and scan rules applied
You can validate this using:
Get-ScannerConfiguration
References
- Resolve issues with MIP Scanner deployment
- Deploy and configure the Microsoft Purview Information Protection scanner
I hope this information helps.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.