A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Dear @rajesh kumar,
Thank you for reaching out to the Microsoft Q&A forum. I’m happy to assist you.
Since your data‑movement workflow works correctly for a custom SharePoint library but fails specifically for the default “Documents” library, this issue is very likely related to configuration or permission behavior inside your tenant. These backend details (such as library internal paths, permission inheritance, API responses, or connector authentication) cannot be reviewed or accessed through this community forum.
As a forum moderator, my role is limited to providing general guidance. I do not have access to your tenant backend, diagnostic logs, or internal SharePoint/Logic Apps configuration, so I’m unable to verify what is causing the connector to skip the “Documents” library.
Because this issue impacts a core SharePoint site library and requires a deeper investigation, I strongly recommend opening a support ticket so the Microsoft engineering team can review your tenant and connector logs directly. The Global Admin can create a support ticket by sign in to the Microsoft 365 Admin Center > Support > Help & Support.
For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin.
Note: If you’re an end-user, please coordinate with your Office 365 Global Administrator to handle these steps. If you receive any update from Support or additional information, feel free to share it here so the community can learn from your findings.
If you need any further assistance, feel free to reach out. I am here to help. Thank you very much for your understanding and your cooperation.