Salesforce + Microsoft OneDrive for Business Integration — Secure CRM Document Access
Salesforce + Microsoft OneDrive for Business Integration is an API integration and implementation service for organizations that use Salesforce and Microsoft 365 and need unified document access across CRM and cloud storage. Salesforce's native OneDrive connector and Files Connect for OneDrive are retired, so IT Partner implements a currently supported approach instead: an AppExchange connector app (such as CloudFiles or sFiles), Microsoft Power Automate flows, or a custom Microsoft Graph API integration. Files remain in OneDrive, access stays governed by Microsoft 365 permissions, and organizations whose Files Connect integration stopped being supported in April 2026 can migrate to a supported replacement.
What this engagement is
IT Partner connects Salesforce with Microsoft OneDrive for Business so Salesforce records reference documents that remain in OneDrive — no manual uploads, no outdated copies, and access governed end to end by Microsoft 365 permissions, sensitivity labels, and audit logging. An important 2026 reality shapes this service: Salesforce Files Connect for SharePoint Online and OneDrive for Business is effectively retired — Microsoft retired the Azure Access Control Services (ACS) authentication it depended on on November 1, 2024, and grandfathered support for existing setups ended in April 2026 — and Salesforce has also retired its native OneDrive connector. IT Partner therefore implements one of the currently supported approaches: an AppExchange connector app (such as CloudFiles, sFiles, Share Connect, 24Files, or Egnyte) that connects Salesforce to OneDrive and SharePoint directly through the Microsoft Graph API with live document access, per-record folder automation, and reduced Salesforce file-storage consumption; Microsoft Power Automate flows for per-record folder creation and file copy or sync triggers; or a custom integration built on the Microsoft Graph API — or MuleSoft — where requirements are bespoke. The right approach is selected during discovery, and organizations that lost a working Files Connect integration can be migrated to a supported replacement as part of this service. Third-party connector apps carry their own license fees, which are identified during scoping.
Success criteria
What you receive
How the work unfolds
Confirm Salesforce record objects, OneDrive document locations, user access model, automation requirements, and whether a retired Files Connect or native OneDrive connector configuration needs to be replaced. Recommend a connector app, Power Automate flows, or a custom Microsoft Graph API integration, and identify any third-party connector license fees. Acceptance gate: approach and scope approved by the client.
Install and configure the selected connector app or register the integration in Microsoft Entra ID, grant the approved Microsoft Graph permissions, and complete the Salesforce-side connection (connected app or connector configuration).
Configure the agreed Salesforce objects to surface OneDrive documents as secure links, previews, or connected folders, including per-record folder automation where the selected approach supports it.
Align access with Microsoft Entra ID security groups and Microsoft 365 sharing policies so Salesforce users reach only the documents they are licensed and permitted to open.
Configure optional Power Automate workflows where licensed and in scope, run functional testing across representative records, file types, and permission scenarios, and hand over implementation notes and configuration documentation.
Prerequisites
Who does what
IT Partner
- Lead discovery sessions to confirm Salesforce record objects, OneDrive document locations, user access model, automation requirements, and whether an existing Files Connect or native OneDrive connector configuration must be replaced.
- Recommend and design the integration approach — AppExchange connector app, Power Automate flows, or custom Microsoft Graph API integration — including authentication flow, permission assumptions, and link or preview behavior.
- Configure the agreed connectivity: connector-app installation, Microsoft Entra ID application registrations or connected-app settings, and required delegated or application permissions as approved by the client.
- Implement Salesforce-side configuration or development required to surface OneDrive documents as secure links, previews, or connected folders on the agreed records.
- Configure permission alignment using Microsoft Entra ID security groups and Microsoft 365 sharing policies within the approved scope.
- Configure optional Power Automate workflows when licensed and included in the project scope.
- Perform functional testing for representative Salesforce records, OneDrive files, agreed file types, and user access scenarios.
- Provide implementation notes, configuration summary, and handover guidance for the completed integration.
- Support remediation of implementation defects identified during the agreed project validation period.
Your team
- Provide timely access to qualified Salesforce, Microsoft 365, OneDrive, Microsoft Entra ID, and Power Automate administrators as required for the project.
- Confirm the Salesforce objects, record layouts, fields, business process, document naming conventions, and OneDrive locations to be included.
- Approve required API permissions, application registrations, connected apps, connector-app installations, security groups, sharing policies, and any tenant-level security changes.
- Purchase any third-party connector-app licenses if that approach is selected; license fees are identified during scoping.
- Ensure users have the required Salesforce, Microsoft 365, OneDrive for Business, and Power Automate licenses for the agreed scope.
- Provide sample records, sample documents, and test users covering the main permission and workflow scenarios.
- Validate the integration in the client environment, including business acceptance testing and confirmation that links, previews, folders, and alerts work as expected.
- Communicate internal change-management instructions to end users, including that document edits occur in OneDrive and Salesforce references the OneDrive file.
- Maintain ongoing ownership of Salesforce data quality, OneDrive file structure, user membership in security groups, connector-app subscriptions, and licensing after project handover.
What's not included
Limitations & technical notes
Frequently asked questions
What is the Salesforce + Microsoft OneDrive for Business Integration service?
IT Partner connects Salesforce with Microsoft OneDrive for Business so Salesforce records surface OneDrive documents as secure links, previews, or connected folders instead of storing uploaded copies. Files remain in OneDrive, governed by Microsoft 365 permissions. Because Salesforce's native OneDrive connector and Files Connect are retired, the integration is delivered through a supported approach: an AppExchange connector app, Power Automate flows, or a custom Microsoft Graph API integration.
Doesn't Salesforce have a built-in OneDrive connector or Files Connect for this?
Not anymore. Microsoft retired the Azure Access Control Services (ACS) authentication that Files Connect for SharePoint Online and OneDrive for Business depended on on November 1, 2024, and Microsoft's grandfathered support for existing setups ended in April 2026. Salesforce has also retired its native OneDrive connector. Any Salesforce-to-OneDrive integration today must use a supported approach — an AppExchange connector app, Power Automate, or a direct Microsoft Graph API integration — which is what this service implements.
We used Files Connect for OneDrive and it stopped working. Can you migrate us?
Yes — that migration is exactly what this service covers. IT Partner assesses your previous Files Connect configuration (linked objects, document locations, and access model), recommends a supported replacement — a connector app, Power Automate flows, or a custom Microsoft Graph API integration — and implements it so your Salesforce records again reference documents stored in OneDrive.
Which integration approach will IT Partner use?
The approach is selected during discovery based on your requirements, volumes, and budget. The options are: an AppExchange connector app (such as CloudFiles, sFiles, Share Connect, 24Files, or Egnyte) that connects Salesforce to OneDrive and SharePoint through the Microsoft Graph API with live document access and per-record folder automation; Microsoft Power Automate flows for folder creation and file triggers; or a custom Microsoft Graph API integration where requirements are bespoke. Connector apps carry their own vendor license fees, which are identified during scoping.
Do documents stay in OneDrive, or are they copied into Salesforce?
Documents stay in OneDrive for Business. Salesforce records reference them through secure links, previews, or connected folders, so editing, version history, permissions, and audit logging remain in Microsoft 365. This also reduces Salesforce file-storage consumption, because files are not duplicated into Salesforce storage.
How are permissions and security handled?
Access is enforced by Microsoft 365: Microsoft Entra ID security groups, sharing policies, and sensitivity labels continue to govern every linked document, and Microsoft 365 audit logging keeps recording access. A user who is not licensed and permitted to open a file in OneDrive cannot open it from Salesforce.
Can Salesforce users preview OneDrive files without downloading them?
Yes — depending on the selected approach and file type, Salesforce can display secure previews of OneDrive documents. Common business formats such as PDF, DOCX, XLSX, JPEG, and PNG are validated during testing, and users must still be authenticated and authorized through Microsoft 365 to view them.
Does this service provide two-way synchronization between Salesforce and OneDrive?
The default scope is a linking and reference model: documents live in OneDrive and Salesforce references the current version. Some connector apps support richer bidirectional scenarios, and Power Automate can copy files on agreed triggers — those are designed and quoted separately if you need them.
Is Power Automate required for this integration?
No — not for the core integration. Power Automate is required only for optional automation, such as file-change notifications by email or Microsoft Teams, per-record folder creation, or file copy triggers, and those workflows require appropriate Power Automate licensing.
What licenses and prerequisites do we need?
You need a Salesforce org, a Microsoft 365 tenant with OneDrive for Business, and Microsoft 365 licenses for every user who will open linked files. If a connector app is selected, you purchase its license from the vendor — fees are identified during scoping. If automated workflows are in scope, appropriate Power Automate licensing is required.
How long does the integration take, and how is it priced?
The service is billed hourly at the published rate, with total effort scoped per project. A standard engagement is planned at five days, and the final timeline depends on the selected approach, the number of Salesforce objects, the permission model, and any optional automation.
What is not included in this service?
License costs are not included: Salesforce, Microsoft 365, Power Automate, and any third-party connector-app fees are purchased by the client. Also excluded unless separately scoped: large-scale document migration or cleanup, complex Apex or managed-package development, compliance-program design, integrations with other systems, and restoring the retired Files Connect or native OneDrive connector — this service replaces retired products rather than reviving them. 24/7 support, continuous monitoring, and ongoing maintenance are optional paid add-ons.
What happens after the integration is completed?
You receive implementation notes, a configuration summary, and handover guidance, and IT Partner supports remediation of implementation defects found during the agreed validation period. Ongoing monitoring, maintenance, optimization, and 24/7 support are not included by default but are available as optional paid add-ons through IT Partner's NOC, third-party support partnerships, and a Microsoft Premier Support agreement.