Skip to Content

Attachment Control - OneDrive

by
Odoo

$ 471.44

v 18.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Community Apps Dependencies
Lines of code 6420
Technical Name attachment_storage_manager_onedrive
LicenseOPL-1
Websitehttps://spre.es/shop/attachment-storage-manager-71
Versions 17.0 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Community Apps Dependencies
Lines of code 6420
Technical Name attachment_storage_manager_onedrive
LicenseOPL-1
Websitehttps://spre.es/shop/attachment-storage-manager-71
Versions 17.0 18.0 19.0
Connector banner
OneDrive connector for Attachment Control

Attachment Control - OneDrive

Add OneDrive as a storage backend for Attachment Control so routing, audit, move, storage archive and restore workflows can work with Microsoft OneDrive through OAuth-based credentials.

OneDrive Microsoft OAuth 2.0 Routing, Move, Storage, Restore Optional Connector Add-on
Availability: Odoo Online: not recommended | Odoo.sh: generally supported | On Premise: supported
Support: info@spre.es

What this connector adds

  • OneDrive provider in Storage Credentials: create credentials for Microsoft OneDrive through OAuth 2.0.
  • Credential-based backend usage: the core module can use this provider in routing, move, storage archive and restore flows.
  • Generic backend operations: read, write, delete, list and connection test through the common backend API.
  • Provider isolation: Microsoft-specific OAuth and Graph API logic stays outside the core module.
Opt-in only: installing this connector does not send data to OneDrive by itself. External communication only starts after the user creates and validates a OneDrive credential and explicitly selects it in the corresponding configuration or workflow.
Data sent only after opt-in: attachment binary content, remote path/folder information, and the technical metadata needed by the selected workflow, such as filename, mimetype, file size or checksum when available.
No data is sent to the developer. Data is sent only to the Microsoft APIs explicitly configured by the user.

Compatibility

  • On-premise: supported.
  • Odoo.sh: supported if outbound HTTPS access to Microsoft login and Graph APIs is allowed.
  • Odoo Online: not supported for this connector because custom module code and callback routing are outside normal Odoo Online constraints.
Why a separate add-on? The core module remains provider-agnostic and only this connector knows how to handle Microsoft OAuth, token refresh and Graph API operations.

Requirements

  1. Install the core module Attachment Control.
  2. Ensure the Python dependency requests is available in the same Python environment used by Odoo.
  3. Install this connector module attachment_storage_manager_onedrive.
  4. Configure Microsoft application registration and the exact callback URL used by Odoo.

Microsoft OAuth setup

Get Microsoft app credentials: open https://entra.microsoft.com and go to App registrations.
1. In Microsoft Entra / Azure App Registration, create an application registration.
2. Add a Web redirect URI with this exact callback:
https://your-odoo.example.com/attachment_storage_manager_onedrive/oauth/callback
3. Create a Client Secret and copy its value, not its secret ID.
4. Use the correct supported account types according to your use case. Personal accounts and work/school accounts do not always use the same tenant endpoint.
5. The connector can work with both personal and work/school accounts. If the app is registered only for personal accounts, the connector can fall back from common to consumers automatically during authorization.
Important: the redirect URI must match the effective web.base.url of Odoo exactly, including scheme and domain.

Credential fields

Access Key / Client ID: the Microsoft application (client) ID.
Secret Key / Client Secret: the value of the client secret created in Microsoft Entra, not the secret identifier.
API Token: used as the OAuth Refresh Token. Leave it empty the first time; it is stored automatically after a successful OAuth authorization flow.
Container / Bucket: optional OneDrive Drive ID. Leave empty to use me/drive.
Path Prefix: optional folder path created/used under the selected drive.
Endpoint URL: optional advanced Graph API base override. Leave empty in normal setups.
Extra Parameters (JSON): optional advanced settings such as custom base URLs, timeout values or a fixed tenant.
Free accounts and normal usage: do not use Container / Bucket as a folder name. In OneDrive this field is an advanced Drive ID. For personal accounts and normal setups, leave it empty and use Path Prefix for the folder path. 
{
  "tenant": "common",
  "timeout": 30
}
Important: if you use a personal Microsoft account and the application is registered only for consumer accounts, the connector may need consumers instead of common.

How it is used

1. Create a OneDrive credential in Storage Credentials.
2. Fill Client ID and Client Secret. Leave API Token empty for the first authorization.
3. Click Test Connection. Odoo opens the Microsoft OAuth flow in a new window.
4. Approve access. Odoo stores the refresh token automatically and validates the credential.
5. Select that credential in the corresponding routing or storage configuration of the core module.
6. Use audit, move, storage and restore workflows from the core module as usual; this connector only provides the backend integration.

Operational notes

  • web.base.url must match your public HTTPS URL.
  • Behind a reverse proxy, enable proxy_mode = True and pass the correct HTTPS scheme to Odoo.
  • If Microsoft does not return a refresh token, re-consent may be required.
  • If authorization fails with an audience or tenant mismatch, review the supported account types in Microsoft Entra and the configured tenant in the credential.
  • For long-running jobs, configure limit_time_real_cron = 3600 in odoo.conf.

Operational safety

Important: we recommend carrying out all tests beforehand in a test database and making a complete backup before any intervention. We do not assume responsibility for possible incidents, misuse or data loss that may occur during its use. 
Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.