Search SharePoint and Teams your shared drives in your AI knowledge base.
Document libraries, Teams channel folders and the attachments shared there go into the knowledge base – with the folder structure you already maintain. Channel chat posts are not included; mailboxes and OneDrive are covered on the Outlook and Exchange page and the Microsoft 365 page.
SharePoint & Teams
One click · included in the set-upExample question
“Where is the approved version of the quote for the property at Bahnhofstraße 12?”
1 Answer with sourceConnection
How the connection works
The connection uses Microsoft’s official consent process: you sign in with your Microsoft account and choose which sites, document libraries and Teams channels can be read – read-only, with nothing in SharePoint changed. Depending on your settings, an administrator gives consent once; whether access can be limited to the sites you choose depends on your settings and your licence. If you run SharePoint on your own server, the route is different and subject to a feasibility check.
Once set up, synchronisation runs automatically: new and changed documents from SharePoint & Teams are added without anyone having to upload anything.
Set-upConnected in one click and included in the set-up: you link SharePoint and Teams through your Microsoft account, subject to admin consent in your account. If you have several sites, nested libraries or channels with their own permissions, we go through them with you – ideally with your Microsoft administrator – before anything is set up.
Documents
Typical content: SharePoint & Teams
- Document libraries organised by columns rather than folders – client, property, status and year stored as columns on each file
- The “Documents” folder behind every Teams channel: it holds whatever someone dragged into the channel, even if it was never filed
- Content types and managed metadata from the term store, if someone once set up your document libraries properly
- Site pages and news posts from the intranet – process descriptions, notices, responsibilities, often recorded nowhere else
- Lists where contract terms, properties or contacts are kept row by row rather than in a file
- Project sites created for a single case and left untouched once it was closed
Example questions
Questions you might ask your documents
“Where is the approved version of the quote for the property at Bahnhofstraße 12?”
1 Answer with source
“Which schedule is in the Teams channel for project 2024-118, and which version is the latest?”
2 Answer with source
“Which version of the maintenance contract with Huber is the current one?”
3 Answer with source
Start
Before a connection is set up
You connect it in one click via your account, and it is included in the set-up, subject to admin consent in your account. Together we agree which folders and areas to include.
You can also upload files, whole folders, emails, photos and voice notes at any time. In the demo you see the answers using sample documents from your industry; you check them against your own documents in the first weeks after go-live.
Preliminary check
What we check in advance
Before we start, we check whether and where you use sensitivity labels with encryption – those files can only be opened with the right permission. We also clarify where shared files actually live: anything shared in a Teams chat rather than a channel is stored in the sender’s OneDrive. junova uses the current version of each file; whether you need older versions from the version history is something we discuss. List items are records, not documents – we decide together whether to add them through an export, and how to handle links to other people’s storage.
FAQ
Frequently asked questions about this connection
We have team sites from 2016 that nobody maintains any more. Will they be included?
Yes, if you select them – an inactive team site is treated like any library in use. It makes sense to connect them separately: the answer then names the site and library it comes from, so you can see that the information is from the old records. If you don’t want old records in everyday answers, you can use a cut-off date. Before the set-up, we go through with you which of your sites suit this approach.
Our libraries use columns instead of folders. Does that help or get in the way?
Usually it helps. Library columns such as property, status or year are carried over as attributes on the document, as are content types and terms from the term store. Where columns are empty, the system reads values such as client, property or date from the document itself. Someone confirms the document type on the first run, because it decides who can see a document later on.
Things change in SharePoint all the time. Will that break the connection?
That depends mainly on what you selected. Nothing is installed on your side; reading works through the consent you granted. The sensitive part is changes to the selection itself: a deleted site, a moved library or withdrawn consent. In that case, the knowledge base stays as it was at the last sync, and the date on the source shows this. Reconnecting through your Microsoft account takes one click; if the selection needs more rework than that, we agree the effort with you in advance.
Every project site here has its own permissions. Does the knowledge base copy that?
It takes a different approach: in the knowledge base, permissions are tied to document types and roles, not to individual sites. The team might see minutes and property files, for example, while management also sees contracts and statements; documents from a sensitive project site can be set up as a separate document type reserved for a smaller group. If your role lacks permission, the answer tells you so. Before we start, we discuss how your existing permissions can be mapped onto this.
Industries
Typical for these industries
Guides
Further reading
- Microsoft Copilot vs. AI knowledge base: which is better for company knowledge?Looking for a Microsoft Copilot alternative? This fair comparison shows when Copilot is enough for company knowledge and when an AI knowledge base fits better.
- Migration step by step: from folder-based filing to AI searchMoving to a knowledge base step by step: from reviewing your folders and shared drives to AI search – with a pilot area and clearly defined stages.
- Connecting SharePoint content to an AI knowledge baseMaking SharePoint documents searchable with AI: how to connect your existing content – without switching systems, with permissions and sources.
- SharePoint for document storage: strengths, limits, alternativesLooking for a SharePoint alternative for SMEs? An honest look at what SharePoint does well, where it falls short – and when an AI query is the better choice.
Integrations
Other integrations
- Microsoft 365
- Outlook & Exchange
- Google Workspace
- Dropbox Business
- OneDrive
- Box
- Egnyte
- Zoho WorkDrive
- pCloud
- Microsoft Teams
- Notion
- Confluence
- Slack
- Asana
- Gmail
- HubSpot
- Salesforce
- Pipedrive
- Zoho CRM
- QOMET
- TaxMetall
- Streit
- pds
- Advokat
- Kieselstein
- Werbas
- File server
- Nextcloud / ownCloud
- NAS
- RZL Software
- RA-MICRO
- AUER Success & ABK
- BauMaster
- TopKontor Handwerk
- Scan-to-Folder
- Dictation and voice recordings
- TAIFUN Handwerk
- Labelwin
- NEVARIS
- untermStrich
- Soloplan CarLo
- iX-Haus
- BMD
- Existing DMS
- Schweighofer Manager
- DOMUS
- proALPHA
- Wiki and intranet
- DATEV
- Your own database or specialist application
- kwp-bnWin.net
- ams.erp
- Loco-Soft
Do you look after this system for clients? For IT service providers and software consultants
Request a demo – with examples for SharePoint & Teams
In a 30-minute video call, we use sample documents to show what answers with sources look like. After go-live, you connect SharePoint & Teams in one click via your account.