Still Using Azure Cloud Services (Classic) ? #Azure #ARM #ASM #Cloud #EOL #ESLZ #CAF #WAF

Azure Cloud Services (Classic) was a platform-as-a-service (PaaS) offering from Microsoft Azure that allowed developers to deploy, manage, and scale web applications and services in the cloud. However, Microsoft has announced that Azure Cloud Services (Classic) will reach its end-of-life (EOL) on September 1, 2023. In this blog post, I will provide an overview of Azure Cloud Services (Classic) and explain how to migrate your existing cloud services to the new Azure Resource Manager model.

Azure Cloud Service is a bit like an OS that is EOL, it is still running so why touch it, Well In PaaS someone else makes that choice for you. Preventing you for running Old unsecure apps. A quick query showed me this.

In 2014, Microsoft launched infrastructure as a service (IaaS) on Azure Resource Manager. We’ve been enhancing capabilities ever since. Because Azure Resource Manager now has full IaaS capabilities and other advancements, Microsoft deprecated the management of IaaS virtual machines (VMs) through Azure Service Manager (ASM) on February 28, 2020. This functionality will be fully retired on September 1, 2023. #hardstop

Today, about 90 percent of the IaaS VMs are using Azure Resource Manager. If you use IaaS resources through ASM, start planning your migration now. Complete it by September 1, 2023, to take advantage of Azure Resource Manager.

VMs created using the classic deployment model will follow the Modern Lifecycle Policy for retirement.

But many vendors or apps are still using the old Azure Classic and I must say it is interesting to see what projects are all exposed to the web, a couple of query’s of some apps and some high traffic pages like Cumberland Farms | Convenience Stores and Gas (cfi-webauth-01.cloudapp.net) anyone can reach out if they need help on migration(shameless plugging)

• As of February 28, 2020, customers who didn’t utilize IaaS VMs through ASM in the month of February 2020 can no longer create VMs (classic).
• On September 1, 2023, customers will no longer be able to start IaaS VMs by using ASM. Any that are still running or allocated will be stopped and deallocated.
• On September 1, 2023, subscriptions that are not migrated to Azure Resource Manager will be informed regarding timelines for deleting any remaining VMs (classic).

This retirement does not affect the following Azure services and functionality:

• Storage accounts not used by VMs (classic)
• Virtual networks not used by VMs (classic)
• Other classic resources

Reference list of Azure domains

So have a good look at your Azure Resources and IF you do use Azure Classic Take Action now!.

Migrate Azure Classic (ASM) To Azure ARM (Azure Resource Manager) Cloud be easy or not, there is no onesize fits all but below I do some basic steps that get you started.

Before starting the migration process, it is important to have the following prerequisites in place:

1. An Azure subscription with permissions to create and manage resources.
2. A basic understanding of Azure ARM templates and deployment processes.
3. Familiarity with the Azure Portal and PowerShell.
4. Existing Azure Cloud Services (Classic) deployed and running.
5. Make sure your network is not Classic.
6. Make sure your storage account is not Classic.

Step-by-step guide:

1. Create a new Azure Resource Group to contain the resources that will be created during the migration process.
2. Review the existing Azure Cloud Services (Classic) deployed to identify the resources needed for the migration process.
3. Export the configuration of each existing Azure Cloud Service (Classic) by running the following command in PowerShell
4. Get-AzVM –ResourceGroupName <Name> | Export-AzVM
5. Modify the configuration of each exported VM to work with ARM by replacing the cloud service name with the new resource group name.
6. Convert each of the exported VMs to ARM templates by running the following command in PowerShell
7. ConvertTo-AzureRMVMResource –ResourceId <Cloud Service Resource ID> –OutputFolder <Output Folder>
8. Create a new ARM template to describe the new environment, including the new resource group, virtual network, and storage account.
9. Modify the ARM template to include the exported VMs and the required configuration for each VM.
10. Deploy the ARM template to create the new environment and VMs.
11. Test the new environment to ensure that all VMs are running and that the application is working correctly.
12. Redirect traffic from the old Azure Cloud Service (Classic) to the new ARM environment by updating the DNS configuration.
13. Decommission the old Azure Cloud Service (Classic) and associated resources.

Conclusion:

The Sample above shows some old AzureRM commands and are replaced by AZ commands. This shows also the methods as not only the Azure portal as resources but also the PowerShell modules needs to be updated!! Migrating from Azure Cloud Services (Classic) to Azure ARM can be a complex process, but it is essential for organizations to take advantage of the latest features and benefits of the Azure platform. By following the (sample) step-by-step guide outlined above, organizations can migrate their existing Azure Cloud Services (Classic) to the new ARM environment, ensuring that their applications and services continue to run smoothly and efficiently.

Also when migration Take a good look at your Azure Foundation does it still Fit is the Governance conform WAF / CAF Enterprise-Scale

Hope it was helpfull thanks for visiting my blog.

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Http://nl.linkedin.com/in/robertsmit