> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/erp/export-to-microsoft-onedrive.md).

# Export to Microsoft OneDrive

**Category:** ERP

**Version:** 1.0

**Last updated:** May 28, 2026

**Author:** Any2Info

***

### Description

The **Export To Microsoft OneDrive** node allows you to upload files from your data flow to Microsoft OneDrive.\
It uses Microsoft Graph APIs to securely store files in your OneDrive environment.

Microsoft OneDrive is a cloud-based storage service that is part of Microsoft 365, allowing users to store, share, and manage files online.\
The Microsoft Graph API provides a unified endpoint to interact with Microsoft services, including OneDrive, enabling secure and standardized access to files and folders.\
By using Microsoft Graph, this node ensures reliable authentication and permission handling.

The node uploads files to Microsoft OneDrive based on the selected input type. The process works as follows:

1. Select a valid **Connection** to Microsoft OneDrive
2. Choose the destination **Folder** using the folder browser
3. Select the **Input type** (File or Base64)
4. Configure the required columns based on the selected input type
5. The node uploads the file(s) to the selected OneDrive folder

***

### Configuration Options

| Setting         | Required     | Description                                                                         |
| --------------- | ------------ | ----------------------------------------------------------------------------------- |
| Connection      | Yes          | Select a Microsoft Office 365 connection or an OAuth2 connection (Microsoft Graph). |
| Folder          | Yes          | Opens a folder browser dialog to select the destination folder in OneDrive.         |
| Input type      | Yes          | Defines how the file is provided: **File** or **Base64**.                           |
| File(s) column  | Yes (File)   | The column that contains the file(s) to upload.                                     |
| Base64 column   | Yes (Base64) | The column that contains the Base64-encoded file content.                           |
| Filename column | Yes (Base64) | The column that contains the file name.                                             |

***

### Input Type

The **Input type** determines how the file content is provided to the node.

#### File

Use this option when working with a column of type **File**.

* The file column already contains:
  * The **file name**
  * The **file content**
* No additional configuration is required besides selecting the file column

#### Base64

Use this option when the file content is provided as Base64-encoded data.

* The Base64 column only contains the **file content**
* A separate **Filename column** is required because Base64 does not include a file name

***

### Tips & Best Practices

* The connection must have sufficient permissions to write files to OneDrive
* Ensure filenames are valid and unique to avoid conflicts
* Use File input when possible for simpler configuration
* Large files may take longer to upload depending on network conditions

***

### Changelog

| Version | Date         | Change                               |
| ------- | ------------ | ------------------------------------ |
| 1.0     | May 28, 2026 | Initial documentation version added. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/erp/export-to-microsoft-onedrive.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.