Skip to content

Microsoft SharePoint

With the SharePoint integration you connect a folder from SharePoint to the Evoya platform as a mount. The Evoya platform can then index the documents in that folder and search them with vector search. The files stay in SharePoint – you don't need to upload them again.

Prerequisite: Microsoft integrations must be enabled for your account

The SharePoint integration only works if Microsoft integrations are enabled for your account on the Evoya platform. If you can't find Microsoft SharePoint on the Integrations page, contact us through our support form to have it enabled.


How SharePoint is organised

To create a mount, you need to know where your files are stored in SharePoint. SharePoint uses this structure (see Microsoft Learn):

Site  (the website, e.g. https://company.sharepoint.com/sites/Marketing)
└── Document library  (e.g. "Documents" / "Dokumente")
    └── Folder → subfolder → files
  • Site: The SharePoint website of a team or project. A site is not a single page.
  • Document library: A site can contain pages, lists and one or more document libraries. The Evoya platform only needs the document library, because that is where the files are stored.
  • Root folder: The folder inside the library that the Evoya platform makes available. Everything below it, including all subfolders, is included.

When you create a mount, you follow exactly this path: Authentication → Site → Document library → Root folder → Mount details.


Setup at a glance

The setup has four parts. Parts A and B are done once by an Administrator. Part C is only needed if users sign in with their personal Microsoft account. Part D is repeated for every folder you want to connect.

Part What Who Where
A Set up Microsoft sign-in (once) Administrator and Microsoft Entra administrator Authentication
B Activate the integration and choose the authentication method Administrator Integrations (admin settings)
C (Optional) Connect your personal Microsoft account Each user Integrations (user area)
D Create the mount Users with access to the Files page Files

Part A: Set up Microsoft sign-in

Microsoft sign-in (SSO via Microsoft Entra ID) is the connection between the Evoya platform and your organisation's Microsoft tenant. Nobody can use the SharePoint integration until it is set up.

Already using Microsoft sign-in?

If your organisation already signs in to the Evoya platform with Microsoft, this part is done. Check on the Authentication page that Microsoft is shown as active and continue with Part B.

Requirements:

  • You have the Administrator role on the Evoya platform. Other roles can't open the Authentication page.
  • You are also a Microsoft Entra administrator in your organisation's tenant, or you have one at hand. Without this role, the Microsoft side of the setup can't be completed.

Steps:

  1. Open the Authentication page.
  2. Add Microsoft as a provider and sign in with the Microsoft Entra administrator account.
  3. Approve the Microsoft consent prompt with Accept.
  4. Check that Microsoft is shown as active.

The detailed steps are described on the Authentication page.


Part B: Activate the integration

  1. Open the Integrations page in the admin settings.
  2. Activate Microsoft SharePoint. If you also want to connect a server, activate VM as well (see VM (SSH server)).
  3. Choose how users authenticate with SharePoint:
    • Organization service account: One shared Microsoft account is used for all users. Technically it is a normal Microsoft user account, but it acts as a general account for everyone. It needs read access to the SharePoint content you want to mount.
    • Personal account per user: Each user signs in with their own Microsoft account. The Evoya platform then accesses SharePoint with that user's permissions.

Which option fits?

Organization service account Personal account per user
Setup effort Low – one account for everyone Each user connects their account once (Part C)
Permissions Everyone using the mount gets the permissions of the service account Access follows each person's SharePoint permissions
Good for Shared team content that everyone may see Content where access differs from person to person

Service account permissions apply to everyone

With the service account, every user who works with the mount can access everything the service account can read in the selected folder. Only give the service account access to content that all users of the mount are allowed to see.

After you activate the integration, the Files menu item appears in the side menu.


Part C: Connect your personal Microsoft account

Only needed for personal accounts

Skip this part if your organisation only uses the organization service account.

If the Administrator allows personal accounts, each user connects their Microsoft account once:

  1. Open the Integrations page in the user area (in the side menu under Custom).
  2. Choose Microsoft SharePoint and sign in with your Microsoft work or school account.
  3. Approve the requested permissions.

Without this step, your personal account isn't offered in the mount wizard.


Part D: Create the mount

  1. Open Files in the side menu.
  2. Click Connect (top right).
  3. Choose SharePoint. You only see the options the Administrator has activated: SharePoint and/or VM.
  4. Click Add mount (top right) to start the wizard.

The wizard has five steps. At each step you can go back with the Change … button.

Step 1 of 5: Authentication

Choose which Microsoft account the Evoya platform uses for this mount:

  • Organization service account: shared by all users.
  • Personal account: your own Microsoft account. This option only appears if you completed Part C.

Click Select.

Step 2 of 5: Site

  1. Paste the full URL of the SharePoint site into the field Site name or URL, for example https://company.sharepoint.com/sites/Marketing. A full URL gives the most reliable match.
  2. Click Find site.
  3. Click Select next to the correct result.

To use a different account, click Change auth.

Finding the site URL

Open the site in SharePoint in your browser and copy the address up to and including the site name, e.g. https://company.sharepoint.com/sites/Marketing. Leave out everything after it, such as /SitePages/Home.aspx or /Shared Documents/....

Step 3 of 5: Document library

Choose the document library that contains your files. Libraries are listed by name and address. The default library is called Documents (in German: Dokumente). A site can have several libraries.

Click Select. To choose a different site, click Change site.

Step 4 of 5: Root folder

  1. Browse the library. Click Open to go into a folder.
  2. When you are in the folder you want to make available, click Use this folder. To use the whole library, stay at the top level of the library and click Use this folder there.

To choose a different library, click Change library.

Only the content of the selected folder and everything below it, including subfolders, is available in the Evoya platform.

Step 5 of 5: Mount details

Field Meaning
Mount name * Name of the mount in the Evoya platform
Description Optional description
Access mode * For example Read only: the Evoya platform reads the files and doesn't change them
Selected location Summary of authentication, site, library and root folder. Check it, or click Change folder to correct it.

* Required field

Click Create mount to finish. Click Cancel to discard the mount.


Troubleshooting

Problem Solution
Microsoft SharePoint isn't listed on the Integrations page Microsoft integrations aren't enabled for your account yet. Contact us through our support form.
Microsoft sign-in setup fails You need both the Administrator role on the Evoya platform and the Microsoft Entra administrator role in your tenant (Part A).
"Files" or "Connect" is missing The Administrator hasn't activated the integration yet (Part B).
Your personal account isn't offered Connect it first in the user area (Part C) and check that the Administrator allows personal accounts.
Site not found Check the URL: it must point to the site, not to a page or folder within it. Check that the selected account has access to the site.
A library or folder is missing The selected account doesn't have access to it. Check its permissions in SharePoint or choose a different account.