Does Visual Studio 2022 Publish wizard for Cloud Service (classic) deployment support General Purpose V1 (ARM) storage account?

CityLightsRBrite 11 Reputation points
2024-03-05T18:41:54.5266667+00:00

Our company has a few projects deployed as Cloud Service (classic) resources in Azure. We are in the process of trying to migrate classic storage accounts and Cloud Service (classic) projects to ARM.

As a test, we converted a storage account used by a Cloud Service (classic) staging instance to a General Purpose V1 (ARM) storage account.

However, in Visual Studio 2022, when using the "Publish" wizard to re-deploy to the staging slot of the Cloud Service (classic) resource, in the dropdown to choose the storage account, the converted General Purpose V1 (ARM) storage account is no longer available to select. From reading, the selected account is just used as temporary storage during the publish/deployment process.

Two questions:

  1. Is that expected behavior (that the "Publish" wizard for Cloud Service (classic) Visual Studio projects can't use General Purpose V1 (ARM) storage accounts)? Another post made it sound like the General Purpose V1 storage account should still work for this purpose (since it still supports the classic deployment model).
  2. If the General Purpose V1 storage account can't be used for Cloud Service (classic) deployment in the Visual Studio publish wizard any longer, is it expected that classic storage accounts have to be migrated to ARM at the same time as the Cloud Service (classic) deployments are migrated to Cloud Service (extended support)? The hope was this could be done in (cautious) steps. These are projects that get occasional minor modification (sometimes unexpectedly requested by a client).
Azure Cloud Services
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
665 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,863 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. vipullag-MSFT 25,606 Reputation points
    2024-03-07T04:27:44.77+00:00

    Hello CityLightsRBrite

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    1. Looks like the publish wizard has No support for GPv1 storage. As Cloud Services (classic) in retiring in August, I don't think there will be any changes done for this support. However, If Cloud Services (classic) supports these, you can check with a work around by building/packaging in Visual Studio and using the azure portal or powershell to deploy.
    2. It looks like to be on the same timeline, please refer this https://azure.microsoft.com/en-us/updates/classic-azure-storage-accounts-will-be-retired-on-31-august-2024/

    The Cloud Service (classic) Create Deployment REST docs can be found here: https://video2.skills-academy.com/en-us/previous-versions/azure/reference/ee460813(v=azure.100)

    The PackageUrl is the field which defines the source of the CSPKG being provided from a storage account: User's image

    If the package is stored in a Storage Service (classic) that is provisioned by the same subscription hosting the deployment, a url referencing the package directly will suffice. RDFE can validate that both resources are owned by the same subscription because it's the source of truth associating both Cloud Services (classic) and Storage Service (classic) resources with a subscription. 

    A SAS URI will work if the package is stored in any storage account. SAS URIs are available on every flavor of storage account and provide much more flexibility.

    Hope this clarifies your query.