Confluence Graph Connector

[Jan-Nicklas Klaassen]

I have tried to set up a Microsoft Graph Connector to Confluence cloud. I followed the instructions according oAuth 2.0 as follows:

1. Sign in to Atlassian Developer console with your Atlassian Confluence admin account.

2. Click on Create and select OAuth 2.0 integration.

3. Provide an appropriate name for the application and create the new app.

4. Navigate to Permissions from the navigation pane on the left. Click Add for Confluence API. Once added, click on Configure, and Edit scopes and select the following scopes.

   Expand table

   Scope name	Code	Description
   View content details	read:content-details:confluence	Crawl content satisfying criteria.
   View groups	read:group:confluence	To access group permissions of content.
   View user details	read:user:confluence	To access individual user details to support permissions.

5. Click Save.

6. Navigate to Authorization from the navigation pane on the left. Add the callback URL, for Microsoft 365 Enterprise: https://gcs.office.com/v1.0/admin/oauth/callback, for Microsoft 365 Government: https://gcsgcc.office.com/v1.0/admin/oauth/callback and save the changes.

7. Navigate to Settings from the navigation pane on the left. You get the Client ID and Secret from this page.

   Complete the connection settings step using the Client ID and Secret.

However, after I try to log in with the client ID and the client secret, I get the error message “Failed to load app”.

Does anyone have any idea what the reason for this could be?

[Florian Obradovic]

Same here with Confluence On-premises Microsoft 365 Copilot connector when clicking authorize:

{"error":{"details":[{"code":"InvalidValue","source":"callbackUri","message":"Invalid callbackUri https://eur1prod.gcs.office.com/v1.0/admin/oauth/callback?error=invalid_scope&error_description=The+scope+used+in+the+request+%5B%27admin%27%5D+is+not+valid+for+client+scope+%5B%27ADMIN%27%5D&state=TENANT-ID-TENANT-ID|confluenceonprem1|2171. Url does not contain 'code'"}],"code":"InvalidRequest","message":"The request is malformed or incorrect."}}

[Florian Obradovic]

I logged a call with Microsoft 

[Florian Obradovic]

I tried it again, but now I get

{"error":{"details":[{"code":"OnPremAgentOffline","message":"Graph connector agent associated with the connection is not reachable. Either the agent is not running or app credentials have been expired/revoked"}],"code":"FailedDependency","message":"The requested action depended on another action, and that action failed"}}

[Florian Obradovic]

I was able to use basic authentication as a "workaround" instead of Oauth 2.0

[Heike Stü]

This seems to be a general problem. We are in contact with both the Atlassian and Microsoft Support about this. There seems to be a problem with how the Client IDs are handled in regards to upper / lower case.

Best,

Heike

[Heike Stü]

In our case Microsoft finally suggested a workaround and use https://admin.microsoft.com instead of https://admin.cloud.microsoft/.

They also said it is supposed to be fixed soon.

Best,

Heike

[Florian Obradovic]

Thanks @Heike Stü 

For me it just re-directs to admin.cloud.microsoft

[Clark Everson]

Hi @Jan-Nicklas Klaassen 

Welcome to community

For your question however I would recommend checking out the developer community as they have their own and there will be more developer centric folk to help there: https://community.developer.atlassian.com/

Best,

Clark