The strange error in the Azure portal went away by itself, so I guess it was an error in the service itself.