Skip to content

Commit 38343d7

Browse files
Merge pull request #314218 from MicrosoftDocs/main
Auto Publish – main to live - 2026-04-03 06:00 UTC
2 parents 560f942 + ee2e04c commit 38343d7

32 files changed

Lines changed: 537 additions & 179 deletions
Lines changed: 160 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,160 @@
1+
---
2+
title: Enable guest user access to dev boxes
3+
titleSuffix: Microsoft Dev Box
4+
description: Learn how to configure Microsoft Dev Box so that guest users from other Microsoft Entra tenants can create and connect to dev boxes.
5+
ms.service: dev-box
6+
ms.topic: how-to
7+
ms.custom: public-preview, awp-ai
8+
ai-usage: ai-assisted
9+
author: RoseHJM
10+
ms.author: rosemalcolm
11+
ms.date: 04/01/2026
12+
13+
#Customer intent: As a platform engineer, I want to enable guest user access so that external collaborators from other tenants can use dev boxes in my projects.
14+
---
15+
16+
# Enable guest user access to dev boxes (preview)
17+
18+
In this article, you learn how to configure Microsoft Dev Box so that guest users from other Microsoft Entra tenants can create and connect to dev boxes. Guest user access uses Microsoft Entra B2B collaboration to invite external users into your tenant and assign them Dev Box roles.
19+
20+
For example, if your organization works with external contractors or partner teams who have their own Microsoft Entra tenants, you can invite them as guest users and give them access to dev boxes in your projects.
21+
22+
> [!IMPORTANT]
23+
> Guest user access for Microsoft Dev Box is currently in preview.
24+
> 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.
25+
26+
## Prerequisites
27+
28+
Before you begin, make sure you have the following prerequisites in place:
29+
30+
- An Azure account with an active subscription.
31+
- A [dev center with at least one project](quickstart-configure-dev-box-service.md) configured in Microsoft Dev Box.
32+
- Permission to [invite guest users](/entra/external-id/add-users-administrator) in your Microsoft Entra tenant.
33+
- An [image definition](how-to-configure-team-customizations.md) that uses a **Windows 11 Enterprise, version 24H2 or later** base image with the **2025-09 Cumulative Update for Windows 11 (KB5065789)** or later installed.
34+
- A dev box pool with [single sign-on (SSO) enabled](how-to-enable-single-sign-on.md). SSO is required for guest user access.
35+
36+
## Register for the preview
37+
38+
During the public preview, you must provide your tenant ID and dev center ID to Microsoft to enable guest user access.
39+
40+
### Find your tenant ID
41+
42+
1. Sign in to the [Azure portal](https://portal.azure.com).
43+
44+
1. In the search box, enter **Tenant properties**. In the list of results, select **Tenant properties**.
45+
46+
1. On the **Tenant properties** page, find the **Tenant ID** field and copy the value.
47+
48+
### Find your dev center resource ID
49+
50+
1. In the Azure portal, in the search box, enter **Dev centers**. In the list of results, select **Dev centers**.
51+
52+
1. Select the dev center that you want to use for guest user access.
53+
54+
1. On the dev center's **Overview** page, select **Properties**.
55+
56+
1. Find the **Resource ID** field and copy the value.
57+
58+
### Submit your details to Microsoft
59+
60+
Contact your Microsoft support representative to submit your tenant ID and dev center resource ID and request that guest user access be enabled for your dev center. You can submit a support ticket to contact your representative. For more information about creating support requests, see: [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request).
61+
62+
After Microsoft confirms that your tenant is enabled, you can proceed with the remaining steps.
63+
64+
## Create an image definition with a supported image
65+
66+
Guest user access requires an image definition that uses a Windows 11 Enterprise base image, version 24H2 or later, with specific cumulative updates installed.
67+
68+
1. Create or update an image definition with a base image that meets these requirements:
69+
70+
| Requirement | Value |
71+
|---|---|
72+
| **Operating system** | Windows 11 Enterprise |
73+
| **Version** | 24H2 or later |
74+
| **Cumulative update** | 2025-09 Cumulative Update for Windows 11 (KB5065789) or later |
75+
76+
1. Verify that the base image in your image definition includes the required update. You can use a marketplace image that already includes the update, or prepare a custom image. For more information on creating image definitions, see [Configure team customizations](how-to-configure-team-customizations.md).
77+
78+
## Create a pool with SSO enabled
79+
80+
Guest user access requires single sign-on (SSO) to be enabled on the dev box pool.
81+
82+
1. Create a new dev box pool or update an existing pool to enable SSO. For the detailed steps, see [Enable single sign-on for dev boxes](how-to-enable-single-sign-on.md).
83+
84+
1. Assign the image definition with the supported image to the pool.
85+
86+
After you enable SSO on the pool, new dev boxes created from the pool support guest user access.
87+
88+
## Invite guest users and assign roles
89+
90+
To give external users access to dev boxes, first invite them as guest users in your Microsoft Entra tenant, and then assign them the Dev Box User role on the project.
91+
92+
1. Invite external users as guests in your Microsoft Entra tenant. For detailed steps, see [Add B2B collaboration users in the Azure portal](/entra/external-id/add-users-administrator).
93+
94+
1. After the guest users accept the invitation and appear in your directory, assign them the **DevCenter Dev Box User** role at the project level. For detailed steps, see [Configure access to Microsoft Dev Box projects](how-to-manage-dev-box-access.md).
95+
96+
After you assign the role, guest users can create dev boxes from the pools in that project.
97+
98+
> [!NOTE]
99+
> If the guest user's dev box was recently created, it can take up to 30 minutes before the dev box appears in the developer portal or Windows App.
100+
101+
## Connect to a dev box as a guest user
102+
103+
Guest users can connect to their dev boxes by using the Windows App or the developer portal. Because the dev box is in a different tenant from the guest user's home tenant, the guest user must switch to the resource tenant before connecting.
104+
105+
### Connect by using the Windows App
106+
107+
To connect to a dev box in a resource tenant by using the Windows App:
108+
109+
1. Make sure you have Windows App version **2.0.804.0 or later** installed. [Download Windows App](https://apps.microsoft.com/detail/9n1f85v9t8bn?hl=en-us&gl=US).
110+
111+
1. Open Windows App. On the sign-in or account picker window, select **Use another account**.
112+
113+
1. Select **Sign-in Options** > **Sign in to an organization**.
114+
115+
1. Enter the domain name of the resource tenant. To find your domain name, in the Azure portal, search for **Domain names** under Microsoft Entra ID.
116+
117+
1. Follow the sign-in prompts to complete authentication.
118+
119+
1. After you sign in, select the **Profile** icon and select the target tenant.
120+
121+
1. Find your dev box in the list. The dev box might appear as a Windows 365 device.
122+
123+
1. Select **Connect** to connect to the dev box.
124+
125+
### Connect by using the developer portal
126+
127+
To connect to a dev box in a resource tenant by using the developer portal:
128+
129+
1. Go to the [Microsoft Dev Box developer portal](https://aka.ms/devbox-portal).
130+
131+
1. In the upper right corner, select the **tenant arrow** next to your account name.
132+
133+
1. Select the tenant in which you're a guest.
134+
135+
1. Find your dev box and select **Connect**.
136+
137+
## Limitations
138+
139+
The following limitations apply during the public preview:
140+
141+
- You must register your tenant and dev center with Microsoft before you can use guest user access.
142+
- The image definition must use a Windows 11 Enterprise 24H2 or later base image with the 2025-09 Cumulative Update (KB5065789) or later.
143+
- SSO must be enabled on the pool.
144+
- Windows App version 2.0.804.0 or later is required for connecting through the Windows App.
145+
146+
## Troubleshooting
147+
148+
| Issue | Resolution |
149+
|---|---|
150+
| Dev box doesn't appear in the developer portal or Windows App after creation. | Wait up to 30 minutes for the dev box to become visible. |
151+
| Can't connect to the dev box. | Verify that SSO is enabled on the pool and that the image definition uses a supported base image. |
152+
| Sign-in fails in Windows App. | Make sure you're using Windows App version 2.0.804.0 or later. Use the **Sign in to an organization** flow and enter the correct domain name. |
153+
| Guest user can't see the project or pools. | Confirm the user was invited as a guest in the tenant and assigned the **DevCenter Dev Box User** role at the project level. |
154+
155+
## Related content
156+
157+
- [Configure access to Microsoft Dev Box projects](how-to-manage-dev-box-access.md)
158+
- [Enable single sign-on for dev boxes](how-to-enable-single-sign-on.md)
159+
- [Configure team customizations](how-to-configure-team-customizations.md)
160+
- [Add B2B collaboration users in the Azure portal](/entra/external-id/add-users-administrator)

articles/dev-box/how-to-enable-single-sign-on.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,9 @@ By using SSO, you can skip the credential prompt when you connect to a dev box a
2222

2323
To enable SSO for dev boxes, you must configure SSO for your organization. For more information, see [Configure single sign-on for Azure Virtual Desktop by using Microsoft Entra ID](/azure/virtual-desktop/configure-single-sign-on) authentication.
2424

25+
> [!NOTE]
26+
> SSO is required if you want to enable guest user access to dev boxes. For more information, see [Enable guest user access to dev boxes](how-to-enable-guest-access.md).
27+
2528
## Enable SSO for dev boxes
2629

2730
SSO is enabled at the pool level. Dev Box supports SSO for dev box pools that use Microsoft Entra joined networks, and Microsoft hosted networks, but not pools that use Microsoft Entra hybrid-joined networks.

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,9 @@ Users can now view the project and all pools within it. Dev box users can create
114114
[!INCLUDE [dev box runs on creation note](./includes/note-dev-box-runs-on-creation.md)]
115115

116116

117+
> [!TIP]
118+
> To grant access to users from other Microsoft Entra tenants, see [Enable guest user access to dev boxes](how-to-enable-guest-access.md).
119+
117120
## Troubleshooting
118121

119122
- Role assignment propagation can take a minute; refresh the portal and wait a short time before retrying.
Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
author: RoseHJM
33
ms.author: rosemalcolm
4-
ms.date: 04/25/2023
4+
ms.date: 04/01/2026
55
ms.topic: include
66
ms.service: dev-box
77
---
88

99
> [!NOTE]
10-
> Microsoft Dev Box supports work and school accounts. It doesn't support the use of guest accounts or personal accounts.
10+
> Microsoft Dev Box supports work and school accounts and guest accounts (preview). It doesn't support the use of personal accounts. For more information about configuring guest access, see [Enable guest user access to dev boxes](../how-to-enable-guest-access.md).

articles/dev-box/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -137,6 +137,8 @@ landingContent:
137137
linkLists:
138138
- linkListType: how-to-guide
139139
links:
140+
- text: Enable guest user access (preview)
141+
url: how-to-enable-guest-access.md
140142
- text: Configure conditional access policies
141143
url: how-to-configure-intune-conditional-access-policies.md
142144
- text: Enable single sign-on for dev box

articles/dev-box/toc.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,9 @@ items:
128128
- name: Manage project access
129129
href: how-to-manage-dev-box-access.md
130130
displayName: project access, RBAC, roles, permissions
131+
- name: Enable guest user access
132+
href: how-to-enable-guest-access.md
133+
displayName: guest, external users, cross-tenant, B2B, preview
131134
- name: Configure conditional access policies
132135
href: how-to-configure-intune-conditional-access-policies.md
133136
- name: Configure elevated privilege for dev boxes

articles/iot-operations/connect-to-cloud/concept-dataflow-graphs.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: sethm
66
ms.service: azure-iot-operations
77
ms.subservice: azure-data-flows
88
ms.topic: concept-article
9-
ms.date: 03/13/2026
9+
ms.date: 04/02/2026
1010
ai-usage: ai-assisted
1111

1212
---
@@ -27,9 +27,9 @@ Azure IoT Operations provides two ways to process data in a pipeline:
2727
| Capability | Data flows | Data flow graphs |
2828
|-----------|-----------|-----------------|
2929
| Pipeline shape | Fixed: enrich, filter, map | Flexible: any order, branching, merging |
30-
| Transform types | Map, filter, enrich | Map, filter, branch, concat, window, enrich |
30+
| Transform types | Map, filter, enrich | Map, filter, branch, concatenate, window, enrich |
3131
| Time-based aggregation | Not available | Window transforms with tumbling windows |
32-
| Conditional routing | Not available | Branch and concat transforms |
32+
| Conditional routing | Not available | Branch and concatenate transforms |
3333
| Endpoint support | All endpoint types | MQTT, Kafka, and OpenTelemetry only |
3434

3535
For new projects that use supported endpoint types, we recommend data flow graphs. Data flows remain fully supported for all scenarios, and they support the full range of endpoint types.
@@ -43,7 +43,7 @@ Each transform is a pre-built processing step that you configure with rules and
4343
| **Map** | Rename, restructure, compute, and copy fields | [Transform data with map](howto-dataflow-graphs-map.md) |
4444
| **Filter** | Drop messages that match a condition | [Filter and route data](howto-dataflow-graphs-filter-route.md) |
4545
| **Branch** | Route each message to a `true` or `false` path based on a condition | [Filter and route data](howto-dataflow-graphs-filter-route.md#branch-transform) |
46-
| **Concat** | Merge two or more paths back into one | [Filter and route data](howto-dataflow-graphs-filter-route.md#merge-paths-with-concat) |
46+
| **Concatenate** | Merge two or more paths back into one | [Filter and route data](howto-dataflow-graphs-filter-route.md#merge-paths-with-concatenate) |
4747
| **Window** | Collect messages over a time interval, then aggregate | [Aggregate data over time](howto-dataflow-graphs-window.md) |
4848

4949
All transforms share an [expression language](concept-dataflow-graphs-expressions.md) for operators, functions, and field references. You can also [enrich](howto-dataflow-graphs-enrich.md) messages with external data from a state store in map, filter, and branch transforms.
@@ -52,7 +52,7 @@ All transforms share an [expression language](concept-dataflow-graphs-expression
5252

5353
Transforms connect in sequence inside a `DataflowGraph` resource: **Source > Transform A > Transform B > … > Destination**.
5454

55-
Branch transforms split the flow into parallel paths, and concat transforms merge them back.
55+
Branch transforms split the flow into parallel paths, and concatenate transforms merge them back.
5656

5757
You can chain any number of transforms in any order. A pipeline with a single map transform is as valid as one that filters, branches, maps each path differently, merges, and then aggregates over a time window.
5858

@@ -84,7 +84,6 @@ resource dataflowGraph 'Microsoft.IoTOperations/instances/dataflowProfiles/dataf
8484
name: 'temperature-conversion'
8585
parent: dataflowProfile
8686
properties: {
87-
profileRef: dataflowProfileName
8887
mode: 'Enabled'
8988
nodes: [
9089
{
@@ -187,7 +186,7 @@ In the how-to articles that follow, examples focus on the transform rules themse
187186

188187
Data flow graphs support two kinds of transforms:
189188

190-
- **Built-in transforms** are pre-built by Microsoft (map, filter, branch, concat, window). You configure them with rules. No coding required.
189+
- **Built-in transforms** are pre-built by Microsoft (map, filter, branch, concatenate, window). You configure them with rules. No coding required.
191190
- **WASM transforms** are custom WebAssembly modules that developers build and deploy. Use them when you need logic that the built-in transforms don't cover.
192191

193192
Both kinds of transforms run inside the same `DataflowGraph` resource and can be mixed in a single pipeline. For information on building and deploying custom transforms, see [Use WASM transforms in data flow graphs](howto-dataflow-graph-wasm.md).

articles/iot-operations/connect-to-cloud/howto-create-dataflow-graph.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: sethm
66
ms.service: azure-iot-operations
77
ms.subservice: azure-data-flows
88
ms.topic: how-to
9-
ms.date: 03/19/2026
9+
ms.date: 04/02/2026
1010
ai-usage: ai-assisted
1111

1212
#CustomerIntent: As an operator, I want to create a data flow graph to process data with transforms like map, filter, and window.
@@ -49,7 +49,7 @@ A data flow graph contains three types of elements: **sources** that bring data
4949

5050
:::image type="content" source="media/howto-create-dataflow-graph/source-configuration.png" alt-text="Screenshot of the operations experience source configuration panel showing endpoint dropdown and topic input." lightbox="media/howto-create-dataflow-graph/source-configuration.png":::
5151

52-
1. **Add transforms**: Select one or more transforms to process the data. Available transforms include map, filter, branch, concat, and window. For details on each transform type, see [Data flow graphs overview](concept-dataflow-graphs.md#available-transforms).
52+
1. **Add transforms**: Select one or more transforms to process the data. Available transforms include map, filter, branch, concatenate, and window. For details on each transform type, see [Data flow graphs overview](concept-dataflow-graphs.md#available-transforms).
5353

5454
:::image type="content" source="media/howto-create-dataflow-graph/transform-selection.png" alt-text="Screenshot of the operations experience transform selection menu showing available transform types." lightbox="media/howto-create-dataflow-graph/transform-selection.png":::
5555

@@ -275,7 +275,7 @@ The available built-in transforms are:
275275
| Map | `azureiotoperations/graph-dataflow-map:1.0.0` | Rename, restructure, compute, and copy fields |
276276
| Filter | `azureiotoperations/graph-dataflow-filter:1.0.0` | Drop messages that match a condition |
277277
| Branch | `azureiotoperations/graph-dataflow-branch:1.0.0` | Route messages to a `true` or `false` path |
278-
| Concat | `azureiotoperations/graph-dataflow-concatenate:1.0.0` | Merge branched paths back together |
278+
| Concatenate | `azureiotoperations/graph-dataflow-concatenate:1.0.0` | Merge branched paths back together |
279279
| Window | `azureiotoperations/graph-dataflow-window:1.0.0` | Aggregate data over a time interval |
280280

281281
For detailed configuration of each transform type, see:

articles/iot-operations/connect-to-cloud/howto-dataflow-graphs-enrich.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: sethm
66
ms.service: azure-iot-operations
77
ms.subservice: azure-data-flows
88
ms.topic: how-to
9-
ms.date: 03/19/2026
9+
ms.date: 04/02/2026
1010
ai-usage: ai-assisted
1111

1212
---
@@ -274,7 +274,6 @@ resource dataflowGraph 'Microsoft.IoTOperations/instances/dataflowProfiles/dataf
274274
name: 'enrich-example'
275275
parent: dataflowProfile
276276
properties: {
277-
profileRef: dataflowProfileName
278277
mode: 'Enabled'
279278
nodes: [
280279
{

0 commit comments

Comments
 (0)