# Media set syncs

This page discusses how to set up a media set source and sync into Foundry via Data Connection.

The following source types support media syncs:

* [Amazon S3](../../available-connectors/amazon-s3/index.md)
* [OneLake and Azure Blob Filesystem (ABFS)](../../available-connectors/onelake-and-azure-blob-filesystem/index.md)

A growing list of sources support media syncs. However, if your desired file-based source is not yet supported, you can ingest your files within a dataset and convert them into media sets via [Python transforms](../../transforms-python/media-sets/index.md). For example, to ingest files from SharePoint Online into a media set, you can use the [SharePoint Online connector](../../available-connectors/sharepoint-online/index.md) to sync files into a Foundry dataset, then create a Python transform that reads those files and writes them into a media set. The [SMB connector](../../available-connectors/smb/index.md#read-files-from-smb-and-upload-as-media-sets) documentation includes a similar example.

## Set up a media set source and sync

For supported source types, you can also create a virtual media set sync instead of a regular media set sync. Virtual media sets read directly from the external source system without copying files into Foundry's backing store. To set up a virtual media set sync, follow the instructions below but select **Virtual media set sync** instead of **Media set sync**. Learn more about [virtual media sets](../../media-sets-advanced-formats/virtual-media-sets/index.md).

1. Find a supported source by navigating to the **Source** page via **+ New Source**. Then, search for **Media Sync** to find all supported sources.

![Media Syncs.](../../../assets/3e607f33f241a379eef4ca651ad9431ee350466f10cfb0f64203e9fc524b7a43.webp)

2. Ensure you have permissions to import any necessary network policies and then set up the supported source using the appropriate instructions below:

* [Amazon S3](../../available-connectors/amazon-s3/index.md)
* [OneLake and Azure Blob Filesystem (ABFS)](../../available-connectors/onelake-and-azure-blob-filesystem/index.md)

3. In the **Overview** page of the source, find the **Media set syncs** section to create a media set sync.

![Media set sync section](../../../assets/1d71c51bd6963daa7b8f072b5d07a66f2cae295db1bed59a51c515d7ddd309ed.webp)

4. Set up the media set sync by selecting the desired media file types. See [supported media set schemas](../../media-sets-advanced-formats/media-overview/index.md#supported-media-set-schemas).

![Media set sync file type configuration](../../../assets/7a87424aa123159cfd9030bfbef99c9fdacb685130771c04293ddf8df118ae2f.webp)

5. Create the desired build schedule for your media sync ingest. You can edit the schedule after the initial configuration.

![Media set sync schedule](../../../assets/ffbeb0b8c86c0f7b049a54acce9d48a0338bb3d70237fbbca41c6e0d69d1a67c.webp)

6. Select the relevant subfolder within your source. If your media files are at the root path, there is no need to add a subfolder configuration.

![Media set sync subfolder Configuration](../../../assets/b8e8df9697f85fa91c6af9b2b5dee34b64e716379468c5e10f8228c0bf1e35f1.webp)

7. Set up your sync filters. Available sync filters include **Exclude files already synced**, **Path matches**, **File size limit**, and **Ignore items not matching schema**.

![Media set sync filters](../../../assets/ffe42840df5e506d477686326fe34819d760d1fa75d2c0b824902e9de4aa9474.webp)

8. Choose **Save media set sync** when you have selected your initial configuration.

9. Select **Run** to trigger your first sync and view your media sync.

![Run initial media set sync](../../../assets/a298d406ed102335339065abad2c7e40f0280472329204d0fa844c06bb6b4b29.webp)

Once you have set up your media set sync, learn how to leverage your media set with [transforms in Pipeline Builder](../../pipeline-builder/transforms-transform-media/index.md).