How to deploy an application on Azure - Cloud Services (classique) - even it's deprecated

Question

Hi everyone,

I need to deploy an application under a sub-domain *.cloudapp.net.

I've used the Cloud service (classic), but I can't load my application during deployment. My cspkg and cscfg files are causing an error. I then tried to use a simple sample (https://github.com/ttu/scratchpad/tree/master/Azure/helloworld-cloud-service) but got the same error.

{"code": "DeploymentSlotCreateOperationFailed", "message": "Deployment creation operation failed for domain "cwap-proxy-asia1-seas-2" in deployment slot "staging" with name "test": "Instead of creating Cloud Services (classic), you now need to create Cloud Services (extended support) using Azure Resource Manager. Find out more at: [https://aka.ms/cloudservicesretirement."."}]}]()

Is it still possible to deploy applications on a classic cloud service? If so, how? In Azure CLI? From what the Azure interface shows, it would appear that this is still possible.

Thanks,

Eric

Answer 1

Hi Eric,

I understand you're trying to deploy an application on Azure Cloud Services (classic) using a subdomain (*.cloudapp.net). While the Azure interface might still show options for classic Cloud Services, it's important to know that this service is now deprecated and will be retired on August 31, 2024.

Here's the key point:

• Classic Cloud Services are no longer recommended.

Microsoft strongly advises migrating your applications to a more modern Azure service for better long-term stability and support.

Let's explore your options:

Migrate Your Application:

• Azure Cloud Services (extended support): This is a temporary solution (supported until at least 2026) if your application can work with it. But it's not a long-term plan.
  • Modern Azure Services: Choose the service that best suits your application type:

    - **Web apps and APIs:** Azure App Service
    
          - **Serverless functions:** Azure Functions
    
                - **Containerized applications:** Azure Kubernetes Service (AKS)
    
                **Using Classic Cloud Services (Not Recommended):**
    
                   - **Limited Functionality:** Keep in mind that classic Cloud Services will have fewer features and support as the retirement date nears.
    
                      - **Troubleshooting:** While I can't give specific deployment steps due to the deprecation, here are some resources that might help you with the error you're facing (but use them with caution):
    
                            - **Azure Portal:** The interface might still show classic options, but they might not work as expected.
    
                                  - **Azure CLI:** Similar to the portal, using Azure CLI commands for classic Cloud Services is discouraged.
    
                                     - **Focus on Migration:** It's crucial to prioritize migrating to a modern service for long-term benefits.
    

The error message you're getting ("Cloud Services (classic) are deprecated...") is a clear warning. Moving to a modern service will ensure your application has ongoing support, better security, easier scaling, and access to the latest features.

If you have any questions about migrating to a modern Azure service, feel free to ask!Hi Eric,

I understand you're trying to deploy an application on Azure Cloud Services (classic) using a subdomain (*.cloudapp.net). While the Azure interface might still show options for classic Cloud Services, it's important to know that this service is now deprecated and will be retired on August 31, 2024.

Here's the key point:

• Classic Cloud Services are no longer recommended.

Microsoft strongly advises migrating your applications to a more modern Azure service for better long-term stability and support.

Let's explore your options:

Migrate Your Application:

• Azure Cloud Services (extended support): This is a temporary solution (supported until at least 2026) if your application can work with it. But it's not a long-term plan.
  • Modern Azure Services: Choose the service that best suits your application type:

    - **Web apps and APIs:** Azure App Service
    
          - **Serverless functions:** Azure Functions
    
                - **Containerized applications:** Azure Kubernetes Service (AKS)
    
                **Using Classic Cloud Services (Not Recommended):**
    
                   - **Limited Functionality:** Keep in mind that classic Cloud Services will have fewer features and support as the retirement date nears.
    
                      - **Troubleshooting:** While I can't give specific deployment steps due to the deprecation, here are some resources that might help you with the error you're facing (but use them with caution): 
    
                            - **Azure Portal:** The interface might still show classic options, but they might not work as expected.
    
                                  - **Azure CLI:** Similar to the portal, using Azure CLI commands for classic Cloud Services is discouraged.
    
                                     - **Focus on Migration:** It's crucial to prioritize migrating to a modern service for long-term benefits.
    

The error message you're getting ("Cloud Services (classic) are deprecated...") is a clear warning. Moving to a modern service will ensure your application has ongoing support, better security, easier scaling, and access to the latest features.

If you have any questions about migrating to a modern Azure service, feel free to ask!