Components common to Microsoft Dev Box and Azure Deployment Environments
Microsoft Dev Box and Azure Deployment Environments are complementary services that share certain architectural components. Dev centers and projects are common to both services, and they help organize resources in an enterprise. You can configure dev centers and projects in the Azure portal.
Common components
The diagram shows the components of Dev Box and Deployment Environments. Dev centers and projects are common to both services. Both use managed identities to support authentication, and both services provide access for developers through the developer portal.
The following table lists Dev Box and Deployment Environments components:
Component | Dev Box | Deployment Environments |
---|---|---|
Dev centers | Yes | Yes |
Projects | Yes | Yes |
Dev box pools | Yes | No |
Dev box definitions | Yes | No |
Dev boxes | Yes | No |
Compute galleries | Yes | No |
Managed identities | Yes | Yes |
Environment types | No | Yes |
Environments | No | Yes |
Catalogs | No | Yes |
Developer portal | Yes | Yes |
How components appear in the Azure portal
As you work with Dev Box or Deployment Environments in the Azure portal, you can access components from both services.
In the dev center overview, you can access options to:
(1) Configure your dev boxes.
(2) Configure your environments.
In the projects overview, you can access options to:
(1) Configure environment types for a specific project.
(2) Manage dev box pools and environments.
You might also see informational messages that refer to a service you aren't using, like this one from the projects overview:
If you're not configuring for the service named in the informational message, you can safely ignore it.
Developer portal
You can access your dev boxes and deployment environments through the developer portal. You see existing dev boxes and environments displayed as shown in this screenshot:
You can create new dev boxes and environments through the developer portal menu at the top right.
And you can manage your existing dev boxes and environments, too. Select the more actions menu on the relevant card. Here's an example of managing an environment:
Next steps
To learn how to configure Microsoft Dev Box, see Quickstart: Configure the Microsoft Dev Box service.
To learn how to configure Azure Deployment Environments, see Quickstart: Create and configure a dev center.
Feedback
Submit and view feedback for