Merge branch 'main' of https://github.com/microsoftdocs/memdocs-pr into erikre-2210ID-15477561

Erikre · Erikre · commit 79bd6dc0f0bb · 2022-09-23T10:15:38.000-07:00
diff --git a/memdocs/intune/configuration/settings-catalog-printer-provisioning.md b/memdocs/intune/configuration/settings-catalog-printer-provisioning.md
@@ -7,7 +7,7 @@ keywords:
 author: MandiOhlinger
 ms.author: mandia
 manager: dougeby
-ms.date: 07/21/2022
+ms.date: 09/22/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: configuration
@@ -38,7 +38,7 @@ Using the settings catalog in Intune, you can create a printer policy, and deplo
 This feature applies to:
 
 - Windows 11
-- Windows 10 and later
+- Windows 10 21H2 with [July 2022 update](https://support.microsoft.com/topic/july-12-2022-kb5015807-os-builds-19042-1826-19043-1826-and-19044-1826-8c8ea8fe-ec83-467d-86fb-a2f48a85eb41) and later
 
 This article shows you how to create a Universal Print policy in Microsoft Intune. To learn more about Universal Print and onboarding, go to [What is Universal Print](/universal-print/fundamentals/universal-print-whatis) and [Set up Universal Print](/universal-print/fundamentals/universal-print-getting-started).
 
diff --git a/memdocs/intune/fundamentals/deployment-guide-enrollment-android.md b/memdocs/intune/fundamentals/deployment-guide-enrollment-android.md
@@ -294,7 +294,7 @@ There are some situations when you must use Device Administrator enrollment:
 - Android Enterprise requires access to Google services. Google services may not be available because of geography, or because of the device manufacturer. For example:
 
   - There are places where Google services aren’t available, like China. In this situation, use Android device administrator enrollment.  
-  - Some devices are based on Android, but don't have access to Google Services, such as Amazon Fire tablets. In this situation, use Android device administrator enrollment.
+  - Some devices are based on Android, but don't have access to Google Services, such as Microsoft Teams Android devices and Amazon Fire tablets. In this situation, use Android device administrator enrollment.
 
 - Android OS versions older than 5.0 must use Android device administrator enrollment. Android Enterprise enrollment isn't an option.
 
diff --git a/memdocs/intune/protect/antivirus-microsoft-defender-settings-macos.md b/memdocs/intune/protect/antivirus-microsoft-defender-settings-macos.md
@@ -22,7 +22,7 @@ search.appverid: MET150
 #ms.tgt_pltfrm:
 ms.custom: intune-azure
 ms.collection: M365-identity-device-management
-ms.reviewer: laarrizz
+ms.reviewer: laarrizz        
 
 ---
 
diff --git a/memdocs/intune/protect/app-based-conditional-access-intune.md b/memdocs/intune/protect/app-based-conditional-access-intune.md
@@ -67,7 +67,7 @@ In this example, the admin has applied app protection policies to the Outlook ap
 
 1. The user tries to authenticate to Azure AD from the Outlook app.
 
-2. The user gets redirected to the app store to install a broker app when trying to authenticate for the first time. The broker app can be the Microsoft Authenticator for iOS, or either the Microsoft Authenticator or Microsoft Company portal for Android devices.
+2. The user gets redirected to the app store to install a broker app when trying to authenticate for the first time. The broker app can be the Microsoft Authenticator for iOS, or Microsoft Company portal for Android devices.
 
    If users try to use a native e-mail app, they'll be redirected to the app store to then install the Outlook app.
 
diff --git a/memdocs/intune/protect/endpoint-protection-configure.md b/memdocs/intune/protect/endpoint-protection-configure.md
@@ -24,7 +24,7 @@ search.appverid: MET150
 #ms.tgt_pltfrm:
 ms.custom: intune-azure
 ms.collection: M365-identity-device-management
-mr.reviewer: karthib
+ms.reviewer: mattcall
 ---
 
 # Add Endpoint protection settings in Intune
diff --git a/memdocs/intune/protect/endpoint-protection-macos.md b/memdocs/intune/protect/endpoint-protection-macos.md
@@ -19,6 +19,7 @@ ms.technology:
 #ROBOTS:
 #audience:
 
+ms.reviewer: mattcall
 ms.suite: ems
 search.appverid: MET150
 #ms.tgt_pltfrm:
diff --git a/memdocs/intune/protect/includes/security-config-mgt-prerequisites.md b/memdocs/intune/protect/includes/security-config-mgt-prerequisites.md
@@ -118,7 +118,8 @@ To support Microsoft Defender for Endpoint security configuration management thr
 
 1. Sign in to [Microsoft 365 Defender portal](https://security.microsoft.com/) and go to **Settings** > **Endpoints** > **Configuration Management** > **Enforcement Scope** and enable the platforms for security settings management:
    :::image type="content" source="../media/mde-security-integration/enable-mde-settings-management-defender.png" alt-text="Enable Microsoft Defender for Endpoint settings management in the Microsoft 365 Defender portal.":::
-1. Configure Pilot Mode and Configuration Manager authority settings to fit your organization needs:
+1. Configure Pilot Mode and Configuration Manager authority settings to fit your organization's needs.
+1. Uncheck both **Windows Client devices** and **Windows Server devices** to be able to use Pilot Mode using tagging:  
    :::image type="content" source="../media/mde-security-integration/pilot-CMAuthority-mde-settings-management-defender.png" alt-text="Configure Pilot mode for Endpoint settings management in the Microsoft 365 Defender portal.":::
    > [!TIP]
    > Use pilot mode and the proper device tags to test and validate your rollout on a small number of devices. Without using pilot mode, any device that falls into the scope configured will automatically be enrolled.
diff --git a/memdocs/intune/protect/media/mde-security-integration/pilot-CMAuthority-mde-settings-management-defender.png b/memdocs/intune/protect/media/mde-security-integration/pilot-CMAuthority-mde-settings-management-defender.png
diff --git a/memdocs/intune/protect/microsoft-tunnel-prerequisites.md b/memdocs/intune/protect/microsoft-tunnel-prerequisites.md
@@ -405,15 +405,15 @@ To use the readiness tool:
 
    You can run the script from any Linux server that is on the same network as the server you plan to install, allowing network admins to run it and troubleshoot network issues independently.
 
-2. To validate your network configuration, run the script with the following commands to first set the execute permissions on the script and then to validate the Tunnel can connect to the correct endpoints:
+2. To validate your network and Linux configuration, run the script with the following commands to set the execute permissions on the script, to validate the Tunnel can connect to the correct endpoints, and then to check for the presence of utilities that Tunnel uses:
 
    - `sudo chmod +x ./mst-readiness`
-   - `sudo ./mst-readiness network`
 
-   The second command runs the following actions and reports on success or error for both:
+   - `sudo ./mst-readiness network` - This command runs the following actions and reports on success or error for both:
+     - Tries to connect to each Microsoft endpoint the tunnel will use.
+     - Checks that the required ports are open in your firewall.
 
-   - Tries to connect to each Microsoft endpoint the tunnel will use.
-   - Checks that the required ports are open in your firewall.
+   - `sudo ./mst-readiness utils` - This command validates that utilities that are used by Tunnel like Docker or Podman and ip_tables are available.
 
 3. To validate that the account you’ll use to install Microsoft Tunnel has the required roles and permissions to complete enrollment, run the script with the following command line: `./mst-readiness account`
 
diff --git a/memdocs/intune/protect/toc.yml b/memdocs/intune/protect/toc.yml
@@ -237,6 +237,11 @@ items:
         items:
         - name: Symantec and Intune integration
           href: skycure-mtd-connector-integration.md
+      - name: Set up Trend Micro Mobile Security as a Service
+        href: trend-micro-mobile-threat-defense-connector.md
+        items:
+        - name: Trend Micro Mobile Security as a Service and Intune integration
+          href: trend-micro-mtd-connector-integration.md 
       - name: Set up Wandera
         href: wandera-mtd-connector.md
         items:
diff --git a/memdocs/intune/protect/tutorial-protect-email-on-enrolled-devices.md b/memdocs/intune/protect/tutorial-protect-email-on-enrolled-devices.md
@@ -21,7 +21,7 @@ ms.assetid:
 #ROBOTS:
 #audience:
 
-ms.reviewer:
+ms.reviewer: demerson
 ms.suite: ems
 search.appverid: MET150
 #ms.tgt_pltfrm:
diff --git a/memdocs/intune/protect/tutorial-protect-email-on-unmanaged-devices.md b/memdocs/intune/protect/tutorial-protect-email-on-unmanaged-devices.md
@@ -21,7 +21,7 @@ ms.assetid:
 #ROBOTS:
 #audience:
 
-ms.reviewer:
+ms.reviewer: demerson
 ms.suite: ems
 #ms.tgt_pltfrm:
 ms.custom: intune-azure
diff --git a/windows-365/enterprise/health-checks-connectivity.md b/windows-365/enterprise/health-checks-connectivity.md
@@ -0,0 +1,104 @@
+---
+# required metadata
+title: Connectivity health checks in Windows 365
+titleSuffix:
+description: Learn about connectivity health checks.
+keywords:
+author: ErikjeMS
+ms.author: erikje
+manager: dougeby
+ms.date: 09/22/2022
+ms.topic: how-to
+ms.service: cloudpc
+ms.subservice:
+ms.localizationpriority: high
+ms.technology:
+ms.assetid: 
+
+# optional metadata
+
+#ROBOTS:
+#audience:
+
+ms.reviewer: abpineda
+ms.suite: ems
+search.appverid: MET150
+#ms.tgt_pltfrm:
+ms.custom: intune-azure; get-started
+ms.collection: M365-identity-device-management
+---
+
+# Connectivity health checks
+
+Connectivity health checks are run on individual Cloud PCs and give information on the state of the Cloud PC's connection. These checks are constantly run by the Windows 365 service in the backend. When any of these checks fail, the end user won’t be able to connect to their Cloud PC.
+
+You can review any connectivity errors and use the **Troubleshoot this connection** button to troubleshoot.
+
+## View Cloud PC connectivity status
+
+1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **All Cloud PCs**.
+2. Select a connection in the list > **Overview** > **Connectivity and usage (preview)**.
+
+If the Cloud PC is connected, the status will show as **Available**.
+
+If there is a problem with the Cloud PC's connection, the status will show as **Unavailable**. Details appear on the right. Select **Troubleshoot this connection** to troubleshoot the issue.
+
+## Connectivity errors
+
+When a connectivity check fails, you'll see one of the following errors. Review the status pane to see more details. You can use the **Troubleshoot this connection** button to troubleshoot.
+
+- **Azure Resource Availability Check**: Azure resources are not up and running.
+- **DomainJoin**: This Cloud PC isn't joined to a domain.
+- **omainReachable**: This Cloud PC can't connect to the domain.
+- **DomainTrust**: The domain doesn't trust this Cloud PC.
+- **SxSStackListener**: The side-by-side stack installed on the Cloud PC is malfunctioning or blocked. 
+- **Unknown**: This Cloud PC might not be running or the network isn't connected to the public Internet.
+- **UrlsAccesible**: This Cloud PC is blocking traffic to [these URLs](requirements.md).
+- **VM Power Status Check**: This Cloud PC is powered off and an issue is preventing it from turning back on.
+
+
+<!--
+Possible different view of this data:
+
+| Check | Failure description | Troubleshooting |
+| --- | --- | --- |
+| Azure Resource Availability Check | Azure resources are not up and running. | If this persists, contact Microsoft support. |
+| DomainJoin | This Cloud PC isn't joined to a domain. | Try reprovisioning the Cloud PC or join it to a domain. |
+| DomainReachable | This Cloud PC can't connect to the domain. | Check for an issue with your virtual network configuration by reviewing your [Azure network connection checks](troubleshoot-azure-network-connection.md). |
+| DomainTrust | The domain doesn't trust this Cloud PC. | Make sure that the local device password matches the device password in the domain. |
+| SxSStackListener | The side-by-side stack installed on the Cloud PC is malfunctioning or blocked. | Run the troubleshooting tool to fix this issue. |
+| Unknown | This Cloud PC might not be running or the network isn't connected to the public Internet. | Run the troubleshooting tool to get more information. |
+| UrlsAccesible | This Cloud PC is blocking traffic to [these URLs](requirements.md). | Unblock the URLs this Cloud PC uses to connect to Windows 365. |
+| VM Power Status Check | This Cloud PC is powered off and an issue is preventing it from turning back on. |  If this persists, contact Microsoft support. |
+
+
+-->
+If any of these issues persist, contact Microsoft support.
+
+Connectivity errors can occur even when all connectivity health checks have successfully passed.
+
+## User connectivity history report
+
+The user connectivity history report shows when a user started a connection and when the connection finished. There are different ways a connection can start/finish and these are logged as activities in the report.
+
+### View Connectivity history report
+
+1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **All Cloud PCs**.
+2. Select a connection in the list > **Overview** > **Connectivity and usage (preview)** > **View connectivity history**.
+
+### Activities
+
+The report shows of the following activities:
+
+| Activity | Description |
+| --- | --- | --- |
+| Connection started | The user successfully connected to their Cloud PC. |
+| Connection finished | The user signs out of their Cloud PC or finishes their work session. If the connection fails because of an unexpected network connectivity error, it's listed as a **Connection finished** with a **Failure** status.|
+| Connectivity check | If the connection fails because of a failed connectivity check, the failed check is listed. |
+
+Select any activity to get more information about the event.
+
+<!-- ########################## -->
+## Next steps
+
+[Learn more about Azure network connections](azure-network-connections.md).
diff --git a/windows-365/enterprise/in-development.md b/windows-365/enterprise/in-development.md
@@ -87,7 +87,7 @@ You'll be able to set up system alerts and automated emails to be notified when
 ### Cloud PC utilization report<!--40636545-->
 A new report will be available for Cloud PCs. The **Cloud PC utilization** report will show how many hours users have been connected to their Cloud PCs. Information for individual Cloud PCs and aggregated data will be shown.
 
-### Cloud PC wit connection quality issues report<!--40636545-->
+### Cloud PC with connection quality issues report<!--40636545-->
 A new report will be available for Cloud PCs. The **Cloud PCs with connection quality issues** report will show information for round-trip time, available bandwidth, and remoting sign-in time. Information for individual Cloud PCs and aggregated data will be shown.
 
 ### Review Cloud PC connectivity health checks and errors in Microsoft Endpoint Manager admin center<!--38469622 -->
