Managed Connector using MS Entra ID (AAD) integrated authentication type shows error status when editing Edit API connection in existing API connection page.

[zhangadreedom]

Describe the Bug

Hi Team,

Managed Connector using MS Entra ID (AAD) integrated authentication type shows error status when editing Edit API connection in existing API connection page.
I can repro this error with SQL Connector and Blob connector

Plan Type

Consumption

Steps to Reproduce the Bug or Issue

1. as shown in the attached image, we are connecting to "sqlsr-datakit-prod-001". I created sql-13 several tens of minutes ago.

2. If I edit the sql-13 API connection in the order shown in the image after running the logic app above, the same error as before will occur.

Workflow JSON

No response

Screenshots or Videos

No response

Additional context

Kusto query to show the error:
cluster('azconnectjapan.kusto.windows.net').database('LogicApps').HttpIncomingRequests
| where clientRequestId =="69eebbed-dae7-44dd-9ad8-6e497a4387d4"

cluster('azconnectjapan.kusto.windows.net').database('LogicApps').Message
| where TIMESTAMP between (datetime(2024-09-18 05:45:44.4780772) .. datetime(2024-09-18 05:50:44.4780772))
| where * has "69eebbed-dae7-44dd-9ad8-6e497a4387d4"

Error message
{
"status": 400,
"message": "Invalid connection settings\r\n inner exception: Not enough information to establish a Sql Connection\r\nclientRequestId: 69eebbed-dae7-44dd-9ad8-6e497a4387d4",
"error": {
"message": "Invalid connection settings\r\n inner exception: Not enough information to establish a Sql Connection"
},
"source": "sql-je.azconn-je-001.p.azurewebsites.net"
}

[github-actions]

This issue is stale because it has been open for 45 days with no activity.