Skip to content
OneLessTool

Guide · updated

Can your existing Microsoft 365 account collect customer files with OneDrive?

Check OneDrive Request Files eligibility, signed-out uploads, isolation, ownership and shutdown before replacing a separate file-collection service.

OneDrive Request Files is worth testing for a simple customer upload job if your work or school account and administrator's policies support it. A personal Microsoft 365 subscription is not enough. The outcome is a folder of submitted files that staff can identify and retrieve, not a questionnaire, authenticated customer portal or approval system.

Start with one bounded request, such as collecting approved artwork for a customer project. This guide evaluates the feature within Microsoft 365 you already keep. It does not establish that every Microsoft 365 plan or tenant has suitable access, storage or sharing permissions.

Check the account and policy before building the process

Microsoft requires OneDrive for work or school, enabled Anyone links and compatible folder-link permissions; its prerequisites also exclude the setting that limits external sharing to specified security groups. OneDrive for home, Office 365 operated by 21Vianet and Office 365 Germany are excluded. Disabling Anyone links disables file requests. Microsoft's administrator requirements.

Ask your administrator to confirm eligibility and approval for the proposed customer files. Microsoft's setup instructions specify folder permissions allowing uploads and a separate OneDrive file-request setting. The page's overview lists View, edit, and upload, while its detailed OneDrive steps also allow View and upload. Have the administrator resolve the applicable configuration; do not change organization-wide sharing policy just to make a missing button appear. Microsoft's OneDrive setup instructions.

If the approved policy forbids this route, keep the existing collection service or ask for an approved alternative. Do not substitute a broadly shared editable folder. For a genuine file-request link, Microsoft documents upload-only access: submitters cannot browse, edit, download or delete folder contents, or see other uploaders. Microsoft's file-request overview.

Separate collection from proof of identity

Customers do not need OneDrive; Microsoft explicitly documents signed-out uploads. A signed-out sender supplies a name that is not validated, whereas a signed-in sender's identity is recorded. Microsoft's recipient instructions.

Treat a typed name as a sorting aid. Even an account identity is not proof that somebody is authorized to act for a particular customer. If that distinction matters, reconcile the submission through your existing customer contact process or retain a service that meets your authentication requirement.

The staff requestor should use the intended work account and send the link through a known business channel with a project reference, requested documents, deadline and contact for mistakes. Tell the customer how to verify an unexpected request with your team. Do not put sensitive customer details into a description that may travel with a forwarded link.

Choose a dedicated pilot folder. In OneDrive, select it and use Request files, then enter the request description and copy the link. Microsoft says uploads trigger an email notification to the requestor. Microsoft's request-creation instructions. Assign someone to inspect the folder and reconcile expected submissions; notification alone should not close the job.

Run a customer-and-staff rehearsal

These are proposed user-run tests. No tenant settings were changed and no files were uploaded for this article. Use dummy files and authorized test participants, including someone outside the organization.

Test Action Acceptance condition
Signed-out recipient Open the request on a phone and computer without an existing session The permitted audience completes the upload without staff coaching
Isolation After one participant uploads, give only the request link to a second participant No customer content or uploader list becomes visible
Wrong file Submit a clearly marked dummy document for the wrong project Staff detect it, record the issue and give a clear correction route
Duplicate filename Submit two different dummy files with the same filename Staff retrieve both, compare their contents and select the intended version
Recipient and staff access Test the public link and the staff archive with their respective accounts Customers see only the intended request; the authorized backup staff member retrieves the files
Stop request Close the pilot request, then retry its old link New intake stops; staff can still retrieve the previously collected test material

Microsoft says duplicate filenames receive a numeric suffix. That prevents a filename collision from being a reliable indicator of which document is current. Microsoft's filename behavior. Use a small receipt log with project reference, filename, arrival date, review status and reviewer. Mark superseded and incorrect submissions explicitly rather than assuming the latest name is authoritative.

For the wrong-file test, have the customer contact the named staff member and submit a clearly identified replacement through the approved route. The staff reviewer decides what to retain or remove under the organization's policy. A successful transfer does not establish that the document is complete, correct or appropriate for the project.

To stop collection, delete the request link through Manage Access. Microsoft says deletion cannot be undone; restarting collection requires a new request link. Microsoft's stop-request instructions. Test closure before distributing a live request, and record everywhere the old link was placed.

Budget for storage and for the owner's departure

Work or school OneDrive accounts over quota cannot upload, edit or sync new files, and recycle-bin items count toward storage. Microsoft's work-account storage guidance. Record the actual available capacity and typical incoming file sizes before the pilot. Assign a person to monitor capacity and specify where customers should report failed uploads. Do not fill production storage merely to simulate failure; use an administrator-approved test or document that failure handling remains untested.

Decide who receives and maintains the files when the requestor is absent or leaves. Microsoft's deletion process has a configurable retention period and access delegation dependent on configuration and a manager or secondary owner. Removing a license also has separate unlicensed-account consequences. A colleague's current access is not a permanent archive guarantee. Microsoft's retention and deletion documentation.

Rehearse handoff without deleting a real staff account: have the designated backup locate the request, retrieve sample submissions and explain the shutdown procedure. Ask the administrator to document the actual departure plan, ownership destination and relevant deadlines. Do not assume the same request URL survives a file move or account change; verify the intended replacement route before publishing it.

Keep a route back and count only a removable charge

Retain your existing service if you require an authenticated client workspace, structured questions, customer self-service corrections or a review process that this upload job does not reproduce. Keep it if permitted sharing, storage or ownership cannot be established. A simple request link may cover one project while leaving the rest of the subscription necessary.

Before reducing access to the old service, preserve its submitted files, customer references, review notes and distribution links. Ask another authorized colleague to open several archived files and connect them to the right project. Keep the old intake route available during the pilot, with its access requirements confirmed. If the pilot fails, stop the new request, reconcile all arrivals and tell affected customers which approved route to use next.

Compare one billing period: current collection-service charge − remaining charge with that vendor − incremental Microsoft 365, storage or replacement costs. The unchanged Microsoft 365 bill is already retained and should not be subtracted again. Record administration time separately, and do not count an avoided annual renewal as an immediate refund. Enter only the cancellation or downgrade you can actually make in the subscription audit.