Configurable batch node minimum count?

[jormdav]

We’ve opted for 500 Azure batch nodes for our production runs. During a recent run, 499 of these prestaged fine, but one was stuck in the “Unusable” state, which we’d never encountered before. Our support staff ended up deleting the bad node manually, and since sbm prestage was still running, it took care of getting the number back to 500 on its own, as it hadn’t crossed our timeout threshold yet.

The team was wondering if there was a means to configure a minimum count of health nodes before allowing the database job to start.
E.g., we’d like 500 but would be ok if just 350 of those were available.