I dont know why this error keeps popping up when i want to create a VM. this is on a free account and i have tried changing the region severaly

Glad to have you here. This community is for people who want to grow in Cloud, DevOps, DevSecOps, SRE, GitOps, Platform Engineering, and AI Infrastructure by actually learning, building, and asking good questions. How this page works 1. Community tab This is where we talk. Ask questions, share what you're learning, post your wins, discuss problems you're facing, and connect with other members. 2. Classroom tab This is where the structured learning lives. You’ll find courses, modules, and practical learning resources designed to help you build real technical skills step by step. 3. Weekly live classes We’ll be hosting live classes every SUNDAY - FRIDAY. These sessions will cover things like: - Cloud & DevOps concepts - Hands-on learning - Labs and projects - Q&A and problem solving - Career and technical guidance What to do next - Introduce yourself in the community - Share what you're currently learning - Check the classroom - Join the live classes on SUNDAY - FRIDAY - Stay active and keep building This is not a noisy group and it’s not a hype group. The goal here is simple: learn real skills, build real projects, and grow into a stronger engineer. Drop a comment below and tell us: Who are you, what are you learning right now, and what do you want to become?

The project requires three Linux VMs, with two in the Hub VNet and one in the Spoke VNet, using Azure Bastion for secure access without public IPs. I successfully created the first two VMs in South Africa North, but my Azure subscription has a 4-core regional quota, which is already fully utilized. The third VM requires an additional 2 cores, so Azure won't allow me to create it in the same region. To continue, I would have to deploy the third VM in UAE, which would require creating the Spoke VNet in UAE and potentially introducing another Bastion because of the regional architecture. This would significantly change the architecture we've been building and would no longer match the original single-region design. Should I proceed with the multi-region approach, or would you recommend that I stop here and use a different approach to resolve the regional quota limitation? I want to make sure I don't unnecessarily redesign the architecture before proceeding.

Today I got hands-on with Terraform and Microsoft Azure. I used Terraform to: - Configure the Azure provider - Create an Azure Resource Group using Infrastructure as Code - Run terraform plan to review proposed changes - Deploy the resource with terraform apply - Verify the Resource Group in the Azure Portal - Remove the infrastructure safely using terraform destroy - One of the biggest things I learned is that Terraform is not just about creating cloud resources — it is about managing infrastructure in a repeatable, controlled and trackable way. Seeing the Resource Group appear in Azure after terraform apply, and then disappear after terraform destroy, really helped connect the code to what is actually happening in the cloud. Taking it one step at a time making sure i understand and not rushing it. Another practical step forward in my Cloud/DevOps learning journey. #Terraform #Azure #DevOps #InfrastructureAsCode #CloudComputing #LearningInPublic