Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ertoc

Author: duongau

articles/communication-services/concepts/analytics/insights/voice-and-video-insights.md

@@ -152,7 +152,7 @@ Since the Voice and Video insights dashboard is powered by [Azure Monitor Workbo
 
 #### Collect Call Logs
 
-The Insights Dashboards uses [Azure Monitor Workbooks](/azure/azure-monitor/visualize/workbooks-overview) which displays call log data from Azure Communication Services. These call logs aren't stored in your Azure account by default so you need to begin storing them for the dashboard to work. To collect these call logs, you need to enable a diagnostic setting that sends call data to a Log Analytics workspace in the same resource group as your calling resource. 
+The Insights Dashboards uses [Azure Monitor Workbooks](/azure/azure-monitor/visualize/workbooks-overview) which displays call log data from Azure Communication Services. These call logs aren't stored in your Azure account by default so you need to begin storing them for the dashboard to work. To collect these call logs, you need to enable a diagnostic setting that directs the call data to a Log Analytics workspace. 
 
 **Data isn’t stored retroactively, so you begin capturing call logs only after configuring the diagnostic setting.**
 
@@ -181,4 +181,4 @@ Interact with Copilot in Azure for quality improvement guidance and explanations
 
 <!-- - NOTES
 
-:::image type="content" source="..\media\workbooks\insights-overview-2.png" alt-text="Screenshot of Communication Services Insights dashboard."::: -->
+:::image type="content" source="..\media\workbooks\insights-overview-2.png" alt-text="Screenshot of Communication Services Insights dashboard."::: -->

articles/communication-services/concepts/voice-video-calling/call-diagnostics.md

@@ -25,12 +25,12 @@ Just like a real conversation, many things happen simultaneously in a call that
 
 ## Enable Call Diagnostics
 
-Azure Communication Services generates call data in the form of metrics and events as you make calls. You must store these data in a Log Analytics workspace that is in the same resource group as your calling resource in order for Call Diagnostics to work. To store these data, you must enable a diagnostic setting in Azure Monitor that directs these call data to be stored in a Log Analytics workspace as they're created. These call data aren't retroactively available from Azure Communication Services, but once you set up your diagnostic setting you control the data retention periods for your Log Analytics resource.  
+Azure Communication Services generates call data in the form of metrics and events as you make calls. You must store these data in a Log Analytics workspace in order for Call Diagnostics to work. To store these data, you must enable a diagnostic setting in Azure Monitor that directs these call data to be stored in a Log Analytics workspace as they're created. These call data aren't retroactively available from Azure Communication Services, but once you set up your diagnostic setting you control the data retention periods for your Log Analytics resource.  
 
 > [!IMPORTANT]
 > To enable Call Diagnostics in your calling resource see: [**How do I set up Call Diagnostics?**](#how-do-i-set-up-call-diagnostics) 
 >
->You need to start collecting the log data for Call Diagnostics to visualize. Call Diagnostics can only query data sent to a Log Analytics workspace that is located in the same resource group as your calling resource. Keep in mind, call data isn't stored anywhere until you set up a Diagnostic Setting to store it in a Log Analytics workspace. You need to enable a Diagonstic Setting for each Azure Communications Services resource ID you want to monitor. 
+>You need to start collecting the log data for Call Diagnostics to visualize. Call Diagnostics can only query data after you setup a diagnostic setting in Azure Monitor to send your call data to a Log Analytics workspace. Keep in mind, call data isn't stored anywhere until you set up a Diagnostic Setting to store it in a Log Analytics workspace. You need to enable a Diagonstic Setting for each Azure Communications Services resource ID you want to monitor. 
 
 Since Call Diagnostics is an application layer on top of data for your Azure Communications Services resource, you can query the call data and [build workbook reports on top of your data](/azure/azure-monitor/logs/data-platform-logs#built-in-insights-and-custom-dashboards-workbooks-and-reports).
 

articles/deployment-environments/includes/developer-portal-landing-page.md

@@ -0,0 +1,25 @@
+---
+author: RoseHJM
+ms.author: rosemalcolm
+ms.date: 11/13/2024
+ms.topic: include
+ms.service: dev-box
+---
+
+1. Go to the [developer portal](https://aka.ms/devbox-portal). The landing page contains useful information and links. When you're ready, select **Sign in**. 
+
+   :::image type="content" source="../media/developer-portal-landing-page/developer-portal-landing-page-sign-in.png" alt-text="Screenshot of the developer portal landing page with sign-in highlighted.":::
+
+#### [No existing environments](#tab/no-existing-environments)
+
+2. If you don't have any dev boxes, you see this screen. Select **New environment**.
+
+   :::image type="content" source="../media/developer-portal-landing-page/developer-portal-new-deployment-environment.png" alt-text="Screenshot of the developer portal with new environment highlighted." lightbox="../media/developer-portal-landing-page/developer-portal-new-deployment-environment.png":::
+
+#### [Existing environments](#tab/existing-environments)
+
+2. Select **New** > **New environment**.
+ 
+   :::image type="content" source="../media/developer-portal-landing-page/developer-portal-new-environment-menu.png" alt-text="Screenshot of the developer portal with the New menu and Dev box option highlighted." lightbox="../media/developer-portal-landing-page/developer-portal-new-environment-menu.png":::
+ 
+---

articles/deployment-environments/media/developer-portal-landing-page/developer-portal-landing-page-sign-in.png

@@ -28,13 +28,9 @@ An environment in Azure Deployment Environments is a collection of Azure resourc
 
 [!INCLUDE [note-deployment-environments-user](includes/note-deployment-environments-user.md)]
 
-1. Sign in to the [developer portal](https://devportal.microsoft.com).
-
-1. From the **New** menu at the top left, select **New environment**.
- 
-   :::image type="content" source="media/quickstart-create-access-environments/dev-new-environment.png" alt-text="Screenshot showing the new menu with new environment highlighted." lightbox="media/quickstart-create-access-environments/dev-new-environment-expanded.png":::
+[!INCLUDE [developer-portal-landing-page](includes/developer-portal-landing-page.md)]
 
-1. In the **Add an environment** pane, select the following information:
+3. In the **Add an environment** pane, select the following information:
 
    |Field  |Value  |
    |---------|---------|
@@ -47,7 +43,7 @@ An environment in Azure Deployment Environments is a collection of Azure resourc
 
    If your environment is configured to accept parameters, you can enter them on a separate pane. In this example, you don't need to specify any parameters.
 
-1. Select **Create**. You see your environment in the developer portal immediately, with an indicator that shows creation in progress.
+4. Select **Create**. You see your environment in the developer portal immediately, with an indicator that shows creation in progress.
 
 ## Access an environment
 

articles/deployment-environments/media/developer-portal-landing-page/developer-portal-new-deployment-environment.png

@@ -5,35 +5,40 @@ services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: concept-article
-ms.date: 10/16/2023
+ms.date: 01/31/2025
 ms.author: duau
 ---
 
 # About upgrading ExpressRoute circuit bandwidth
 
-ExpressRoute is a dedicated and private connection to Microsoft's global network. Connectivity is facilitated through an ExpressRoute partner's network, or a direct connection to the Microsoft Enterprise Edge (MSEE) devices. Once physical connectivity has been configured and tested, you can enable layer-2 and layer-3 connectivity by creating an ExpressRoute circuit and configuring peering.
+ExpressRoute provides a dedicated, private connection to Microsoft's global network. You can establish this connectivity through an ExpressRoute partner's network or directly to the Microsoft Enterprise Edge (MSEE) devices. After setting up and testing the physical connection, you can enable layer-2 and layer-3 connectivity by creating an ExpressRoute circuit and configuring peering.
 
 ## <a name="considerations"></a>Capacity considerations
 
 ### Insufficient capacity for physical connection
 
-An ExpressRoute circuit is created on a physical connection between Microsoft and a ExpressRoute Partner. The physical connection has a fixed capacity. If you're unable to increase your circuit size that means that the underlying physical connection for your existing circuit doesn’t have capacity for the upgrade. You need to create a new circuit if you want to change the circuit size. For more information, see [Migrate to a new ExpressRoute circuit](circuit-migration.md).
+If you're unable to increase your circuit size, it means the underlying physical connection for your existing circuit lacks the capacity for the upgrade. In this case, you need to create a new circuit. For more information, see [Migrate to a new ExpressRoute circuit](circuit-migration.md).
 
-After you've successfully created the new ExpressRoute circuit, you should link your existing virtual networks to this circuit. You can then test and validate the connectivity of the new ExpressRoute circuit before you deprovision the old circuit. These recommended migration steps minimize down time and disruption to your production work load.
+After creating the new ExpressRoute circuit, link your existing virtual networks to it. Test and validate the connectivity of the new circuit before deprovisioning the old one. These steps help minimize downtime and disruption to your production workload.
 
 ### <a name="bandwidth"></a>Insufficient ExpressRoute partner bandwidth
 
-If you're unable to create a new ExpressRoute circuit because of a capacity error. It means this ExpressRoute partner doesn’t have capacity to connect to Microsoft at this peering location. Contact your ExpressRoute partner to request for more capacity.
+If you're unable to create a new ExpressRoute circuit due to a capacity error, it means the ExpressRoute partner doesn’t have sufficient capacity at the peering location to connect to Microsoft. Contact your ExpressRoute partner to request additional capacity.
 
-Once the new capacity gets provisioned, you can use the methods contained in the [Upgrade circuit bandwidth](#upgrade) section to create a new circuit, configure connectivity, and delete the old circuit.
+Once the new capacity is provisioned, you can follow the methods in the [Upgrade circuit bandwidth](#upgrade) section to create a new circuit, configure connectivity, and delete the old circuit.
 
 ### <a name="bandwidth"></a>Insufficient ExpressRoute Direct bandwidth
 
-If the ExpressRoute Direct doesn't have sufficient capacity, you have two options. You can either delete circuits that are associated to the ExpressRoute Direct resource that you no longer need, or create a new ExpressRoute Direct resource. For guidance on managing the ExpressRoute Direct resource, refer to [How to configure ExpressRoute Direct](how-to-expressroute-direct-portal.md).
+If ExpressRoute Direct lacks sufficient capacity, you have two options: 
+
+- Delete any unnecessary circuits associated with the ExpressRoute Direct resource.
+- Create a new ExpressRoute Direct resource.
+
+For detailed guidance on managing ExpressRoute Direct resources, see [How to configure ExpressRoute Direct](how-to-expressroute-direct-portal.md).
 
 ## <a name="upgrade"></a>Upgrade circuit bandwidth
 
-To upgrade circuit bandwidth, the ExpressRoute Direct, or ExpressRoute partner needs to have [sufficient available bandwidth](#considerations) for the upgrade to succeed.
+To upgrade circuit bandwidth, ensure that the ExpressRoute Direct or ExpressRoute partner has [sufficient available bandwidth](#considerations) for the upgrade to succeed.
 
 If capacity is available, you can upgrade the circuit using the following methods:
 

articles/deployment-environments/media/developer-portal-landing-page/developer-portal-new-environment-menu.png

@@ -6,7 +6,7 @@ author: duongau
 ms.author: duau
 ms.service: azure-expressroute
 ms.topic: tutorial
-ms.date: 01/02/2024
+ms.date: 01/31/2025
 # Customer intent: As a network engineer, I want to establish a private connection from my on-premises network to my Azure virtual network using ExpressRoute.
 ---