I keep trying to spin one up but, No matter what I do, when I create the dev center, it disappears.. this is annoying, morever, azure still isnt available in so many countries. :(
Just finished setting this up and there definitely seems to be some changes. At 13:14, I saw that you were able to click into the Pool to view all the machines in the pool but it doesn't seem like it's possible anymore. Not to mention there doesn't seem to be a way to limit users from creating an endless amount of DevBoxes as well.
In my tenant I can still click on the pool to view all machines and from there stop or delete them. Haven't heard anything about this going away, but then again it is in preview and bugs can occur. Regarding the limiting you are correct, there is now limit you can set as of now. But then again, the maximum cores you can use per region per subscription for dev boxes is really low now in the preview. I expect there to be a limit setting somewhere before Dev Box is GA, but I'll make sure to pass this feedback along to the product group :)
@@PetterTech Maybe it could do with the region. I also notice that your interface at 13:14 is also different slightly. Under "Manage", I can see both Dev Box pools as well as something else called "Environments"
Well, every dev box is personally assigned so I guess do it whatever way works for you :) The dev boxes are connected to a vNet that you set up yourself so if you want to connect to your on-prem network from there that is totally doable. You can use either a vpn or expressroute to create a link between your on-prem and the vNet the dev boxes are attached to. Or if you already have a connection setup with another vNet in Azure you can peer that vNet with your dev box vNet
From my understanding these two services will both live on. They serve a bit different purposes as the DevTest Labs is more for creating entire environments, classrooms and so on. While Dev Box is more of a user centric service that only provides each user with one or more VMs to develop (or just plainly work) on. You can of course create entire environments around the Dev Boxes, but that will not be a part of the service itself.
With more flexibility comes more complexity :) But I would not call this setup too complicated. After all, the setup is done by IT people and not users. The users would only need to use the dev box portal and there's not a whole they can do there except from creating and deleting dev boxes. The Dev Box service is by design not as simple as for example Windows 365 because it's meant to provide more functionality and flexibility. And keep in mind that I went from not having seen the service myself to having a dev box running in less than two hours, I feel that is more than acceptable. That being said, there's potential for improvement for sure :)
@UC-qV6thN7vA51NpmGVH3ijg Well, yeah surely that's the most flexible for you as a dev. I believe I was comparing Dev Box against Windows 365 when I was typing out my reply, at least in my head 😅😅 As regards to where you put your application, Dev Box isn't meant to the final destination. It's just a place to develop and test applications. Which, of course, you also could just as well do locally. But if you're part of a larger team it often (but not always) makes sense for everyone to be working from devices that are close to each other networkwise. Which could pose a challenge if everyone's scattered across the globe. That's one usecase where Dev Box could aid.
What are your thoughts on Dev Box? How do you feel it fits in the ecosystem with Azure Virtual Desktop and Windows 365?
Nice
I keep trying to spin one up but, No matter what I do, when I create the dev center, it disappears.. this is annoying, morever, azure still isnt available in so many countries. :(
Just spun up mine. Super stoked to be trying this.
Great video thanks..
Thanks for watching 👍
Is there a way to stop the VMs to save cost? Would it be possible to allow the user to start/stop the devboxes?
Yes, the users can start and stop their own VMs by default. But they can also be stopped from the admin portal :)
@@PetterTech Fantastic! Thanks for the reply.
Just finished setting this up and there definitely seems to be some changes. At 13:14, I saw that you were able to click into the Pool to view all the machines in the pool but it doesn't seem like it's possible anymore. Not to mention there doesn't seem to be a way to limit users from creating an endless amount of DevBoxes as well.
In my tenant I can still click on the pool to view all machines and from there stop or delete them. Haven't heard anything about this going away, but then again it is in preview and bugs can occur.
Regarding the limiting you are correct, there is now limit you can set as of now. But then again, the maximum cores you can use per region per subscription for dev boxes is really low now in the preview. I expect there to be a limit setting somewhere before Dev Box is GA, but I'll make sure to pass this feedback along to the product group :)
@@PetterTech Maybe it could do with the region. I also notice that your interface at 13:14 is also different slightly. Under "Manage", I can see both Dev Box pools as well as something else called "Environments"
How would you get a developer's SSH key(s) onto a Dev Box? Can you access on-premise network files from a Dev Box?
Well, every dev box is personally assigned so I guess do it whatever way works for you :)
The dev boxes are connected to a vNet that you set up yourself so if you want to connect to your on-prem network from there that is totally doable. You can use either a vpn or expressroute to create a link between your on-prem and the vNet the dev boxes are attached to. Or if you already have a connection setup with another vNet in Azure you can peer that vNet with your dev box vNet
@@PetterTech Thanks! Looking forward to more videos about Dev Box :)
Thanks for watching ;)
More videos will be coming 👍
How different is this from Azure DevTest Labs? is Microsoft DevBox a successor to Azure DevTest Labs?
From my understanding these two services will both live on.
They serve a bit different purposes as the DevTest Labs is more for creating entire environments, classrooms and so on.
While Dev Box is more of a user centric service that only provides each user with one or more VMs to develop (or just plainly work) on. You can of course create entire environments around the Dev Boxes, but that will not be a part of the service itself.
little bit complicated all these things to setup. Not really user friendly from MS
With more flexibility comes more complexity :)
But I would not call this setup too complicated. After all, the setup is done by IT people and not users. The users would only need to use the dev box portal and there's not a whole they can do there except from creating and deleting dev boxes.
The Dev Box service is by design not as simple as for example Windows 365 because it's meant to provide more functionality and flexibility. And keep in mind that I went from not having seen the service myself to having a dev box running in less than two hours, I feel that is more than acceptable.
That being said, there's potential for improvement for sure :)
@@PetterTech yeah i think also when you understand the idea and the process of this then it is ok and smart
@UC-qV6thN7vA51NpmGVH3ijg Well, yeah surely that's the most flexible for you as a dev. I believe I was comparing Dev Box against Windows 365 when I was typing out my reply, at least in my head 😅😅
As regards to where you put your application, Dev Box isn't meant to the final destination. It's just a place to develop and test applications. Which, of course, you also could just as well do locally. But if you're part of a larger team it often (but not always) makes sense for everyone to be working from devices that are close to each other networkwise. Which could pose a challenge if everyone's scattered across the globe. That's one usecase where Dev Box could aid.
it's really straightoward, provided you have some AVD knowledge. it's a twinbrother, though based on w365 engine actually