How to setup Dev Box, a tutorial for simple scenarios
ฝัง
- เผยแพร่เมื่อ 1 ก.ค. 2024
- In this video I show you how to setup Microsoft Dev Box in Azure. It's pretty straight forward for simpler scenarios 👍
More on Dev Box:
Custom Images: • How to Use Your Own Im...
Livestream about Dev Box:
th-cam.com/users/liveYJekPLapUAs
Microsoft's documentation: learn.microsoft.com/en-us/azu...
Socials:
Ask me stuff on Twitter: / pettertech
Catch me live on Twitch: / pettertech
Follow me on LinkedIn: / pettertech
Check out my awful code at Github: github.com/PetterTech
I also have merch: merch.streamelements.com/nere...
#DevBox #Azure - วิทยาศาสตร์และเทคโนโลยี
For those wondering: the deployment of my devbox in this video took about 23 minutes 🫡
I would be interested in the Azure Naming Tool as well.
Great to hear! It's in the works, should be out in a week or two 👍
Stumbled upon this video somehow and this Azure Naming Tool sounds interesting! I also had no idea that M365 Business Premium included this feature. Curious about cost of running these boxes. There also seems to be quite a number of steps to set this up but they aren't obviously related. Are these boxes useful for only development or can they be used to test sysadmin related things like Intune testing?
Well, I'm glad you stumbled upon it 🥳
I covered a lot more about the Dev Box service in the livestream I did on it, you could give that a watch if you want to learn more: th-cam.com/users/liveYJekPLapUAs
But to give you the short answers to you questions:
It's not entirely correct to say that M365 Business Premium includes Dev Box, but it does include the licensing prerequisites for Dev Box (which is the same as for Windows 365) like Entra ID, Intune and Windows.
The cost for Dev Box is consumption based, meaning you pay for what you use. If you have 5 dev boxes, then you pay for those 5 dev boxes. The cost is per hour and varies depending on the specs for the dev boxes. There's a compute cost and there's a storage cost, so shutting down dev boxes will save you on compute but you still have to pay for storage.
I will say that Dev Box has a lot of usecases other than development. Both the naming and the marketing material from Microsoft leads you to believe it's only for developers, but things like Intune testing (as you suggest) is certainly among the things it can be used for.
Oh, and a video on Azure Naming Tool is in the works 🫡
@@PetterTech thanks for the livestream link, will check it out. I think the cost is the biggest driver for us in using them. I can easily deploy a VM on-prem but the dev box would be quicker. Curious to see a cost breakdown calculator (will hunt around for one). Just more stuff to learn about! haha
You can find the cost details here: azure.microsoft.com/en-us/pricing/details/dev-box/
Or you could use the Azure Pricing calculator: azure.microsoft.com/en-us/pricing/calculator/
You could always argue that your time is worth money as well, in that case dev box might end up cheaper in total ;)
@@PetterTech Awesome, thank you!
How billing will work for different department in same organization having same DevCenter instance with multiple projects for each department.?
The consumption billing should follow the projects. So if you place the projects in separate subscriptions you can split the cost in that way
@@PetterTech Subscription could be same as architecture prefers same VNet and different subnets. However, Resource group could help. Thank you for your response.