I have only one resource( storage account) in east us location as I accidentally selected the location as east us , Now I'm trying to move this particular resource to my my desired location , but when I'm using Azure resource Mover and select Source location as east us It doesn't show any resources
Hi, may I have a question? I'm going to migrate the resource group (SA, EventHub, IoT Hub) to different Azure region. Does the Connection String for configured Iot Edge devices on Iot Hub change??? many thanks in advance!
Hi there! A) If you use symmetric key authentication, then an IoT Edge device connection string takes this format: HostName=.azure-devices.net;DeviceId=;SharedAccessKey= The hub name shouldn’t change, and the device name shouldn’t change, but I suppose the device’s primary key and secondary key might get regenerated when the data is cloned over? If yes, then yes you’ll need to update the connection string on the IoT Edge device. B) If you use x.509 certificate authentication, then an IoT Edge device connection string takes this format: HostName=.azure-devices.net;DeviceId=;x509=true In this case, nothing should have to change on the device. Assuming the x.509 certificate thumbprints get migrated over to the new hub with the rest of the device info.
If I use resource mover to move sql pass from one to another subscription do we really move the data or just update the ownership of database. ..? Thanks
It's great to have such a feature, but still the process itself a little bit complicated. There a lot of required steps but luckily the documentation is pretty clear.
DOES NOT WORK!!! unless your Linux kernel just happens to be exactly right (not latest, not older, specific list. so apt or yum upgrade is out the question) at least 1.5GB RAM The sun the moon and the stars must align precisely. This half baked "feature" should still be in preview
@@wademiller3323 No, the first error was not enough RAM, after resizing and 2nd attempt, the error was Linux kernel version not supported - literally a minor version too old - so I did an apt upgrade - then the minor kernel version was too new - takes the whole day to fiddle around might as well do an azcopy
