Merge pull request #295837 from stevenmatthew/dbxV2030525

dbxV2030525: DBX V2 updates

Author: ttorble

.openpublishing.redirection.json

@@ -3364,6 +3364,16 @@
       "redirect_url": "/azure/databox/data-box-quickstart-export?pivots=dbx-ng",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/databox/data-box-next-gen-safety.md",
+      "redirect_url": "/azure/databox/data-box-safety?pivots=dbx-ng",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/databox/data-box-next-gen-security.md",
+      "redirect_url": "/azure/databox/data-box-security?pivots=dbx-ng",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/ddos-protection/ddos-disaster-recovery-guidance.md",
       "redirect_url": "../reliability/reliability-ddos.md",

articles/azure-signalr/includes/signalr-add-role-assignments.md

@@ -1,62 +1,62 @@
----
-title: include file
-description: include file
-author: terencefan
-ms.service: azure-signalr-service
-ms.topic: include
-ms.date: 03/12/2025
-ms.author: tefa
-ms.custom: include file
----
-
-The following steps describe how to assign a **SignalR App Server** role to a service principal or a managed identity for an Azure SignalR Service resource. For detailed steps, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml).
-
-> [!NOTE]
-> A role can be assigned to any scope, including management group, subscription, resource group, or single resource. To learn more about scope, see [Understand scope for Azure RBAC](../../role-based-access-control/scope-overview.md).
-
-1. In the [Azure portal](https://portal.azure.com/), go to your Azure SignalR Service resource.
-
-1. Select **Access control (IAM)** in the sidebar.
-
-1. Select **Add** > **Add role assignment**.
-
-   :::image type="content" source="~/reusable-content/ce-skilling/azure/media/role-based-access-control/add-role-assignment-menu-generic.png" alt-text="Screenshot that shows the page for access control and selections for adding a role assignment.":::
-
-1. On the **Role** tab, select **SignalR App Server** or other SignalR built-in roles depends on your scenario.
-
-   | Role                                                                                              | Description                                                                                               | Use case                                                                                                                                     |
-   | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
-   | [SignalR App Server](../../role-based-access-control/built-in-roles.md#signalr-app-server)           | Access to the server connection creation and key generation APIs.                                                | Most commonly used for app server with Azure SignalR resource run in **Default** mode.                                                                                                             |
-   | [SignalR Service Owner](../../role-based-access-control/built-in-roles.md#signalr-service-owner)     | Full access to all data-plane APIs, including REST APIs, the server connection creation, and key/token generation APIs. | For negotiation server with Azure SignalR resource run in **Serverless** mode, as it requires both REST API permissions and authentication API permissions. |
-   | [SignalR REST API Owner](../../role-based-access-control/built-in-roles.md#signalr-rest-api-owner)   | Full access to data-plane REST APIs.                                                                      | For using [Azure SignalR Management SDK](/azure/azure-signalr/signalr-howto-use-management-sdk) to manage connections and groups, but does **NOT** make server connections or handle negotiation requests.                          |
-   | [SignalR REST API Reader](../../role-based-access-control/built-in-roles.md#signalr-rest-api-reader) | Read-only access to data-plane REST APIs.                                                                 | Use it when write a monitoring tool that calls readonly REST APIs.                                      |
-
-1. Select Next.
-
-
-1. For Microsoft Entra application.
-
-
-   1. In the `Assign access` to row, select **User, group, or service principal**.
-   1. In the `Members` row, click `select members`, then choose the identity in the pop-up window.
-
-1. For managed identity for Azure resources.
-
-   1. In the `Assign access` to row, select **Managed identity**.
-   1. In the `Members` row, click `select members`, then choose the application in the pop-up window.
-
-1. Select Next.
-
-
-1. Review your assignment, then click **Review + assign** to confirm the role assignment.
-
-> [!IMPORTANT]
-> Newly added role assignments might take up to 30 minutes to propagate.
-
-To learn more about how to assign and manage Azure roles, see these articles:
-
-- [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml)
-- [Assign Azure roles using the REST API](../../role-based-access-control/role-assignments-rest.md)
-- [Assign Azure roles using Azure PowerShell](../../role-based-access-control/role-assignments-powershell.md)
-- [Assign Azure roles using the Azure CLI](../../role-based-access-control/role-assignments-cli.md)
+---
+title: include file
+description: include file
+author: terencefan
+ms.service: azure-signalr-service
+ms.topic: include
+ms.date: 03/12/2025
+ms.author: tefa
+ms.custom: include file
+---
+
+The following steps describe how to assign a **SignalR App Server** role to a service principal or a managed identity for an Azure SignalR Service resource. For detailed steps, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml).
+
+> [!NOTE]
+> A role can be assigned to any scope, including management group, subscription, resource group, or single resource. To learn more about scope, see [Understand scope for Azure RBAC](../../role-based-access-control/scope-overview.md).
+
+1. In the [Azure portal](https://portal.azure.com/), go to your Azure SignalR Service resource.
+
+1. Select **Access control (IAM)** in the sidebar.
+
+1. Select **Add** > **Add role assignment**.
+
+   :::image type="content" source="~/reusable-content/ce-skilling/azure/media/role-based-access-control/add-role-assignment-menu-generic.png" alt-text="Screenshot that shows the page for access control and selections for adding a role assignment.":::
+
+1. On the **Role** tab, select **SignalR App Server** or other SignalR built-in roles depends on your scenario.
+
+   | Role                                                                                              | Description                                                                                               | Use case                                                                                                                                     |
+   | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+   | [SignalR App Server](../../role-based-access-control/built-in-roles.md#signalr-app-server)           | Access to the server connection creation and key generation APIs.                                                | Most commonly used for app server with Azure SignalR resource run in **Default** mode.                                                                                                             |
+   | [SignalR Service Owner](../../role-based-access-control/built-in-roles.md#signalr-service-owner)     | Full access to all data-plane APIs, including REST APIs, the server connection creation, and key/token generation APIs. | For negotiation server with Azure SignalR resource run in **Serverless** mode, as it requires both REST API permissions and authentication API permissions. |
+   | [SignalR REST API Owner](../../role-based-access-control/built-in-roles.md#signalr-rest-api-owner)   | Full access to data-plane REST APIs.                                                                      | For using [Azure SignalR Management SDK](/azure/azure-signalr/signalr-howto-use-management-sdk) to manage connections and groups, but does **NOT** make server connections or handle negotiation requests.                          |
+   | [SignalR REST API Reader](../../role-based-access-control/built-in-roles.md#signalr-rest-api-reader) | Read-only access to data-plane REST APIs.                                                                 | Use it when write a monitoring tool that calls readonly REST APIs.                                      |
+
+1. Select Next.
+
+
+1. For Microsoft Entra application.
+
+
+   1. In the `Assign access` to row, select **User, group, or service principal**.
+   1. In the `Members` row, click `select members`, then choose the identity in the pop-up window.
+
+1. For managed identity for Azure resources.
+
+   1. In the `Assign access` to row, select **Managed identity**.
+   1. In the `Members` row, click `select members`, then choose the application in the pop-up window.
+
+1. Select Next.
+
+
+1. Review your assignment, then click **Review + assign** to confirm the role assignment.
+
+> [!IMPORTANT]
+> Newly added role assignments might take up to 30 minutes to propagate.
+
+To learn more about how to assign and manage Azure roles, see these articles:
+
+- [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml)
+- [Assign Azure roles using the REST API](../../role-based-access-control/role-assignments-rest.md)
+- [Assign Azure roles using Azure PowerShell](../../role-based-access-control/role-assignments-powershell.md)
+- [Assign Azure roles using the Azure CLI](../../role-based-access-control/role-assignments-cli.md)
 - [Assign Azure roles using Azure Resource Manager templates](../../role-based-access-control/role-assignments-template.md)

articles/azure-web-pubsub/includes/web-pubsub-add-role-assignments.md

@@ -1,58 +1,58 @@
----
-title: include file
-description: include file
-author: terencefan
-ms.service: azure-web-pubsub
-ms.topic: include
-ms.date: 03/12/2025
-ms.author: tefa
-ms.custom: include file
----
-
-This section shows how to assign a `Web PubSub Service Owner` role to a service principal or managed identity for a Web PubSub resource.
-For detailed steps, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml).
-
-> [!NOTE]
-> A role can be assigned to any scope, including management group, subscription, resource group, or single resource. To learn more about scope, see [Understand scope for Azure RBAC](../../role-based-access-control/scope-overview.md).
-
-1. In the [Azure portal](https://portal.azure.com/), go to your Web PubSub resource.
-
-1. Select **Access control (IAM)** in the sidebar.
-
-1. Select **Add** > **Add role assignment**.
-
-   :::image type="content" source="~/reusable-content/ce-skilling/azure/media/role-based-access-control/add-role-assignment-menu-generic.png" alt-text="Screenshot that shows the page for access control and selections for adding a role assignment.":::
-
-1. On the **Role** tab, select **Web PubSub Service Owner** or other Web PubSub built-in roles depends on your scenario.
-
-   | Role                                                                                              | Description                                                                                               | Use case                                                                                                                                     |
-   | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
-   | [Web PubSub Service Owner](/azure/role-based-access-control/built-in-roles#web-pubsub-service-owner)           | Full access to data-plane APIs, including read/write REST APIs and Auth APIs.                                               | Most commonly used for building a upstream server that handles negotiation requests and client events.                                                                                                             |
-   | [Web PubSub Service Reader](/azure/role-based-access-control/built-in-roles#web-pubsub-service-reader)           | Readonly access to data-plane APIs.                                                | Use it when write a monitoring tool that calls readonly REST APIs.
-
-1. Select Next.
-
-1. For Microsoft Entra application.
-
-   1. In the `Assign access` to row, select **User, group, or service principal**.
-   1. In the `Members` row, click `select members`, then choose the identity in the pop-up window.
-
-1. For managed identity for Azure resources.
-
-   1. In the `Assign access` to row, select **Managed identity**.
-   1. In the `Members` row, click `select members`, then choose the application in the pop-up window.
-
-1. Select Next.
-
-1. Review your assignment, then click **Review + assign** to confirm the role assignment.
-
-> [!IMPORTANT]
-> Newly added role assignments might take up to 30 minutes to propagate.
-
-To learn more about how to assign and manage Azure roles, see these articles:
-
-- [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml)
-- [Assign Azure roles using the REST API](../../role-based-access-control/role-assignments-rest.md)
-- [Assign Azure roles using Azure PowerShell](../../role-based-access-control/role-assignments-powershell.md)
-- [Assign Azure roles using the Azure CLI](../../role-based-access-control/role-assignments-cli.md)
+---
+title: include file
+description: include file
+author: terencefan
+ms.service: azure-web-pubsub
+ms.topic: include
+ms.date: 03/12/2025
+ms.author: tefa
+ms.custom: include file
+---
+
+This section shows how to assign a `Web PubSub Service Owner` role to a service principal or managed identity for a Web PubSub resource.
+For detailed steps, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml).
+
+> [!NOTE]
+> A role can be assigned to any scope, including management group, subscription, resource group, or single resource. To learn more about scope, see [Understand scope for Azure RBAC](../../role-based-access-control/scope-overview.md).
+
+1. In the [Azure portal](https://portal.azure.com/), go to your Web PubSub resource.
+
+1. Select **Access control (IAM)** in the sidebar.
+
+1. Select **Add** > **Add role assignment**.
+
+   :::image type="content" source="~/reusable-content/ce-skilling/azure/media/role-based-access-control/add-role-assignment-menu-generic.png" alt-text="Screenshot that shows the page for access control and selections for adding a role assignment.":::
+
+1. On the **Role** tab, select **Web PubSub Service Owner** or other Web PubSub built-in roles depends on your scenario.
+
+   | Role                                                                                              | Description                                                                                               | Use case                                                                                                                                     |
+   | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+   | [Web PubSub Service Owner](/azure/role-based-access-control/built-in-roles#web-pubsub-service-owner)           | Full access to data-plane APIs, including read/write REST APIs and Auth APIs.                                               | Most commonly used for building a upstream server that handles negotiation requests and client events.                                                                                                             |
+   | [Web PubSub Service Reader](/azure/role-based-access-control/built-in-roles#web-pubsub-service-reader)           | Readonly access to data-plane APIs.                                                | Use it when write a monitoring tool that calls readonly REST APIs.
+
+1. Select Next.
+
+1. For Microsoft Entra application.
+
+   1. In the `Assign access` to row, select **User, group, or service principal**.
+   1. In the `Members` row, click `select members`, then choose the identity in the pop-up window.
+
+1. For managed identity for Azure resources.
+
+   1. In the `Assign access` to row, select **Managed identity**.
+   1. In the `Members` row, click `select members`, then choose the application in the pop-up window.
+
+1. Select Next.
+
+1. Review your assignment, then click **Review + assign** to confirm the role assignment.
+
+> [!IMPORTANT]
+> Newly added role assignments might take up to 30 minutes to propagate.
+
+To learn more about how to assign and manage Azure roles, see these articles:
+
+- [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml)
+- [Assign Azure roles using the REST API](../../role-based-access-control/role-assignments-rest.md)
+- [Assign Azure roles using Azure PowerShell](../../role-based-access-control/role-assignments-powershell.md)
+- [Assign Azure roles using the Azure CLI](../../role-based-access-control/role-assignments-cli.md)
 - [Assign Azure roles using Azure Resource Manager templates](../../role-based-access-control/role-assignments-template.md)