OneDrive · drafts
OneDrive integration in a custom workflow
OneDrive integration means a user in your app can open or save their files via Microsoft Graph, typically as a draft before the document is lifted onto the case in [SharePoint](/articles/integrations/sharepoint-integration). OneDrive is personal. SharePoint is shared. If five people must see the file, it is not OneDrive. We see that mistake in briefs every month. You do not build a new drive. You let the user fetch a draft, edit it in your flow and lift it onto the case when it is shared. Scopes are still the product: Files.ReadWrite on the user’s drive is not Files.ReadWrite.All on the tenant. The hub is [Microsoft 365](/articles/integrations/microsoft-365-integration).
7 min read · Updated 28 August 2026
Calendar and mail are Outlook. Shared documents are SharePoint. OneDrive is only the personal step in between. Automation of the draft.
The split that saves weeks
OneDrive
- The user’s drafts and uploads
- Delegated: on behalf of the person
- No steering group on the file yet
SharePoint
- The case, the customer, the steering group
- Known rights in the tenant
- Five people must see it: here
Fetch
The user picks a file in their own drive.
Work
Your case owns status. The file still lives personally.
Lift
When it is shared, it is copied or moved to SharePoint.
What to do now
Write whether the file is a personal draft or a shared case file. The first is this article. The second is SharePoint. Align it.
FAQ about OneDrive integration
Can the steering group work in OneDrive?
Which scope should OneDrive use?
Must we build a new drive in the app?
Want us to build it for you?
You get a fixed-price proposal within 24 hours.
