Comment 1 for bug 1914589

Assuming {NUMBER} is like for units where it's monotonically increasing, there would need to be a place to store the previously used number etc. There's an argument that doing this work could be considered holistically across all providers, not just Azure, given the need to tweak the model to deal with the next number to use etc.

It's not necessarily super hard to do, but not totally trivial either given the doc and testing that would need to go along with it.