This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(310.4, 40%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMZ%3C/text%3E%3C/svg%3E)
I am able to successfully create a new Cloud Service using the following command:
New-AzCloudService -Name $cloudServiceName
-ResourceGroupName $resourceGroupName -Location $location
-DefinitionFile $definitionFilePath -ConfigurationFile $configurationFilePath
-PackageFile $packageFilePath -KeyVaultName $keyVaultName
-StorageAccount $storageAccountName
I am trying to also set the Cloud Service to be swappable with another Cloud Service. Based on the documentation here, I tried:
$networkProfile = @{SwappableCloudService = $swappableCloudService.Id }
New-AzCloudService -Name $cloudServiceName
-ResourceGroupName $resourceGroupName -Location $location
-DefinitionFile $definitionFilePath -ConfigurationFile $configurationFilePath
-PackageFile $packageFilePath -KeyVaultName $keyVaultName
-StorageAccount $storageAccountName `
-NetworkProfile $networkProfile
This however results in the following error: New-AzCloudService: Parameter set cannot be resolved using the specified named parameters. One or more parameters issued cannot be used together or an insufficient number of parameters were provided.
I see the documentation also provides other methods of creating a Cloud Service, by specifying the -PackageUrl and -Configuration instead of a PackageFile and ConfigurationFile. In the example, the NetworkProfile is included with this method.
Is setting a swappable Cloud Service only possible when using these methods? So it is not possible to set a swappable Cloud Service when providing the Configuration File and Package File directly (like it is in the portal)? If this is the case, then why?
If it is supported, then can you please explain how to do so?
I did some research before posting this, and I am not the only person having this issue: https://stackoverflow.com/questions/72940711/azure-cloud-services-extended-support-deploy-using-new-azcloudservice-powershell
Apologies in delayed response on this.
I am checking with internal team on this and will update back here.
This looks like an oversight in the implementation. It should be as simple as requiring an option for a Swappable Cloud Service in the command e.g.:
$cloudService = New-AzCloudService -Name ContosoCS
-ResourceGroupName ContosOrg -Location EastUS
-ConfigurationFile C:\files\CS.cscfg -DefinitionFile C:\files\CS.csdef
-PackageFile C:\CS.cspkg -StorageAccount ContosoStorAcc
-KeyVaultName ContosoKV `
-SwappableCloudService $SwappableCloudServiceId
(The bit in bold I added - it is not part of the command, but it should be)
I have shared this feedback to the concerned team.
![](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(54.400000000000006, 68%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERD%3C/text%3E%3C/svg%3E)
@Morné Zaayman How did you solve this? I am also trying to create a cloud service with a .csdef file and being able to swap.
@vipullag-MSFT Is there any update on this? We are also trying to publish a swappable web-role that requires a .csdef file.
![](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(220.8, 41%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFH%3C/text%3E%3C/svg%3E)
Hi @Morné Zaayman ,
In case I can tempt you back into giving this another look:
You cannot specify a -NetworkProfile when making use of -ConfigurationFile & -DefinitionFile as they are then used to build the network profile hence the error of parameters that cannot be used together.
You can however upload the cspkg and then use -PackageUrl and end up something like this:
New-AzCloudService `
-StartCloudService:$false `
-Name "$CloudServiceName" `
-ResourceGroupName $ResourceGroupName `
-Location "$Location" `
-PackageUrl $cspkgUrl `
-Configuration $cscfgContent `
-NetworkProfile $networkProfile `
-RoleProfile $roleProfile `
-OSProfile $osProfile
Although I believe that'll change how you do things as you will then need to create the RoleProfile and OSProfile from what's normally specified in the csdef:
$role1 = New-AzCloudServiceRoleProfilePropertiesObject -Name 'Frontend' -SkuName 'Standard_D2_v3' -SkuTier 'Standard' -SkuCapacity 1
$role2 = New-AzCloudServiceRoleProfilePropertiesObject -Name 'Backend' -SkuName 'Standard_D2_v3' -SkuTier 'Standard' -SkuCapacity 1
$role3 = New-AzCloudServiceRoleProfilePropertiesObject -Name 'WorkerRoleLowPriority' -SkuName 'Standard_D2_v3' -SkuTier 'Standard' -SkuCapacity 1
$roleProfile = @{role = @($role1, $role2)}
Although to be completely honest I seem to be stuck with IP's now. The cscfg can't be parsed if <ReservedIPs> is used as it should be <PublicIPs>, but then the deployment doesn't work as it's looking for <ReservedIPs>:
New-AzCloudService_CreateExpanded: A static IP address is being used in the cloud service deployment template. A ReservedIp reference is mandatory in the cloud service configuration XML (cscfg) for a Public IP of type ‘static’. If you do not intend to change the cscfg, please change the public IP address type to be ‘dynamic’ and retry the deployment. For more details on the steps for creating a cloud service deployment in ARM, refer here: https://aka.ms/cses-network-config.
We gave up using the New-AzCloudService command and instead used New-AzResourceGroupDeployment. I made a blog post about it here: https://mzansibytes.com/2023/04/11/powershell-script-to-update-a-cloud-service-extended-support-deployment/
This post in the techcommunity shows in detail how this can be achieved:
https://techcommunity.microsoft.com/t5/azure-paas-blog/how-to-manage-the-vip-swap-in-cloud-service-extended-support-via/ba-p/3694504
As I mention in another common the cause for the Parameter set cannot be resolved using the specified named parameters. One or more parameters issued cannot be used together or an insufficient number of parameters were provided. error is because -NetworkProfile cannot be used along with -ConfigurationFile and/or -DefinitionFile as those files are used to build the network profile.
From the link I ended up with the following (I just formatted it for readability) which works well with an automation that uploads the cspk & cscfg to a container from which a SAS token is generated for the URLs:
New-AzCloudService `
-StartCloudService:$false `
-Name $CloudServiceName `
-ResourceGroupName $ResourceGroupName `
-Location $Location `
-PackageUrl $cspkgUrl `
-ConfigurationUrl $cscfgUrl `
-NetworkProfile $networkProfile `
-RoleProfile $roleProfile `
-OSProfile $osProfile