Upgrade your SharePoint and OneDrive connection in Atlassian

 

To keep SharePoint and OneDrive Smart Links and search working, a Microsoft 365 administrator must grant consent to Atlassian's new Microsoft publisher-verified application by November 15, 2026.

What you need to know

  • Who needs to act: A Microsoft 365 administrator

  • Application name: Atlassian

  • Application ID: 0c8611af-925f-491b-86f4-32fad2901689

  • Deadline: November 15, 2026

  • Affected experiences: SharePoint and OneDrive Smart Links in Jira and Confluence, and SharePoint and OneDrive experiences in Rovo (if SharePoint/OneDrive connector is enabled)

If consent is not granted by the deadline, users may no longer be able to resolve SharePoint and OneDrive Smart Links, display link previews, or find SharePoint and OneDrive content through Rovo.

What's changing

Atlassian's SharePoint and OneDrive integration is moving to a Microsoft-verified app. This means:

  • Same functionality: Your team's SharePoint and OneDrive experience in Confluence, Jira, and Rovo remains the same.

  • One-time reconnection: Users will be prompted to reconnect their account. This takes a few seconds.

Publisher verification helps Microsoft administrators confirm that Atlassian is the organization publishing the application. Users will continue to access only the SharePoint sites and OneDrive files that their Microsoft account permits them to access.

After a Microsoft 365 administrator grants consent, users will be prompted to reconnect their Microsoft accounts.

Connect to OneDrive

Experiences included in this upgrade

This upgrade applies to:

  • SharePoint and OneDrive link previews and inline previews

  • SharePoint and OneDrive experiences in Rovo that use this connection (if SharePoint/OneDrive connector is setup)

A Microsoft 365 administrator with one of the following roles must complete the consent flow:

  • Global Administrator

  • Application Administrator

  • Cloud Application Administrator

Before granting consent, verify these application details on the Microsoft consent screen:

  • App Name: Atlassian

  • Application ID: 0c8611af-925f-491b-86f4-32fad2901689(not seen on the consent screen)

  • Verified publisher: Atlassian

To grant consent:

  1. Open the admin consent link provided in the email, or Atlassian Administration.

  2. Sign in to an Atlassian account if prompted.

  3. Sign in with a Microsoft 365 administrator account.

  4. Review the requested permissions.

  5. Select Accept.

The Microsoft administrator needs 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 administrator

Send the consent link to someone with one of the required Microsoft 365 roles.

You can obtain the link in one of these ways:

  1. [Recommended/Easiest] Use the site-specific consent link included in the email from Atlassian.

  2. To obtain the consent URL, an Atlassian organization admin should go to Atlassian Administration → Connectors. If you have multiple sites, select the relevant Atlassian site from the Sites menu.

    1. If Microsoft SharePoint and OneDrive is already listed:

      1. Open the Actions (•••) menu and select Manage connector.

      2. On the connector management page, open the Actions (•••) menu beside Connector.

      3. Select Edit connector.

      4. In the modal, select Copy consent link from the Admin consent section.

    2. If Microsoft SharePoint and OneDrive isn’t listed:

      1. Select Add connector.

      2. Choose Microsoft SharePoint and OneDrive.

      3. Select Copy consent link from the Admin consent section.

You don’t need to complete the connector setup or add the connector. Opening the setup page is only necessary to obtain the admin consent URL.

  1. Create a site-specific consent link using the instructions below:

  2. In Atlassian Administration, select Apps, then Sites.

    • Open the site for which consent is required.

    • Copy the site ID from the site's URL. On your address bar, look for the site ID right after the /s/

    • Replace <siteId> in the following URL:

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>

e. Send the completed URL to your Microsoft administrator.

When admin uses a copied or shared consent link, the browser may display a blank page after they click the grant consent / accept button. This is an expected limitation of the current flow.

To verify completion:

  1. Open the Microsoft Entra admin center.

  2. Go to Enterprise applications.

  3. Search for application ID 0c8611af-925f-491b-86f4-32fad2901689.

  4. Open the Atlassian application.

  5. Open Permissions.

  6. 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.

Permissions requested

Permission

What it allows

Why it is needed

Sites.Read.All

Read items in SharePoint sites that the signed-in user can access

Provides site and folder information for Smart Links and Rovo

Files.Read.All

Read SharePoint and OneDrive files that the signed-in user can access

Provides link previews, inline previews, and file-search experiences

User.Read

Read the signed-in user's basic profile

Identifies the user completing the connection

offline_access

Maintain access to data the user has granted access to

Keeps the SharePoint and OneDrive connection active after the initial sign-in

email

View the user's email address

Identifies the Microsoft account used for the connection

openid

Sign the user in

Authenticates the user through the Microsoft identity platform

These permissions are read-only. They do not allow Atlassian to create, modify, or delete files in SharePoint or OneDrive.

Admin consent does not bypass Microsoft access controls:

  • If a user can access a site or file in Microsoft, they can access it through the applicable Atlassian experience.

  • If a user cannot access it in Microsoft, granting consent does not give them access through Atlassian.

How data is handled

If your organization separately configures a synced Teamwork Graph connector for Rovo, content may be ingested and indexed according to that connector's configuration. Learn more about connecting SharePoint to Teamwork Graph and Teamwork Graph data usage.

  • Existing smartlink users will be prompted to reconnect their Microsoft account.

  • SharePoint and OneDrive connections will use the publisher-verified Atlassian application.

  • Existing SharePoint and OneDrive links in Jira and Confluence will be preserved.

  • SharePoint and OneDrive Smart Links, previews, and applicable Rovo experiences will continue working.

Frequently asked questions

Why is this change happening?

Microsoft requires apps that request organization-wide permissions to go through a verification process. The verified app provides your organization with stronger security assurances and is required for continued access to SharePoint data.

No. Existing SharePoint and OneDrive links in Confluence pages and Jira issues are preserved. After reconnecting, they'll display as normal.

Existing connections may continue to work until

After that date, users in your Microsoft tenant may be unable to:

  • Resolve SharePoint and OneDrive Smart Links

  • Display rich-link or inline-file previews

  • Reconnect their SharePoint and OneDrive accounts

  • Find SharePoint and OneDrive content through applicable Rovo experiences

Grant consent before the deadline to avoid interruption.

You'll need to grant consent again for the new verified app.

You can revoke consent at any time in the Microsoft Entra admin center under Enterprise applications. Search for "Atlassian" and remove the app. Note that revoking consent will disable SharePoint and OneDrive features in Atlassian for all users in your organization.

Still need help?

The Atlassian Community is here for you.