OneDrive File Request: Setup, Folder Permissions & Workspace Ingestion

Collecting external documents through email attachments or standard shared folders creates persistent operational and security vulnerabilities. Shared folders with edit rights risk accidental deletion and unauthorized browsing of other clients' submissions, while email attachments scatter unmanaged versions across individual inboxes. OneDrive File Request addresses this intake dilemma by generating an upload-only link where external contributors deposit files directly into a designated folder without viewing other contents, modifying existing records, or authenticating through an account.

OneDrive File Request is a Microsoft 365 feature that creates a secure upload-only link where external users can upload files to a designated folder without viewing folder contents or requiring an account. External contributors access a clean web interface where they drag and drop files and enter their names. When users upload files through this link, they cannot view, edit, delete, or download existing folder files, nor can they identify other contributors who have submitted assets.

+-----------------------------------------------------------------------------+
|                     External Document Ingestion Flow                        |
+-----------------------------------------------------------------------------+
         |                                                    |
  (Client Upload)                                      (Folder Security)
         v                                                    v
+-----------------------------+                      +------------------------+
| Web Browser Upload Form     |                      | Target OneDrive Folder |
| - No Microsoft account      |                      | - Write-only access    |
| - Custom request title      |                      | - Hidden directory tree|
| - Enter First & Last Name   |                      | - Existing files hidden|
+-----------------------------+                      +------------------------+
         |                                                    |
         +--------------------> [ Upload Token ] <------------+
                                      |
                                      v
                       +-------------------------------+
                       | Inbound File Processing       |
                       | - Prepends uploader name      |
                       | - Non-destructive collision   |
                       | - Automated email alert       |
                       +-------------------------------+

Security Boundaries and Inbound File Attribution

The architecture of OneDrive File Request relies on anonymous upload tokens that restrict the recipient strictly to write operations. Unlike standard OneDrive sharing links that expose folder navigation, a file request URL isolates the uploader inside a standalone submission form.

When a file lands in the folder, OneDrive prepends the contributor's entered first and last name to the file name, producing an identifier such as Sarah_Connor_Financial_Statement.pdf. This naming structure provides clear attribution for team reviewers.

To protect data integrity, OneDrive handles identical file names non-destructively. If an external client uploads a file named TaxReturn.pdf and the destination folder already contains a document with that name, OneDrive does not overwrite the existing record. Instead, it appends an incremental number to the file name, saving the new upload as Sarah_Connor_TaxReturn (1).pdf.

Account Types and Platform Availability

OneDrive File Request is available exclusively on OneDrive for work or school accounts associated with Microsoft 365 commercial tenants. The capability is not supported on consumer OneDrive personal accounts (@outlook.com, @hotmail.com, or personal Microsoft subscriptions). Furthermore, Microsoft restricts the feature in sovereign cloud deployments, meaning it is unavailable in Office 365 operated by 21Vianet and Office 365 Germany.

For commercial tenants, the feature functions on top of tenant-wide external sharing policies managed within Microsoft Entra ID and the SharePoint Admin Center. If an organization restricts anonymous link creation, file requests cannot be generated.

• OneDrive File Size Limit: Upload Caps, Sync Bottlenecks, and AI Large-Corpus WorkspacesThe OneDrive file size limit is 250 GB per individual file across all account types, including Personal, Business, and...
• How to Download Files via OneDrive API: Microsoft Graph GuideDownloading a file via the OneDrive API requires requesting the binary stream from a driveItem content endpoint using...
• How to Upload Files to OneDrive via API: Simple PUT vs Upload SessionsUploading files to OneDrive through the Microsoft Graph API requires selecting between simple PUT requests and...
• OneDrive Shared Folders vs. Fast.io Agent Rooms: Solving the Storage GapWhen multiple AI agents and human teams collaborate in a shared folder, traditional sync tools like Microsoft OneDrive...
• Airtable Attachment Limits: File Sizes, Base Storage, and WorkaroundsThe Airtable attachment limit framework caps individual file uploads at 5 GB across all subscription tiers, while...
• AWS Bedrock File Size Limits: Document Constraints in Knowledge Bases and Converse APIAWS Bedrock Knowledge Bases enforces a 50 MB per-document limit for file ingestion, while the Bedrock Converse API caps...

More on this subject: Agent File and Document Workflows (298 guides)

Creating a file request in OneDrive requires only a few steps inside the web interface. Because the request generates an upload portal rather than a shared workspace, the setup process focuses on defining the destination folder and setting clear intake instructions for contributors.

Step-by-Step Procedure to Generate a File Request

Follow these steps to create an upload-only link in OneDrive for Business:

