Skip to main content
Neo Agent syncs documentation from your SharePoint document libraries so agents can search and read it during ticket resolution. You choose which libraries to sync, and then map top-level folders to the companies they belong to — so a search for one client only surfaces that client’s documents.
No API key. SharePoint runs on a dedicated read-only Microsoft 365 app — a Microsoft 365 admin consents it once, and you pick which libraries to sync. Nothing else about your Microsoft setup has to change.

​
How Neo reads SharePoint

Neo reads SharePoint through the Neo SharePoint Connector application, which a Microsoft 365 admin consents on your own tenant. It holds exactly two permissions, both read-only: Neo never writes to, moves, or deletes anything in SharePoint.
This is its own app, on purpose. SharePoint search doesn’t ride the broader Neo Azure Automations app that powers Microsoft 365 administration. The two consents are independent in both directions, so you can have SharePoint search without granting Neo any Microsoft 365 admin access at all.
Who can grant consent. Every tenant starts here — Microsoft permissions only exist where an admin has granted them, so a missing grant is the normal first step, not a misconfiguration. Microsoft accepts consent only from a Global Administrator, Privileged Role Administrator, or Cloud Application Administrator; any other account is sent back to Neo without a grant, and Neo shows Microsoft’s own reason (the AADSTS… code). If your tenant uses the admin consent request workflow, the click files a request and access starts once an approver grants it.

​
Connect SharePoint

1

Open the SharePoint tile

In the Neo Dashboard, open Integrations and click the SharePoint tile in the Documentation section.
2

Verify access

Click Verify access. Neo checks whether the Neo SharePoint Connector app can read SharePoint on your tenant.
  • Not consented yet (the usual first time) → an amber Admin consent needed notice with a Grant admin consent button. An admin opens it and approves the two read permissions; Microsoft returns to Neo, which rechecks the grant itself and opens the library picker. I’ve granted consent — recheck re-runs that check by hand if you need it.
  • Consent refused → a red notice with Microsoft’s reason. Almost always the signed-in account isn’t one of the three roles above; retry as an admin who is.
  • Already consented → you go straight to the library picker.
3

Choose your document libraries

Neo lists your SharePoint sites. Expand a site to see its document libraries, and tick the ones you want Neo to sync. You can select libraries across multiple sites.
Sync the libraries that hold client-facing documentation — runbooks, procedures, network diagrams. You’ll map their folders to companies in the next step.
4

Connect

Click Connect N libraries. Neo saves your selection and starts the first sync. Larger libraries take a little longer on the first run; subsequent syncs only pull in what changed.
The tile flips to a Connected view: a connection card listing the synced libraries with the sync status, Trigger sync, Change libraries, and Disconnect — plus a Document scoping section with Folder mappings and Global folders.

​
Map folders to companies

SharePoint has no built-in notion of which company a folder belongs to, so Neo asks you once. After the first sync, Neo scans the top folders in your libraries (2–3 levels deep), matches each to a company by name, and presents the matches for you to confirm — so you approve a list instead of mapping every folder by hand.
1

Open the review queue

On the connected SharePoint page, click Review next to Folder mappings (or open it from a company’s linked-systems column on the Companies page).
2

Review Neo's matches

Each row shows a folder, the company Neo matched it to, and how confident the match is:Tick the rows that are right, retarget any folder to a different company with the picker, and click the ✕ to dismiss a folder that isn’t client documentation (dismissed folders won’t be suggested again).
3

Confirm

Click Map N folders. Neo saves the mappings and scopes each folder’s documents — and everything beneath it — to that company. Nothing is applied until you confirm, and only the rows you kept are mapped.
Unmapped folders stay private. A folder you don’t map (or dismiss) still syncs, but its documents are not shared across companies — they surface only where their own company mapping applies. A subfolder always inherits the nearest mapped folder above it, so you only map at the level that matters. To make a folder’s documents available to every company, designate it global (below) — global is an explicit choice, never inferred from a folder being unmapped.
If a mapping saves but Neo can’t immediately re-scope the already-synced documents (a transient hiccup), the review queue tells you which folders are affected and offers Retry re-scoping. The mappings themselves are always saved.

​
Mark global folders

Some documentation applies to every client — shared runbooks, internal knowledge bases, vendor guides. Mark those folders global so their documents surface in every company’s searches, regardless of folder-to-company mapping.
1

Open the picker

On the connected SharePoint page, click Manage next to Global folders. The row shows how many folders are currently designated global.
2

Choose folders

Browse the library tree and tick any folder — or a whole library — whose documents should be global. A company-mapped subfolder inside a global folder keeps its own company, so you can share a parent broadly while still scoping specific children.
3

Save

Click Save global folders. Neo re-stamps the already-synced documents immediately, so the change takes effect without waiting for the next sync.
Global is explicit. Only folders you designate here are shared across companies. This is a deliberate safeguard — a folder is never treated as global just because Neo couldn’t match it to a company.

​
What gets synced

Once synced, your SharePoint documents are searchable alongside IT Glue, Hudu, Confluence, and any other documentation sources you’ve connected — scoped to the company you mapped their folder to.

​
Sync on demand

Syncs run automatically on a schedule. To pull in changes right away, click Trigger sync on the connected card — the status badge next to it shows whether the last sync succeeded, is still running, or failed, and the details table below it breaks down what each sync step did.

​
Change which libraries sync

On the connected card, click Change libraries to open the picker with your current selection pre-ticked. Adjust the set and click Save libraries. Libraries you remove stop syncing; new ones are picked up on the next sync.

​
Disconnect

On the connected card, click Disconnect and confirm. Neo stops syncing SharePoint and its synced documents stop updating. Your SharePoint content and the admin-consent grant on your tenant are not affected — reconnecting later picks up where you left off.

​
Security

  • Sites.Read.All and Files.Read.All are the only permissions the Neo SharePoint Connector app declares, so consenting it cannot grant anything beyond SharePoint read access.
  • Access runs on your own tenant; there are no separate credentials to manage, and you can revoke it at any time from Enterprise applications in the Microsoft Entra admin center.
  • Folder→company mappings are only ever the ones you explicitly confirm — Neo never auto-applies a mapping.
  • All traffic is over HTTPS, and synced content is isolated per tenant.