...
Select a different user: Depending on what you need the scan to do, you may need to select a different user. Read-only access is sufficient for scanning and classifying content, but Move most actions will fail for read-only users. While Approval, Email, and Remediate actions will work for a read-only user, all other actions (Apply Metadata, Delete, MIP Label, Modify Permissions, Move, Remove Permissions, or Remove Shared Links) will fail since they require edit rights. For some platforms, you can’t create a data source using a disabled user because access to the account and content is restricted.
Update the user within the platform: Someone may be able to log into the platform and update the user.
Continue with the selected user: The scan may perform properly with the selected user. You can attempt to continue with the selected user.
Note that different platforms treat read-only and disabled users differently. As noted above, read-only access is sufficient for scanning and classifying content, but if a policy uses a Move actionan action that requires editing content (Apply Metadata, Delete, MIP Label, Modify Permissions, Move, Remove Permissions, or Remove Shared Links), the action will fail since a read-only user account doesn’t have sufficient access to move content on complete the platformaction.
Below is an example of scan results for a Box data source set up to impersonate a read-only user. The policy contains a tracking group that uses the Move action when content is classified as part of this tracking group. Note that the scan succeeded and that a tracking group was successfully assigned. However, the action failed since the account doesn't have sufficient access to move content as required by the action set for the tracking group.
...