1. Open OneDrive for Business in your web browser and locate the destination folder. File requests must target an existing folder; you cannot attach a request to an individual file or create one on the root directory view.
2. Select the circle next to the folder name to highlight it.
3. In the command ribbon at the top of the screen, select Request files. If the command bar is collapsed, click the three vertical dots next to the folder name and choose Request files from the menu.
4. Under "What files are you requesting", enter a descriptive title for your intake request, such as "Q4 Vendor Invoices and Supporting Schedules". This title appears as the primary heading on the external upload page.
5. Select Next to generate the link.
6. Select Copy link to copy the URL to your clipboard for distribution via email, customer portals, or messaging apps. Alternatively, enter recipient email addresses into the dialog box to send an invitation email directly from OneDrive.
7. Select Done to complete the configuration.

The External Contributor Upload Flow

When an external user opens the file request URL, OneDrive loads a dedicated web interface that eliminates account creation barriers:

• The custom request title created during setup displays prominently at the top of the page.
• A Select files button opens the contributor's native operating system file picker, and users can also drag and drop documents directly onto the browser window.
• If the uploader is not signed in to a Microsoft account, the form prompts them to enter their First name and Last name. This metadata is prepended to the uploaded files.
• Clicking Upload initiates the transfer, accompanied by an active progress bar. Once the transfer finishes, OneDrive displays a confirmation screen offering the option to upload more files.

The external uploader never sees what else resides in the folder, cannot view other people's submissions, and cannot download or delete files after completing the transfer.

Modifying Request Details and Monitoring Uploads

Whenever an external contributor deposits files through the link, OneDrive sends an automated notification email to the user who created the file request. The message identifies the contributor's entered name and includes a direct link to the newly uploaded document.

If you need to change the descriptive title of an active file request, select the target folder in OneDrive, click Request files again, and enter the updated description. Contributors who open the link after the change see the revised text.

How to Stop Requesting Files and Revoke Links

When your intake period concludes or a project reaches completion, you can deactivate the link to prevent further submissions:

1. In OneDrive, locate and select the file request folder.
2. Open the Details pane by selecting the information icon in the upper-right corner.
3. Under Has Access, select Manage access.
4. In the Links tab, locate the file request link.
5. Select the trash can icon or choose Delete link to revoke access.

Once deleted, the link stops functioning immediately. Anyone who attempts to access the URL receives an HTTP 404 error page indicating that the resource is no longer available.

A common obstacle for teams attempting to use OneDrive File Request is finding that the Request files button is missing from the command bar or greyed out in the context menu. This issue almost always stems from tenant-wide external sharing policies or administrative settings within Microsoft 365.

1. Enable Anyone Links in the SharePoint Admin Center

OneDrive File Request operates on anonymous link infrastructure. Disabling Anyone links across a Microsoft 365 tenant automatically disables the Request files feature in OneDrive and SharePoint.

To verify and adjust tenant sharing settings:

1. Sign in to the SharePoint Admin Center as a Global Administrator or SharePoint Administrator.
2. In the left navigation menu, expand Policies and select Sharing.
3. Under External sharing, check the slider for OneDrive. The slider must be set to Anyone. If it is configured to "New and existing guests" or "Only people in your organization", OneDrive disables file request links across the entire organization.
4. Review the link expiration settings under More external sharing settings. Administrators can enforce an expiration period for Anyone links to ensure upload links do not remain open indefinitely.
5. Select Save to apply the configuration.

2. Verify and Enable File Requests Using PowerShell

Even when external sharing is permitted, the specific setting governing OneDrive file requests can be disabled at the tenant level. Administrators can inspect and toggle this setting using the SharePoint Online Management Shell.

Launch PowerShell with administrative privileges and connect to your tenant:

Connect-SPOService -Url https://yourtenant-admin.sharepoint.com

Inspect the tenant configuration:

Get-SPOTenant | Select-Object OneDriveRequestFilesLinkEnabled, CoreRequestFilesLinkEnabled

If OneDriveRequestFilesLinkEnabled returns False, execute the following command to activate file requests across all user OneDrive accounts:

Set-SPOTenant -OneDriveRequestFilesLinkEnabled $True

Administrators can also specify a mandatory expiration window (in days) specifically for OneDrive file requests:

Set-SPOTenant -OneDriveRequestFilesLinkExpirationInDays 30

3. Folder Permissions and Inheritance Requirements

Beyond global administrative toggles, individual user permissions dictate whether the Request files button is available:

• Edit Rights Required: The user attempting to create the file request link must hold Edit or Contribute permissions on the target folder. Users with read-only access cannot create upload links.
• Root Directory Restriction: The button never appears when viewing the root "My files" directory. Users must create or open a subfolder to reveal the option.
• Storage Quotas: If the destination OneDrive account has exceeded its allocated storage quota, incoming uploads will fail even if the link was created successfully.

Diagnostic Troubleshooting Matrix

Automate OneDrive Document Ingestion with Fast.io Workspaces

