Merge pull request #220153 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/active-directory/conditional-access/howto-conditional-access-policy-compliant-device.md

@@ -55,7 +55,7 @@ The following steps will help create a Conditional Access policy to require mult
 After confirming your settings using [report-only mode](howto-conditional-access-insights-reporting.md), an administrator can move the **Enable policy** toggle from **Report-only** to **On**.
 
 > [!NOTE]
-> You can enroll your new devices to Intune even if you select **Require device to be marked as compliant** for **All users** and **All cloud apps** using the steps above. **Require device to be marked as compliant** control does not block Intune enrollment. 
+> You can enroll your new devices to Intune even if you select **Require device to be marked as compliant** for **All users** and **All cloud apps** using the steps above. **Require device to be marked as compliant** control does not block Intune enrollment and the access to the Microsoft Intune Web Company Portal application. 
 
 ### Known behavior
 

articles/active-directory/manage-apps/configure-admin-consent-workflow.md

@@ -59,4 +59,4 @@ To configure the admin consent workflow programmatically, use the [Update adminC
 
 [Grant tenant-wide admin consent to an application](grant-admin-consent.md)
 
-[Reivew admin consent requests](review-admin-consent-requests.md)
+[Review admin consent requests](review-admin-consent-requests.md)

articles/iot-edge/module-deployment-monitoring.md

@@ -18,6 +18,8 @@ Automatic deployments and layered deployment help you manage and configure modul
 
 Azure IoT Edge provides two ways to configure the modules to run on IoT Edge devices. The first method is to deploy modules on a per-device basis. You create a deployment manifest and then apply it to a particular device by name. The second method is to deploy modules automatically to any registered device that meets a set of defined conditions. You create a deployment manifest and then define which devices it applies to based on [tags](../iot-edge/how-to-deploy-at-scale.md#identify-devices-using-tags) in the device twin.
 
+You can't combine per-device and automatic deployments. Once you start targeting IoT Edge devices with automatic deployments (with or without layered deployments), per-device deployments are no longer supported.
+
 This article focuses on configuring and monitoring fleets of devices, collectively referred to as *IoT Edge automatic deployments*. The basic deployment steps are as follows:
 
 1. An operator defines a deployment that describes a set of modules and the target devices. Each deployment has a deployment manifest that reflects this information.

articles/machine-learning/how-to-troubleshoot-environments.md

@@ -58,7 +58,7 @@ Updates for AzureML based images are released regularly, with a commitment of no
 It's your responsibility to evaluate the threat and address vulnerabilities in environments.
 Not all the vulnerabilities are exploitable, so you need to use your judgment when choosing between reproducibility and resolving vulnerabilities.
 > [!IMPORTANT]
-> There's no guarantee that the same set of python dependencies will be materialized with an image rebuild or for a new environment with the same set of Python dependencies. 
+> There's no guarantee that the same set of Python dependencies will be materialized with an image rebuild or for a new environment with the same set of Python dependencies. 
 
 ## **Environment definition problems**
 

articles/synapse-analytics/monitoring/how-to-monitor-using-azure-monitor.md

@@ -106,6 +106,10 @@ Here are the logs emitted by Azure Synapse Analytics workspaces:
 | SynapseIntegrationActivityRuns | IntegrationActivityRuns | Azure Synapse integration activity runs. |
 | SynapseIntegrationTriggerRuns | IntegrationTriggerRuns | Azure Synapse integration trigger runs. |
 
+   > [!NOTE]  
+   > The event **SynapseBuiltinSqlReqsEnded** is only emitted for queries that read data from storage. It will not be emitted for queries that only process metadata.
+
+
 ### Dedicated SQL pool logs
 
 Here are the logs emitted by dedicated SQL pools: