Feature · Sending from SharePoint

Send files fromSharePointto the outside.

The file already sits in SharePoint, the recipient sits outside the organisation. Conbool SecureFiles fetches it straight from Microsoft 365 and delivers it encrypted, with no anonymous sharing link, no guest account and no detour through the sender's computer.

Request a demo SecureFiles in detail

Chosen from SharePoint

Delivered encrypted

Why sending from SharePoint fails

The file is there, the way out is missing.

Anonymous sharing links are blocked

Many organisations have turned external sharing off, because a link without sign-in can be passed on without limit. The convenient route is closed, and teams fall back on private services.

A guest account is too much for one file

Sending a single file to an accountant or a customer should not require a guest identity in the directory that has to be maintained and removed again.

Download and re-attach costs twice

The usual workaround runs through the sender's own machine: download from SharePoint, attach to a mail. Large files hit the attachment limit, and a second copy appears outside any control.

How sending works with Conbool

Four steps, no change to the SharePoint configuration.

Pick the file in the familiar dialog

The sender picks the file in Microsoft's own file picker, in the web interface or in the Outlook add-in, if the installation supports this route. Visible is exactly what the sender may already see in SharePoint.

Conbool fetches the file itself

The transfer runs between Microsoft 365 and Conbool's servers. The file never passes through the sender's computer, so neither the office line nor the attachment limit matters.

Deliver encrypted, with an expiry

Each recipient gets their own link, optionally with a password, an expiry date and single retrieval. No guest account required.

The audit trail stays in house

Every retrieval is logged with time and recipient. Once the retention period ends, the copy is deleted automatically.

What makes the route dependable

Sending from SharePoint is an operating procedure, not a workaround.

No sharing setting is opened

External sharing in Microsoft 365 stays as strict as IT set it. Conbool acts on behalf of the signed-in user rather than through an anonymous link.

User permissions apply unchanged

Only what the user sees in SharePoint can be picked. The application has no access to other libraries, and no token stays behind at Conbool.

Large files without attachment limits

Video cuts, plans and database exports can be sent as well. The size per file is set by your administration, not by the recipient's mailbox.

Straight from Outlook

The add-in offers the same route inside the mail window. The link appears in the message that is being written anyway.

Hosted in Europe

The copy sits on European servers, encrypted with AES-256. On request in the customer's own storage or on their own hardware.

Teams channels included

Files from Teams live in the SharePoint site of the respective team and can be sent the same way.

Anonymous sharing link or sending via Conbool

Both move the file outside. The difference is control.

	Conbool SecureFiles	Anonymous SharePoint link
External sharing in the tenant	Stays blocked	Has to be opened
Passing the link on	Password and single retrieval available	Can be forwarded without limit
Expiry	Period set per transfer, copy is deleted	Optional, the file stays in SharePoint
Evidence per recipient	Log with timestamp	Only in the tenant audit log
Guest account needed	No	Depends on policy

As of October 2026. The right-hand column describes the usual approach without Conbool, not a specific vendor.

Common questions about sending from SharePoint

Does external sharing have to be enabled in Microsoft 365?

No. Conbool does not create a SharePoint sharing link. It fetches the file on behalf of the signed-in user and delivers it through its own protected link. The tenant's sharing settings stay untouched.

Which permissions does Conbool receive in the Microsoft 365 tenant?

Delegated permissions only, valid on behalf of the signed-in user. There is no application access to mailboxes or libraries, and no token stays behind at Conbool. Users can send exactly the files they already see in SharePoint.

Who has to grant the approval?

An administrator of the Microsoft 365 tenant approves the application once. It takes a single click and is available in the SecureFiles settings.

Can files from Teams channels be sent?

Yes. Channel files live in the SharePoint site of the team and appear in the file picker. Shortcuts are not taken over, and the page lists them under Not taken over.

How large may a file be?

The mailbox attachment limit is irrelevant, because the file is never attached to the mail. The size per file is set by your administration, plus the storage you have booked.

Does the file stay in SharePoint?

Yes. The original stays where it is. Sending creates an encrypted copy that is deleted automatically once the retention period ends.

Does this work from Outlook as well?

Yes. The Outlook add-in offers the same picker and inserts the link into the message being written.

What if external parties work on files over the long term?

For that there is the pool as a data room, where guests without an account can be invited via a personal link.

See the route out of SharePoint once

A short demo on your own library, without changing a single sharing setting.