I found this a lot harder to do than I would have thought necessary, which leads me to believe that there is some other obvious way of dealing with this issue. Nonetheless, after several hours of stuffing about with the AzureRM Powershell Module, I finally figured out how to remove