SharePoint
SharePoint is Microsoft's collaboration platform for documents, libraries, and team sites. Ordalie can connect to it in two different ways, and which one you choose depends on whether you want your own personal access or a single shared connection for the whole organization.
A personal connection signs you in with your own Microsoft account, so Ordalie sees exactly the sites and libraries that account can already reach. An organization-level connection instead uses admin-registered application credentials, so everyone in your organization works from the same connection without each person signing in to Microsoft. The personal route is open to any member; the organization route is set up by an organization administrator.
Both routes start in the same place. From your workspace, you can open Connect a source in the left sidebar, or go to Settings and open the Integrations tab. Integrations is a top-level tab in Settings; it is not nested under the Organization tab. Personal connectors appear under Personal Integrations, and organization connectors under Organization Integrations (the Enterprise & Admin section in the Connect a source window), which only an administrator can manage.
Connecting your own SharePoint access
Open Connect a source or go to Settings > Integrations, and look for SharePoint (Personal) among the personal connectors. You enter the SharePoint site URL you want to reach, using the site root address, for example https://tenant.sharepoint.com/sites/MySite. Choose whether Ordalie should have read-only access or read and write, then continue. A Microsoft sign-in window opens, and once you authorize Ordalie the site is connected.
Because this connection is delegated to your own Microsoft account, you only see the sites and libraries that account is allowed to open. If a colleague cannot reach a site, that is a SharePoint permission question on the Microsoft side rather than something to change in Ordalie.
Setting up SharePoint for the whole organization
The organization-level connection is the right choice when you want one shared SharePoint connection for the firm rather than each person connecting individually. It relies on application credentials registered in Azure, so the steps below happen partly in the Azure portal and partly in Ordalie. You need to be an organization administrator to complete it.
Start in the Azure portal and register a new application under App registrations. A single-tenant application (accounts in your organization's directory only) is enough, and no redirect URI is needed for this credential-based flow. Once it is created, note the Application (client) ID and the Directory (tenant) ID shown on the overview page, because you will enter both into Ordalie.
Next, give the application the Microsoft Graph application permissions it needs and grant admin consent for them:
- Sites.Read.All for reading, or Sites.ReadWrite.All if Ordalie should write back to SharePoint.
- Files.Read.All for reading files, or Files.ReadWrite.All for write access.
Then decide how the application will authenticate. You can create a client secret, copying its value (shown only once), or you can upload a certificate and use the matching PEM private key. The certificate path is worth considering because it can be issued with a longer validity than a secret.
You also need the Site ID of the SharePoint site you want to connect. You can find it through the Microsoft Graph API for the site, or you can save your credentials in Ordalie first and let it list the sites it can reach so you pick one.
With those pieces ready, go to Settings > Integrations, open the Organization Integrations section, and add SharePoint. You give the connection a Name, then fill in the Tenant ID, Site ID, and Client ID. Under Authentication you choose App Secret or Certificate (PEM), and enter either the Client Secret or the Certificate (PEM) and Private Key (PEM) accordingly. You set the Access Level to read only or read and write, and you can set a Search Region (covered below).
When you select Create Mount, Ordalie checks the connection by acquiring a token, listing content, and running a search. If the site holds more than one document library, it then asks which libraries to include, and you can revisit that choice later by editing the connection.
The Search Region setting
Microsoft Search is tied to where your Microsoft 365 tenant stores its data, and the Search Region field has to match that geography for search to work at all. It is not a performance preference, and there is no default: you pick the code that corresponds to your tenant's region. The dropdown offers around twenty ISO-style region codes such as FRA, GBR, EUR, and NAM, so if search returns nothing the region code is the first thing to check.
Questions that come up
You can connect several SharePoint sites by creating one connection per site. With the organization-level setup each connection can point to a different site, and with a personal connection you can reuse the same Microsoft account across different sites.
If a client secret expires, the organization connection stops working until you edit it in Ordalie and enter a new secret. This is one reason to consider certificate authentication, which can be issued for a longer period.
If some document libraries are missing, the cause depends on the connection type. An organization connection only sees what its application permissions allow, so it needs at least Sites.Read.All. A personal connection only sees what your own Microsoft account can open, which you can confirm in SharePoint itself.