Sync your OneDrive folders into Fast.io workspaces, index uploaded documents for hybrid search and AI retrieval, and query files through the remote MCP server. Monthly plans start with a 14-day free trial (credit card required).

Start 14-Day Trial

Collecting files through a OneDrive file request link solves the initial challenge of gathering client documentation. However, intake is rarely the final step. Once files arrive, teams must organize, review, audit, and extract information from incoming PDFs, spreadsheets, and scanned documents.

Modern operations increasingly deploy automated AI agents to process these files. Whether auditing financial statements, reviewing legal contracts, or extracting vendor invoice details, software agents need programmatic access to newly ingested documents.

Limitations of Direct OneDrive API Connectors

Connecting AI agents directly to OneDrive through Microsoft Graph introduces architectural and operational hurdles:

• API Throttling and Rate Limits: Microsoft Graph enforces strict per-tenant throttling thresholds. When an automated agent attempts to scan and read batches of incoming files, Graph endpoints return HTTP status code 429 (Too Many Requests), delaying execution pipelines.
• Prompt Context Window Bloat: Direct cloud connectors pull entire document payloads into the model prompt. Loading multi-megabyte PDFs or complex spreadsheets into an agent context window consumes tokens rapidly, increases API inference costs, and degrades reasoning performance.
• Overly Broad Tenant Permissions: Granting an agent direct Microsoft Graph access often requires delegated permissions like Files.Read.All, which exposes corporate files across the entire tenant rather than scoping access strictly to the intake folder.

In connector benchmarks across cloud storage providers in Claude Cowork (published at https://fast.io/benchmarks/), Fastio was measured the fastest and the lowest cost of the providers tested.

Decoupling Intake with Scheduled Cloud Sync and Remote MCP

Rather than forcing AI models to query OneDrive directly over rate-limited APIs, teams can decouple document collection from document processing. Organizations maintain OneDrive as their client-facing upload surface while routing incoming assets into an intelligent workspace:

1. Client Submission: External contributors upload files using the standard OneDrive file request link.
2. Cloud Sync to Fast.io: Using Cloud Sync for OneDrive, the intake folder synchronizes into a Fast.io workspace. Cloud Sync operates one-way or two-way, on a schedule or on demand (never continuous, live, or real-time).
3. Automated Semantic Indexing: When files arrive in the Fast.io workspace, Intelligence Mode auto-indexes content for hybrid search (combining full-text keyword matching and semantic search).
4. Targeted Agent Access via MCP: Autonomous AI agents connect to the workspace through the remote Fast.io MCP server (https://mcp.fast.io/mcp/tools) using consolidated MCP tools. Instead of reading whole folder trees, the agent executes targeted semantic queries against indexed files and extracts relevant passages.

While OneDrive File Request works well for organizations standardized on Microsoft 365, it introduces an administrative compromise: enabling the feature requires turning on tenant-wide Anyone links, which relaxes external sharing policies across the entire company.

For teams that require secure document intake without altering global tenant security baselines, Fast.io provides purpose-built Receive Shares within shared workspaces.

Purpose-Built Receive Shares vs. OneDrive File Request

Fast.io Receive Shares allow organizations to create dedicated upload portals on any workspace folder without enterprise-wide policy changes:

• Isolated Folder Links: Create public upload portals for external clients without enabling anonymous links across your entire organization.
• Branded Client Experience: Configure custom branding, project logos, and clear upload instructions to deliver a professional client presentation through branded file sharing.
• Granular Expiration and Access Controls: Set link expiration dates, access passwords, or per-recipient access restrictions directly in the share settings.
• Structured Data Extraction: Using Metadata Views, incoming documents such as invoices, receipts, and contracts are automatically converted into typed schema fields (Text, Integer, Decimal, Boolean, URL, JSON, Date & Time) without configuring OCR templates.

Version History, Auditability, and Collaborative Notes

Every document deposited in a Fast.io workspace is tracked by per-file version history and a detailed activity log. If a client uploads an updated version of a file, previous revisions remain accessible, allowing teams to review changes over time. The audit log maintains a detailed record of upload times, contributor identities, and file access events.

Teams can also use Collaborative Notes to maintain real-time checklists, intake logs, and internal review summaries alongside ingested files, allowing human team members and AI assistants to coordinate inside the same workspace context.

Transparent Subscription Plans and Commercial Model

Fast.io operates on a transparent subscription model. Monthly plans start with a 14-day free trial (credit card required); annual billing is paid upfront with no trial. Plans scale with organizational storage and AI processing requirements:

Credits meter AI work, including semantic search indexing, natural language queries, and Metadata Views extraction. Storage and team seats come included with each plan. Extra storage beyond plan limits is billed at 1.5 cents per GB per month, and additional bandwidth is billed at 4 cents per GB.