Connect Outlook Mail to Rovo
Easily find that ‘as per my previous email’ by bringing your inbox to search.
Before you begin
You need Microsoft Entra global admin permissions to connect Outlook Mail to Rovo.
Rovo returns emails using Outlook's search capabilities. Only your email’s contents will be searchable to Rovo. Attachments are not available.
Your email content (subject, body, etc) is never ingested or stored within Atlassian.
Atlassian may ingest and store certain data about user interactions with emails, such as unique identifiers and timestamps for when an email was opened or sent. This data may be shown as part of your search results.
Rovo will always respect permissions. Users will only ever see emails that they have sent or received.
Connecting to Outlook Mail
To get to the setup screen for Outlook Mail 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 Outlook Mail 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 OneDrive or SharePoint), 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, “Outlook Mail 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 the following permissions one by one, and paste them into the search line. Click the checkbox. Repeat for all permissions.
1
2
3
4
5
User.Read.All
Group.Read.All
GroupMember.Read.All
Mail.Read
Mail.ReadBasic.All7. Select Add permissions.
8. Select Grant admin consent for <workspaceName>.
9. 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).
10. Navigate to Manage > Certificates & secrets, and select New client secret and fill in the form.
11. Once you’ve created a secret, copy the Value field. You’ll need this soon.
12. Go to Overview and copy the following details back into the Admin screen for the Rovo connector:
Your application ID
The directory ID
13. Enter the Client secret value you copied earlier as Client secret.
14. Finally, review the disclaimer, and select Save.
Next steps
After you’ve finished connecting Outlook Mail:
Emails will start to show in Search incrementally over the next few hours.
Your team members will see Outlook Mail show up as a filter option in Search. If they haven’t connected to Outlook 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 emails they have sent or received.
Depending on the number of emails in Outlook, it may take some time for all your Outlook content to be indexed and appear in Search.
Was this helpful?