If your organization already uses the Microsoft SharePoint connector in Rovo, an admin needs to complete an updated authentication flow by April 2, 2026.
This now includes two admin actions:
Grant admin consent for the updated SharePoint user app.
Reauthorize the existing SharePoint connector.
Both steps usually take a few minutes. You do not need to create a Microsoft app registration, generate certificates, or manage client secrets.
Who: Existing SharePoint connector customers
What: Grant admin consent, then reauthorize the connector
When: By April 2, 2026
Why: Microsoft is retiring the legacy SharePoint auth path, and Rovo is moving to an updated Microsoft Entra-based flow
We’re making two updates to how Rovo connects to SharePoint:
A more secure admin connection: Rovo is moving from the legacy Azure ACS-based setup to an Atlassian-managed Microsoft Entra app.
Expanded SharePoint understanding for Rovo: the updated user app permissions let Rovo understand more of SharePoint’s site and library structure, not just individual files, while continuing to maintain and respect permissions.
A simpler admin experience: no app registration, client secret, or certificate setup is required in the new flow.
This change aligns with Microsoft’s retirement of Azure ACS for SharePoint Online. See Microsoft’s announcement: Azure ACS retirement in Microsoft 365.
If you do not complete these steps by April 2, 2026, SharePoint connectors still using the legacy auth flow are expected to start failing and may stop syncing which will result in rovo reasoning over stale data.
You need access to Rovo connector management in Atlassian.
You also need a Microsoft admin who can grant tenant-wide consent and complete the Microsoft authorization flow. In many organizations this is a SharePoint admin or Global admin.
In some organizations, the Atlassian admin and the Microsoft admin are the same person. In others, this may require coordination between two admins.
Sign into to admin.atlassian.com > Apps > AI Settings > Rovo
Select your active SharePoint connector, and from the actions menu select Manage, and from the popup select
Grant admin consent for the updated SharePoint app and check the box attesting it.
Reauthorize your existing SharePoint connector and complete the Microsoft OAuth screen.
I can access Rovo, but I can’t grant Microsoft consent: ask your Microsoft tenant admin, often a SharePoint admin or Global admin, to complete the Microsoft steps.
I granted consent, but users still don’t see the updated SharePoint experience: it can take a short time for changes to propagate. If needed, ask affected users to reconnect their Microsoft account later once your rollout guidance is confirmed.
Consent is blocked by policy: your security team may need to allow the Atlassian enterprise application and approve the requested read-only permissions.
The connector still shows auth errors after reauthorization: wait a few minutes, refresh the page, and try again. If the issue continues, contact Atlassian Support with the connector status and any visible error message.
Yes. The connector is read-only. It is used to index SharePoint content and structure so users can search and get answers in Rovo.
No. Rovo continues to respect SharePoint permissions. Users should only see content they already have access to in Microsoft 365.
No immediate end-user action is required. Users will later be asked to reconnect their Microsoft account to pick up the updated SharePoint permissions.
This update improves security, removes legacy setup burden for admins, and aligns the connector with Microsoft’s modern authentication model for SharePoint Online.
Chait Donthini
0 comments