Microsoft.Network/connections: Inaccurate requirements for this resource type.

### Resource Type

Microsoft.Network/connections

### Api Version

2022-11-01

### Issue Type

Other

### Other Notes

The Connections resource is throwing an error stating that the following code requires virtualNetworkGateway1: {} to have a properties field within it. However, I can deploy it just fine without properties. The only necessary part is the ID. The same issue happens within localNetworkGateway2: {}

resource connection1 'Microsoft.Network/connections@2022-11-01' = {
name: '${rgName}_to_vhub_${vhubIteration}_1'
location: location
properties: {
virtualNetworkGateway1: {
id: existingVNGID
}

### Bicep Repro

resource connection1 'Microsoft.Network/connections@2022-11-01' = {
name: '${rgName}_to_vhub_${vhubIteration}_1'
location: location
properties: {
virtualNetworkGateway1: {
id: existingVNGID
}
localNetworkGateway2: {
id: lng1.id
}
}
}

### Confirm

- [X] I have read the troubleshooting guide and looked for duplicates.

Start from the Microsoft.Network/connections type definition for API version 2022-11-01 and compare its virtualNetworkGateway1 and localNetworkGateway2 shapes with the Bicep repro in this issue. Validate the definition against a deployment that supplies only each gateway ID; done means the type accepts the repro without requiring an unnecessary properties field.

Written by the indexing model from the issue text.