Bitrix24 and Microsoft 365 Integration: Exchange, SharePoint, SSO

Managers copy emails from Outlook into deal comments, leaders create meetings in the calendar—participants don't see them in Bitrix24. Files are approved in SharePoint, but the deal card holds an outdated version. Sound familiar? We encounter such scenarios daily and know how to automate them. Bitrix24 integration with Microsoft 365 eliminates manual data transfer and reduces approval time by 30–50%. For example, on a project with 200 users, manual calendar synchronization consumed up to 2 hours per manager per week—after automation, it dropped to 10 minutes. Operational cost savings amounted to about 1.5 million RUB per year. Get a consultation—we'll evaluate your project in one hour.

How to Synchronize Outlook and Bitrix24 Calendars?

Calendar synchronization is the first request in integration. Meetings from Outlook appear in B24 and vice versa. Setup:

• In B24: Calendar → Settings → Sync with Outlook / Exchange
• For cloud Microsoft 365—authorization via OAuth 2.0 (Azure AD)
• For on-premise Exchange Server—connection via CalDAV or Exchange Web Services

Synchronized fields:

Nuances:

• Meeting rooms—Exchange resources do not sync with B24. Booking remains in Outlook.
• Invitations—if a meeting is created in B24, participants receive a notification in B24, not an Outlook invitation. And vice versa. Designate one system as primary for meetings.
• Latency—synchronization via Microsoft Graph API updates every 5–15 minutes. For critical scenarios, we configure webhook subscriptions (change notifications).

OneDrive and SharePoint ↔ B24 Drive

Two options for connecting Microsoft cloud storage:

OneDrive (personal). Each employee connects their OneDrive to B24 Drive: Drive → Connect storage → OneDrive. Files are accessible from the B24 interface and can be attached to tasks and deals.

SharePoint (team). For shared document libraries. We connect specific SharePoint libraries to B24 Drive. The entire team sees one file structure.

Features:

• Office documents (.docx, .xlsx, .pptx) open in Office Online directly from B24
• File versioning is managed on the OneDrive/SharePoint side—B24 displays the current version
• Co-authoring via Office Online works when opening from B24
• Limitation: B24 business processes (approval workflows) apply only to files on B24 Drive. Files in SharePoint must first be copied.

Exchange Mail ↔ CRM

Connecting Outlook mail to Bitrix24 CRM links correspondence with client data. Setup:

1. CRM → Mail → Connect mailbox—select Microsoft 365, authorize via OAuth
2. Link to CRM—incoming emails automatically attach to contacts and companies. New addresses create a lead.
3. Send from CRM—email is sent from the deal card through the manager's Outlook account. A copy is saved both in CRM and in the Outlook Sent Items folder.

Additionally:

• Email templates—standard replies with CRM data substitution (name, amount, products)
• Open tracking—the manager sees if the client opened the email
• Routing rules—emails from specific domains are automatically assigned to the responsible manager

For clarity, here are the email integration features:

Why SSO is More Convenient Than Separate Authentication?

Single sign-on via corporate Microsoft account—employees authorize in B24 with the same login and password as in Outlook, Teams, SharePoint. It's 10 times more convenient than remembering different passwords.

Setup for cloud B24:

• Portal → Settings → Authorization → Enable "Sign in with Microsoft"
• Employee clicks "Sign in with Microsoft" → Azure AD confirms → access to B24

Setup for on-premise B24:

1. In Azure Portal → App registrations → create an application
2. Specify Redirect URI (B24 portal address)
3. Obtain Application (client) ID and Client Secret
4. Configure in B24 module "Social Services" settings
5. Set attribute mapping: email, name, department

Comparison of SSO and separate authentication:

Advantages:

• Single management point—blocking an account in Azure AD blocks access to B24
• Conditional Access—Azure AD policies (allowed IPs, devices, MFA) apply to B24 login
• Automatic user creation—on first SSO login, the user is created in B24 with a profile populated from Azure AD (SCIM provisioning—via middleware)

Interaction with Microsoft Teams

There is no direct native integration of B24 with Teams, but working scenarios exist:

• B24 tab in Teams—add the B24 portal as a tab in a Teams channel. The employee opens CRM or tasks without leaving Teams.
• Notifications via webhook—events from B24 (new lead, overdue task, completed approval) are sent to a Teams channel via Incoming Webhook.
• Power Automate—connect B24 REST API and Microsoft Power Automate for automation: task created in B24 → message in Teams; email with keyword in Outlook → lead created in B24.

What's Included

• Two-way synchronization of Outlook Calendar and B24 calendar
• Connection of OneDrive and SharePoint to B24 Drive
• Exchange mail integration with CRM: email linking, sending from card, tracking
• SSO via Azure AD with Conditional Access and automatic provisioning
• Notifications from B24 to Microsoft Teams via webhook
• Automations via Power Automate (B24 REST API ↔ Microsoft Graph API)
• Team training on working with B24 + Microsoft 365
• Documentation on setup and operation, working access, support during implementation

Integration timeline—from 2 to 5 business days depending on complexity. Cost is calculated individually. Contact us to discuss integration details—we'll prepare a commercial proposal within one day. Experience: over 50 integrations, guaranteed transparent reporting and adherence to deadlines.