Post migration changes
The Cloud Services (classic) deployment is converted to a Cloud Service (extended support) deployment. For more information, see Cloud Services (extended support) documentation.
Changes to deployment files
Minor changes are made to customer’s .csdef and .cscfg file to make the deployment files conform to the Azure Resource Manager and Cloud Services (extended support) requirements. Post migration retrieves your new deployment files or update the existing files. This will be needed for update/delete operations.
Virtual Network uses full Azure Resource Manager resource ID instead of just the resource name in the NetworkConfiguration section of the .cscfg file. For example,
/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.Network/virtualNetworks/vnet-name. For virtual networks belonging to the same resource group as the cloud service, you can choose to update the .cscfg file back to using just the virtual network name.
Classic sizes like Small, Large, ExtraLarge are replaced by their new size names, Standard_A*. The size names need to be changed to their new names in .csdef file. For more information, see Cloud Services (extended support) deployment prerequisites
Use the Get API to get the latest copy of the deployment files.
Changes to customer’s Automation, CI/CD pipeline, custom scripts, custom dashboards, custom tooling, etc.
Customers need to update their tooling and automation to start using the new APIs / commands to manage their deployment. Customer can easily adopt new features and capabilities of Azure Resource Manager/Cloud Services (extended support) as part of this change.
Changes to Resource and Resource Group names post migration
- As part of migration, the names of few resources like the Cloud Service, public IP addresses, etc. change. These changes might need to be reflected in deployment files before update of Cloud Service. Learn More about the names of resources changing.
Recreate rules and policies required to manage and scale cloud services
- Auto Scale rules are not migrated. After migration, recreate the auto scale rules.
- Alerts are not migrated. After migration, recreate the alerts.
- The Key Vault is created without any access policies. Create appropriate policies on the Key Vault to view or manage your certificates. Certificates will be visible under settings on the tab called secrets.
Changes to Certificate Management Post Migration
As a standard practice to manage your certificates, all the valid .pfx certificate files should be added to certificate store in Key Vault and update would work perfectly fine via any client - Portal, PowerShell or REST API.
Currently, Azure Portal does a validation for you to check if all the required Certificates are uploaded in certificate store in Key Vault and warns if a certificate is not found. However, if you are planning to use Certificates as secrets, then these certificates cannot be validated for their thumbprint and any update operation which involves addition of secrets would fail via Portal. Customers are reccomended to use PowerShell or RestAPI to continue updates involving Secrets.
Changes for Update via Visual Studio
If you were publishing updates via Visual Studio directly, then you would need to first download the latest CSCFG file from your deployment post migration. Use this file as reference to add Network Configuration details to your current CSCFG file in Visual Studio project. Then build the solution and publish it. You may have to choose the Key Vault and Resource Group for this update.
- Overview of Platform-supported migration of IaaS resources from classic to Azure Resource Manager
- Migrate to Cloud Services (extended support) using the Azure portal
- Migrate to Cloud Services (extended support) using PowerShell