`MicrosoftNetwork/applicationGateways` - doesn't update reordering of elements unless something has been added or removed.

I'm running into an issue where I want to update the ordering of elements in a list for various attributes. These include `frontendPorts`, `frontendIPConfigurations` `backendAddressPools`, `backendHttpSettings`, `httpListeners`, `privateLinkConfigurations`, `requestRoutingRules`, `redirectConfigurations`, `probes`, `sslCertificates`, and `frontendPorts`.

I am unable to update the ordering from something like:

```
"frontendPorts": [{
"name": "three",
}, {
"name": "two",
},{
"name": "one",
},
}]
```

to

```
"frontendPorts": [{
"name": "one",
}, {
"name": "two",
},{
"name": "three",
},
}]
```

Instead I have to add or remove an element to get the ordering to be correct ie - if we started with:

```
"frontendPorts": [{
"name": "three",
}, {
"name": "two",
},{
"name": "one",
},
}]
```

and then updated the gateway to look like

```
"frontendPorts": [ {
"name": "two",
},{
"name": "one",
},
}]
```

and then updated it again to look like

```
"frontendPorts": [{
"name": "one",
}, {
"name": "two",
},{
"name": "three",
},
}]
```

For some reason the ordering of these attributes get updated only when something is added or removed but I'd like to see it get updated if the ordering of the list is changed without anything being removed.

Also #2313 is something that we'd like to see get worked on as it was commited to back in 2018. Would it be helpful to reopen that issue or to open another issue in the same vein?

Review the reported frontendPorts reorder examples and the other listed gateway attributes in the Azure REST API specifications; the payload does not identify a file or test. Compare the expected behavior with issue #2313, and define completion as preserving a reorder when no elements are added or removed.

Written by the indexing model from the issue text.