You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/dev-box/concept-dev-box-concepts.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -46,10 +46,10 @@ IT administrators and platform engineers configure the network that's used for d
46
46
47
47
When you're creating a network connection, you must choose the Active Directory join type:
48
48
49
-
- If your dev boxes need to connect exclusively to cloud-based resources, use native Azure Active Directory (Azure AD).
50
-
- If your dev boxes need to connect to on-premises resources and cloud-based resources, use hybrid Azure AD.
49
+
- If your dev boxes need to connect exclusively to cloud-based resources, use native Microsoft Entra ID.
50
+
- If your dev boxes need to connect to on-premises resources and cloud-based resources, use hybrid Microsoft Entra ID.
51
51
52
-
To learn more about native Azure AD join and hybrid Azure AD join, see [Plan your Azure Active Directory device deployment](../active-directory/devices/plan-device-deployment.md).
52
+
To learn more about native Microsoft Entra join and Microsoft Entra hybrid join, see [Plan your Microsoft Entra device deployment](../active-directory/devices/plan-device-deployment.md).
53
53
54
54
The virtual network specified in a network connection also determines the region for a dev box. You can create multiple network connections based on the regions where you support developers. You can then use those connections when you're creating dev box pools to ensure that dev box users create dev boxes in a region close to them. Using a region close to the dev box user provides the best experience.
Copy file name to clipboardExpand all lines: articles/dev-box/dev-box-faq.yml
+1-1
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ sections:
39
39
For more information, see: [Compute gallery image requirements](how-to-configure-azure-compute-gallery.md#compute-gallery-image-requirements).
40
40
41
41
- question: Why does it take 25 minutes or more to provision a dev box?
42
-
answer: The provisioning process for a dev box involves interacting with several services, including authenticating with Azure Active Directory (Azure AD). The new dev box must be created, initiate networking connectivity services, authenticate to and join the Azure AD, register with Intune, and check for any Azure AD security requirements. Depending on the complexity of the dev box definition, there might also be installation and configuration tasks on the dev box itself to provide you with the environment you need to start work. When your dev box is fully provisioned, it's running, ready for you to sign in.
42
+
answer: The provisioning process for a dev box involves interacting with several services, including authenticating with Microsoft Entra ID. The new dev box must be created, initiate networking connectivity services, authenticate to and join the Microsoft Entra ID, register with Intune, and check for any Microsoft Entra security requirements. Depending on the complexity of the dev box definition, there might also be installation and configuration tasks on the dev box itself to provide you with the environment you need to start work. When your dev box is fully provisioned, it's running, ready for you to sign in.
43
43
44
44
- question: How can I check my Dev Box quota? # Question.
Copy file name to clipboardExpand all lines: articles/dev-box/how-to-authenticate.md
+12-8
Original file line number
Diff line number
Diff line change
@@ -14,19 +14,21 @@ ms.date: 09/07/2023
14
14
> Before authenticating, ensure that the user or identity has the appropriate permissions to perform the desired action. For more information, see [configuring project admins](./how-to-project-admin.md) and [configuring Dev Box users](./how-to-dev-box-user.md).
Use the following procedures to authenticate with Azure AD. You can follow along in [Azure Cloud Shell](../../articles/cloud-shell/quickstart.md), on an Azure virtual machine, or on your local machine.
19
+
## Using Microsoft Entra authentication for REST APIs
20
+
21
+
Use the following procedures to authenticate with Microsoft Entra ID. You can follow along in [Azure Cloud Shell](../../articles/cloud-shell/quickstart.md), on an Azure virtual machine, or on your local machine.
20
22
21
23
### Sign in to the user's Azure subscription
22
24
23
-
Start by authenticating with Azure AD by using the Azure CLI. This step isn't required in Azure Cloud Shell.
25
+
Start by authenticating with Microsoft Entra ID by using the Azure CLI. This step isn't required in Azure Cloud Shell.
24
26
25
27
```azurecli
26
28
az login
27
29
```
28
30
29
-
The command opens a browser window to the Azure AD authentication page. It requires you to give your Azure AD user ID and password.
31
+
The command opens a browser window to the Microsoft Entra authentication page. It requires you to give your Microsoft Entra user ID and password.
30
32
31
33
Next, set the correct subscription context. If you authenticate from an incorrect subscription or tenant you may receive unexpected 403 Forbidden errors.
32
34
@@ -35,9 +37,11 @@ az account set --subscription <subscription_id>
35
37
```
36
38
37
39
38
-
### Retrieve the Azure AD access token
40
+
<aname='retrieve-the-azure-ad-access-token'></a>
41
+
42
+
### Retrieve the Microsoft Entra access token
39
43
40
-
Use the Azure CLI to acquire an access token for the Azure AD authenticated user.
44
+
Use the Azure CLI to acquire an access token for the Microsoft Entra authenticated user.
41
45
Note that the resource ID is different depending on if you are accessing administrator (control plane) APIs or developer (data plane) APIs.
42
46
43
47
For administrator APIs, use the following command:
@@ -50,7 +54,7 @@ For developer APIs, use the following command:
50
54
az account get-access-token --resource https://devcenter.azure.com
51
55
```
52
56
53
-
After authentication is successful, Azure AD returns an access token for current Azure subscription:
57
+
After authentication is successful, Microsoft Entra ID returns an access token for current Azure subscription:
54
58
55
59
```json
56
60
{
@@ -72,4 +76,4 @@ The token is a Base64 string. The token is valid for at least 5 minutes with the
72
76
To access REST APIs, you must set the Authorization header on your request. The header value should be the string `Bearer` followed by a space and the token you received in the previous step.
73
77
74
78
## Next steps
75
-
- Review [Azure Active Directory fundamentals](../../articles/active-directory/fundamentals/whatis.md).
Copy file name to clipboardExpand all lines: articles/dev-box/how-to-configure-network-connections.md
+16-12
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ When you're planning network connectivity for your dev boxes, you must:
20
20
- Ensure that you have sufficient permissions to create and configure network connections.
21
21
- Ensure that you have at least one virtual network and subnet available for your dev boxes.
22
22
- Identify the region or location that's closest to your dev box users. Deploying dev boxes into a region that's close to users gives them a better experience.
23
-
- Determine whether dev boxes should connect to your existing networks by using Azure Active Directory (Azure AD) join or hybrid Azure AD join.
23
+
- Determine whether dev boxes should connect to your existing networks by using Microsoft Entra join or Microsoft Entra hybrid join.
24
24
25
25
## Permissions
26
26
@@ -78,20 +78,22 @@ The following sections show you how to create and configure a network connection
78
78
79
79
The Dev Box service requires a configured and working Active Directory join, which defines how dev boxes join your domain and access resources. There are two choices:
80
80
81
-
-**Azure AD join**: If your organization uses Azure AD, you can use an Azure AD join (sometimes called a native Azure AD join). Dev box users sign in to Azure AD-joined dev boxes by using their Azure AD account and access resources based on the permissions assigned to that account. Azure AD join enables access to cloud-based and on-premises apps and resources.
81
+
-**Microsoft Entra join**: If your organization uses Microsoft Entra ID, you can use a Microsoft Entra join (sometimes called a native Microsoft Entra join). Dev box users sign in to Microsoft Entra joined dev boxes by using their Microsoft Entra account and access resources based on the permissions assigned to that account. Microsoft Entra join enables access to cloud-based and on-premises apps and resources.
82
82
83
-
For more information, see [Plan your Azure Active Directory join deployment](../active-directory/devices/device-join-plan.md).
84
-
-**Hybrid Azure AD join**: If your organization has an on-premises Active Directory implementation, you can still benefit from some of the functionality in Azure AD by using hybrid Azure AD-joined dev boxes. These dev boxes are joined to your on-premises Active Directory instance and registered with Azure AD.
83
+
For more information, see [Plan your Microsoft Entra join deployment](../active-directory/devices/device-join-plan.md).
84
+
-**Microsoft Entra hybrid join**: If your organization has an on-premises Active Directory implementation, you can still benefit from some of the functionality in Microsoft Entra ID by using Microsoft Entra hybrid joined dev boxes. These dev boxes are joined to your on-premises Active Directory instance and registered with Microsoft Entra ID.
85
85
86
-
Hybrid Azure AD-joined dev boxes require network line of sight to your on-premises domain controllers periodically. Without this connection, devices become unusable.
86
+
Microsoft Entra hybrid joined dev boxes require network line of sight to your on-premises domain controllers periodically. Without this connection, devices become unusable.
87
87
88
-
For more information, see [Plan your hybrid Azure Active Directory join deployment](../active-directory/devices/hybrid-join-plan.md).
88
+
For more information, see [Plan your Microsoft Entra hybrid join deployment](../active-directory/devices/hybrid-join-plan.md).
89
89
90
90
### Create a network connection
91
91
92
92
Follow the steps on the relevant tab to create your network connection.
|**Subscription**|Select the subscription in which you want to create the network connection.|
110
112
|**ResourceGroup**|Select an existing resource group, or select **Create new** and then enter a name for the new resource group.|
111
113
|**Name**|Enter a descriptive name for the network connection.|
112
114
|**Virtual network**|Select the virtual network that you want the network connection to use.|
113
115
|**Subnet**|Select the subnet that you want the network connection to use.|
114
116
115
-
:::image type="content" source="./media/how-to-manage-network-connection/create-native-network-connection-full-blank.png" alt-text="Screenshot that shows the Basics tab on the pane for creating a network connection, with the option for Azure Active Directory join selected.":::
117
+
:::image type="content" source="./media/how-to-manage-network-connection/create-native-network-connection-full-blank.png" alt-text="Screenshot that shows the Basics tab on the pane for creating a network connection, with the option for Microsoft Entra join selected.":::
116
118
117
119
1. Select **Review + Create**.
118
120
119
121
1. On the **Review** tab, select **Create**.
120
122
121
123
1. When the deployment is complete, select **Go to resource**. Confirm that the connection appears on the **Network connections** page.
122
124
123
-
#### [**Hybrid Azure AD join**](#tab/HybridAzureADJoin/)
|**Subscription**|Select the subscription in which you want to create the network connection.|
139
143
|**ResourceGroup**|Select an existing resource group, or select **Create new** and then enter a name for the new resource group.|
140
144
|**Name**|Enter a descriptive name for the network connection.|
@@ -145,7 +149,7 @@ Follow the steps on the relevant tab to create your network connection.
145
149
|**AD username UPN**| Enter the username, in user principal name (UPN) format, that you want to use for connecting Cloud PCs to your Active Directory domain. For example: `svcDomainJoin@corp.contoso.com`. This service account must have permission to join computers to the domain and the target OU (if one is set). |
146
150
|**AD domain password**| Enter the password for the user. |
147
151
148
-
:::image type="content" source="./media/how-to-manage-network-connection/create-hybrid-network-connection-full-blank.png" alt-text="Screenshot that shows the Basics tab on the pane for creating a network connection, with the option for hybrid Azure Active Directory join selected.":::
152
+
:::image type="content" source="./media/how-to-manage-network-connection/create-hybrid-network-connection-full-blank.png" alt-text="Screenshot that shows the Basics tab on the pane for creating a network connection, with the option for Microsoft Entra hybrid join selected.":::
Copy file name to clipboardExpand all lines: articles/dev-box/overview-what-is-microsoft-dev-box.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -46,8 +46,8 @@ Dev Box has the following benefits for IT admins:
46
46
- Dev boxes automatically enroll in Intune. Use the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) to manage dev boxes.
47
47
- Keep all Windows devices up to date by using expedited quality updates in Intune to deploy zero-day patches across your organization.
48
48
- If a dev box is compromised, isolate it while helping users get backup and running on a new dev box.
49
-
- Dev Box provides secure access in a secure environment. Access controls in Azure Active Directory (Azure AD) organize access by project or user type:
50
-
- Join dev boxes natively to an Azure AD or Active Directory domain.
49
+
- Dev Box provides secure access in a secure environment. Access controls in Microsoft Entra ID organize access by project or user type:
50
+
- Join dev boxes natively to a Microsoft Entra ID or Active Directory domain.
51
51
- Set conditional access policies that require users to connect via a compliant device.
52
52
- Require multifactor authentication at sign-in.
53
53
- Configure risk-based sign-in policies for dev boxes that access sensitive source code and customer data.
@@ -75,7 +75,7 @@ This diagram shows the components of the Dev Box service and the relationships b
75
75
76
76
Dev Box service configuration begins with the creation of a dev center, which represents the units of organization in the enterprise. Dev centers are logical containers to help organize dev box resources. There's no limit on the number of dev centers that you can create, but most organizations need only one.
77
77
78
-
Azure network connections enable dev boxes to communicate with your organization's network. The network connection provides a link between the dev center and your organization's virtual networks. In the network connection, you define how a dev box joins Azure AD. Use an Azure AD join to connect exclusively to cloud-based resources, or use a hybrid Azure AD join to connect to on-premises resources and cloud-based resources.
78
+
Azure network connections enable dev boxes to communicate with your organization's network. The network connection provides a link between the dev center and your organization's virtual networks. In the network connection, you define how a dev box joins Microsoft Entra ID. Use a Microsoft Entra join to connect exclusively to cloud-based resources, or use a Microsoft Entra hybrid join to connect to on-premises resources and cloud-based resources.
79
79
80
80
Dev box definitions define the configuration of the dev boxes that are available to users. You can use an image from Azure Marketplace, like the **Visual Studio 2022 Enterprise on Windows 11 Enterprise + Microsoft 365 Apps 22H2** image. Or you can create your own custom image and store it in Azure Compute Gallery. Specify a SKU with compute and storage to complete the dev box definition.
0 commit comments