---
title: "VAST SyncEngine 3.4.0 Release Notes"
slug: "vast-syncengine-3-4-0-release-notes"
updated: 2026-09-16T08:46:52Z
published: 2026-09-16T08:46:52Z
canonical: "kb.vastdata.com/vast-syncengine-3-4-0-release-notes"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.vastdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# VAST SyncEngine 3.4.0 Release Notes

VAST SyncEngine 3.4.0 has been released in September, 2026. The release includes: ​

## New Features

​​

### OneDrive Connector

​ The OneDrive connector extracts files from Microsoft OneDrive into a VAST S3 bucket. The migration can be include all drives within a certain Microsoft 365 tenant, or it can be limited to drives of certain tenant users. ​ SyncEngine authenticates with credentials of a client application registered with Microsoft Entra ID, reads the drive content through through Microsoft Graph and copies the files to a S3 bucket on the VAST cluster, with OneDrive permissions converted into S3 ACLs.

To learn more about the OneDrive connector, see [Migrate from OneDrive to VAST S3](https://kb.vastdata.com/documentation/docs/migrate-from-onedrive-to-vast-s3-34). ​​​

## Enhancements

- Added an ability to migrate from multiple Confluence, Google Drive or OneDrive stores to the same destination bucket on the VAST cluster, where objects from each source store get an object key prefix specified for that store in migration settings. Prior to this change, each migration required a separate destination bucket on the VAST cluster.  

​​
- You can set rate limits to prevent SyncEngine from causing excessive load on the source store and/or the VAST S3 destination. Rate limits are set when creating a connector. Connectors where rate limits are supported: S3, GCS, Confluence, Google Drive, OneDrive.  

​​
- When migrating from S3 to VAST S3, you can configure SyncEngine to preserve the last-modified date and time that the objects had at the source S3 store. Preserving source object last-modified date and time is supported for migrations from S3 and GCS to VAST S3.  

​​
- The VAST S3 connector lets you specify the VAST tenant where the destination bucket resides. Prior to this change, only default tenant could be used.  

​  

​