Comment 2 for bug 1208351

We had assumed that what gwacl did here was poor use of the Azure API. As it turns out, it's not. It's a problem with Azure's API itself, and one that could be addressed better at that end (delete name records immediately when deleting the items they describe; ignore name clashes with deleted items; change names of deleted items to something that clients can not create for themselves; return a more recognizable error when a newly created item conflicts with a deleted one). Working around the problem adds moving parts and risks, and the problem may just go away in a future version of Azure. Until then, this is a nuisance rather than a fatal problem.

For all these reasons I'm downgrading this bug to Low priority.