Connect SharePoint to Teamwork Graph

This connector covers both Microsoft SharePoint and OneDrive. Connecting SharePoint automatically makes OneDrive content available in Rovo Search as well.Existing SharePoint Connector users: Learn more about the required admin consent and re-authorization for continued sync of SharePoint assets. Action Required: SharePoint Connector Auth UpgradeGet answers from your documents and bring your files alongside your company knowledge.What is indexed?The SharePoint connector indexes these objects:Word Documents (.doc, .docx)Excel Spreadsheets (.xls, .xlsx)PowerPoint Presentations (.ppt, .pptx)PDFs (maximum 10 MB)Web pages(.html, .aspx)Encrypted documents do not get ingested.For each object, it indexes these attributes:NameURLCreated dateLast updated dateCreatorCollaboratorsDocument bodyUser data indexed:IDCreated dateLast updated dateDisplay nameJob titleDepartmentEmailHire dateBefore you beginThis setting controls what data is synced from SharePoint into Atlassian for indexing and search. When you access SharePoint data through Rovo at runtime, your own SharePoint access is used.You need SharePoint global admin permissions to connect SharePoint to Teamwork Graph.Teamwork Graph will always respect permissions. Users will only ever see files that they already have access to.Confirm that your Microsoft tenant allows user consent by going to Entra consent settings and ensuring "Let Microsoft manage your consent settings" is enabled. If this is not set, end-user authorization may fail.Many permissions in SharePoint are controlled through M365 Site groups. For the connector to correctly sync them, site groups should allow everyone to view its membership. To configure this:Go to https://[tenant-name].sharepoint.com/_layouts/15/groups.aspx and select each site for content to ingest.Under "Who can view the membership of the group", select Everyone and save.If this is not set, the connector cannot read group membership and permissions for content tied to those groups will not sync correctly.Connecting to SharePointTo get to the setup screen for SharePoint in Atlassian Admin:Go to admin.atlassian.com. Select your organization if you have more than one.Select Connectors, then All connectorsSelect Add connector, then, if you have more than one site, choose the site you want to connect to.Select Microsoft SharePoint and OneDrive and press Next.While you are on the SharePoint and OneDrive connector setup page,In a new tab, log in to your Microsoft account at Entra at entra.microsoft.com.In the side navigation, under Entra ID, select Overview.Copy the Tenant ID using the copy to clipboard button.7. Choose content to include: Select which SharePoint and OneDrive content is indexed. You can update these settings at any time.Two toggles control what's included. At least one must be on. If both are off, nothing is indexed.Include SharePoint sites: indexes content from SharePoint sites. Use the tabs to control which sites are included:Allow SharePoint sites: add SharePoint site URLs to include. Only those sites are indexed.Block SharePoint sites: add SharePoint site URLs to exclude. All other sites are indexed.Limit by date: index only content created or modified after a date you set.Limit by label: block content based on Microsoft Information Protection (MIP) sensitivity labels. Add sensitivity label GUIDs to the blocklist — any file or site carrying a blocked label is skipped during ingestion. This works at two levels:Document-level: individual files with a blocked label are skipped regardless of which site they are in.Site-level: if a site itself carries a blocked label (for example, marked Confidential at the site level), the entire site is skipped.Unlike site blocklists, sensitivity labels travel with the document. If a file moves between sites, the protection follows automatically — no blocklist updates needed. For content already indexed before the policy was configured, it stops appearing in Rovo search immediately and is purged from the index on the next full scan.To get your label GUIDs, use Microsoft Graph Explorer (not the Purview portal) with an admin account that has SensitivityLabels.Read.All. Use the id field from the response.For the full walkthrough, see Rovo Enhances SharePoint & OneDrive Connector with Sensitivity Label Blocking.For help adding URLs, see Manage blocklist and allowlist.Include personal sites: indexes content from users' personal sites, including OneDrive files. Use the tabs to control which groups are included:Allow personal sites: add Microsoft 365 Group IDs. Only those groups' personal sites are indexed. If left blank, all users' personal sites are included.Block personal sites: add Microsoft 365 Group IDs to exclude those groups' personal sites.Both toggles can be on at the same time.Layering controls: Sensitivity labels don't replace site blocklists or group scoping — they layer on top. For example, you might block high-sensitivity tiers (Highly Confidential, Restricted) via the label policy, exclude specific project sites via the site blocklist, and scope OneDrive to a subset of users via group controls. Each mechanism covers a different kind of risk.8. Admin consent: Click the button to navigate to Microsoft app to grant admin consent to allow users in the Atlassian account to connect to SharePoint and access SharePoint assets via Rovo Search or Rovo Chat. Once complete, check the box to attest that the admin consent is granted.9. Admin Authorize: Click the button to navigate to the Microsoft OAuth page. On this page, you are granting Atlassian Teamwork Graph access to your SharePoint/OneDrive accounts.Note: Although the permissions here are broad, Atlassian Teamwork Graph will only ingest assets that comply with the admin policy controls that were selected in the ‘Choose content to include’ section.