Skip to content

Commit 33a1f28

Browse files
authored
Update dev-box-faq.yml
1 parent b1c1596 commit 33a1f28

File tree

1 file changed

+1
-40
lines changed

1 file changed

+1
-40
lines changed

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

Lines changed: 1 addition & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ metadata:
66
ms.author: rosemalcolm
77
ms.service: dev-box
88
ms.topic: faq
9-
ms.date: 05/16/2023
9+
ms.date: 01/16/2024
1010
title: "Microsoft Dev Box: Frequently asked questions"
1111
summary: This article provides answers to some of the most commonly asked questions about [Microsoft Dev Box](https://azure.microsoft.com/services/dev-box/).
1212

@@ -85,46 +85,7 @@ sections:
8585

8686
- question: Is there a policy or a feature to prevent users copying data or code from the Dev Box to their laptop using the clipboard?
8787
answer: You can prevent users copying data or code from the Dev Box to their local machine by disabling the clipboard redirection feature in the RDP client. You can manage this setting through a device configuration policy in Microsoft Intune. For more information, see [RDP device redirection settings](/windows-365/enterprise/manage-rdp-device-redirections#rdp-device-redirection-settings).
88-
89-
- name: Dev Box quota
90-
questions:
91-
- question: What is quota?
92-
answer: |
93-
To ensure that resources are available for customers, Microsoft Dev Box has a limit on the number of each type of resource that can be used in a subscription. This limit is called a quota.
94-
There are different types of quota that you can encounter in the Developer portal and Azure portal, such as quota for:
95-
- Dev Box vCPU (This is a quota error you'll encounter in devportal.microsoft.com during dev box creation)
96-
97-
Or, for Azure portal resource limits:
98-
- Dev Centers
99-
- Network connections
100-
- Dev Box Definitions
101-
102-
- question: What should I do if I hit a vCPU quota error?
103-
answer: |
104-
If you are in the developer portal, you might see a *QuotaExceeded* error during dev box creation.
105-
If you see this error, contact your administrator for assistance to increase this quota. You can point them to the documentation on [requesting a quota limit](/azure/dev-box/how-to-request-quota-increase).
106-
If your admin can't increase the quota limit at this time, try selecting another pool with a region close to your location.
107-
108-
- question: How can I check my Dev Box quota?
109-
answer: |
110-
You can check your Dev Box quota using either:
111-
- REST API - [Usages - List By Location - REST API (Azure Dev Center) | Microsoft Learn](/rest/api/devcenter/administrator/usages/list-by-location?tabs=HTTP)
112-
- CLI - [az devcenter admin usage | Microsoft Learn |](/cli/azure/devcenter/admin/usage?view=azure-cli-latest)
113-
114-
- name: Dev Box hibernation
115-
questions:
116-
- question: Can I use auto-stop schedules to hibernate Dev Boxes on a schedule? # Question.
117-
answer:
118-
The ability to use auto-stop schedules to initiate hibernation is in Preview.
119-
120-
- question: I enabled hibernation on a Dev Box definition, but my Dev Box definition reports that hibernation couldn't be enabled. # Question.
121-
answer: |
122-
- We recommend using the Visual Studio for Dev Box marketplace images, either directly, or as base images for generating your custom image.
123-
- The Windows + OS optimizations image contains optimized power settings, and they can't be used with hibernation.
124-
- 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.
125-
- 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.
12688

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

12990
additionalContent: |
13091
## Related content

0 commit comments

Comments
 (0)