3=h=%The resource write operation failed to complete successfully, because it reached terminal provisioning state ‘Failed’. (Code: ResourceDeploymentFailure, Target: /subscriptions/a2b28c85-1948-4263-90ca-bade2bac4df4/resourceGroups/kml_rg_main-63f86954f7eb4c98/providers/Microsoft.Compute/virtualMachines/vm1
Hi @Vinaykumar
Please share the lab link. If it’s a KKE task, also provide the course name, level, and task name.
kk_lab_user_main-006b4c28186a439e@azurekmlprodkodekloud.onmicrosoft.com
I am learning Azure 104.
i used practice in Sandbox link
kindly look into this iam facing this issue from so many days
That’s not what he means, actually. What we need is a link that has “*.kodekloud.com” in it, so we can figure out what lab you’re doing. The microsoft.com link doesn’t tell us anything we’d need to know in order to help you.
kindly check this one if you any further information iam ready share .
Hi @Vinaykumar
I guess you’re using the KodeKloud Playground to practice the Azure knowledge from the AZ-104 course. If so, please provide more details about the steps you’ve taken, sharing only the final error logs makes it difficult for us to understand the context and provide proper support.
Also, please check the list of allowed services in the Azure Playground here to ensure you’re not trying to create any unsupported resources.
Yes iam using Azure playground and kodekloud engineer also
firstly Iam logging with User id and Password which are provided by kodekloud then trying to do lab on that , but here iam not able to create Users and VMs ,kindly do the needful ASAP iam trying it from last 1 month
I was able to create the VM in the KodeKloud Playground without any errors. Please share the steps you followed and a screenshot of the issue, just saying “I couldn’t do it” doesn’t give us enough information to help.
I am unable to create a VM kindly find the Snaps of Errors which i face during configuring VM
Could you please update me with the details once available. I am ready to send any further details if you want.
It’s always worth looking at the error output closely; in this case, it shows the problem:
Short version: you’ve used either too much storage, or too expensive of storage. The fix is to look carefully at the playground limitations on the landing page for the Azure playground; it tells you what you need to do here:
