Today I’ve spent quite some time figuring out why my new Azure Subscription Settings file was not picked up by Octopus Deploy. And I was getting an obscure error message:
Get-AzureWebsite : Communication could not be established. This could be due to an invalid subscription ID. Note that subscription IDs are case sensitive.
Turned out that old Subscription Settings File was stuck in user cache and I had to “unstuck” it by executing this script from under the user account I was trying to execute PowerShell.
Remove-AzureSubscription 'Subscription Name' -Force
This does not actually do anything to the actual Azure subscription (I panicked about it first). Documentation says this only deletes subscription data file from so PowerShell can’t use it. Nothing to do with the actual Azure Subscription.
After removing old subscription data you can re-import new Subscription Settings File:
Import-AzurePublishSettingsFile 'C:/path/to/subscription.publishsettings' Select-AzureSubscription -SubscriptionName "Subscription Name"
Hope this helps someone!