Set up Microsoft Teams Graph spoke instructions are missing something

[johnfeist]

This is the first time that I'm working with Integration Hub or Oauth and I'm a bit confused.

I'm following the instructions in the documentation very carefully.  I've entered the initial data in the Application Registry.  I don't have a token revocation URL, but as that is not mandatory I don't know if I need one.

When entering the entity scopes, the column headings in the documentation differ for each object.  When I go to enter the data, they remain as Name and OAuth Scope.  As far as I can tell, I have the values entered correctly and the entity profile is created.

When I create the credential, I enter the values as described in the documentation and hit Save.  From there, I get this error:

Since I followed all the instructions and confirmed that I've entered the correct values I go ahead and click the Get OAuth Token link.  That produces the following error from Microsoft:

This raises the following questions:

• What do I need to do to avoid getting the OAuth Access or Refresh token messages?
• Since I'm using OOTB functionality, how do I add a name value pair to the request body and what do I use for scope?  I assume that must come from the Microsoft side?

All suggestions are gratefully appreciated.

:{)

[johnfeist]

Hi Ashutosh,

Per the documentation, I selected:

From there, the system created this profile

Here are the scope details

I didn't include offline_access as a profile scope because in one of my attempts, I had that as the first scope and MSFT came back with that not being valid.

Thank you for taking the time to help me get this right.

:{)

[Ashutosh Munot1]

So you are consuming the oAuth of the third party tool and not severing servicenow as oAuth provider.

I need to check on this.

-Ashutosh

[johnfeist · Accepted solution]

I opened a HI ticket and between the support engineer and one of my colleagues who supports Azure it turned out to be an issue with what values were included in some of the URLs.  The strange message still appeared when I set up the credentials, but I got a token and that message was replaced with an acknowledgement that there was a token and it's expiry.

[Ashutosh Munot1]

HI,

So in short the issue was somewhere with the token.

Great