Merge pull request #244124 from MicrosoftDocs/release-ga-dev-box

Release ga dev box--scheduled release at 8am of 7/10

Author: huypub

articles/dev-box/concept-common-components.md

@@ -8,7 +8,7 @@ ms.author: rosemalcolm
 author: RoseHJM
 ms.date: 06/23/2023
 ---
-# Components common to Microsoft Dev Box and Azure Deployment Environments  
+# Components common to Microsoft Dev Box and Azure Deployment Environments 
 
 > [!TIP]
 > Welcome to the **Microsoft Dev Box** documentation. If you're looking for information about **Azure Deployment Environments**, follow this link: [*Components common to Azure Deployment Environments and Microsoft Dev Box*](../deployment-environments/concept-common-components.md).

articles/dev-box/concept-dev-box-concepts.md

@@ -11,7 +11,7 @@ ms.custom: template-concept
 #Customer intent: As a developer, I want to understand Dev Box concepts and terminology so that I can set up a Dev Box environment.
 ---
 
-# Key concepts for Microsoft Dev Box Preview
+# Key concepts for Microsoft Dev Box 
 
 This article describes the key concepts and components of Microsoft Dev Box.
 
@@ -26,7 +26,7 @@ As a dev box user, you have control over your own dev boxes. You can create more
 A dev center is a collection of projects that require similar settings. Dev centers enable dev infrastructure managers to:
 
 - Manage the images and SKUs available to the projects by using dev box definitions.
-- Configure the networks that the development teams consume by using network connections.  
+- Configure the networks that the development teams consume by using network connections. 
 
 ## Project
 

articles/dev-box/dev-box-faq.yml

@@ -27,12 +27,14 @@ sections:
           When you create a generalized VM to capture to an image, the following issues can impact provisioning and startup times:
           1. Enable the Read/Write cache on the OS disk. 
              - To verify, open the Azure portal and navigate to the image. Select **JSON view**, and make sure `properties.storageProfile.osDisk.caching` value is `ReadWrite`.
-          2. Create the image using the following sysprep options: `/mode:vm flag: Sysprep /generalize /oobe /mode:vm`.
-             - This prevents a lengthy search for and installation of drivers during the first boot.
+          2. Create the image using the following sysprep options:
+            `/mode:vm flag: Sysprep /generalize /oobe /mode:vm`.
+             - These options prevent a lengthy search for and installation of drivers during the first boot.
           3. Enable nested virtualization in your base image.
              - In the UI, open **Turn Windows features on or off** and select **Virtual Machine Platform**. 
              - Or run the following PowerShell command, Enable-WindowsOptionalFeature -FeatureName VirtualMachinePlatform -Online 
