Improve inconsistent support for ReservedIP address casing
Just spent a couple days trying to figure out why I was getting an error when trying to update CSCFG from the Azure portal.
Turns out I had messed up the casing of my ReservedIP in the cscfg. I was able to deploy correctly, and the Cloud Service ran fine, but when I tried to update the settings I would get the error:
Failed to save configuration settings for slot 'production'. Error: The Change Deployment Configuration operation failed for the domain 'xxxxxxxxxxx' in the deployment slot 'production' with the name 'xxxxxxxxxxxxxxx': 'A reserved IP cannot be added, removed or changed during deployment update or upgrade. '.
Either Azure shouldn't let me deploy with the incorrectly cased reserved IP name, or it should support it fully throughout the system.