Outlook Integration error

Question

I am using connected system with Oauth2.0 to connect to office365 and get the calendars i m able to authorize using connected system however when testing the base url I get the below error 
 Invalid credentials 
 Appian was not able to authenticate with the access token you provided. This request requires Bearer authentication. HTTP/1.1 401 Unauthorized Next Steps 
 
 This integration is using a connected system with OAuth 2.0 authentication configured. You may need to authorize access to the external system and retry the request. 
 Make sure that you are using the correct OAuth 2.0 configuration for this external system 
 Make sure that the OAuth 2.0 configuration provides the required scope to make this request 
 Check the request and response for more details 
 Review the external systems documentation for information on what may have caused the problem 
 
 When i run the authorization its executes successfully. Has any one seen this issue before or can someone share the Oauth2.0 configuration related to outlook ( For outlook defining a scope is mandatory)

Steven Miccile · Accepted Answer

The Integration details for #2 are completely dependent on what Graph REST API you are trying to call and the format that API expects. You will have to read the Graph API documentation. I showed you the headers section which is important because that is how you pass the token. 
 But here is an example:

Steven Miccile · Answer

You have to build the details (url, parameters, body) of the 2 requests yourself. Integrations can be created outside connected systems so I recommend starting with that. For both of them you will select "None" for authentication since you will be configuring the token exchange yourself. This method below requests a new bearer token every call. You could also cache the token in the database for re-use, but we decided against that method in favor of this one to limit the exposure of where the token is accessible. 
 
 Integration 1 - Getting the bearer token 
 URL: https://login.microsoftonline.com/<INSERT_ORG_SPECIFIC_URL>/oauth2/v2.0/token 
 
 Parameters: None 
 Headers: None 
 Body: 
 "grant_type=client_credentials& scope=https%3A%2F%2Fgraph.microsoft.com%2F.default& client_id="&cons!YOUR_CLIENT_ID&"& client_secret="&cons!YOUR_CLIENT_SECRET 
 
 make sure to lock down the security on these constants to admins only 
 
 Integration 2 - Making a request using this token 
 URL/parameters/body: This is whatever Graph REST API you are trying to use 
 Headers: Authorization - "Bearer "&rule!MG_ws_getGraphBearerTokenQ().result.body.access_token 
 
 In this case, rule!MG_ws_getGraphBearerTokenQ() is what we configured in "Integration 1"

Karikalan Ramakrishnan · Answer

This has been fixed by adding the parameter " resource=https://graph.microsoft.com" on the request body. 
 However, still wondering why its not possible to achieve using HTTP connected system object. 
 Update: 
 Thanks Tim / Steve, 
 Connected System object Graph integration issue has been fixed with the parameters Scope https://graph.microsoft.com/.default and &ldquo;OAuth 2.0 token endpoint (v2). (In case of Azure AD personal a/c).

Outlook Integration error

Top Replies