Merge pull request #264012 from RoseHJM/mdb-device-updates

MBD - Added compute and storage information.

Author: prmerger-automator[bot]

articles/dev-box/how-to-manage-dev-box-definitions.md

@@ -75,11 +75,11 @@ The following steps show you how to create a dev box definition by using an exis
 
    | Setting | Value | Note |
    |---|---|---|
-   | **Name** | Enter a descriptive name for your dev box definition. | You can't change the dev box definition name after it's created. |
+   | **Name** | Enter a descriptive name for your dev box definition. | You can't change the dev box definition name after creation. |
    | **Image** | Select the base operating system for the dev box. You can select an image from Azure Marketplace or from Azure Compute Gallery. </br> If you're creating a dev box definition for testing purposes, consider using the **Visual Studio 2022 Enterprise on Windows 11 Enterprise + Microsoft 365 Apps 22H2** image or **Visual Studio 2022 Pro on Windows 11 Enterprise + Microsoft 365 Apps 22H2** image. | To access custom images when you create a dev box definition, you can use Azure Compute Gallery. For more information, see [Configure Azure Compute Gallery](./how-to-configure-azure-compute-gallery.md). |
    | **Image version** | Select a specific, numbered version to ensure that all the dev boxes in the pool always use the same version of the image. Select **Latest** to ensure that new dev boxes use the latest image available. | Selecting the **Latest** image version enables the dev box pool to use the most recent version of your chosen image from the gallery. This approach ensures the created dev boxes stay up to date with the latest tools and code for your image. Existing dev boxes aren't modified when an image version is updated. |
-   | **Compute** | Select the compute combination for your dev box definition. | |
-   | **Storage** | Select the amount of storage for your dev box definition. | |
+   | **Compute** | Select the compute combination for your dev box definition. | Dev boxes use [Dsv5-series virtual machines](/azure/virtual-machines/dv5-dsv5-series#dsv5-series) for compute. |
+   | **Storage** | Select the amount of storage for your dev box definition. | Dev boxes use [Azure Premium SSDs](/azure/virtual-machines/disks-types#premium-ssds) for storage. |
    | **Enable hibernation**| Leave this checkbox unselected. | |
 
    :::image type="content" source="./media/how-to-manage-dev-box-definitions/recommended-test-image.png" alt-text="Screenshot that shows the pane for creating a dev box definition.":::

articles/dev-box/overview-what-is-microsoft-dev-box.md

@@ -73,6 +73,8 @@ Dev Box supports developers who are working on multiple projects. Developers can
 
 Organizations can even define dev boxes for various roles on a team. You might configure standard dev boxes with admin rights to give full-time developers greater control, while applying more restricted permissions for contractors.
 
+Dev boxes use [Dsv5-series virtual machines](/azure/virtual-machines/dv5-dsv5-series#dsv5-series), which have sufficient vCPUs and memory to meet the requirements associated with most general-purpose workloads. For storage, dev boxes use [Azure Premium SSDs](/azure/virtual-machines/disks-types#premium-ssds), which deliver high-performance and low-latency disk support.
+
 ## Components shared with Azure Deployment Environments
 
 Microsoft Dev Box and [Azure Deployment Environments](../deployment-environments/overview-what-is-azure-deployment-environments.md) are complementary services that share certain architectural components. Deployment Environments provides developers with preconfigured cloud-based environments for developing applications. Dev centers and projects are common to both services, and they help organize resources in an enterprise.