cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ecornell
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
v-yuxima-msft
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.

jayeshmhatre
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.

ThinkHaven
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...

alsomat
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
PA_User Group Leader_768x460.jpg

Manage your user group events

Check out the News & Announcements to learn more.

Power Query PA Forum 768x460.png

Check it out!

Did you know that you can visit the Power Query Forum in Power BI and now Power Apps

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

R2 (Green) 768 x 460px.png

Microsoft Dynamics 365 & Power Platform User Professionals

DynamicsCon is a FREE, 4 half-day virtual learning experience for 11,000+ Microsoft Business Application users and professionals.

Users online (2,829)