nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I need help figuring out why the Sharepoint connector is not working.

Anthony Powell

I have added the SharePoint connector and verified all the settings. I even had JSM ask me to sign in to SharePoint in the search bar, but for over 24 hours, nothing has been indexed, and the search returns nothing from our SharePoint site. This is actually the second time we have done this; the first time it sat for 2 days with nothing indexed.

I have it pointing to the root of our SharePoint, where there is a lot of content. On the Microsoft side, I don't see any communication, and there's nothing in the logs on the Atlassian side either.

Is there some secret to making this work that I am missing?? I used these instructions: https://support.atlassian.com/organization-administration/docs/connect-sharepoint-to-rovo/

Accepted answers

Mirek

Hi @Anthony Powell

That is interesting since you are not alone.. Few days back I noticed someone reported a similar problem here (maybe it was your colleague in first attempt? )

https://community.atlassian.com/forums/Rovo-questions/Rovo-Sharepoint-Connector-Not-Indexing-Objects/qaq-p/3175512

Anyway wondering what might be the problem.. and what we can do before asking Atlassian Support..

There are a lot od steps and relations between one system and another..

I would definitively recommend start with smaller set of pages (not whole directory). Sometimes large hierarchies or permissions complexity blocks indexing..

There might be also block/whitelists ..
https://support.atlassian.com/organization-administration/docs/manage-blocklist/
So it is worth checking if nothing like tha is set .. or any Limiting by date which might reindex only specific content created after that date..

Might be also permissions.. so good to double check everything (or again create from scratch with smaller set)

However if you see a successful connection status and do not see any progress or logs it strongly suggests the issue may be on the Atlassian connector backend or the sync job, rather than something you’re missing in permissions..

So we might actually end up with asking Atlassian Support what is going on (at least they have access to logs in the backed.. )

All comments

Mirek

Hi @Anthony Powell

Anthony Powell

I came back today, and it looks like it did start indexing. This is a huge SharePoint site, as it is our internal intranet, so it could just be taking forever.

Thanks for chiming in, though I do really appreciate it.

Although saying that, it still doesn't seem to find things I know are docx files and whatnot. Is there a way to see what it has indexed?

Dustin Alcock

That other post was mine, different org. "Glad" to see more people reporting it, will help to get Atlassian to provide better guides/logs/fixes for the future if we not only post here but also submit a ticket, which I'll go do now.

Dr Valeri Colon (Connect Centric)

@Anthony Powell welcome to the community. The SharePoint connector may be slow at first, but no results after 24–48 hours usually means a permission or scope issue. The Graph app must have site-level read access and all required permissions granted by an admin. Indexing also works better when pointed to a specific site, not the tenant root. If syncing stays at zero items for over 72 hours, open an Atlassian Support ticket so they can check the backend job.