This post was co-authored by Altaf Tambawala, Principle Program Manager, Azure
Today we announce the general availability of Cloud Services (Extended Support) that are new ARM-based deployment model (Azure Resource Manager) for Azure Cloud Services. The platform-supported tool for migrating existing cloud services to cloud services (extended support) will also be included in the preview today.
Cloud Services (Extended Support) provide the primary benefit of providing regional resilience and feature parity with Azure Cloud Services provided with Azure Service Manager (ASM). It also offers some ARM features like role-based access and control (RBAC), tags, policies, private link support and use of provisioning templates.
The ASM-based delivery model for cloud services has been renamed Cloud Services (classic). Customers retain the ability to build and quickly deploy web and cloud applications and services. Customers can scale the cloud service infrastructure based on current demand and ensure that application performance is maintained while costs are reduced. By migrating to ARM, customers can set up a robust infrastructure platform for their applications.
Available migration paths
Cloud Services (extended support) offer customers two options for migrating from ASM to ARM:
- Deploy again: Customers can deploy a new cloud service directly in ARM and delete the old cloud service after thorough validation in ASM. The general availability of Cloud Services (extended support) comes with one Service Level Agreement (SLA) of 99.95 percent.
- In-place migration:: Migration tool This enables a seamless, platform-controlled migration of existing (classic) cloud services deployments to cloud services (extended support).
- Cloud Services (extended support) also supports two types of roles: Web and workers. There are no changes to the design, architecture, or components of the web and worker roles.
- No changes are required to the runtime code as the data level is identical to the cloud services.
- Azure GuestOS versions and associated updates are geared towards cloud services (classic).
- The underlying update process with regard to update domains, the process of the upgrade, the rollback and the permitted service changes during an update do not change.
- Customers need to use Azure Key Vault to Manage Certificates in Cloud Services (Extended Support). Azure Key Vault allows you to securely store and manage application credentials such as secrets, keys, and certificates in a central and secure cloud repository.
- All resources provided through the Azure Resource Manager must be in a virtual network.
- Each cloud service (extended support) is a single independent deployment. VIP exchange The function can be used to switch between two cloud services (extended support).
Working with customers to meet their needs
“”Cloud Services (Extended Support) is a long-awaited and much-needed platform support for Azure Early Adopter customers to migrate to ARM. The ability to run cloud services alongside other compute and data workloads in the same VNET enables flexible architecture options. Another advantage is the additional visibility and metrics for monitoring network components such as load balancers that were previously implicitly defined. Other benefits include improved security with SSL certificates stored and referenced in Azure Key Vault. Our DevOps team loved when they were able to leverage their RBAC knowledge and existing CI / CD pipelines for ARM templates instead of having to maintain service management certificates and use outdated SDKs and scripts that Written in PowerShell and Golang. Migrating to the new delivery model was a moderate amount of work for the DevOps team. “-Nikhil Shampur, Environmental Systems Research Institute Inc.
“We took part in the Cloud Services Preview (Extended Support) and were able to successfully deploy and run our service with no code changes. We just had to develop the ARM templates for provisioning the Cloud Service resources and our service, and then create some configuration changes to it The Cloud Service Configurations: We had no issues with a number of the Cloud Service startup tasks that we needed, such as installers for certain C / C ++ runtime libraries and third-party Windows services that were required to operate We can use ARM template deployments that are consistent with our Service Fabric services and include virtual network deployment with our Service Fabric services. Overall, the transition to cloud services (extended support) is relatively painless. “Chris Donovan of Instec Corp Insurance Technologies Corporation
Direct migration details
The migration tool is now available in preview and has the following additional benefits:
- Allows for a seamless platform-driven migration with no downtime for most scenarios. Learn more about supported scenarios.
- Migrates existing cloud services in three easy steps: validate, prepare, commit (or cancel). Learn more about how the Migration tool works.
- Provides the ability to test migrated deployments after successful preparation. Apply and exit the migration while the abort will roll back the migration.
- Existing deployments and associated deployment files can be reused with minor changes.
- Retains the IP address and Domain Name System (DNS) label of the cloud services as part of the migration. No client-side changes required.
The migration can be accessed in two different ways
- Migration of the virtual network migrates all cloud services deployments (classic) that are located in an explicit virtual network configured by the customer (classic).
- Migration of cloud service delivery can only be used for authorized (classic) cloud service deployments that are not located in a virtual network. The API response “Validate” confirms the authorization of the cloud service for the migration.
Both deployment models (Extended Support and Classic) are available with similar versions Pricing structures. Cloud Services (Extended Support) uses Azure Key Vault and Basic (ARM) public IP addresses. Learn more about Azure Key Vault pricing and Public IP address pricing. Prices do not change between preview and general availability.
Additional Azure services to consider when migrating to ARM
When evaluating migration plans from Cloud Services (Classic) to Cloud Services (Extended Support), customers may want to investigate the possibility of adding additional Azure services such as Virtual machine scale sets, App service, Azure Kubernetes service, and Azure Service Fabric. These services will continue to have additional functions, while cloud services (extended support) primarily maintain the function parity with cloud services (classic).
Depending on the application, cloud services (extended support) may require significantly less effort to migrate to ARM compared to other options. If the application is not evolving, Cloud Services (extended support) is a viable option as it provides a quick migration path. However, as the application continues to evolve and need more modern functionality, consider exploring other Azure services to better meet current and future needs.
There are several resources that customers can use to learn more about cloud services (extended support).