Hello CityLightsRBrite
Welcome to Microsoft Q&A Platform, thanks for posting your query here.
- 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.
- 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://learn.microsoft.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:
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.