Microsoft 365 is missing or needs admin approval
If Microsoft 365 is missing from the available import integrations, ask your Pickit administrator to check your role and whether Microsoft 365 import is enabled for the account.
If Microsoft shows Need admin approval, give your Microsoft 365 administrator the permission request and sign-in error. A Pickit administrator role does not grant Microsoft consent.
A site, folder or source file is missing
For missing subfolder content, edit the import and check that Nested is selected. If the job exceeds 8,000 files, use Direct items or split the folder structure into smaller jobs.
- Open the source in Microsoft with the same account used by the import connection. Confirm that you can read the file there.
- Check the connected Microsoft account. Use Logout in the integration and reconnect with the correct account if needed.
- Try Browse by source → SharePoint and open the site and document library directly. Browse recent files is not a complete inventory.
- Use Show empty folders or Show unsupported files in the integration settings to diagnose hidden results. Unsupported files still cannot be imported.
The job stops or a source update has not arrived
- Open Pickit in the browser where you connected Microsoft. Reconnect Microsoft if requested and leave Pickit open.
- Open Imported assets and check whether the job is queued, running, finished or showing an error.
- Choose Sync again for a manual check. If the problem repeats, record the job time and exact error text.
- Confirm that the source file was saved in the mapped folder and that the connected account still has access. Check the destination library and collection for the updated copy.
The destination collection was deleted
For Sync failed. Collection has been deleted., edit the job from Imported assets. Under Destination, select an existing collection or choose the intended library destination. Choose Save & Import and check the next result.
Do not delete existing imported files just to reconnect a destination. Changing the job does not guarantee that existing files move to a different library.
Check sharing on the imported Pickit copies
First check that the files exist in the destination in Manage. Then check their Pickit sharing settings. SharePoint permissions are not copied to imported assets.
If the import went into Media or Assets without a collection, the files are not automatically shared with all users. Add them to a collection with the intended audience, or select the appropriate file access setting.
If the whole library’s uncollected, inherited files should be shared, an administrator can review Library Settings → Assets → Sharing → Share inherited assets with all users. This changes the audience of those files across the library, so use it only when that is the intended policy. Collections have their own access settings.
What to send support
- The Pickit account and destination library or collection.
- Whether the source is SharePoint, Teams or OneDrive, and the affected folder or file.
- The job’s occurrence, last run time, selected folder options and exact error text.
- Whether the file opens in Microsoft for the connected account, and whether Sync again reproduces the problem.