Hello Tung Nguyen,
Thank you for posting your question in the Microsoft Q&A forum.
The most common root causes fall into three primary categories. First, subscription and permission issues frequently trigger 500 errors, particularly when the deploying account lacks sufficient permissions or when subscription quotas have been exhausted. Users should verify they have Owner or Contributor rights and check their vCPU quotas in the Azure Portal under Usage + Quotas. Second, regional limitations can cause deployment failures, as Elastic Cloud isn't available in all Azure regions. Trying alternative regions like East US or West Europe often resolves this. Third, temporary service outages or problems with the Microsoft.Elastic resource provider registration may be the culprit, which can be checked and remedied through Azure CLI commands.
There are few recommendations you may try:
- Try a different Azure region (East US/West Europe).
- Verify quotas and retry with smaller VM sizes.
- Use CLI/Terraform if the Azure Portal fails.
If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated.