Revert changes

Author: asergaz

articles/iot-operations/connect-to-cloud/howto-configure-adx-endpoint.md

@@ -159,7 +159,7 @@ To use these authentication methods, the Azure IoT Operations Arc extension must
 
 ### System-assigned managed identity
 
-Azure IoT Operations creates the managed identity automatically and assigns it to the Azure Arc-enabled Kubernetes cluster. It eliminates the need for secret management and allows for seamless authentication.
+Using the system-assigned managed identity is the recommended authentication method for Azure IoT Operations. Azure IoT Operations creates the managed identity automatically and assigns it to the Azure Arc-enabled Kubernetes cluster. It eliminates the need for secret management and allows for seamless authentication.
 
 In the *DataflowEndpoint* resource, specify the managed identity authentication method. In most cases, you don't need to specify other settings. This configuration creates a managed identity with the default audience `https://api.kusto.windows.net`.
 

articles/iot-operations/connect-to-cloud/howto-configure-fabric-endpoint.md

@@ -176,7 +176,7 @@ To learn more, see [Give access to a workspace](/fabric/get-started/give-access-
 
 ### System-assigned managed identity
 
-Azure IoT Operations creates the managed identity automatically and assigns it to the Azure Arc-enabled Kubernetes cluster. It eliminates the need for secret management and allows for seamless authentication.
+Using the system-assigned managed identity is the recommended authentication method for Azure IoT Operations. Azure IoT Operations creates the managed identity automatically and assigns it to the Azure Arc-enabled Kubernetes cluster. It eliminates the need for secret management and allows for seamless authentication.
 
 In the *DataflowEndpoint* resource, specify the managed identity authentication method. In most cases, you don't need to specify other settings. This configuration creates a managed identity with the default audience.