Odoo's native attachment handling was designed to keep files inside the Odoo filestore, not inside your document platform. For a Microsoft 365-centric organization this creates a painful split: contracts, quotes, and delivery notes live as ir.attachment blobs in Odoo, while the rest of the business collaborates, co-authors, and version-controls documents in SharePoint and OneDrive. Teams download from one system and re-upload to the other, the Odoo filestore balloons on every server and backup it touches, and there is no single place where a file's permissions, version history, and audit trail actually live. Odoo core (base, mail, web) gives you the chatter attachment widget, and Enterprise adds Documents, but neither connects your records to a Microsoft 365 tenant or lets a user co-author a spreadsheet in Office Online straight from a sale order.

This is a made-to-order Odoo module that ECOSIRE builds against your specific tenant and record model. At its core is a clean-room connector to the Microsoft Graph API, authenticated with OAuth2 through a Microsoft Entra ID app registration that you own — so tokens, consent, and data residency stay entirely inside your Microsoft 365 environment. We extend ir.attachment and add supporting models (models.Model with typed fields, @api.depends computes for live sync state, and locked-down ir.model.access.csv plus record rules) so that when a document is attached to a record it is uploaded in the background to a mapped SharePoint document library or OneDrive folder. The Odoo record then shows the live file through a two-way link rather than a duplicated copy, and an "Open in Office Online" action launches Word, Excel, or PowerPoint editing in the browser directly from the chatter and from Documents.

Technically, the sync runs on Graph through a queued, retrying worker (built on Odoo automated actions / ir.cron) that respects Graph throttling and rate limits, records a per-document status (uploaded, linked, failed, retried) in an audit log, and provisions folders from a configurable per-record naming template — for example a dedicated SharePoint folder per sale order or per project. Folder-mapping rules are defined per model, so each res.model you nominate routes to the right site and library, with multi-site and multi-library support for large tenants. Permission mapping aligns Odoo record access with SharePoint sharing links, storage offload shrinks the filestore by keeping the master copy in Microsoft 365, and a one-click bulk migration tool moves your existing Odoo attachments into SharePoint on go-live. Everything is delivered as clean __manifest__.py-declared source with XML/OWL views and works across Odoo 17.0, 18.0, and 19.0 (Community or Enterprise — we confirm your edition during scoping since Enterprise Documents changes some integration points).

Because this is build-to-order, nothing is auto-downloaded. After you request a quotation we run a short scoping call to confirm your tenant setup, the models and libraries in scope, permission rules, and migration volume; then we build, test on a staging database, and install on your Odoo. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company routing, additional models and SharePoint sites, deeper permission/sharing-link mapping, and large existing-attachment migration volumes increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise on delivery.