Upgrade your SharePoint and OneDrive connection in Atlassian
A Microsoft 365 administrator must grant consent to Atlassian’s new Microsoft publisher-verified application by November 15, 2026 to keep SharePoint and OneDrive Smart Links and previews working in Jira and Confluence.
This applies even if your organization does not use Rovo. If your users paste SharePoint or OneDrive links as Smart Links or previews in Jira or Confluence, this upgrade applies to those experiences.
What you need to know
Deadline: November 15, 2026
Who grants consent: A Microsoft 365 administrator
Application name: Atlassian
Application ID:
0c8611af-925f-491b-86f4-32fad2901689What users need to do: Reconnect their Microsoft accounts when prompted after administrator consent is granted.
Existing links in Jira and Confluence will be preserved. Users will continue to access only the SharePoint sites and OneDrive files that their Microsoft accounts permit them to access.
For organizations using Rovo: This upgrade also affects SharePoint and OneDrive experiences in Rovo that use this connection, if a SharePoint or OneDrive connector is enabled. A Rovo connector is not required for Smart Links to be affected. If your organization separately configures a synced Teamwork Graph connector, content may be ingested and indexed according to its configuration. Learn more about connecting SharePoint to Teamwork Graph and Teamwork Graph data usage.
Why is administrator consent required?
This connection uses delegated permissions, which let Atlassian access SharePoint and OneDrive content on behalf of a signed-in user, within that user’s existing access rights.
Microsoft’s recommended consent policy requires administrator approval for the requested file and site permissions, even though access is delegated. A Microsoft 365 administrator therefore needs to grant consent in your tenant before users reconnect to the new Atlassian application.
Administrator consent approves the application’s use of these permissions. It does not give users access to additional content or allow Atlassian to bypass their Microsoft access controls.
Before you start
The person granting consent must have one of these Microsoft 365 roles:
Global Administrator
Application Administrator
Cloud Application Administrator
They also need an Atlassian account to open the consent flow. They do not need to be an Atlassian organization or site administrator.
If you are not a Microsoft 365 administrator, obtain the consent link using one of the methods below and send it to someone with the required role.
Get the consent link
Choose one method. If you already have the site-specific consent link from Atlassian’s email, you do not need to create another link.
Option 1: Use the link in Atlassian’s email
Use the site-specific admin consent link included in the upgrade email from Atlassian.
If you prefer not to use an email link, an Atlassian organization administrator can create the link using Option 2.
Option 2: Create a site-specific link
Open Atlassian Administration directly.
Select Apps, then Sites.
Open the site for which consent is required.
Copy the site ID from the browser’s address bar. It appears immediately after
/s/in the URL.Replace
<siteId>in the following template with that site ID:
https://id.atlassian.com/outboundAuth/start?containerId=5545d3c9-79a8-4ea3-aa8b-4f69ed5ebf05&serviceKey=prod-microsoft-sharepoint-lmc-admin-consent&prompt=consent&contextAri=ari:cloud:platform::site/<siteId>Send the completed link to your Microsoft 365 administrator, or open it yourself if you have the required role.
Review the application and grant consent
Open the site-specific consent link.
Sign in to your Atlassian account if prompted.
Sign in with a Microsoft 365 administrator account for the Microsoft tenant used by your organization.
On the Microsoft consent screen, confirm:
Application name: Atlassian
Verified publisher: Atlassian
Review the requested permissions listed below.
Select Accept.
The application ID is 0c8611af-925f-491b-86f4-32fad2901689. It is not displayed on the consent screen. Use it to identify the application in Microsoft Entra when verifying completion.
A blank page can appear after you select Accept when using a copied or shared consent link. This is an expected limitation of the current flow. A blank page alone does not tell you whether consent succeeded. Follow the verification steps below.
Verify that consent succeeded
A Microsoft 365 administrator should complete this check before considering the administrator action complete:
Open the Microsoft Entra admin center.
Go to Enterprise applications.
Search for application ID
0c8611af-925f-491b-86f4-32fad2901689.Open the Atlassian application.
Open Permissions.
Confirm that the required permissions show that admin consent has been granted for your Microsoft tenant.
If the application is missing or the permissions do not show admin consent, repeat the consent flow and check again.
Permissions requested
The consent flow requests all six permissions below.
Permission | What it allows | Why it is needed |
|---|---|---|
| Read items in SharePoint sites that the signed-in user can access | Provides site and folder information |
| Read SharePoint and OneDrive files that the signed-in user can access | Supports link previews, inline previews, and applicable file-search experiences |
| Read the signed-in user’s basic profile | Identifies the user completing the connection |
| Maintain access to data the user has granted access to | Keeps the connection active after initial sign-in |
| View the user’s email address | Identifies the Microsoft account used for the connection |
| Sign the user in | Authenticates the user through Microsoft’s identity platform |
These permissions do not allow Atlassian to create, modify, or delete files in SharePoint or OneDrive.
Admin consent does not bypass Microsoft access controls. Granting consent does not give a user access to sites or files they cannot already access in Microsoft.
What happens next
After administrator consent is granted:
Existing users will be prompted to reconnect their Microsoft accounts.
Their connections will use the publisher-verified Atlassian application.
Existing SharePoint and OneDrive links in Jira and Confluence will remain in place and display as normal after reconnection.
Frequently asked questions
We do not use Rovo. Do we still need to act?
Yes, if your users use SharePoint or OneDrive Smart Links or previews in Jira or Confluence. Those experiences are affected independently of Rovo.
Why is this change happening?
Atlassian’s SharePoint and OneDrive integration is moving to a Microsoft publisher-verified application. Publisher verification helps Microsoft administrators confirm that Atlassian publishes the application.
What happens if we miss November 15, 2026?
After the deadline, users may be unable to resolve SharePoint and OneDrive Smart Links, display rich-link or inline-file previews, or reconnect their Microsoft accounts. Applicable SharePoint and OneDrive experiences in Rovo may also stop working.
Grant consent by November 15, 2026 to avoid interruption.
Will existing links or files be deleted?
No. Existing SharePoint and OneDrive links in Jira and Confluence are preserved. This upgrade does not delete your SharePoint or OneDrive files.
We already granted consent to the old application. Do we need to do it again?
Yes. A Microsoft 365 administrator must grant consent to the new publisher-verified application.
How do we know the administrator’s work is complete?
Verify the application and its granted permissions in Microsoft Entra using the steps under Verify that consent succeeded. Users will still need to reconnect their Microsoft accounts when prompted.
How do we revoke access later?
In the Microsoft Entra admin center, go to Enterprise applications and locate the Atlassian application using application ID 0c8611af-925f-491b-86f4-32fad2901689.
Removing the application revokes its access and disables the SharePoint and OneDrive experiences that depend on it for users in your Microsoft tenant.
Was this helpful?