This line would send mdsd.err logs to the Azure extension status message in the portal if new ones were found while LAD was running successfully. However, this was leading to noise from the customer's perspective - they were seeing error messages output even when provisioning succeeded. Specifically, there was one transient situation where we'd fail initially but succeed on a retry during initial startup, and the logs output to mdsd.err on the initial failure were causing red herrings.
This removes updating the status message in Azure Portal with these log messages, to minimize confusion as to if LAD is running successfully or not.
This line would send mdsd.err logs to the Azure extension status message in the portal if new ones were found while LAD was running successfully. However, this was leading to noise from the customer's perspective - they were seeing error messages output even when provisioning succeeded. Specifically, there was one transient situation where we'd fail initially but succeed on a retry during initial startup, and the logs output to mdsd.err on the initial failure were causing red herrings.
This removes updating the status message in Azure Portal with these log messages, to minimize confusion as to if LAD is running successfully or not.