cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Frequent Visitor

Error testing custom connector in GCC

I'm getting the following token error when trying to test a new custom connector.

 

Is this an issue or limitation with the current state of the Government Community Cloud (GCC) instances of PowerApps?

 

-

During the setup of a new connector, when clicking "Test operation" on step 4. Test.

 

Error Message:   Operation failed (400), see response below
 
Request
Method get
Headers
{
"Authorization": "Bearer ........"
}
 
Response
Status
tokenexchange (400)
Headers
{
"content-length": "340",
"content-type": "application/json",
"x-ms-apihub-cached-response": "false",
"x-ms-failure-cause": "apihub-token-exchange"
}
Body
{
"status": 400,
"source": "https://power-apis-usgov001-public.token.azure-apihub.us:443/tokens/power-apis-usgov001-public/nd.2D...",
"message": "Error from token exchange: Bad authorization token. The access token is from wrong audience or resource."
}
 
9 REPLIES 9
Community Support
Community Support

Hi @ecornell ,

 

You should use a different set of URLs to access PowerApps US Government

More information:

powerapps-us-government#powerapps-us-government-service-urls

 

And more information about GCC

powerapps-us-government

 

Hope this could be helpful.

 

Best Regards.

Yumia

We are using the new government URLs to create and test the connector.

 

https://gov.web.powerapps.us/environments/Default-2dea0464-da51-4a88-bae2-b3db94bc0c54/customconnectors

Anonymous
Not applicable

Hi @ecornell are you still receiving this error? 

 

@Anonymous 

Yes, the error is still occuring.

New Member

Is this issue resolved? We're still getting this on our environment. Thanks.

No, custom connectors are still broken in our GCC environment.

Regular Visitor

Hi, I'm working for another organization using GCC and we are running into this same error message while doing the same thing. We've validated in a regular commercial tenant that everything works as expected but the same settings in a GCC tenant are resulting in this error.

We thought it could have something to do with the fact that my organization is using a Commercial Azure tenant while the Office 365 tenant is GCC. Are you setup the same way or is everything GCC? If not, then it could just be an issue with GCC in general and Microsoft needs to look further into this...

Regular Visitor

Getting the same error, not sure if you have found a fix to it.

I had a ticket open with Microsoft for a few months and they finally told me they believe the test functionality is broken in the configuration window of custom connectors in GCC tenants. Sure enough, when I added the connector to my Flow and ran it there it worked as expected. May want to just ignore the test tab for now and see if it works.

Helpful resources

Announcements
New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

New Power Super Users

Congratulations!

We are excited to announce the Power Apps Super Users!

Power Apps Community Call

Power Apps Community Call: February

Did you miss the call? Check out the Power Apps Community Call here.

Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

Top Solution Authors
Top Kudoed Authors
Users online (21,373)