CloudServiceDefinitionXml exceeds max input endpoints per deployment (it doesn't)

So I reduced the number of endpoints in my service to 24 (instead of 25), published it, then bumped it back up to 25 and re-published again and that solved the issue. Looks like the bug is with the Remote Desktop removal; it's not lowering the internal count correctly.

Hi Guy Godin,

It appears you're encountering an issue that your cloud service deployment has exceeded the maximum number of input endpoints allowed, which is 25. It’s possible that a lingering or failed endpoint from your earlier attempt to add remote desktop connectivity is causing the issue.

The limits imposed on Azure Cloud Services, the maximum number of input endpoints is only 25.

When you attempted to add Remote Desktop connectivity through the Azure portal, Azure likely added an additional input endpoint to facilitate RDP access. Even though the attempt failed and no RDP entries are visible under Settings → Remote Desktop, the system may have retained this endpoint configuration internally.

To remove the RDP extension using Azure PowerShell, you can follow the steps:

Connect to your AZ account and set the correct subscription:

Connect-AzAccount

Set-AzContext -SubscriptionId "<your-subscription-id>"

Retrieve the existing cloud service:

$resourceGroupName = "<your-resource-group>"
$cloudServiceName = "<your-cloud-service-name>"
$cloudService = Get-AzCloudService -ResourceGroupName $resourceGroupName -CloudServiceName $cloudServiceName

Remove the RDP extension from the cloud service's extension profile:

$cloudService.ExtensionProfile.Extension = $cloudService.ExtensionProfile.Extension | Where-Object { $_.Type -ne "RDP" }

Then update the cloud service, to apply changes:

$cloudService | Update-AzCloudService

For detailed information, please check: Update Remote Desktop Extension using PowerShell

If you have any further queries, let me know. If the information is helpful, please click on Upvote.