-          4. Disable the reserved storage state feature in the image by using the following command: `DISM.exe /Online /Set-ReservedStorageState /State:Disabled`.   
+          4. Disable the reserved storage state feature in the image by using the following command: 
+            `DISM.exe /Online /Set-ReservedStorageState /State:Disabled`.   
 
           For more information, see: [Compute gallery image requirements](how-to-configure-azure-compute-gallery.md#compute-gallery-image-requirements).
 
@@ -42,6 +44,21 @@ sections:
                 - REST API - [Usages - List By Location - REST API (Azure Dev Center) | Microsoft Learn](/rest/api/devcenter/administrator/usages/list-by-location?tabs=HTTP)
                 - CLI - [az devcenter admin usage | Microsoft Learn |](/cli/azure/devcenter/admin/usage?view=azure-cli-latest) 
 
+  - name: Dev Box hibernation
+    questions:
+      - question: Can I use auto-stop schedules to hibernate Dev Boxes on a schedule? # Question.
+        answer: 
+          The ability to use auto-stop schedules to initiate hibernation is in Preview.
+
+      - question: I enabled hibernation on a Dev Box definition, but my Dev Box definition reports that hibernation couldn't be enabled. # Question.
+        answer: |
+          - We recommend using the Visual Studio for Dev Box marketplace images, either directly, or as base images for generating your custom image.
+          - The Windows + OS optimizations image contain optimized power settings, and they can't be used with hibernation.  
+          - If you're using a custom Azure Compute Gallery image, enable hibernation on your Azure Compute Gallery image before enabling hibernation on your Dev Box definition.
+          - If hibernation can't be enabled on the definition even after you enable it on your gallery image, your custom image likely has a Windows configuration that prevents hibernation. 
+
+            For more information, see [Settings not compatible with hibernation](how-to-configure-dev-box-hibernation.md#settings-not-compatible-with-hibernation).
+
 additionalContent: |
     ## Next steps
 

articles/dev-box/how-to-configure-azure-compute-gallery.md

@@ -31,7 +31,7 @@ To learn more about Azure Compute Gallery and how to create galleries, see:
 - A compute gallery. Images stored in a compute gallery can be used in a dev box definition, provided they meet the requirements listed in the [Compute gallery image requirements](#compute-gallery-image-requirements) section.
 
 > [!NOTE]
-> Microsoft Dev Box Preview doesn't support community galleries.
+> Microsoft Dev Box doesn't support community galleries.
 
 ## Compute gallery image requirements 
 
@@ -62,13 +62,13 @@ The image version must meet the following requirements:
 
 ## Provide permissions for services to access a gallery
 
-When you use an Azure Compute Gallery image to create a dev box definition, the Windows 365 service validates the image to ensure that it meets the requirements to be provisioned for a dev box. The Dev Box Preview service replicates the image to the regions specified in the attached network connections, so the images are present in the region that's required for dev box creation.
+When you use an Azure Compute Gallery image to create a dev box definition, the Windows 365 service validates the image to ensure that it meets the requirements to be provisioned for a dev box. The Dev Box service replicates the image to the regions specified in the attached network connections, so the images are present in the region that's required for dev box creation.
 
 To allow the services to perform these actions, you must provide permissions to your gallery as follows.
 
 ### Add a user-assigned identity to the dev center
 
-1. [Follow the steps to create a user-assigned managed identity](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity).  
+1. [Follow the steps to create a user-assigned managed identity](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity). 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. In the search box, enter **dev box**. In the list of results, select **Dev centers**.
 1. Open your dev center. On the left menu, select **Identity**.
@@ -179,4 +179,4 @@ The gallery is detached from the dev center. The gallery and its images aren't d
 
 ## Next steps
 
-- Learn more about [key concepts in Microsoft Dev Box Preview](./concept-dev-box-concepts.md).
+- Learn more about [key concepts in Microsoft Dev Box ](./concept-dev-box-concepts.md).

articles/dev-box/how-to-configure-dev-box-azure-diagnostic-logs.md

@@ -12,14 +12,14 @@ ms.date: 04/28/2023
 
 # Configure Azure diagnostic logs for a dev center 
 
-With Azure diagnostic logs for DevCenter, you can view audit logs for dataplane operations in your dev center.  These logs can be routed to any of the following destinations:
+With Azure diagnostic logs for DevCenter, you can view audit logs for dataplane operations in your dev center. These logs can be routed to any of the following destinations:
 
 * Azure Storage account
 * Log Analytics workspace
 
 This feature is available on all dev centers. 
 
-Diagnostics logs allow you to export basic usage information from your dev center to different kinds sources so that you can consume them in a customized way.  The dataplane audit logs expose information around CRUD operations for dev boxes within your dev center.  Including, for example,  start and stop commands executed on dev boxes. Some sample ways you can choose to export this data:
+Diagnostics logs allow you to export basic usage information from your dev center to different kinds sources so that you can consume them in a customized way. The dataplane audit logs expose information around CRUD operations for dev boxes within your dev center. Including, for example, start and stop commands executed on dev boxes. Some sample ways you can choose to export this data:
 
 * Export data to blob storage, export to CSV.
 * Export data to Azure Monitor logs and view and query data in your own Log Analytics workspace 
@@ -127,7 +127,7 @@ DevCenter stores data in the following tables.
 
 | Table | Description |
 |:---|:---|
-| DevCenterDiagnosticLogs | Table used to store dataplane request/response information on dev box or environments within the dev center.   |
+| DevCenterDiagnosticLogs | Table used to store dataplane request/response information on dev box or environments within the dev center.  |
 
 
 ### Sample Kusto Queries

articles/dev-box/how-to-configure-dev-box-hibernation.md

@@ -0,0 +1,146 @@
+---
+title: Configure hibernation for Microsoft Dev Box
+titleSuffix: Microsoft Dev Box
+description: Learn how to enable, disable and troubleshoot hibernation for your dev boxes. 
+services: dev-box
+ms.service: dev-box
+author: RoseHJM
+ms.author: rosemalcolm
+ms.date: 07/05/2023
+ms.topic: how-to
+#Customer intent: As a platform engineer, I want dev box users to be able to hibernate their dev boxes as part of my cost management strategy and so that dev box users can resume their work where they left off.
+---
+
+# How to configure Dev Box Hibernation (preview)
+
+Hibernating dev boxes at the end of the workday can help you save a substantial portion of your VM costs. It eliminates the need for developers to shut down their dev box and lose their open windows and applications.
+
+With the introduction of Dev Box Hibernation (Preview), you can enable this capability on new dev boxes and hibernate and resume them. This feature provides a convenient way to manage your dev boxes while maintaining your work environment.
+
+There are two steps in enabling hibernation; you must enable hibernation on your dev box image and enable hibernation on your dev box definition.
+
+> [!IMPORTANT]
+> Dev Box Hibernation is currently in PREVIEW.
+> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+
+
+## Key concepts for hibernation-enabled images
+
+- The following SKUs support hibernation: 8, 16 vCPU SKUs. 32 vCPU SKUs do not support hibernation.
+
+- You can enable hibernation only on new dev boxes created with hibernation-enabled dev box definitions. You cannot enable hibernation on existing dev boxes.
+
+- You can hibernate a dev box only using the dev Portal, CLI, PowerShell, SDKs, and API. Hibernating from within the dev box in Windows is not supported.
+
+- If you use a marketplace image, we recommend using the Visual Studio for dev box images.
+
+- The Windows 11 Enterprise CloudPC + OS Optimizations image contains optimized power settings, and they cannot be used with hibernation.
+
+- Once enabled, you cannot disable hibernation on a dev box. However, you can disable hibernation support on the dev box definition so that future dev boxes do not have hibernation.
+
+- To enable hibernation, you need to enable nested virtualization in your Windows OS. If the "Virtual Machine Platform" feature is not enabled in your DevBox image, DevBox will automatically enable nested virtualization for you if you choose to enable hibernation.
+
+- Hibernation doesn't support hypervisor-protected code integrity (HVCI)/ Memory Integrity features. Dev box disables this feature automatically.
+
+- Auto-stop schedules still shutdown the dev boxes. If you want to hibernate your dev box, you can do it through the developer portal or using the CLI.
+
+### Settings not compatible with hibernation
+
+These settings are known to be incompatible with hibernation, and aren't supported for hibernation scenarios: 
+
+- **Memory Integrity/Hypervisor Code Integrity.** 
+    
+    To disable Memory Integrity/Hypervisor Code Integrity:
+    1. In the start menu, search for *memory integrity* 
+    1. Select **Core Isolation**
+    1. Under **Memory integrity**, ensure that memory integrity is set to Off.
+
+- **Guest Virtual Secure Mode based features without Nested Virtualization enabled.** 
+
+    To enable Nested Virtualization:
+    1. In the start menu, search for *Turn Windows features on or off*
+    1. In Turn Windows features on or off, select **Virtual Machine Platform**, and then select **OK**    
+ 
+## Enable hibernation on your dev box image 
+
+The  Visual Studio and Microsoft 365 images that dev Box provides in the Azure Marketplace are already configured to support hibernation. You don't need to enable hibernation on these images, they're ready to use. 
+
+If you plan to use a custom image from an Azure Compute Gallery, you need to enable hibernation capabilities as you create the new image. To enable hibernation capabilities, set the IsHibernateSupported flag to true. You must set the IsHibernateSupported flag when you create the image, existing images cannot be modified.  
+
+To enable hibernation capabilities, set the `IsHibernateSupported` flag to true:
+
+```azurecli-interactive
+az sig image-definition create /
+   --resource-group <resourcegroupname> --gallery-name <galleryname> --gallery-image-definition <imageName> --location <location> / 
+   --publisher <publishername> --offer <offername> --sku <skuname> --os-type windows --os-state Generalized / 
+   --features "IsHibernateSupported=true SecurityType=TrustedLaunch" --hyper-v-generation V2 
+```
+
+For more information about creating a custom image, see [Configure a dev box by using Azure VM Image Builder](how-to-customize-devbox-azure-image-builder.md).
+
+## Enable hibernation on a dev box definition 
+
+You can enable hibernation as you create a dev box definition, providing that the dev box definition uses a hibernation-enabled custom or marketplace image. You can also update an existing dev box definition that uses a hibernation-enabled custom or marketplace image. 
+
+All new dev boxes created in dev box pools that use a dev box definition with hibernation enabled can hibernate in addition to shutting down. If a pool has dev boxes that were created before hibernation was enabled, they continue to only support shutdown. 
+
+Dev Box validates your image for hibernate support. Your dev box definition may fail validation if hibernation couldn't be successfully enabled using your image. 
+
+### Enable hibernation on an existing dev box definition by using the Azure portal
+
+1. Sign in to the [Azure portal](https://portal.azure.com).
+
+1. In the search box, enter **dev center**. In the list of results, select **Dev centers**.
+
+1. Open the dev center that contains the dev box definition that you want to update, and then select **Dev box definitions**.
+  
+   :::image type="content" source="./media/how-to-configure-dev-box-hibernation/select-dev-box-definitions.png" alt-text="Screenshot that shows the dev center overview page and the menu option for dev box definitions.":::
+  
+1. Select the dev box definition that you want to update, and then select the edit button.
+
+   :::image type="content" source="./media/how-to-configure-dev-box-hibernation/update-dev-box-definition.png" alt-text="Screenshot of the list of existing dev box definitions and the edit button.":::
+
+1. On the Editing \<dev box definition\> page, select **Enable hibernation**.
+
+   :::image type="content" source="./media/how-to-configure-dev-box-hibernation/dev-box-pool-enable-hibernation.png" alt-text="Screenshot of the page for editing a dev box definition, with Enable hibernation selected..":::
+
+1. Select **Save**.
+
+### Update an existing dev box definition by using the CLI
+ 
+```azurecli-interactive
+az devcenter admin devbox-definition update --dev-box-definition-name <DevBoxDefinitionName> -–dev-center-name <devcentername> --resource-group <resourcegroupname> –-hibernateSupport enabled
+``` 
+
+## Disable hibernation on a dev box definition
+
+ If you have issues provisioning new VMs after enabling hibernation on a pool or you want to revert to shut down only dev boxes, you can disable hibernation on the dev box definition.
+
+### Disable hibernation on an existing dev box definition by using the Azure portal
+
+1. Sign in to the [Azure portal](https://portal.azure.com).
+
+1. In the search box, enter **dev center**. In the list of results, select **Dev centers**.
+
+1. Open the dev center that contains the dev box definition that you want to update, and then select **Dev box definitions**.
+  
+1. Select the dev box definition that you want to update, and then select the edit button.
+
+1. On the Editing \<dev box definition\> page, clear **Enable hibernation**.
+
+   :::image type="content" source="./media/how-to-configure-dev-box-hibernation/dev-box-pool-disable-hibernation.png" alt-text="Screenshot of the page for editing a dev box definition, with Enable hibernation not selected.":::
+
+1. Select **Save**.
+
+### Disable hibernation on an existing dev box definition by using the CLI
+ 
+```azurecli-interactive
+az devcenter admin devbox-definition update --dev-box-definition-name <DevBoxDefinitionName> -–dev-center-name <devcentername> --resource-group <resourcegroupname> –-hibernateSupport disabled  
+``` 
+
+## Next steps
+
+- [Create a dev box pool](how-to-manage-dev-box-pools.md)
+- [Configure a dev box by using Azure VM Image Builder](how-to-customize-devbox-azure-image-builder.md)  
+- [How to hibernate your dev box](how-to-hibernate-your-dev-box.md)
+- [CLI Reference for az devcenter admin devbox-definition update](/cli/azure/devcenter/admin/devbox-definition?view=azure-cli-latest&preserve-view=true)

articles/dev-box/how-to-configure-network-connections.md

@@ -1,7 +1,7 @@
 ---
 title: Configure network connections
 titleSuffix: Microsoft Dev Box
-description: Learn how to create, delete, attach, and remove Microsoft Dev Box Preview network connections.
+description: Learn how to create, delete, attach, and remove Microsoft Dev Box network connections.
 services: dev-box
 ms.service: dev-box
 author: RoseHJM
@@ -68,11 +68,11 @@ To create a network connection, you need an existing virtual network and subnet.
 
 An organization can control network ingress and egress by using a firewall, network security groups, and even Microsoft Defender.
 
-If your organization routes egress traffic through a firewall, you need to open certain ports to allow the Microsoft Dev Box Preview service to function. For more information, see [Network requirements](/windows-365/enterprise/requirements-network).
+If your organization routes egress traffic through a firewall, you need to open certain ports to allow the Microsoft Dev Box service to function. For more information, see [Network requirements](/windows-365/enterprise/requirements-network).
 
 ## Plan a network connection
 
-The following sections show you how to create and configure a network connection in Microsoft Dev Box Preview.
+The following sections show you how to create and configure a network connection in Microsoft Dev Box .
 
 ### Types of Active Directory join
 
@@ -165,7 +165,7 @@ You need to attach a network connection to a dev center before you can use it in
 
 1. Select the dev center that you created, and then select **Networking**.
 
-1. Select  **+ Add**.
+1. Select **+ Add**.
 
 1. On the **Add network connection** pane, select the network connection that you created earlier, and then select **Add**.