Atlassian Rovo's SharePoint connector carries a 15 November 2026 Microsoft consent deadline

Atlassian's Rovo assistant can now pull SharePoint and OneDrive content into its index, and the rollout puts a firm date in front of Microsoft 365 administrators: they must consent to a new Atlassian application in Microsoft Entra by 15 November 2026, or SharePoint and OneDrive features across Atlassian products break for their users. The details come from a hands-on walkthrough published on dev.to, whose author traced the connector wizard through a test organisation as far as Microsoft's sign-in page on 25 October 2026, with the caveat that, lacking a real Microsoft tenant, nothing was actually connected and everything beyond sign-in rests on documentation.

What the connector does

According to the dev.to write-up, the Rovo SharePoint connector copies SharePoint and OneDrive files into the Teamwork Graph, the index Atlassian keeps for search and AI. Rovo answers from that copy rather than querying Microsoft directly. The connector needs a Standard Rovo plan or higher, and Atlassian Government organisations do not get it.

Two apps, two permission requests

The setup talks to two distinct Microsoft app registrations, which the dev.to author calls the consent app and the indexing app.

The consent app, Entra application ID 0c8611af-925f-491b-86f4-32fad2901689 and displayed as Atlassian, requests six named, read-only scopes: email, openid, Files.Read.All, Sites.Read.All, User.Read and offline_access. An Entra Global Administrator, Application Administrator or Cloud Application Administrator approves it.

The indexing app is a separate registration whose Authorize step requests Microsoft's .default scope plus offline_access. Because .default means all permissions registered on the app, the request itself names nothing, and the dev.to author's central complaint is that the setup page never shows the list being approved. It appears once on Microsoft's consent screen, and afterwards in Entra under the app's Permissions view. Atlassian's own connect page warns only that the permissions involved are broad.

Up to three administrators may be involved in total: the Atlassian organisation admin running the wizard, the Entra admin granting consent, and whoever authorises indexing. Atlassian's pages disagree on whether that third role requires Entra admin or SharePoint global admin permissions.

What the deadline covers

Atlassian's upgrade notice, as quoted by dev.to, requires a Microsoft 365 administrator to consent to the publisher-verified application by 15 November 2026. If nobody does, users may lose SharePoint and OneDrive Smart Links, link previews, and the ability to find that content through Rovo. The deadline applies only to the consent app, though: Atlassian says the grant can be made without completing connector setup or turning indexing on. Revoking it later disables SharePoint and OneDrive features in Atlassian for the entire organisation.

The documented scopes themselves behave conservatively on the delegated side, since Sites.Read.All exposes only items the signed-in user can already open in Microsoft. What could not be verified from the outside is whether the indexing app also holds application permissions, which would allow reading all site collections without any signed-in user. Only the consent screen or Entra's permissions list settles that.

Fine print and limits

Beneath the Authorize button, admins agree that Atlassian may access or ingest sensitive data, and that Atlassian may share data from the third-party product with MCP clients or apps that users connect to Teamwork Graph. That second clause reaches beyond Rovo, and matters to organisations that have locked MCP down through Atlassian Guard.

Site allow and block lists cap at 50 entries each, and neither can target individual files or folders. The dev.to author also found Atlassian's documentation and its public tracker contradicting each other twice, over SharePoint pages and over whether agents actually read file contents. For context, the piece notes that the old setup, retired in spring 2026, had customers build their own Entra app with eight application-level Graph permissions, and that Glean's competing connector asks for Sites.FullControl.All as standard; no Atlassian page mentions Microsoft's narrower Sites.Selected scope.

Why it matters

Admins who miss 15 November 2026 degrade functionality their users already rely on, not merely a new feature. The .default request means they are approving an Atlassian-controlled permission set they cannot see in advance and that Atlassian can change, and the MCP clause means indexed SharePoint data can flow onward to connected clients. The dev.to recommendation is to split the two decisions: grant the admin consent now, test the Authorize step in a pilot tenant and inspect the granted list in Entra before production, or screenshot the consent screen and cancel, and when indexing goes live, scope it with an allow list of sites rather than a block list.