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

Author: halkazwini

articles/azure-vmware/extended-security-updates-windows-sql-server.md

@@ -63,7 +63,7 @@ When you contact support, the ticket should be raised under the category of Azur
 ## Related content
 - [What are Extended Security Updates - SQL Server](https://learn.microsoft.com/sql/sql-server/end-of-support/sql-server-extended-security-updates)
 - [Extend Security Updates for Windows Server overview](https://learn.microsoft.com/windows-server/get-started/extended-security-updates-overview)
-- Planning your Windows Server and SQL Server end of support: [Extended Security Updates for SQL Server and Windows Server](https://www.microsoft.com/en-us/windows-server/extended-security-updates)
+- [Plan your Windows Server and SQL Server end of support](https://www.microsoft.com/windows-server/extended-security-updates)
 
 
 [Microsoft Support]: https://ms.portal.azure.com/#view/Microsoft_Azure_Support/NewSupportRequestV3Blade/assetId/%2Fsubscriptions%2F5a79c43b-b03d-4610-bc59-627d8a6744d1%2FresourceGroups%2FABM_CSS_Lab_Enviroment%2Fproviders%2FMicrosoft.AVS%2FprivateClouds%2FBareMetal_CSS_Lab/callerWorkflowId/a7ecc9f7-8578-4820-abdf-1db09a2bdb47/callerName/Microsoft_Azure_Support%2FAurora.ReactView/subscriptionId/5a79c43b-b03d-4610-bc59-627d8a6744d1/productId/e7b24d57-0431-7d60-a4bf-e28adc11d23e/summary/Issue/topicId/9e078285-e10f-0365-31e3-6b31e5871794/issueType/technical

articles/azure-vmware/use-hcx-run-commands.md

@@ -16,11 +16,9 @@ This article describes two VMware HCX commands: **Restart HCX Manager** and **Sc
 
 This Command checks for active VMware HCX migrations and replications. If none are found, it restarts the VMware HCX Cloud Manager (VMware HCX VM's guest OS). 
 
-1. Navigate to the Run Command panel in an Azure VMware Solution private cloud on the Azure portal.
-
-   :::image type="content" source="media/hcx-commands/run-command-private-cloud.png" alt-text="Diagram that  lists all available Run command packages and Run commands." border="false" lightbox="media/hcx-commands/run-command-private-cloud.png":::        
+1. Navigate to the Run Command panel under Operations in an Azure VMware Solution private cloud on the Azure portal. Select package "Microsoft.AVS.HCX" to view available HCX run commands.  
 
-1. Select the **Microsoft.AVS.Management** package dropdown menu and select the **Restart-HcxManager** command. 
+1. Select the **Microsoft.AVS.HCX** package dropdown menu and select the **Restart-HcxManager** command. 
 1. Set parameters and select **Run**. 
 Optional run command parameters.   
 
@@ -47,7 +45,7 @@ Use the Scale VMware HCX Cloud Manager Run Command to increase the resource allo
 
 1. Navigate to the Run Command panel on in an Azure VMware Solution private cloud on the Azure portal. 
 
-1. Select the **Microsoft.AVS.Management** package dropdown menu and select the ``Set-HcxScaledCpuAndMemorySetting`` command.
+1. Select the **Microsoft.AVS.HCX** package dropdown menu and select the ``Set-HcxScaledCpuAndMemorySetting`` command.
 
     :::image type="content" source="media/hcx-commands/set-hcx-scale.png" alt-text="Diagram that shows run command parameters for Set-HcxScaledCpuAndMemorySetting command." border="false" lightbox="media/hcx-commands/set-hcx-scale.png"::: 
 

articles/devtest-labs/devtest-lab-restart-vm.md

@@ -4,43 +4,45 @@ description: This article provides steps to quickly and easily restart virtual m
 ms.topic: how-to
 ms.author: rosemalcolm
 author: RoseHJM
-ms.date: 06/26/2020
+ms.date: 04/18/2024
 ms.custom: UpdateFrequency2
+
+#customer intent: As a lab admin, I want to restart a virtual machine in a lab in Azure DevTest Labs so that I can restart a virtual machine as part of a troubleshooting plan.
 ---
 
 # Restart a VM in a lab in Azure DevTest Labs
+
 You can quickly and easily restart a virtual machine in  DevTest Labs by following the steps in this article. Consider the following before restarting a VM:
 
 - The VM must be running for the restart feature to be enabled.
 - If a user is connected to a running VM when they perform a restart, they must reconnect to the VM after it starts back up.
 - If an artifact is being applied when you restart the VM, you receive a warning that the artifact might not be applied.
 
-    ![Warning when restarting while applying artifacts](./media/devtest-lab-restart-vm/devtest-lab-restart-vm-apply-artifacts.png)
-
+    :::image type="content" source="media/devtest-lab-restart-vm/devtest-lab-restart-vm-apply-artifacts.png" alt-text="Screenshot showing the restarting while applying artifacts warning." lightbox="media/devtest-lab-restart-vm/devtest-lab-restart-vm-apply-artifacts.png":::
 
    > [!NOTE]
    > If the VM has stalled while applying an artifact, you can use the restart VM feature as a potential way to resolve the issue.
-   >
-   >
 
-## Steps to restart a VM in a lab in Azure DevTest Labs
 1. Sign in to the [Azure portal](https://go.microsoft.com/fwlink/p/?LinkID=525040).
 1. Select **All Services**, and then select **DevTest Labs** from the list.
 1. From the list of labs, select the lab that includes the VM  you want to restart.
 1. In the left panel, select **My Virtual Machines**.
 1. From the list of VMs, select a running VM.
 1. At the top of the VM management pane, select **Restart**.
 
-    ![Restart VM button](./media/devtest-lab-restart-vm/devtest-lab-restart-vm.png)
+    :::image type="content" source="media/devtest-lab-restart-vm/devtest-lab-restart-vm.png" alt-text="Screenshot of the Azure portal showing the Restart VM button." lightbox="media/devtest-lab-restart-vm/devtest-lab-restart-vm.png":::
 
 1. Monitor the status of the restart by selecting the **Notifications** icon at the top right of the window.
 
-    ![Viewing the status of the VM restart](./media/devtest-lab-restart-vm/devtest-lab-restart-notification.png)
+    :::image type="content" source="media/devtest-lab-restart-vm/devtest-lab-restart-notification.png" alt-text="Screenshot of the Azure portal showing the notification icon and message." lightbox="media/devtest-lab-restart-vm/devtest-lab-restart-notification.png":::
 
 You can also restart a running VM by selecting its ellipsis (...) in the list of **My Virtual Machines**.
 
-![Restart VM through ellipses](./media/devtest-lab-restart-vm/devtest-lab-restart-elipses.png)
+:::image type="content" source="media/devtest-lab-restart-vm/devtest-lab-restart-ellipses.png" alt-text="Screenshot of the Azure portal showing the Restart VM option in the ellipses menu." lightbox="media/devtest-lab-restart-vm/devtest-lab-restart-ellipses.png":::
+
+
+After the VM restarts, you can reconnect to it by selecting **Connect** on the VM management pane.
+
+## Related content
 
-## Next steps
-* Once it is restarted, you can reconnect to the VM by selecting **Connect** on the its management pane.
-* Explore the [DevTest Labs Azure Resource Manager quickStart template gallery](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates)
+- [DevTest Labs Azure Resource Manager quickStart template gallery](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates)

articles/devtest-labs/media/devtest-lab-restart-vm/devtest-lab-restart-elipses.png

@@ -179,6 +179,63 @@ Name | Description
 `OffsetCommit` | Number of offset commit calls made to the event hub 
 `OffsetFetch` | Number of offset fetch calls made to the event hub.
 
+## Diagnostic Error Logs
+Diagnostic error logs capture error messages for any client side, throttling and Quota exceeded errors. They provide detailed diagnostics for error identification.
+
+Diagnostic Error Logs include elements listed in below table:
+
+Name | Description | Supported in Azure Diagnostics | Supported in AZMSDiagnosticErrorLogs (Resource specific table)
+---|---|---|---|
+`ActivityId` | A randomly generated UUID that ensures uniqueness for the audit activity. | Yes | Yes
+`ActivityName` | Operation name  | Yes | Yes
+`NamespaceName` | Name of Namespace | Yes | yes
+`EntityType` | Type of Entity | Yes | Yes 
+`EntityName` | Name of Entity | Yes | Yes  
+`OperationResult` | Type of error in Operation (Clienterror or Serverbusy or quotaexceeded) | Yes | Yes
+`ErrorCount` | Count of identical errors during the aggregation period of 1 minute. | Yes | Yes 
+`ErrorMessage` | Detailed Error Message | Yes | Yes 
+`ResourceProvider` | Name of Service emitting the logs. Possible values: Microsoft.Eventhub and Microsoft.Servicebus | Yes | Yes 
+`Time Generated (UTC)` | Operation time | No | Yes
+`EventTimestamp` | Operation Time | Yes | No
+`Category` | Log category | Yes | No
+`Type`  | Type of Logs emitted | No | Yes
+
+Here's an example of Diagnostic error log entry:
+
+```json
+{
+    "ActivityId": "0000000000-0000-0000-0000-00000000000000",
+    "SubscriptionId": "<Azure Subscription Id",
+    "NamespaceName": "Name of Event Hubs Namespace",
+    "EntityType": "EventHub",
+    "EntityName": "Name of Event Hub",
+    "ActivityName": "SendMessage",
+    "ResourceId": "/SUBSCRIPTIONS/xxx/RESOURCEGROUPS/<Resource Group Name>/PROVIDERS/MICROSOFT.EVENTHUB/NAMESPACES/<Event hub namespace name>",,
+    "OperationResult": "ServerBusy",
+    "ErrorCount": 1,
+    "EventTimestamp": "3/27/2024 1:02:29.126 PM +00:00",
+    "ErrorMessage": "the request was terminated because the entity is being throttled by the application group with application group name <application group name> and policy name <throttling policy name>.error code: 50013.",
+    "category": "DiagnosticErrorLogs"
+ }
+
+```
+Resource specific table entry:
+```json
+{
+    "ActivityId": "0000000000-0000-0000-0000-00000000000000",
+    "NamespaceName": "Name of Event Hubs Namespace",
+    "EntityType": "Event Hub",
+    "EntityName": "Name of Event Hub",
+    "ActivityName": "SendMessage",
+    "ResourceId": "/SUBSCRIPTIONS/xxx/RESOURCEGROUPS/<Resource Group Name>/PROVIDERS/MICROSOFT.EVENTHUB/NAMESPACES/<Event hub namespace name>",,
+    "OperationResult": "ServerBusy",
+    "ErrorCount": 1,
+    "TimeGenerated [UTC]": "1/27/2024 4:02:29.126 PM +00:00",
+    "ErrorMessage": "The request was terminated because the entity is being throttled by the application group with application group name <application group name> and policy name <throttling policy name>.error code: 50013.",
+    "Type": "AZMSDiagnosticErrorLogs"
+ }
+
+```
 
 ## Azure Monitor Logs tables
 Azure Event Hubs uses Kusto tables from Azure Monitor Logs. You can query these tables with Log Analytics. For a list of Kusto tables the service uses, see [Azure Monitor Logs table reference](/azure/azure-monitor/reference/tables/tables-resourcetype#event-hubs).

articles/devtest-labs/media/devtest-lab-restart-vm/devtest-lab-restart-ellipses.png

@@ -74,13 +74,11 @@ For metrics that support dimensions, you can apply filters using a dimension val
 :::image type="content" source="./media/monitor-event-hubs/metrics-filter-split.png" alt-text="Screenshot showing the Metrics Explorer for an Event Hubs namespace with a filter." lightbox="./media/monitor-event-hubs/metrics-filter-split.png":::
 
 ## Analyze logs
-Using Azure Monitor Log Analytics requires you to create a diagnostic configuration and enable __Send information to Log Analytics__. For more information, see the [Collection and routing](#collection-and-routing) section. Data in Azure Monitor Logs is stored in tables, with each table having its own set of unique properties. Azure Event Hubs stores data in the following tables: **AzureDiagnostics** and **AzureMetrics**.
+Using Azure Monitor Log Analytics requires you to create a diagnostic configuration and enable __Send information to Log Analytics__. For more information, see the [Collection and routing](#collection-and-routing) section. Data in Azure Monitor Logs is stored in tables, with each table having its own set of unique properties. Azure Event Hubs has the capability to dispatch logs to either of two destination tables - Azure Diagnostic or Resource specific tables in Log Analytics.For a detailed reference of the logs and metrics, see [Azure Event Hubs monitoring data reference](monitor-event-hubs-reference.md).
 
 > [!IMPORTANT]
 > When you select **Logs** from the Azure Event Hubs menu, Log Analytics is opened with the query scope set to the current workspace. This means that log queries will only include data from that resource. If you want to run a query that includes data from other databases or data from other Azure services, select **Logs** from the **Azure Monitor** menu. See [Log query scope and time range in Azure Monitor Log Analytics](../azure-monitor/logs/scope.md) for details.
 
-For a detailed reference of the logs and metrics, see [Azure Event Hubs monitoring data reference](monitor-event-hubs-reference.md).
-
 ### Sample Kusto queries
 
 > [!IMPORTANT]

articles/devtest-labs/media/devtest-lab-restart-vm/devtest-lab-restart-notification.png

@@ -97,6 +97,11 @@ Suggested order of operations for manually upgrading a Basic Load Balancer in co
 1. Remove the temporary frontend configuration
 1. Test that inbound and outbound traffic flow through the new Standard Load Balancer as expected 
 
+## FAQ
+
+### Will the Basic Load Balancer retirement impact Cloud Services Extended Support (CSES) deployments?
+No, this retirement will not impact your existing or new deployments on CSES. This means that you can still create and use Basic Load Balancers for CSES deployments. However, we advise using Standard SKU on ARM native resources (those that do not depend on CSES) when possible, because Standard has more advantages than Basic.
+
 ## Next Steps
 
 For guidance on upgrading basic Public IP addresses to Standard SKUs, see: