Add warning to Azure Portal ARM Mover/update documentation when moving attached NICs between Resource Groups with ARM Mover

ecstatic-shamir 0 Reputation points
2024-09-09T13:48:24.2166667+00:00

Raising this request off the back of support ticket #2409030050001303 which has more details.

We have confirmed behaviour that when moving multiple NICs attached to a VM between resource Groups, they are detached from the VM as expected but not guaranteed to be re-attached to the VM in the same order. For some workloads this NIC's changing attachment order causes issues as older linux machines that don't use udev and some virtual network appliances (eg FortiGate firewalls) don't keep track of which NIC is which logical interface, and can lead to outages as the NIC the device is expecting is not the correct one. EG: https://community.fortinet.com/t5/Support-Forum/Fortigate-Interface-order/m-p/228417

This behaviour does not appear to be documented anywhere and the ARM Mover does not warn users that this can happen.

Azure Resource Mover
Azure Resource Mover
An Azure service used for moving multiple resources between Azure regions.
240 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Ryan Hill 28,731 Reputation points Microsoft Employee
    2024-09-09T14:08:00.5566667+00:00

    Hi @ecstatic-shamir

    Thanks for raising this attention. I'll be sure to elevate this to right audience. Getting a banner in the Azure portal won't be instantaneous but adding a warning to documentation is easily doable.

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.