web
You’re offline. This is a read only version of the page.
close
Skip to main content
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps - Connector Development / Service Principal Conn...
Power Apps - Connector Development
Suggested answer

Service Principal Connection Broken

(2) ShareShare
ReportReport
Posted on by MK-16072110-0 2
No matter what I do, when I create a custom connector using Azure Active Directory and Service Principal Connection in make.powerapps.com UI I get an error message when creating the connection "Failed to login. Code grant authentication is not supported on a client credential connection."  If I perform the same steps in Power Automate it works just fine.  What gives? Does PowerApps not support client code flow? Why does it allow you to choose the authentication type when creating the connection.
Categories:
Authentication
I have the same question (0)
  • Michael E. Gernaey Profile Picture
    Michael E. Gernaey 47,123 Super User 2025 Season 2 on at
    Service Principal Connection Broken
     
    I believe the issue is, they have been changing IP addresses in the back ends. Its very possible this broke your connection so you had to recreate it. It happened to me as well
     

    If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

    Thank you!
    Sincerely, Michael Gernaey
     
  • Suggested answer
    rohitsbots Profile Picture
    rohitsbots 264 on at
    Service Principal Connection Broken
    This was working fine until last week for me from PowerApps as well. Today suddenly the connection broke and then i had to open the custom connector from Power Automate and recreate the connection using Client ID, Client Secret, Tenant Id
  • Suggested answer
    Michael E. Gernaey Profile Picture
    Michael E. Gernaey 47,123 Super User 2025 Season 2 on at
    Service Principal Connection Broken
     
    This is accurate and done intentionally by the platform. It is ok to run things as a service connection (with a license), in power platform as long as the users who trigger also have a license. Licenses are not just based on what connector you use, but what data is accessed and where it is moved too and a bunch of other things.
     
    In this scenario, the front end is not intended to allow you to do this. Its just intentionally that way because they do not want the front end being run by delegation to other services.
     
    The work around is essentially to use a flow.
     
    There have been many who have asked for this functionality but the answer has always been no.
  • MK-16072110-0 Profile Picture
    MK-16072110-0 2 on at
    Service Principal Connection Broken
    The custom connector is used to call an Azure function integrated with Azure AD Auth use app registration to expose API permissions via Application permissions instead of user delegation.  Ultimately I want the connector to use certificate based authentication using service principal connection to not have to worry about client secrets expiration.  The Azure function does not need to know who the end user is, and app auth will suffice for our needs.  This scenario is working fine when you create the custom connector in power automate.  As mentioned when trying to create the same custom connector in power apps you get the Failed to login. Code grant authentication is not supported on a client credential connection." error.  In fact you can put in fake clientid, secret, and tenantid in the connection UI and it will always return that error, it seems as though you can not choose service principal connection in oAuth azure ad in power apps, even though they expose these options in the security UI when creating the custom connector.
  • Michael E. Gernaey Profile Picture
    Michael E. Gernaey 47,123 Super User 2025 Season 2 on at
    Service Principal Connection Broken
     
    So Power Apps as the UI does in fact act differently because unlike Power Automate, which is Uiless (unless you mean Desktop), Power Apps in fact is logged in as the user and doing things like delegation app permissions and stuff like that.. can work, but is not intended specifically too work. again its possible, but I'd have to see and fully understand the scenario.

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

News and Announcements

Welcome to the Power Platform Communities
Announcing our 2025 Season 2 Super Users!
Responsible AI policies for the Community

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Telen Wang – Community Spotlight

We are honored to recognize Telen Wang as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 637 Most Valuable Professional

#2
stampcoin Profile Picture

stampcoin 570 Super User 2025 Season 2

#3
Power Apps 1919 Profile Picture

Power Apps 1919 473

Last month Overall leaderboard

Featured topics

Product updates

Microsoft Power Platform Community release plans