RandallBreneman-6024 avatar image
0 Votes"
RandallBreneman-6024 asked RandallBreneman-6024 commented

How to self-redeploy a VM under classic services web role in Azure portal?

I recently received an email Notice: Required Maintenance stating 'we recommend that you self-redeploy your virtual machine as soon as possible.' Documentation I can find says 'Select the VM you wish to redeploy, then select the Redeploy button in the Settings blade.'

The VM shows up in a list under Cloud Service (classic) | Cloud Service Role (classic). When I click on the instance link there, a blade pops up on the right showing things like location and status, and options to Connect, Reboot, or Reimage. Under Cloud Service Role (classic) left blade is a Settings group but all it has is Scale and Locks. There is no option to Redeploy anywhere I can find. The cloud service role instance VM does not show up under the Virtual machines list from the console Home.

How to satisfy the email suggestion and self-redeploy using the Azure portal?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

vipullag-MSFT avatar image
1 Vote"
vipullag-MSFT answered RandallBreneman-6024 commented


The re-deploy functionality of Azure VM is to transfer VM's to a new host and is for ARM based deployments and not the ASM.

However, I am sharing information that can help you plan your Classic VM migration to ARM. Document to refer for more information on this.

From the documentation, Migration workflow is as follows:
Key Migrations Points:

o Validate

o Prepare

o Commit / Abort

It is recommend to replicate your environment and perform a test migration, document reference.

There are four supported scopes of migration, check this document.

o Migration of virtual machines (NOT in a virtual network)

o Migration of virtual machines (in a virtual network)

o Migration of storage accounts

o Migration of unattached resources

Migration of virtual machines (in a virtual network) - Preferred - Please not that your applications running on top of VMs (classic) do not incur downtime during the migration. For most VM configurations, only the metadata is migrating between the Classic and Resource Manager deployment models. The underlying VMs are running on the same hardware, in the same network, and with the same storage. The management-plane operations may not be allowed for a certain period of time during the migration. However, the data plane continues to work.

As per this document, Cloud Services containing web and worker roles cannot migrate to Azure Resource Manager. The web/worker roles must first be removed from the virtual network before migration can start.

For information on the Unsupported features and configurations, refer to this document.

For Classic to ARM migration FAQs, please check this page.

Hope this information is helpful.
Incase you need more help on migration, requesting you to open a support case. Support team can help in the migration.

Please 'Accept as answer' if it helped, so that it can help others in the community looking for help on similar topics.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

The VM has been deprecated and will be allowed to be automatically de-allocated in March 2023 per We would like to keep it running until then to serve any remaining legacy clients. The email stated, "If self-service maintenance has not been completed by then, Azure will automatically redeploy these VM(s) after March 27, 2021." We will simply allow them to follow through with that as they deem appropriate.

Your response is most helpful. Thank you.

0 Votes 0 ·