Azure Resource Manager: While creating new connection showing a error message

[vgouth]

Describe the Bug with repro steps

1. Create a consumption logic app
2. Open designer and add http request trigger
3. Add any action from Azure Resource Manager Eg: Read a subscription
4. Create a new connection, if there is any existing connection click on change connection and select Add new
5. Change Authentication type to Service Principal
6. Give connection name as mandatory field
7. Click on create new
8. Connection status is showing some error

Expected: Connection status should show connected.

Actual: Connection status is showing error message.

What type of Logic App Is this happening in?

Consumption (Portal)

Which operating system are you using?

Windows

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

Screenshots or Videos

Browser

Edge

Additional context

Version : 2.41028.1.6

[ccastrotrejo]

Talked with @vgouth offline and the connection is created successfully, however as there is clientSecret and clientID when creating it. This is expected by design.

[ccastrotrejo]

Reopen it and marked it as a feature request to mark the secret and id as required

[vgouth]

Issue still repro in latest test pass
Client secret and client id should be in mandatory field if those fields are required for creating a connection.
Version: 0.2022.1.794

[ccastrotrejo]

The API call to get the connector properties retrieve the inputs as not required

[vgouth]

Issue repro in latest canary environment
Version: 0.2022.1.806

[vgouth]

Issue repro in latest canary test pass
Version: 0.2022.1.811

[vgouth]

Issue repro in latest canary test pass
Version: 0.2022.1.811

[vgouth]

Issue repro in latest staging test pass

Version: 2.41231.2.4

[takyyon]

@ccastrotrejo Mind looking into this please?

[ccastrotrejo]

Hi @takyyon this is something that backend engineers need to take a look at. The reason on why we are displaying the error message after creating the connection, is because its getting created without Client ID and Client secret. Therefore there is no way to get a solid connection without these.

I checked the connector and neither of these properties come back as required. They need to enable that.

[takyyon]

@ccastrotrejo Do you mind starting a thread with backend teams for this? I'll consider this as a non-blocker for our deployment right now but let me know if you feel otherwise.

[ccastrotrejo]

@takyyon Yep I can do that, and I agree, this isn't a blocker for the deployment

[vgouth]

Issue repro in latest test pass
Version: 2.50107.1.3

[vgouth]

Issue repro in latest stage test pass
Version: 2.50203.1.1

[vgouth]

Issue repro in latest canary test pass
Version: 2.0.20250207.1

[vgouth]

Issue repro in latest stage test pass
Version: 2.50224.1.3