To automatically copy files from a SharePoint site in Tenant A to a SharePoint site in Tenant B while adhering to your company's policies, you can consider using Microsoft Power Automate (Flow) with some adjustments to accommodate the limitations you've mentioned. Here are some suggestions:
- Use Power Automate with Batch Processing: Since Power Automate has limitations on file size and path length, consider breaking down the file transfer into smaller batches. You can create flows that trigger on a schedule (e.g., every hour) to check for new or modified files in Tenant A and then copy them to Tenant B. This way, you can manage larger files by processing them in smaller chunks.
- Utilize SharePoint API: If Power Automate's limitations are too restrictive, you could consider using the SharePoint REST API or Microsoft Graph API to programmatically handle file transfers. This would require some development work but can provide more flexibility and control over file handling, including larger files and complex directory structures.
- Consider Azure Logic Apps: If your organization has access to Azure, Azure Logic Apps can be a more robust alternative to Power Automate. It allows for more complex workflows and can handle larger files and more intricate directory structures.
- Manual Migration for Large Files: For particularly large files that exceed Power Automate's limits, consider a manual migration approach for those specific files, while automating the transfer of smaller files.
- Monitor and Optimize: Regularly monitor the performance of your flows or API calls to ensure they are working as expected and optimize them as necessary.
By combining these approaches, you should be able to effectively manage the transfer of files between the two tenants while adhering to your company's policies.
References: