Skip to main content

Notifications

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate - Using Connectors / SQL Server Connector E...
Power Automate - Using Connectors
Unanswered

SQL Server Connector Error

(1) ShareShare
ReportReport
Posted on by aaronllanes 18

Could not retrieve values.
The dynamic invocation request failed with error:
{"status":403,"source":"https://power-te-westus.azurewebsites.net:443/tokens/msmanaged-na/sql/673e40aac7f443d2832ba19a0652274b/exchange",
"message":"Error from token exchange: Connection msmanaged-na/logicflows/2d52a15d-7c2f-4f7b-9a9e-ff06300fae87
@https://msmanaged-na.azure-apim.net/ version -9223372036854775808 msmanaged-na/sql/673e40aac7f443d2832ba19a0652274b is not allowed to access connection msmanaged-na/sql/673e40aac7f443d2832ba19a0652274b"}.

  • bcampbell13 Profile Picture
    bcampbell13 58 on at
    Re: SQL Server Connector Error

    To Help any others and clarify, it does seem that sharing the connection makes it loose it server in.  What you need to fill in after you done all the sharing, is go to the Connections section (Under Data), find the connection, click edit and re-enter the username and password.

  • aaronllanes Profile Picture
    aaronllanes 18 on at
    Re: SQL Server Connector Error

    Hi  @Erlandcrf 

    we found the issue, it looks like when sharing the flow with other users the SQL Server Connector is losing all the setup,
    so you need to provide all the info again

    thank you for your help

  • erlycrf Profile Picture
    erlycrf Microsoft Employee on at
    Re: SQL Server Connector Error

    Hello @aaronllanes 

     

    Based on the error message, this is a permissions issue, so, does the user affected has the right access to the SQL Server resource that it's trying to reach?

    For this scenarios I would validate with the affected user if they can reach the SQL Server resource out of the context of Power Automate.

    Then, it's this something happening to a single user? Also, it's this happening only to single resource inside of SQL Server (table)?

     

    Another test that I would do is to validate in a different environment (if available) if the user it's getting the same issue.

     

    Hope this can help to isolate better the issue.

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

Quick Links

Paul Stork – Community Spotlight

We are honored to recognize Paul Stork as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 497 Super User 2025 Season 1

#2
David_MA Profile Picture

David_MA 436 Super User 2025 Season 1

#3
Riyaz_riz11 Profile Picture

Riyaz_riz11 244 Super User 2025 Season 1

Last month Overall leaderboard

Featured topics

Product updates

Microsoft Power Platform Community release plans