Azure-docs: Default Low-priority cores per Batch account is incorrect

[mtarng]

Low-priority cores per Batch account 10-100 is listed. However, I've noticed that by default, Low-priority vCPUs is being set to 0 when the Batch account is first created. I've tried this in West Central US, North Central US, South Central US, East US.

Either this is a bug, or documentation should reflect the new behavior.

May be similar to this issue: https://github.com/MicrosoftDocs/azure-docs/issues/47290

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 941b0a34-c223-297c-4560-43c0c7dc5bcf
• Version Independent ID: e46f1e5f-606e-c42a-6374-2904e2c40a1c
• Content: Service quotas and limits - Azure Batch - Azure Batch
• Content Source: articles/batch/batch-quota-limit.md
• Service: batch
• GitHub Login: @LauraBrenner
• Microsoft Alias: labrenne

[Karishma-Tiwari-MSFT]

I am reaching out to the product owner and will share as soon as I get an update. Thanks.

[Karishma-Tiwari-MSFT]

@mscurrell @pkshultz Can you please share your insights on this issue? Thanks. :)

[Mikkel-Gram]

i am experiencing this too, not just with low-priority machines but with all VMs for newly created batch accounts. Have only tried in EU West.

It is a recent issue, just a couple of weeks ago new accounts would have some low priority cores available.
It is preventing me from deploying my solution in a CI/CD manner, where i create a batch account for the purpose of testing, and destroy it afterwards. This does not work if a support ticket has to be created before the batch account is operational. (and what is the point of creating batch accounts which are not able to use any VMs - low-priority or otherwise?)

Swift solution would be appreciated

[Mikkel-Gram]

i saw in a note here that this is due to the corona virus: https://docs.microsoft.com/en-us/azure/batch/batch-quota-limit#view-batch-quotas

Would it not be more reasonable to limit it to a few machines instead? then people could still run stuff on a newly created batch account, just very slowly. Now it is unusable by default until you contact support, breaking all CI/CD workflows that use it

[JasonWHowell]

FYI @JnHs

[DCtheGeek]

reassign:DCtheGeek

[DCtheGeek]

@mtarng and @Mikkel-Gram Sorry you are impacted by this change. As noted, the doc has been updated with a note about the cause for this temporary change in behavior. If have alternative recommendations for the behavior, the best path is an item on Batch's UserVoice. Thank you again for the feedback.

@MicrosoftDocs/azure-cxp-triage #please-close