Connect OneDrive to Rovo
Get answers from your documents and bring your files alongside the rest of your company knowledge.
This connector is only supported in Rovo Search. We're actively working on supporting this connector in Rovo Chat and Agents.
Before you begin
You need Microsoft Entra global admin permissions to connect OneDrive to Rovo.
Only Microsoft Excel, PowerPoint, and Word documents are available to Rovo.
Rovo will always respect permissions. Users will only ever see files that they already have access to.
Connecting to OneDrive
To get to the setup screen for OneDrive in Atlassian Admin:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Settings > Rovo.
Under the Sites tab, next to the site you want to connect, select More actions () and select Add connector.
Select Microsoft OneDrive and press Next.
Azure portal
Log in to your Azure portal and navigate to Microsoft Entra ID.
2. In the side navigation, under Manage, select App registrations > New registration.
If you’ve set up other Entra app registrations for Rovo connectors (such as SharePoint or Teams), we strongly recommend setting up a new registration for each connector to avoid issues with rate limiting.
3. On the Register an application page in the Azure portal, name the connection to Rovo (for example, “OneDrive Atlassian Rovo”), select Accounts in this organizational directory only, and then select Register.
4. In the side navigation, under Manage, select API permissions, select Add a permission on the API permissions page, then Microsoft Graph.
5. Select Application permissions and select expand all.
6. Copy these permissions one by one, and paste them into the search line. Click the checkbox. Repeat for all permissions.
1
2
3
4
5
Directory.Read.All
Files.Read.All
Group.Read.All
GroupMember.Read.All
User.Read.All
7. Select Add permissions.
8. There’s one more permission to add, but it’s in a different API. Select Add a permission again, then this time Office 365 Management APIs.
9. Select Application permissions, and look for ActivityFeed.Read. Select the checkbox, and select Add permissions.
10. Select Grant admin consent for <workspaceName>.
11. Once this is done, back on the Manage > API permissions screen, in the Status column of the table, you should see green ticks and Granted for <workspace> (except the permission User.Read, which doesn't require Admin consent).
![Screenshot of list of permissions in Azure, with Granted showing against each permission type](http://images.ctfassets.net/zsv3d0ugroxu/4GEzv7KgTyFuAOE0ULMEjs/38edf6f97b7dd47605b2db0818165989/screenshot_OneDriveSetupExtra3.png)
12. Navigate to Manage > Certificates & secrets, and select Create app secret and fill in the form.
13. Once you’ve created a secret, copy the Value field. You’ll need this soon.
14. Go to Overview and copy the following details back into the admin.atlassian.com connector setup screen:
Your application ID
The directory ID
15. Enter the Client secret value you copied earlier as Client secret.
16. Finally, review the disclaimer, and select Save.
Next steps
After you’ve finished Connecting OneDrive:
Documents will start to show in Search incrementally over the next few hours.
Your team members will see OneDrive show up as a filter option in Search. If they haven’t connected to OneDrive from their Atlassian account, they may be asked to connect before they can see results. This is required so Rovo can make sure your teammates only see results they usually have access to.
Depending on the number of documents in OneDrive, it may take some time for all your OneDrive content to be indexed and appear in Search.
Was this helpful?