Hi Sachin,
I reviewed the Knowledge Fabric documentation before replying because this is an important architectural decision.
Based on the current documentation, Knowledge Fabric connects to SharePoint by configuring a SharePoint source, selecting a specific SharePoint site, and then selecting the folders that should be synchronized and indexed. The documentation does not mention any special handling of SharePoint Hub Sites or automatic discovery of all Hub-associated sites.
Because of that, I would not assume that associating sites to a SharePoint Hub automatically makes them available to Knowledge Fabric.
My expectation would be:
- The SharePoint site must be accessible through the configured connection.
- The site must be selected as a Knowledge Fabric source.
- The folders to be indexed must be explicitly selected for synchronization.
For permissions, I would pay particular attention to the Microsoft Graph permissions and the service account/application used by the SharePoint integration. Since indexing depends on what the configured connection can access, site-level permissions are likely more important than the Hub relationship itself.
If you are moving to a Hub architecture, I would strongly recommend a pilot using:
- One Hub site
- Multiple Hub-associated sites
- Different permission models
and then verify whether each site appears as an independently selectable source and whether content from all intended locations is synchronized correctly.
From what I can see in the current documentation, Knowledge Fabric is clearly SharePoint-site aware, but there is no documented statement that it is Hub-aware in the sense of automatically crawling all associated sites.
https://help.genesys.cloud/articles/about-the-knowledge-fabric/
------------------------------
Gabriel Garcia
NA
------------------------------