Merge pull request #216210 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/defender-for-iot/device-builders/concept-agent-portfolio-overview-os-support.md

@@ -27,8 +27,6 @@ For additional information on supported operating systems, or to request access
 
 ## Azure RTOS micro agent
 
-The Microsoft Defender for IoT micro agent provides a comprehensive and lightweight security solution for devices that use Azure RTOS. Microsoft Defender for IoT micro agent provides coverage for common threats, and potential malicious activities on real-time operating system (RTOS) devices. The micro agent comes built in as part of the Azure RTOS NetX Duo component, and monitors the device's network activity.
-
 The Microsoft Defender for IoT micro agent comes built in as part of the Azure RTOS NetX Duo component, and monitors the device's network activity. The micro agent consists of a comprehensive and lightweight security solution that provides coverage for common threats, and potential malicious activities on a real-time operating system (RTOS) devices.
 
 ## Next steps

articles/iot-edge/how-to-connect-downstream-iot-edge-device.md

@@ -231,7 +231,7 @@ You should already have IoT Edge installed on your device. If not, follow the st
 
     ```toml
     [agent.config]
-    image: "mcr.microsoft.com/azureiotedge-agent:1.4"
+    image = "mcr.microsoft.com/azureiotedge-agent:1.4"
     ```
 
 01. The beginning of your parent configuration file should look similar to the following example.

articles/partner-solutions/elastic/troubleshoot.md

@@ -13,7 +13,7 @@ This document contains information about troubleshooting your solutions that use
 
 ## Unable to create an Elastic resource
 
-Elastic integration with Azure can only be set up by users who have *Owner* access on the Azure subscription. [Confirm that you have the appropriate access](../../role-based-access-control/check-access.md).
+Elastic integration with Azure can only be set up by users who have *Owner* or *Contributor* access on the Azure subscription. [Confirm that you have the appropriate access](../../role-based-access-control/check-access.md).
 
 ## Logs not being emitted to Elastic
 
@@ -43,4 +43,4 @@ In the Elastic site, open a support request.
 
 ## Next steps
 
-Learn about [managing your instance](manage.md) of Elastic.
+Learn about [managing your instance](manage.md) of Elastic.