Issue Summary

The following endpoint builds the OAuth URL (outboundAuthUrl) with only 3 scopes instead of the full 5 required scopes.

GET /agents/configuration/knowledge

As a result, the Microsoft access token is issued without "Files.Read.All" and "Sites.Read.All", causing Rovo Chat to fail when retrieving SharePoint/OneDrive content.

Steps to Reproduce

1. Set up the Rovo Connector for SharePoint & OneDrive in https://admin.atlassian.com/ and complete the admin consent flow in Microsoft Entra ID.
2. Open Rovo Chat and click the "Connect" button for the Microsoft SharePoint knowledge source.
3. Complete the Microsoft OAuth authentication flow.
4. In Rovo Chat, type a prompt requesting SharePoint content.

Expected Results

The outboundAuthUrl should include all 5 scopes defined in the Forge manifest:

 &scopes=Files.Read+Files.Read.All+Sites.Read.All+User.Read+offline_access 

Rovo Chat should successfully retrieve SharePoint/OneDrive content after OAuth.

Actual Results

The outboundAuthUrl returned by "GET /agents/configuration/knowledge" only includes 3 scopes:

 "outboundAuthUrl": "https://id.atlassian.com/outboundAuth/start ?containerId=... &serviceKey=onedrive &scopes=Files.Read+User.Read+offline_access" 

Rovo Chat returns an error to the user:

 Missing scopes: Files.Read.All, Sites.Read.All 

Workaround

The M365 admin can manually grant admin consent for Files.Read.All and Sites.Read.All on the Atlassian Links app in Microsoft Entra ID via App Registrations > API permissions > Grant admin consent.
Reference: Grant admin consent in App registrations (Microsoft Docs)