SharePoint Team Sites Without M365 Groups Not Visible in AppFlow

Question

We're using Amazon AppFlow with the SharePoint Online connector (AWS-managed client app) to transfer documents to S3.
Issue: When selecting SharePoint sites during flow configuration, Team Sites created without Microsoft 365 Groups are not appearing in the site dropdown, even though the authenticated user has access to these sites.
Questions:

Does AppFlow support SharePoint Team Sites without M365 Groups (STS#3 template)?
Is there a documented list of supported SharePoint site templates?
What workarounds exist to access these site types?

Setup Details:

AWS-managed client app with delegated permissions (Sites.Read.All, Sites.ReadWrite.All)
User has verified access to the missing sites
Region: [your region]

Thank you for any clarification on this limitation.

re:Post Agent · Answer

Based on the available information, there are some limitations with the Amazon AppFlow SharePoint connector that may explain your issue.

The Amazon AppFlow connector for Microsoft SharePoint Online is designed specifically to transfer documents and metadata from SharePoint document libraries to Amazon S3. The documentation doesn't explicitly mention support or lack of support for specific SharePoint site templates like STS#3 (Team Sites without M365 Groups).

There is no documented list of supported SharePoint site templates in the provided information. The connector requires specific permissions for the Microsoft Graph API, including `Sites.Read.All`, `offline_access`, and `User.Read`, which you have correctly configured.

As for workarounds, you might consider:

1. Using scheduled flows instead of on-demand flows if possible. Scheduled flows perform incremental data transfers after the initial full transfer, which might help with performance.

2. If you're using your own app registration (rather than AWS-managed), ensure you've granted all the necessary permissions in the Microsoft Azure portal.

3. Verify that the sites in question have document libraries that can be accessed by the user credentials you're using with AppFlow.

It's worth noting that the AppFlow SharePoint connector has several limitations - it only supports document libraries (not SharePoint Lists), doesn't support partitioning options that are available for other sources, and always transfers entire document libraries when run on-demand. These limitations suggest that site template support might also be restricted, though this isn't explicitly confirmed in the available information.  
**Sources**  
[Unable to Access SharePoint Lists via AWS AppFlow Connector | AWS re:Post](https://repost.aws/questions/QUXdvTWcPVSf6kL4bvwe90Lw/unable-to-access-sharepoint-lists-via-aws-appflow-connector)  
[No partitioning option possible when connecting AppFlow to Sharepoint? | AWS re:Post](https://repost.aws/questions/QUS8j9TTnVQRmte7A0v67MoQ/no-partitioning-option-possible-when-connecting-appflow-to-sharepoint)  
[Microsoft SharePoint Online connector for Amazon AppFlow - Amazon AppFlow](https://docs.aws.amazon.com/appflow/latest/userguide/connectors-microsoft-sharepoint-online.html)  
[Appflow using Microsoft sharepoint always downloads all files for every App flow run and other questions | AWS re:Post](https://repost.aws/questions/QUtHgpJE49TKGe61BRS8kzcg/appflow-using-microsoft-sharepoint-always-downloads-all-files-for-every-app-flow-run-and-other-questions)

SharePoint Team Sites Without M365 Groups Not Visible in AppFlow

Add your answer

Relevant content