Merge pull request #302731 from MicrosoftDocs/main

Auto Publish – main to live - 2025-07-15 05:00 UTC

Author: learn-build-service-prod[bot]

articles/communication-services/concepts/voice-video-calling/calling-sdk-features.md

@@ -178,7 +178,7 @@ The Azure Communication Services Calling SDK supports the following streaming co
 | Limit | Web | Windows/Android/iOS |
 | --- | --- | --- |
 | **Maximum # of outgoing local streams that can be sent simultaneously**     | 1 video and 1 screen sharing | 1 video + 1 screen sharing |
-| **Maximum # of incoming remote streams that can be rendered simultaneously** | 16 videos + 1 screen sharing on desktop browsers*, 4 videos + 1 screen sharing on web mobile browsers | 9 videos + 1 screen sharing |
+| **Maximum # of incoming remote streams that can be rendered simultaneously** | GA Webjs SDK - [16 videos + 1 screen sharing on desktop browsers](../../quickstarts/voice-video-calling/optimizing-video-placement.md#how-many-videos-to-place-in-a-grid-at-a-time) <br />4 videos + 1 screen sharing on web mobile browsers <br /> <br />  Public preview - [25 videos + 1 screen sharing on desktop browser](../../quickstarts/voice-video-calling/optimizing-video-placement.md#how-many-videos-to-place-in-a-grid-at-a-time) <br />4 videos + 1 screen sharing on web mobile browsers | 9 videos + 1 screen sharing |
 
 \* Starting from Azure Communication Services Web Calling SDK version [1.16.3](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1163-stable-2023-08-24). While the Calling SDK doesn't enforce these limits, your users might experience performance degradation if they're exceeded. Use the API of [Optimal Video Count](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#remote-video-quality) to determine the number of incoming video streams your web environment can support. To properly support 16 incoming videos, the computer needs a minimum of 16-GB RAM and a 4-core or greater CPU that is less than three years old.
 

articles/communication-services/quickstarts/voice-video-calling/optimizing-video-placement.md

@@ -5,7 +5,7 @@ description: This article describes how to place video on a web page based on re
 author: sloanster
 ms.author: micahvivion
 services: azure-communication-services
-ms.date: 06/26/2025
+ms.date: 07/08/2025
 ms.topic: quickstart
 ms.service: azure-communication-services
 ms.subservice: calling
@@ -67,7 +67,7 @@ The optimal video count returns an integer defining the ideal number of videos t
 
 Developers should ensure that their application subscribes to changes in the `Optimal Video Count` in group calls and adjust the number of videos being rendered on a web page dynamically based on the OVC count. The value from optimal video count (OVC) updates every 10 seconds.
 
-You need to reference the feature `OptimalVideoCount` via the feature method of the Call object. You can then set a listener via the *on* method of the `OptimalVideoCountCallFeature` to be notified when the `optimalVideoCount` changes.
+You need to reference the feature `OptimalVideoCount` via the feature method of the Call object. You can then set a listener via the `on` method of the `OptimalVideoCountCallFeature` to be notified when the `optimalVideoCount` changes.
 
 To unsubscribe from the changes, you can call the off method. The current maximum number of incoming videos that can be rendered on a web page is **16**. To properly support 16 incoming videos, the computer should have a minimum of 16-GB RAM and a 4-core or greater CPU that is no older than three years old.
 
@@ -169,6 +169,30 @@ getSupportedResolutions();
 | 240p | 15 | 15 | 650 K |
 | 180p | 7.5 | 15 | 250 K(350 K if 15 FPS)|
 
+### How many videos to place in a grid at a time
+As the Azure Communication Services WebJS Calling SDK continues to evolve, one of its key capabilities is supporting many incoming video streams in a grid layout on desktop and mobile browsers. This feature is valuable for scenarios like virtual classrooms, large team meetings, or customer support centers where multiple participants need to be visible simultaneously.
+
+However, this scalability introduces a trade-off between the number of video streams rendered and the visual quality of each stream. Since the total screen real estate is fixed, increasing the number of video tiles means each individual video renderer must occupy a smaller portion of the screen. To maintain performance and avoid overloading the browser’s rendering pipeline, the SDK dynamically adjusts the resolution of each incoming video stream based on its rendered size. This ensures that bandwidth and CPU usage remain within acceptable limits, but it also means that as more participants join, the resolution of each video may decrease to accommodate the grid.
+
+This adaptive behavior helps ensure stable user performance. For instance, in a 2x2 grid with 4 participants, each video can be rendered at a higher resolution. In contrast, with a 5x5 grid displaying 25 participants, each tile is smaller and the SDK may downscale video streams to fit the display size. This approach reduces bandwidth usage and lowers the chances of dropped frames or lag. To support up to 25 incoming video streams, it is recommended to use a computer with at least an 8-core processor and 16GB of RAM
+
+The following table illustrates how video resolution changes based on the number of participants displayed in the incoming video grid at any one time.
+
+| **Number of incoming streams** | **Incoming video resolution** |
+|------------------|----------------------|
+| 1                | 1080p                 |
+| 2                | 720p                  |
+| 3                | 540p                  |
+| 4 to 9              | 360p                  |
+| 10 to 16            | 240p                  |
+| 17 to 25         | 180p                  |
+
+> [!NOTE]  
+> The GA version of the calling WebJS SDK allows for up to **16** incoming video streams for desktop browsers (4x4 grid).
+
+> [!NOTE]  
+> The public preview 1.37.1-beta.1 and greater of the calling WebJS SDK currently supports up to **25** incoming video streams for desktop browsers (5x5 grid).
+
 ## Conclusion
 
 To determine how many videos to place on a web page, you need to carefully consider resolution, device type, bandwidth, and user experience. Follow these guidelines and best practices to create web apps that not only look appealing but also function seamlessly, providing an optimal viewing experience for users across various devices and connection speeds.

articles/dev-box/how-to-auto-delete-dev-box.md

@@ -0,0 +1,91 @@
+---
+title: Enable Dev Box Auto-Delete to Control Costs
+description: Dev Box autodeletion helps you control costs by removing unused Dev Boxes. Learn how to enable, configure, and cancel autodeletion in Azure.
+#customer intent: As a Dev Box admin, I want to enable auto-deletion for unused Dev Boxes so that I can control costs in my Azure subscription.
+author: RoseHJM
+contributors: null
+ms.topic: how-to
+ms.date: 07/11/2025
+ms.author: rosemalcolm
+ms.reviewer: rosemalcolm
+ms.custom:
+  - ai-gen-docs-bap
+  - ai-gen-title
+  - ai-seo-date:07/11/2025
+  - ai-gen-description
+---
+
+# Configure Microsoft Dev Box autodeletion
+
+Microsoft Dev Box Auto Delete (Preview) helps organizations manage resources and control costs by automatically deleting unused Dev Boxes. This article explains how to enable the feature, configure autodeletion settings, and cancel scheduled deletions in both the Azure portal and developer portal. Use these steps to optimize Dev Box usage in your Azure subscription.
+
+## Prerequisites
+
+- Microsoft Dev Box configured with a dev center and at least one project.
+
+## Enable the preview feature
+
+While the Dev Box Auto Delete feature is in Preview, you must manually enable it in your Azure subscription. Follow these steps:
+
+1. Sign in to the [Azure portal](https://portal.azure.com).
+1. Go to the Azure subscription where you want to enable Dev Box autodeletion.
+1. In the left menu, select **Preview features**.
+1. In the search box, type "Dev Box Auto".
+1. Select **Dev Box Auto Delete Preview**, and then select **Register**.
+
+   :::image type="content" source="media/how-to-auto-delete-dev-box/dev-box-auto-delete-enable-preview.png" alt-text="Screenshot of the Azure portal showing the Preview features pane with Dev Box Auto Delete Preview selected." lightbox="media/how-to-auto-delete-dev-box/dev-box-auto-delete-enable-preview.png":::
+
+   After you register the feature, it will be available for use in your subscription.
+
+## Set up autodeletion in a project
+
+To configure autodeletion for unused dev boxes in a project, follow these steps in the Azure portal:
+
+1. Open an existing Dev Box project, or create a new one in your subscription.
+1. In the left menu, under **Settings**, select **Dev box settings**.
+1. On the **Dev box settings** page, in the **Cost controls** section, select **Automatically delete unused dev boxes**.
+
+   :::image type="content" source="media/how-to-auto-delete-dev-box/dev-box-auto-delete-enable.png" alt-text="Screenshot of the Azure portal showing the option to enable automatic deletion of unused dev boxes in project settings." lightbox="media/how-to-auto-delete-dev-box/dev-box-auto-delete-enable.png":::
+ 
+1. When automatic deletion is enabled, you can configure the following options:
+   - **Inactivity threshold**: Enter the number of inactive days before a Dev Box is scheduled for automatic deletion (for example, 30 days).
+   - **Grace period**: Enter the number of days the developer or admin has to respond and keep the Dev Box (for example, 30 days).
+
+   :::image type="content" source="media/how-to-auto-delete-dev-box/dev-box-auto-delete-settings.png" alt-text="Screenshot of the Dev box settings page in Azure portal showing the cost controls section with autodeletion options." lightbox="media/how-to-auto-delete-dev-box/dev-box-auto-delete-settings.png"::: 
+
+1. Select **Apply**.
+
+## Cancel scheduled deletions in the Azure portal
+
+To cancel a scheduled deletion in the Azure portal, follow these steps:
+
+1. Go to the pool that has your Dev Box scheduled for deletion.
+1. Select that pool to view its Dev Boxes. You need Project Admin access to finish this step.
+1. Select the ellipses (**...**) next to the Dev Box scheduled for deletion.
+1. Select **Cancel deletion**. 
+
+   :::image type="content" source="media/how-to-auto-delete-dev-box/dev-box-azure-portal-cancel-auto-delete.png" alt-text="Screenshot of the Azure portal showing the pool details and the cancel deletion option for a Dev Box." lightbox="media/how-to-auto-delete-dev-box/dev-box-azure-portal-cancel-auto-delete.png":::
+
+The selected dev box isn't deleted.
+
+## Cancel scheduled deletions in the developer portal
+
+After reaching the inactivity threshold, you'll get an email notification warning you that your Dev Box is scheduled for deletion. 
+
+:::image type="content" source="media/how-to-auto-delete-dev-box/dev-box-auto-delete-email.png" alt-text="Screenshot showing an email notification informing the user that their dev box will be deleted. The message states when dev box will be deleted." lightbox="media/how-to-auto-delete-dev-box/dev-box-auto-delete-email.png":::
+
+If you want to cancel the scheduled deletion and keep your dev box, follow these steps:
+
+1. Sign in to the [developer portal](https://aka.ms/devbox-portal).
+1. In the developer portal, find the dev box scheduled for deletion.
+1. Select **Keep this dev box** to cancel the automatic deletion.
+
+   :::image type="content" source="media/how-to-auto-delete-dev-box/dev-box-developer-portal-keep.png" alt-text="Screenshot of the Dev Box developer portal showing the scheduled deletion notice and the option to keep the dev box.":::
+
+The selected dev box isn't deleted.
+
+If you don't see a dev box tile with a pending deletion notice, check with your admin that you still have access to the project containing the dev box.
+
+## Related content
+
+- [Autostop your Dev Boxes on schedule](how-to-configure-stop-schedule.md)

articles/dev-box/index.yml

@@ -87,6 +87,8 @@ landingContent:
             url: how-to-request-quota-increase.md
           - text: Configure Dev Box Hibernation
             url: how-to-configure-dev-box-hibernation.md
+          - text: Delete unused dev boxes
+            url: how-to-auto-delete-dev-box.md
           - text: Autostop Dev Boxes on schedule             
             url: how-to-configure-stop-schedule.md
           - text: Skip or delay a scheduled shutdown