Showing results for 
Search instead for 
Did you mean: 
Level: Powered On

Custom Connector with AD Token frequently expires with 401, fix connection...

Users are frequently presented with PowerApps error:
One or more of your connections may not be authenticated. Tap here to fix them.


  • Our custom connector points to a REST API secured by Azure AD. 
  • Problem is that while using our PowerApp, users are frequently and randomly requested to 'fix connection' and refresh the PowerApp because their session has expired. 
  • I imagine the reason behind this is to allow connector to acquire a new access token.
  • Should this not last for an hour at least. Should this not automatically refresh using refresh token?
  • We are trying to understand, thereby control or avoid this happening altogether. 
  • We only have 5 users making so do not believe the issue is in exceeding PowerApps throttling limits:

PowerApps currently support 600 requests per minute per user and up to 30 concurrent calls per user.

We suspect it might be something to do with idle time within the PowerApp, should such a concept exist, or something related to connector renewal time. More information is needed around these concepts in regards to behaviour and configurability. 


In regards to idle time, some users suspect any inactivity in PowerApp over 2 minutes results in the connector expiring. 




Helpful resources


Power Apps Super User Class of 2020

Check it out!


New Badges

Check it out!


Power Apps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!


Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020


Difinity Conference

The largest Power BI, Power Platform, and Data conference in New Zealand

Top Solution Authors
Users online (6,202)