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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Unable to make Connect...
Copilot Studio
Suggested Answer

Unable to make Connections to SQL work when copying app to new environment

(1) ShareShare
ReportReport
Posted on by 2
I exported an APP (not in a solution) from one environment (DEV) and restored it into another new environment (DEV). I then created a 'Solution' from the App in the DEV environment. I then ran into the problem noted below. However, two days later I was able to edit the app in DEV, without getting the App Permissions errors and the SQL showed as connected properly. Now, the next day, once again it gives the same access issue. Any idea on how to fi this? I have wasted days on this. Short of dropping ALL my connections (many dozens of them - all to tons of different SQL tables) and recreating them again, is there something I can do to get this to work? Not sure how it worked yesterday, but that was the only time it has allowed SQL permissions since moving to this DEV environment (I had admin rights to the environments). And, if I have to recreate all these connections, should I do it through Connection References? Not sure how much more work that will then be as well. The end goal is to be able to do development in DEV environment and then update the app in the PROD environment. So lost trying to get this in place and working. Losing days and days of time on this an not sure where to turn. Would appreciate ANY help! Thanks!
 
I have the same question (0)
  • Suggested answer
    Vinoth Selvam Profile Picture
    1,592 Super User 2025 Season 1 on at
     
    Double-check that your admin role in the new DEV environment has all required permissions not just at the Power Platform level but also for SQL data access within the environment. Sometimes admin roles vary subtly across environments or don’t propagate instantly.
     
    Using connection references can indeed help when moving solutions between environments, especially for SQL connections. A connection reference allows you to define connections centrally within your solution, so if you rebuild them once with connection references, they should automatically bind as you migrate across environments, reducing the need to reset individual connections for every table.
     
    Thanks.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 594

#2
chiaraalina Profile Picture

chiaraalina 170 Super User 2026 Season 1

#3
deepakmehta13a Profile Picture

deepakmehta13a 118

Last 30 days Overall leaderboard