web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Custom Connector - For...
Power Automate
Unanswered

Custom Connector - Forbidden: Status 403

(0) ShareShare
ReportReport
Posted on by 35

Found several posts in this forum but none actually helps in my case. Appreciate if anyone can provide some insight for the case below.

 

Issue & Description:
We are using We have 2 groups of users that located in different location and network infrastructure.

- Group A users (e.g. userid1@abc.com; userid2@abc.com) able to trigger the Flow without any issue.
- Group B users (e.g. userid3@abc.com; userid4@abc.com) failed with the following error message (Forbidden code 403).

 

What we have tried so far, but result is still the same:
- Recreate the Flow and reconnect the connector with Encodian custom connectors.
- Cross checked and ensure connection authority are shared to group B user IDs, user roles are the same for all user IDs.
- Checked the support page on Encodian webpage, don’t find any information related to firewall/whitelist information.
- Cleared cache, relog to app.

 

 

Initially we suspected the firewall of group B network is the root cause. However, when group B users login with userid1 & userid2 in their network, the flow run successfully. Does not seem like a firewall issue now, more to the individual profiles that having access limit to this connector even though access is shared?

 

1.png

Categories:
I have the same question (0)
  • v-litu-msft Profile Picture
    on at

    Hi @Eagerboy,

     

    What's the license of userid3@abc.com and userid4@abc.com? If they are free trial, they could not use the custom connector:

    https://asia.flow.microsoft.com/en-us/pricing/

    Annotation 2019-10-17 094134.png

    Best Regards,
    Community Support Team _ Lin Tu
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

  • Eagerboy Profile Picture
    35 on at

    Hi @v-litu-msft ,

     

    We did cross checked all the licenses on the user IDs, and they should be able to use the custom connector (PA Plan 2).

     

    Anyway, this morning we resaved the app (that using the Flow in question) in different name, without any changes on coding/setting/authority, and guess what, now it is working properly and all our users can successfully run the flow.

     

    Seems like some sort of bugs in PowerApps where it failed to recognize the access authority in the initial app?

  • v-litu-msft Profile Picture
    on at

    Hi @Eagerboy,

     

    It seems like a bug, but I have ever met it, I will record it. If I met more of this situation, I will report it to the development team.

    Thank you for your feedback and solution!

    Best Regards,
    Community Support Team _ Lin Tu
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard