Merge branch 'MicrosoftDocs:main' into main

Author: garchiro7

articles/aks/node-auto-repair.md

@@ -1,69 +1,65 @@
 ---
-title: Automatically repairing Azure Kubernetes Service (AKS) nodes 
-description: Learn about node auto-repair functionality, and how AKS fixes broken worker nodes.
+title: Automatically repair Azure Kubernetes Service (AKS) nodes 
+description: Learn about node auto-repair functionality and how AKS fixes broken worker nodes.
 ms.topic: conceptual
-ms.date: 03/11/2021
+ms.date: 05/30/2023
 ---
 
 # Azure Kubernetes Service (AKS) node auto-repair
 
-AKS continuously monitors the health state of worker nodes and performs automatic node repair if they become unhealthy. The Azure virtual machine (VM) platform [performs maintenance on VMs][vm-updates] experiencing issues. 
+Azure Kubernetes Service (AKS) continuously monitors the health state of worker nodes and performs automatic node repair if they become unhealthy. The Azure virtual machine (VM) platform [performs maintenance on VMs][vm-updates] experiencing issues. AKS and Azure VMs work together to minimize service disruptions for clusters.
 
-AKS and Azure VMs work together to minimize service disruptions for clusters.
-
-In this document, you'll learn how automatic node repair functionality behaves for both Windows and Linux nodes. 
+In this article, you learn how the automatic node repair functionality behaves for Windows and Linux nodes.
 
 ## How AKS checks for unhealthy nodes
 
-AKS uses the following rules to determine if a node is unhealthy and needs repair: 
-* The node reports **NotReady** status on consecutive checks within a 10-minute timeframe.
-* The node doesn't report any status within 10 minutes.
+AKS uses the following rules to determine if a node is unhealthy and needs repair:
 
-You can manually check the health state of your nodes with kubectl.
+* The node reports the **NotReady** status on consecutive checks within a 10-minute time frame.
+* The node doesn't report any status within 10 minutes.
 
-```
-kubectl get nodes
-```
+You can manually check the health state of your nodes with the `kubectl get nodes` command.
 
 ## How automatic repair works
 
-> [!Note]
+> [!NOTE]
 > AKS initiates repair operations with the user account **aks-remediator**.
 
-If AKS identifies an unhealthy node that remains unhealthy for 5 minutes, AKS takes the following actions:
+If AKS identifies an unhealthy node that remains unhealthy for *five* minutes, AKS performs the following actions:
+
+1. Attempts to restart the node.
+2. If the node restart is unsuccessful, AKS reimages the node.
+3. If the reimage is unsuccessful and it's a Linux node, AKS redeploys the node.
 
-1. Restarts the node.
-1. If the restart is unsuccessful, reimages the node.
-1. If the reimage is unsuccessful, and this is a Linux node, redeploys the node.
+AKS engineers investigate alternative remediations if auto-repair is unsuccessful.
 
-Alternative remediations are investigated by AKS engineers if auto-repair is unsuccessful. 
-As well as if you want to get the node to reimage you can always add the nodeCondition "customerMarkedAsUnhealthy": true, and remediator will reimage your node that way. 
+If you want the remediator to reimage the node, you can add the `nodeCondition "customerMarkedAsUnhealthy": true`.
 
-## Node Autodrain
-[Scheduled Events][scheduled-events] can occur on the underlying virtual machines (VMs) in any of your node pools. For [spot node pools][spot-node-pools], scheduled events may cause a *preempt* node event for the node. Certain node events, such as  *preempt*, cause AKS node autodrain to attempt a cordon and drain of the affected node, which allows for a graceful reschedule of any affected workloads on that node. When this happens, you might notice the node to receive a taint with *"remediator.aks.microsoft.com/unschedulable"*, because of *"kubernetes.azure.com/scalesetpriority: spot"*.
+## Node auto-drain
 
+[Scheduled events][scheduled-events] can occur on the underlying VMs in any of your node pools. For [spot node pools][spot-node-pools], scheduled events may cause a *preempt* node event for the node. Certain node events, such as  *preempt*, cause AKS node auto-drain to attempt a cordon and drain of the affected node. This process enables rescheduling for any affected workloads on that node. You might notice the node receives a taint with `"remediator.aks.microsoft.com/unschedulable"`, because of `"kubernetes.azure.com/scalesetpriority: spot"`.
 
-The following table shows the node events, and the actions they cause for AKS node autodrain.
+The following table shows the node events and actions they cause for AKS node auto-drain:
 
 | Event | Description |   Action   |
 | --- | --- | --- |
-| Freeze | The VM is scheduled to pause for a few seconds. CPU and network connectivity may be suspended, but there is no impact on memory or open files  | No action |
-| Reboot | The VM is scheduled for reboot. The VM's non-persistent memory is lost. | No action | 
-| Redeploy | The VM is scheduled to move to another node. The VM's ephemeral disks are lost. | Cordon and drain |
+| Freeze | The VM is scheduled to pause for a few seconds. CPU and network connectivity may be suspended, but there's no impact on memory or open files.  | No action. |
+| Reboot | The VM is scheduled for reboot. The VM's non-persistent memory is lost. | No action. |
+| Redeploy | The VM is scheduled to move to another node. The VM's ephemeral disks are lost. | Cordon and drain. |
 | Preempt | The spot VM is being deleted. The VM's ephemeral disks are lost. | Cordon and drain |
-| Terminate | The VM is scheduled to be deleted.| Cordon and drain |
-
-
+| Terminate | The VM is scheduled for deletion.| Cordon and drain. |
 
 ## Limitations
 
-In many cases, AKS can determine if a node is unhealthy and attempt to repair the issue, but there are cases where AKS either can't repair the issue or can't detect that there is an issue. For example, AKS can't detect issues if a node status is not being reported due to error in network configuration, or has failed to initially register as a healthy node.
+In many cases, AKS can determine if a node is unhealthy and attempt to repair the issue. However, there are cases where AKS either can't repair the issue or detect that an issue exists. For example, AKS can't detect issues in the following example scenarios:
+
+* A node status isn't being reported due to error in network configuration.
+* A node failed to initially register as a healthy node.
 
 ## Next steps
 
-Use [Availability Zones][availability-zones] to increase high availability with your AKS cluster workloads.
+Use [availability zones][availability-zones] to increase high availability with your AKS cluster workloads.
 
-<!-- LINKS - External -->
 <!-- LINKS - Internal -->
 [availability-zones]: ./availability-zones.md
 [vm-updates]: ../virtual-machines/maintenance-and-updates.md

articles/communication-services/tutorials/chat-interop/includes/meeting-interop-features-file-attachment-javascript.md

@@ -1,6 +1,6 @@
 ---
 title: Tutorial - Enable File Attachment Support
-author: jopeng
+author: jpeng-ms
 ms.author: jopeng
 ms.date: 05/26/2023
 ms.topic: include

articles/communication-services/tutorials/chat-interop/meeting-interop-features-inline-image.md

@@ -1,8 +1,8 @@
 ---
 title: Enable Inline Image Support in your Chat app
 titleSuffix: An Azure Communication Services quickstart
-description: In this tutorial, you'll learn how to enable inline image interoperability with the Azure Communication Chat SDK
-author: jopeng
+description: In this tutorial, you learn how to enable inline image interoperability with the Azure Communication Chat SDK.
+author: jpeng-ms
 ms.author: jopeng
 ms.date: 03/27/2023
 ms.topic: quickstart
@@ -13,13 +13,16 @@ ms.custom: mode-other
 
 # Tutorial: Enable inline image support in your Chat app
 
-## Add inline image support
 The Chat SDK is designed to work with Microsoft Teams seamlessly. Specifically, Chat SDK provides a solution to receive inline images sent by users from Microsoft Teams. Currently this feature is only available in the Chat SDK for JavaScript. 
 
-The Chat SDK for JavaScript provides `previewUrl` and `url` for each inline image. Please note that some GIF images fetched from `previewUrl` might not be animated and a static preview image would be returned instead. Developers are expected to use the `url` if the intention is to fetch animated images only.
-
 [!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
 
+## Add inline image support
+
+Inline images are images that are copied and pasted directly into the send box of the Teams client. For images that were uploaded via the "Upload from this device" menu or via drag-and-drop, such as images dragged directly to the send box in Teams, you need to refer to [this tutorial](./meeting-interop-features-file-attachment.md) to enable it as the part of the file sharing feature. (See the section "Handling Image Attachment.") To copy an image, the Teams user can either use their operating system's context menu to copy the image file and then paste it into the send box of their Teams client or use keyboard shortcuts.
+
+The Chat SDK for JavaScript provides `previewUrl` and `url` for each inline image. Note that some GIF images fetched from `previewUrl` might not be animated, and a static preview image may be returned instead. Developers are expected to use the `url` if the intention is to fetch animated images only.
+
 [!INCLUDE [Teams Inline Image Interop with JavaScript SDK](./includes/meeting-interop-features-inline-image-javascript.md)]
 
 ## Next steps

articles/iot-hub/.openpublishing.redirection.iot-hub.json

@@ -1357,6 +1357,11 @@
       "source_path_from_root": "/articles/iot-hub/iot-hub-device-management-iot-toolkit.md",
       "redirect_url": "/azure/iot-hub/reference-iot-hub-extension",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-hub/iot-hub-device-management-iot-extension-azure-cli-2-0.md",
+      "redirect_url": "/azure/iot-hub/reference-iot-hub-extension",
+      "redirect_document_id": false
     }
   ]
 }

articles/iot-hub/TOC.yml

@@ -448,8 +448,6 @@
               href: iot-hub-raspberry-pi-kit-c-get-started.md
     - name: Extended IoT scenarios
       items:
-        - name: Device management with IoT extension for Azure CLI
-          href: iot-hub-device-management-iot-extension-azure-cli-2-0.md
         - name: Remote monitoring and notifications with Logic Apps
           href: iot-hub-monitoring-notifications-with-azure-logic-apps.md
     - name: Troubleshoot and problem solution