Hi,
We created a route based gateway. Then we figured out our Cisco ASA can't handle route based gateways, so we deleted the gateway.
Then I created a policy based gateway with the same name. This failed with an InternServerError and status "conflict". So I deleted that gateway too and wanted to create a new gateway with a different name.
Now I can't create the gateway, because the virtual network is already associated to the gateway 'xxx'. The gateway that Azure said it couldn't deploy, and that I afterwards (after it was not deployed, although it sort of was) deleted. So my network is now
in use by a gateway that doesn't exist and that therefore I can't delete either.
What can I do now?
In case Microsoft sees this: the subscription Id is ee7e246c-1fb6-4288-ae82-8e7040c9c82d, there is only one virtual network which is the one I'm trying to use.
Is there any way to report issues like that? We're still evaluating Azure and I find it wrong as a matter of principle that I have to buy support in order to tell Microsoft their software messed up my data.
Thanks, Chris