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 Secur...
Power Automate
Unanswered

Custom Connector Security Settings Reset after Deployment to Prod via ALM

(0) ShareShare
ReportReport
Posted on by 12

I've observed a peculiar issue when deploying solutions to production, particularly concerning the security settings of custom connectors. These connectors are automatically included in our solution when we add connection references to them. However, it seems that their security settings reset or change after deployment.

 

Example 1:

Screenshot 2023-09-12 at 13.37.03.png

In our development environment, we have a custom connector using API Key authentication. The Parameter name is set to api-key. However, when this is imported to prod, it reverts to the default parameter name, which is Ocp-Apim-Subscription-Key. Once I manually correct this and update the connector in prod, it operates as expected.

I also checked the swagger, but they are identical (except for example 2) in both cases.

 

Example 2:

This situation is trickier. If we use the default Parameter name (Ocp-Apim-Subscription-Key) in the dev environment, after deployment, there's no visible change in the production settings. Despite this, the connector doesn't function correctly. The solution is to click 'Edit' under the security settings in prod and then immediately 'Update' the connector, without actually making any changes. Only then does it work.

 

In both scenarios, until these changes are made, we are met with errors such as "API Key not found" or something similar.

It's evident that some settings or parameters are being altered during the migration between environments, but pinpointing the exact cause has been challenging. Does anyone know of specific environment or deployment pipeline settings that could influence this? Or has anyone encountered a similar issue?

 

As a temporary fix, I've created a 'Custom Connector Tester' flow to verify functionality post-deployment, and I manually correct issues as they arise. However, this isn't a sustainable solution, especially since flows can be disrupted during the rectification process.

 

Any insights or solutions would be greatly appreciated!

Categories:
I have the same question (0)

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
David_MA Profile Picture

David_MA 245 Super User 2025 Season 2

#2
Expiscornovus Profile Picture

Expiscornovus 207 Most Valuable Professional

#3
trice602 Profile Picture

trice602 190 Super User 2025 Season 2

Last 30 days Overall leaderboard