Skip to content

Commit f1c6c8d

Browse files
authored
Merge pull request #296834 from MicrosoftDocs/main
3/24 11:00 AM IST Publish
2 parents bc7de2a + cd96f67 commit f1c6c8d

6 files changed

+63
-44
lines changed

articles/app-service/samples-bicep.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ To learn about the Bicep syntax and properties for App Services resources, see [
1919
|-|-|
2020
| [App Service plan and basic Linux app](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/webapp-basic-linux) | Deploys an App Service app that is configured for Linux. |
2121
| [App Service plan and basic Windows app](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/webapp-basic-windows) | Deploys an App Service app that is configured for Windows. |
22+
| [App Service plan and Windows container app](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/app-service-docs-windows-container) | Deploys an App Service app that is configured for a Windows container. |
2223
| **Configuring an app** | **Description** |
2324
| [App with log analytics module](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/web-app-loganalytics)| Deploys an App Service app with log analytics. |
2425
| [App with regional VNet integration](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/app-service-regional-vnet-integration)| Deploys an App Service app with regional VNet integration enabled. |

articles/backup/azure-file-share-support-matrix.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Support Matrix for Azure files backup by using Azure Backup
33
description: Provides a summary of support settings and limitations when backing up Azure files.
44
ms.topic: reference
5-
ms.date: 03/11/2025
5+
ms.date: 03/24/2025
66
ms.custom: references_regions, engagement-fy24
77
ms.service: azure-backup
88
author: jyothisuri
@@ -59,9 +59,6 @@ Migration of File Shares protected with snapshot backup to vaulted backup is su
5959
>The source Storage Account must have the **Allow storage account key access** setting enabled for successful Azure Files backup and restore.
6060
6161

62-
>[!Note]
63-
>Storage accounts with restricted network access aren't supported.
64-
6562
---
6663

6764
## Supported File Shares

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

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -6,23 +6,23 @@ services: dev-box
66
ms.service: dev-box
77
author: RoseHJM
88
ms.author: rosemalcolm
9-
ms.date: 12/20/2023
9+
ms.date: 03/23/2025
1010
ms.topic: how-to
11+
12+
#customer intent: As a developer, I want to learn how to configure and attach an Azure compute gallery to a dev center in Microsoft Dev Box so that I can use a compute gallery to manage and share dev box images.
1113
---
1214

1315
# Configure Azure Compute Gallery for Microsoft Dev Box
1416

15-
In this article, you learn how to configure and attach an Azure compute gallery to a dev center in Microsoft Dev Box. With Azure Compute Gallery, you can give developers customized images for their dev box.
16-
17-
Azure Compute Gallery is a service for managing and sharing images. A gallery is a repository that's stored in your Azure subscription and helps you build structure and organization around your image resources. Dev Box supports GitHub, Azure Repos, and Bitbucket repositories to provide an image gallery.
17+
This article explains how to configure and attach an Azure compute gallery to a dev center in Microsoft Dev Box. Azure Compute Gallery allows you to manage and share customized images for dev boxes, helping development teams standardize and streamline their workflows. By attaching a compute gallery to a dev center, you can create dev box definitions based on stored images, ensuring consistency and efficiency.
1818

1919
After you attach a compute gallery to a dev center in Microsoft Dev Box, you can create dev box definitions based on images stored in the compute gallery.
2020

21-
Advantages of using a gallery include:
21+
Advantages of using a gallery:
2222

23-
- You maintain the images in a single location and use them across dev centers, projects, and pools.
24-
- Development teams can use the latest version of an image definition to ensure they always receive the most recent image when creating dev boxes.
25-
- Development teams can standardize on a supported image version until a newer version is validated.
23+
- Centralized image management: Maintain images in a single location and reuse them across dev centers, projects, and pools.
24+
- Always up-to-date: Ensure development teams receive the latest validated image versions for consistent dev box creation.
25+
- Standardization: Allow teams to standardize on a supported image version until a newer version is validated.
2626

2727
To learn more about Azure Compute Gallery and how to create galleries, see:
2828

@@ -31,8 +31,8 @@ To learn more about Azure Compute Gallery and how to create galleries, see:
3131

3232
## Prerequisites
3333

34-
- A dev center. If you don't have one available, follow the steps in [Create a dev center](quickstart-configure-dev-box-service.md#create-a-dev-center).
35-
- 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.
34+
- **Dev center:** If you don't have a dev center, follow the steps in [Create a dev center](quickstart-configure-dev-box-service.md#create-a-dev-center).
35+
- **Compute gallery:** Ensure your compute gallery meets the [image requirements](#compute-gallery-image-requirements) to be used in dev box definitions.
3636

3737
> [!NOTE]
3838
> Microsoft Dev Box doesn't support community galleries.
@@ -135,7 +135,7 @@ Use the following steps to manually assign the role.
135135
| --- | --- |
136136
| **Role** | Select **Contributor**. |
137137
| **Assign access to** | Select **Managed Identity**. |
138-
| **Members** | Search for and select the user-assigned managed identity that you created when you [added a user-assigned identity to the dev center](#add-a-user-assigned-identity-to-the-dev-center). |
138+
| **Members** | Search for and select the user-assigned managed identity that you created when you added a user-assigned identity to the dev center. |
139139

140140
You can use the same managed identity in multiple dev centers and compute galleries. Any dev center with the managed identity added has the necessary permissions to the images in the gallery that has the Contributor role assignment added.
141141

@@ -169,7 +169,7 @@ To use the images from a compute gallery in dev box definitions, you must first
169169

170170
:::image type="content" source="media/how-to-configure-azure-compute-gallery/gallery-grid.png" alt-text="Screenshot that shows the page for compute galleries page with example galleries listed.":::
171171

172-
After you successfully add a gallery, the images in the gallery are available to select when you create and update dev box definitions.
172+
After adding a gallery, the images in the gallery are available to select when you create and update dev box definitions.
173173

174174
## Remove a gallery from a dev center
175175

@@ -178,6 +178,8 @@ You can detach galleries from dev centers so their images can no longer be used
178178
> [!NOTE]
179179
> You can't remove galleries that are being actively used in dev box definitions. Before you can remove such a gallery, you must delete the associated dev box definition or update the definition to use an image from a different gallery.
180180
181+
You can't remove galleries actively used in dev box definitions.
182+
181183
1. Sign in to the [Azure portal](https://portal.azure.com).
182184

183185
1. In the search box, enter **dev box**. In the list of results, select **Dev centers**.

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

Lines changed: 21 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,29 @@
11
---
22
title: Configure hibernation for Microsoft Dev Box
33
titleSuffix: Microsoft Dev Box
4-
description: Learn how to enable, disable, and troubleshoot hibernation in Microsoft Dev Box. Configure hibernation settings for your image and dev box definition.
4+
description: "Configure hibernation in Microsoft Dev Box to support cost-effective development and uninterrupted workflows. "
55
services: dev-box
66
ms.service: dev-box
77
ms.custom:
88
- build-2024
9+
- ai-gen-docs-bap
10+
- ai-gen-description
11+
- ai-seo-date:03/23/2025
912
author: RoseHJM
1013
ms.author: rosemalcolm
11-
ms.date: 01/02/2024
14+
ms.date: 03/23/2025
1215
ms.topic: how-to
13-
#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.
16+
17+
#customer intent: As a platform engineer, I want to configure hibernation for dev box definitions so that I can manage resource usage efficiently.
1418
---
1519

1620
# Configure hibernation in Microsoft Dev Box
1721

18-
In this article, you learn how to enable and disable hibernation in Microsoft Dev Box. You control hibernation at the dev box image and dev box definition level.
19-
20-
Hibernating dev boxes at the end of the workday can help you save a substantial portion of your virtual machine (VM) costs. It eliminates the need for developers to shut down their dev box and lose their open windows and applications.
22+
Hibernation in Microsoft Dev Box helps you manage cloud development environments efficiently while reducing costs. By enabling hibernation, you can preserve the state of open applications and windows, saving virtual machine (VM) costs without disrupting workflows. This article explains how to configure hibernation at the dev box image and definition levels, automate hibernation schedules, and address compatibility considerations.
2123

22-
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.
24+
With Dev Box Hibernation (Preview), you can enable hibernation on new dev boxes, allowing you to hibernate and resume them seamlessly. This feature simplifies dev box management while maintaining productivity.
2325

24-
There are three steps to enable hibernation:
26+
Follow these three steps to enable hibernation:
2527

2628
1. Enable hibernation on your dev box image
2729
1. Enable hibernation on your dev box definition
@@ -39,7 +41,7 @@ Before you enable hibernation on your dev box, review the following consideratio
3941

4042
- You can enable hibernation only on new dev boxes created with hibernation-enabled dev box definitions. You can't enable hibernation on existing dev boxes.
4143

42-
- You can hibernate a dev box only by using the Microsoft developer portal, the Azure CLI, PowerShell, SDKs, and the REST API. Hibernating from within the dev box in Windows isn't supported.
44+
- You can hibernate a dev box using the Microsoft developer portal, the Azure CLI, PowerShell, SDKs, or the REST API. Hibernating from within the dev box in Windows isn't supported.
4345

4446
- If you're working with an Azure Marketplace image, we recommend using the Visual Studio for dev box images.
4547

@@ -51,10 +53,10 @@ Before you enable hibernation on your dev box, review the following consideratio
5153

5254
- Hibernation doesn't support hypervisor-protected code integrity (HVCI)/ Memory Integrity features. Dev box disables this feature automatically.
5355

54-
- Auto-stop schedules will hibernate Dev Boxes that were created after you enabled hibernation on the associated Dev Box definition. Dev Boxes that were created before you enabled hibernation on the Dev Box definition will continue to shut down.
56+
- Auto-stop schedules hibernate Dev Boxes created after you enable hibernation on the associated Dev Box definition. Dev Boxes that were created before you enabled hibernation on the Dev Box definition will continue to shut down.
5557

5658
> [!NOTE]
57-
> The functionality to schedule dev boxes to hibernate automatically is available as a public preview. You can read more about the announcement at [Microsoft Dev Box - Auto-Hibernation Schedules Preview](https://aka.ms/devbox/preview/hibernate-on-schedule).
59+
> The functionality to schedule dev boxes to hibernate automatically is available as a public preview.
5860
5961
### Settings not compatible with hibernation
6062

@@ -70,6 +72,7 @@ The following settings are known to be incompatible with hibernation, and aren't
7072
1. Under **Memory integrity**, set the toggle to **Off**.
7173

7274
After you change this setting, you need to restart the machine.
75+
After changing this setting, restart the machine.
7376

7477
- **Guest Virtual Secure Mode based features without Nested Virtualization enabled**
7578

@@ -105,6 +108,8 @@ az sig image-version create
105108

106109
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).
107110

111+
Learn more about creating a custom image in [Configure a dev box by using Azure VM Image Builder](how-to-customize-devbox-azure-image-builder.md).
112+
108113
## Enable hibernation on a dev box definition
109114

110115
In Microsoft Dev Box, you can enable hibernation for a new dev box definition when the definition uses a hibernation-enabled custom or Azure Marketplace image. You can also update an existing dev box definition that uses a hibernation-enabled custom or Azure Marketplace image.
@@ -146,16 +151,18 @@ az devcenter admin devbox-definition update
146151

147152
### Troubleshooting
148153

149-
If you enable hibernation on a Dev Box definition, but the definition reports that hibernation couldn't be enabled:
154+
If you enable hibernation on a Dev Box definition and the definition reports that hibernation isn't enabled:
150155
- We recommend using the Visual Studio for Dev Box marketplace images, either directly, or as base images for generating your custom image.
151-
- The Windows + OS optimizations image contains optimized power settings, and they can't be used with hibernation.
156+
- The Windows + OS optimizations image contains optimized power settings and isn't compatible with hibernation.
152157
- 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.
153158
- 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.
154159

155-
For more information, see [Settings not compatible with hibernation](how-to-configure-dev-box-hibernation.md#settings-not-compatible-with-hibernation).
160+
For more information, see [Settings not compatible with hibernation](#settings-not-compatible-with-hibernation).
156161

157162
## Disable hibernation on a dev box definition
158163

164+
If you encounter issues provisioning new VMs after enabling hibernation on a pool, disable hibernation on the dev box definition.
165+
159166
If you have issues provisioning new VMs after you enable hibernation on a pool, you can disable hibernation on the dev box definition. You can also disable hibernation when you want to revert the setting to only shutdown dev boxes.
160167

161168
You can disable hibernation on a dev box definition by using the Azure portal or the CLI.
@@ -185,7 +192,6 @@ az devcenter admin devbox-definition update
185192

186193
## Related content
187194

188-
189195
- [How to hibernate your dev box](how-to-hibernate-your-dev-box.md)
190196
- [Configure a dev box by using Azure VM Image Builder](how-to-customize-devbox-azure-image-builder.md)
191197
- [Azure CLI reference for az devcenter admin devbox-definition](/cli/azure/devcenter/admin/devbox-definition?view=azure-cli-latest&preserve-view=true)

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

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: dev-box
66
ms.service: dev-box
77
author: RoseHJM
88
ms.author: rosemalcolm
9-
ms.date: 01/05/2024
9+
ms.date: 03/23/2025
1010
ms.topic: how-to
1111
#Customer intent: As a platform engineer, I want to be able to manage dev box definitions so that I can provide appropriate dev boxes to my users.
1212
---
@@ -36,20 +36,22 @@ When you create a dev box definition, you need to select a virtual machine image
3636

3737
Azure Marketplace gives you quick access to various images, including images that are preconfigured with productivity tools like Microsoft Teams and provide optimal performance.
3838

39-
When you're selecting an Azure Marketplace image, consider using an image that has the latest version of Windows 11 Enterprise and the Microsoft 365 apps installed.
39+
When you select an Azure Marketplace image, use an image with the latest version of Windows 11 Enterprise and Microsoft 365 apps installed.
4040

4141
### Azure Compute Gallery
4242

4343
Azure Compute Gallery enables you to store and manage a collection of custom images. You can build an image to your dev team's exact requirements and store it in a compute gallery.
4444

4545
To use the custom image while creating a dev box definition, attach the compute gallery to your dev center in Microsoft Dev Box. Follow these steps to [attach a compute gallery to a dev center](how-to-configure-azure-compute-gallery.md).
4646

47+
To use a custom image when creating a dev box definition, attach the compute gallery to your dev center in Microsoft Dev Box. See [attach a compute gallery to a dev center](how-to-configure-azure-compute-gallery.md).
48+
4749
## Image versions
4850

4951
When you select an image to use in your dev box definition, you must specify which version of the image you want to use:
5052

5153
- **Numbered image versions**: If you want a consistent dev box definition in which the base image doesn't change, use a specific, numbered version of the image. Using a numbered version ensures that all the dev boxes in the pool always use the same version of the image.
52-
- **Latest image versions**: If you want a flexible dev box definition in which you can update the base image as requirements change, use the latest version of the image. This choice ensures that new dev boxes use the most recent version of the image. Existing dev boxes aren't modified when an image version is updated.
54+
- **Latest image versions**: If you want a flexible dev box definition in which you can update the base image as requirements change, use the latest version of the image. This choice ensures that new dev boxes use the most recent version of the image. Existing dev boxes aren't modified when an image version is updated. Select the **Latest** image version to ensure the dev box pool uses the most recent version of your chosen image from the gallery. This approach keeps new dev boxes up to date with the latest tools and code.
5355

5456
## Create a dev box definition
5557

@@ -89,12 +91,11 @@ The following steps show you how to create a dev box definition by using an exis
8991
> [!NOTE]
9092
> Microsoft Dev Box doesn't support:
9193
> - Preview builds from the Windows Insider Program.
92-
> - Dev box definitions with 4 core SKUs.
93-
94+
> - Dev box definitions with 4-core SKUs.
9495
9596
## Update a dev box definition
9697

97-
Over time, your needs for dev boxes can change. You might want to move from a Windows 10 base operating system to a Windows 11 base operating system, or increase the default compute specification for your dev boxes. Your initial dev box definitions might no longer be appropriate for your needs. You can update a dev box definition so new dev boxes use the new configuration.
98+
Over time, your dev box needs might change. For example, you might switch from a Windows 10 base operating system to Windows 11 or increase the default compute specification. Your initial dev box definitions might no longer be appropriate for your needs. You can update a dev box definition so new dev boxes use the new configuration.
9899

99100
When you update the image used in a dev box definition, you must ensure that you have sufficient IP addresses available in your virtual network. Additional free IP addresses are necessary for the Azure Network connection health check. If the health check fails the dev box definition will not update. You need 1 additional IP address per dev box, and two IP addresses for the health check and Dev Box infrastructure.
100101

@@ -120,6 +121,8 @@ You can update the image, image version, compute, and storage settings for a dev
120121

121122
You can delete a dev box definition when you no longer want to use it. Deleting a dev box definition is permanent and can't be undone. Dev box definitions can't be deleted if one or more dev box pools are using them.
122123

124+
You can't delete dev box definitions if one or more dev box pools use them.
125+
123126
To delete a dev box definition in the Azure portal:
124127

125128
1. Sign in to the [Azure portal](https://portal.azure.com).

0 commit comments

Comments
 (0)