For some scenarios, customer application source code / package are not available any more for some reason, but another deployment is needed. This is customer responsibility to manage application source code and apply new deployment, but customer cannot apply new deployment without source code. For such situation, we could try below approach as additional help. This blog will wrap up all information needed for you to get the deployment package of an existing cloud service(classic) and then use the deployment package for another Cloud Service(classic) deployment.
Once you’ve upload the certificate, you would be able to find it in the management certificates list and you can copy the thumbprint to use in the following steps.
Step Two: create a classic storage account.
Secondly, we need to have a classic storage account to store the generated package files. Please also make sure that the classic storage account is in the same subscription with your Cloud Service(classic).
1. Navigate to the storage account creation page, then under instance details, click the legacy storage account type.
2. At the page popup, under the instance details, choose classic deployment model.
3. Now, you would be at the create classic storage account page, fill out the information and click on create.
4. Verify you’ve create a classic storage account as below:
2. Then, navigate to the container, and you would see the package and files.
3. use the deployment package(.cscfg and .cspkg) to make another deployment.
You can also download the .cscfg file and modify it for your needs. In my case, I made a change of the instance counts from 1 to 3 instances. Then created another cloud service(classic) use the package file and .cscfg file.