Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
704 questions
I was on this step:
The result returned:
Issue with Migrate a Classic Cloud Service not in a virtual network
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 42%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELH%3C/text%3E%3C/svg%3E)
Long Ho
0
Reputation points
I have issue when Migrate a Classic Cloud Service not in a virtual network to Cloud Services (extended support). I followed this guide https://learn.microsoft.com/en-us/azure/cloud-services-extended-support/in-place-migration-powershell#option-1---migrate-a-cloud-service-not-in-a-virtual-network But still can not migrate. It still show error when I was on Migrate your Cloud Services step (Option 1) in this step
$validate = Move-AzureService -Validate -ServiceName $serviceName -DeploymentName $deploymentName -CreateNewVirtualNetwork
$validate.ValidationMessages
The powershell return error: Deployment [xxx] in cloud service [zzz] must be within a virtual network to be migrated.
How can I pass that error
Thank you
{count} votes
-
Long Ho 0 Reputation points
2024-09-01T01:33:10.2266667+00:00 I was on this step:
Result error:
Sign in to comment
2 answers
Sort by: Most helpful
-
Long Ho 0 Reputation points
2024-09-01T01:35:58.8633333+00:00 -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 47%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Mounika Reddy Anumandla 825 Reputation points Microsoft Vendor2024-09-04T06:30:26.5166667+00:00 Hi Long Ho,
Just checking in to see if you had a chance to see my response to your question. Please tell us if it was helpful and feel free to reach out to us if you have any queries.
If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.
-
Mounika Reddy Anumandla 825 Reputation points Microsoft Vendor
2024-09-05T03:46:31.3833333+00:00 Hi Long Ho,
Just checking in to see if you had a chance to see my response to your question. Please tell us if it was helpful and feel free to reach out to us if you have any queries.
If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.
Sign in to comment -
-
Mounika Reddy Anumandla 825 Reputation points Microsoft Vendor
2024-09-03T03:42:45.2833333+00:00 Hi Long Ho,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
The result of Validate API contains error message explicitly mentioning this deployment is not eligible to migrate and the error message indicates that the deployment must be within a virtual network to be migrated.
This means that your cloud service is not associated with a virtual network in the classic model, and you need to create one and link it to your cloud service before you can migrate.
Error message:Deployment deployment-name in cloud service cloud-service-name must be within a virtual network to be migrated. Deployment isn't located in a virtual network. For more information, see the Migration of deployments not in a virtual network section of Technical details of migrating to Azure Cloud Services (extended support).
Migration of deployments not in a virtual network
- In late 2018, Azure started automatically creating new deployments (without customer specified virtual network) into a platform created “default” virtual network. These default virtual networks are hidden from customers.
- As part of the migration, this default virtual network is exposed to customers once in Azure Resource Manager. To manage or update the deployment in Azure Resource Manager, customers need to add this virtual network information in the Network Configuration section of the .cscfg file.
- The default virtual network, when migrated to Azure Resource Manager, is placed in the same resource group as the Cloud Service.
- Cloud Services created before this time (before end of 2018) won't be in any virtual network and can't be migrated using the tool.
Solution: One solution to this scenario and the easiest way is to consider redeploying cloud service application directly in Azure Resource Manager (i.e. new cloud service extended support) by creating a VNET and associating the same to cloud service via service configuration file.
Another approach is to migrate via creating new Staging deployment and VIP Swap. Check more details here.
Here is a quick reference guide for the pre-requisites to ensure a successful Cloud Services (extended support) deployment- Prerequisites for deploying Azure Cloud Services (extended support) | Microsoft Learn
The document shows Resources and features not available for migration and also Unsupported configurations / migration scenarios
https://learn.microsoft.com/en-us/azure/cloud-services-extended-support/in-place-migration-technical-details#unsupported-configurations--migration-scenariosFor more information: https://learn.microsoft.com/en-us/azure/cloud-services-extended-support/deploy-portal