Multi-Company Microsoft Outlook Integration – Odoo Mail Server Setup
by Creyox Technologies https://www.creyox.com$ 489.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 242 |
| Technical Name |
cr_multi_company_microsoft_outlook |
| License | OPL-1 |
| Website | https://www.creyox.com |
| Versions | 15.0 16.0 17.0 18.0 19.0 |
Multi Company Microsoft Outlook Integration
Domain-wise Microsoft 365 account setup in Odoo. Configure separate Outlook OAuth2 credentials (Client IDs & Client Secrets) for each company in a multi-company database.
Overview
Multi Company Microsoft Outlook Integration is a premium, essential Odoo extension designed for multi-company or multi-tenant Odoo setups. By default, Odoo restricts databases to a single, global Azure Application Client ID and Client Secret in General Settings. Consequently, all companies and email servers must use the exact same Azure credentials, breaching security boundaries and preventing businesses from using separate Outlook/Office 365 tenants.
Our module bypasses this core limitation by introducing Outlook OAuth Instances. You can now register distinct Azure App registrations (separate Client IDs & Client Secrets) for each company in Odoo. Both Outgoing (SMTP) and Incoming (IMAP) mail servers can be linked to their respective company instances, preserving domain isolation, security compliance, and clean mailing headers across all business units.
Standard Odoo Flow vs. Multi-Company Flow
Standard Odoo Flow
- Single Global Credentials: Forced to use one Azure App Registration (one Client ID / Secret) database-wide.
- Shared Microsoft Tenant: Inability to connect different Microsoft 365 organizations/tenants for different subsidiaries.
- SPF/DKIM Domain Mismatches: Sending mails for Company B using Company A's Outlook credentials flags them as SPAM.
- Security Risks: Sub-companies share a single set of access tokens, violating basic data isolation guidelines.
Multi-Company Flow
- Company-wise OAuth Instances: Register separate Azure Apps (different Client IDs/Secrets) per company.
- True Multi-Tenant Isolation: Seamlessly integrate distinct Microsoft 365 organizations across separate corporate domains.
- Clean SPF & SPF Alignment: Deliver emails from Company B using Company B's authentic Outlook servers, ensuring inbox delivery.
- Independent Access Controls: Security boundaries are strictly maintained between sister companies.
Multi-Company Separation
Separate Outlook OAuth configurations. Keep credentials, tokens, and scopes fully isolated for each Odoo company.
Native Mail Server Hook
Hooks directly into Odoo's standard Outgoing (SMTP) and Incoming (IMAP) mail server configuration forms.
Azure Multi-Tenant / Single-Tenant
Compatible with both single-tenant and multi-tenant Azure AD app registrations across separate corporate tenants.
Microsoft Graph API Security
Fully secure token-based OAuth2 authentication protocol. Eliminates basic authentication and insecure passwords.
Auto Token Refresh
Background token refreshing keeps mail fetchers and senders running without requiring manual re-authentication.
No Custom Controller Setup
Employs Odoo's standard callback routes. Safe, robust, and clean redirect URI flow.
Standard Odoo Outlook Setup vs. Custom Outlook Instances
By default, Odoo restricts databases to a single, global Microsoft Outlook OAuth credential configured in General Settings. This prevents multiple companies from using separate Outlook tenants. Our module introduces the Outlook OAuth Instances model, allowing you to configure independent Client IDs and Secrets for each company. Avoid setting the credentials globally in General Settings; instead, follow the steps below to configure company-specific instances.
Access Outlook OAuth Instances Configuration
Navigate here to configure the Outlook OAuth Instances.
Overview of Outlook Instances
Here you can see the list of all configured Microsoft Outlook Instances. Click on the New button to create a new instance configuration.
Configure Outlook Instance Details
Enter the instance Name, select the Company, and input your Microsoft Azure Client ID and Client Secret. Copy the generated Redirect URI and add it to your Azure App registration.
Configure Outgoing Mail Servers (SMTP)
Navigate here to configure or view Odoo's Outgoing Mail Servers.
Link Instance and Authenticate SMTP
Set "Authenticate with" to "Outlook OAuth Authentication", then select the corresponding company Outlook Instance. Authenticate the account to obtain the OAuth token, and click Test Connection to confirm success.
Configure Incoming Mail Servers (IMAP)
Navigate here to configure or view Odoo's Incoming Mail Servers.
Link Instance and Authenticate IMAP
Set "Server Type" to "Outlook OAuth Authentication", then select the corresponding company Outlook Instance. Authenticate the account to obtain the OAuth token, and click Confirm to verify the incoming connection.
Frequently Asked Questions
Why do I need this module if Odoo already supports Outlook integration?
Can I connect mailboxes from completely different Microsoft 365 tenants?
Do I need to manually refresh tokens?
Is this app compatible with Odoo Community as well as Enterprise?
Is this app compatible with Odoo Online?
How to contact if there is need of any Customization?
Do I get free support when I buy these app?
Do I need to buy all versions separately?
The app I paid for is not working, what should I do?
Our Services
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