Connections not appearing in connectors after being added to the connections.json file

[wbl-patrickpanebianco]

Describe the Bug

I have manually added some SFTP connections to the connections.json file via the web portal. I have had to add the connections this way and not directly through the connectors in the Workflow as they retrieve values from the Azure Keyvault. See below a snippet of connections.json - I have obscured the real data:

  "serviceProviderConnections": {
    "sftp-1": {
        "displayName": "sftp-1",
        "parameterValues": {
            "disableConnectionCache": "false",
            "portNumber": "@appsetting('sftp_1_port')",
            "sshHostAddress": "@appsetting('sftp_1_address')",
            "sshPrivateKey": "@appsetting('sftp_1_key')",
            "username": "@appsetting('sftp_1_user')"
        },
        "serviceProvider": {
            "id": "/serviceProviders/Sftp"
        }
    },
    "sftp-2": {
        "displayName": "sftp-2",
        "parameterValues": {
            "disableConnectionCache": "false",
            "portNumber": "@appsetting('sftp_2_port')",
            "sshHostAddress": "@appsetting('sftp_2_address')",
            "sshPrivateKey": "@appsetting('sftp_2_key')",
            "username": "@appsetting('sftp_2_user')"
        },
        "serviceProvider": {
            "id": "/serviceProviders/Sftp"
        }
    },
    "sftp-3": {
        "displayName": "sftp-3",
        "parameterValues": {
            "disableConnectionCache": "false",
            "portNumber": "@appsetting('sftp_3_port')",
            "sshHostAddress": "@appsetting('sftp_3_address')",
            "sshPrivateKey": "@appsetting('sftp_3_key')",
            "username": "@appsetting('sftp_3_user')"
        },
        "serviceProvider": {
            "id": "/serviceProviders/Sftp"
        }
    },
    "sftp-4": {
        "displayName": "sftp-4",
        "parameterValues": {
            "disableConnectionCache": "false",
            "portNumber": "@appsetting('sftp_4_port')",
            "sshHostAddress": "@appsetting('sftp_4_address')",
            "sshPrivateKey": "@appsetting('sftp_4_key')",
            "username": "@appsetting('sftp_4_user')"
        },
        "serviceProvider": {
            "id": "/serviceProviders/Sftp"
        }
    }

For the purposes of this example, sftp-3 and sftp-4 are the recently-added connections.

After saving the JSON, the connections successfully appear on the Service provider connections tab:

I added the connections to connections.json on Wednesday 10th June and noticed that they weren't appearing in the connector. I decided to give it a day to think and refresh. It is now Friday 12th June, and the connections still aren't showing.

Addition: the connections.json file saves successfully, and the Keyvault values are pulling through to the connections successfully:

I have cleared my browser's cache and used a different browser entirely - same issue.

Plan Type

Standard

Steps to Reproduce the Bug or Issue

1. Via the Azure web portal, open an Azure Logic App Workflow resource
2. Go to Workflows -> Connections
3. JSON view
4. Add an SFTP connection directly in the JSON and click Save; ensure the connection uses Keyvault values
5. Confirm the connection appears in Service provider connections tab
6. Create a new Workflow
7. Add an SFTP action
8. Click Add connection
9. The connection does not appear to be used on this page.

Workflow JSON

N/A

Screenshots or Videos

No response

Additional context

No response