This is a big one for enterprise teams from @Paulo Ramalho :
“Can Rovo index SharePoint intranet pages—not just documents?”
Short answer: No, not today. And you’re not missing anything.
What the SharePoint connector actually does
Today, the Rovo SharePoint connector can index:
- Documents (Word, PDF, etc.)
- Files stored in SharePoint
It does not index SharePoint pages (intranet pages, site pages, etc.).
Why this is a gap
For many organizations:
- SharePoint is the intranet
- Key knowledge lives in pages—not files
- Documents alone don’t represent the full picture
So even with the connector: You’re only indexing part of the knowledge base
“Can we just crawl the site instead?”
This is the common suggestion—but here’s the reality: It usually doesn’t work.
Why?
Most SharePoint intranets are:
- Behind SSO
- Protected by MFA
- Using modern authentication (OAuth)
Rovo’s web crawling (CSM agent):
- Works only for public sites
- Or very simple auth (basic auth)
Which SharePoint Online does not support for pages
So what does work?
Only in this scenario: If SharePoint pages are truly public (no login required)
Then:
- The web crawler can index them
- But with limitations:
- Respects robots.txt
- Limited depth
- Struggles with complex pages
- Not fully reliable
Current workarounds customers are using
Until native page indexing is available:
1. Export pages to documents
- Convert key pages to Word/PDF
- Store them where the connector can index
2. Mirror high-value content
- Sync critical pages into Confluence
- Use Rovo where it performs best
3. Prioritize “indexable” knowledge
- Focus on structured, document-based content
None of these are perfect—but they’re the current reality.
What about roadmap / ETA?
Atlassian has acknowledged: SharePoint page indexing is being worked on
But: No public ETA yet
Champion takeaway
If your customer says:
“We want Rovo to understand our SharePoint intranet”
The honest answer is:
- “Partially today (documents)”
- “Not fully yet (pages)”
