Merge pull request #8558 from MicrosoftDocs/main

Publish 09/27/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/intune/fundamentals/licenses-assign.md

@@ -26,6 +26,7 @@ ms.custom: intune-classic; get-started
 ms.collection: 
   - M365-identity-device-management
   - highpri
+  - EngageScoreOct2022
 ---
 
 # Assign licenses to users so they can enroll devices in Intune

memdocs/intune/protect/encrypt-devices.md

@@ -215,7 +215,7 @@ Following are the relevant settings for each profile type:
 
 ### View details for recovery keys
 
-Intune provides access to the Azure AD blade for BitLocker so you can view BitLocker Key IDs and recovery keys for your Windows 10/11 devices, from within the Microsoft Endpoint Manager admin center. Support to view recovery keys can also [extend to your tenant-attached devices](#view-recovery-keys-for-tenant-attached devices).
+Intune provides access to the Azure AD blade for BitLocker so you can view BitLocker Key IDs and recovery keys for your Windows 10/11 devices, from within the Microsoft Endpoint Manager admin center. Support to view recovery keys can also [extend to your tenant-attached devices](#view-recovery-keys-for-tenant-attached-devices).
 
 To be accessible, the device must have its keys escrowed to Azure AD.
 

windows-365/enterprise/TOC.yml

@@ -145,6 +145,8 @@ items:
       items:
       - name: Overview
         href: device-management-overview.md
+      - name: Alerts
+        href: alerts.md
       - name: Remotely manage Cloud PC devices 
         href: remotely-manage-cloud-pc.md
       - name: RDP Shortpath for public networks 

windows-365/enterprise/alerts.md

@@ -0,0 +1,59 @@
+---
+# required metadata
+title: Alerts in Windows 365
+titleSuffix:
+description: Learn how view, create, and customize alerts in Windows 365.
+keywords:
+author: ErikjeMS  
+ms.author: erikje
+manager: dougeby
+ms.date: 9/26/2022
+ms.topic: how-to
+ms.service: cloudpc
+ms.subservice:
+ms.localizationpriority: high
+ms.technology:
+ms.assetid: 
+
+# optional metadata
+
+#ROBOTS:
+#audience:
+
+ms.reviewer: feadebay
+ms.suite: ems
+search.appverid: MET150
+#ms.tgt_pltfrm:
+ms.custom: intune-azure; get-started
+ms.collection: M365-identity-device-management
+---
+
+# Alerts in Windows 365
+
+The Windows 365 Alerts system notifies you when specific events occur in your Cloud PC environment, like connection, provisioning, or image upload failures. By default, these alerts appear in the Microsoft Endpoint manager admin center as pop-up notifications (you can also turn on email notifications). You can customize the built-in alert rules:
+
+- Set conditions and thresholds for triggering alerts.
+- Define the severity of alerts.
+- Turn each alert rule on or off.
+- Configure each alert to notify you in the console and/or by email.
+
+## View alerts
+
+To view the list of recent alerts, sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Tenant administration** > **Alerts (preview)**.
+
+![Screenshot of view alerts](./media/alerts/view-alerts.png)
+
+## Customize alert rule
+
+1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Tenant administration** > **Alerts (preview)** > **Alert rules**.
+    ![Screenshot of view alert rules.](./media/alerts/view-alert-rules.png)
+
+2. Select a rule in the list.
+3. On the **System rule** page, make any changes that you want in the **Conditions**, **Settings**, and **Notifications** sections.
+    ![Screenshot of system rule.](./media/alerts/system-rule.png)
+4. Select **Apply** to save the changes to the rule.
+
+<!-- ########################## -->
+## Next steps
+
+For more troubleshooting information, see [Troubleshooting](troubleshooting.md).

windows-365/enterprise/health-checks-connectivity.md

@@ -32,45 +32,39 @@ ms.collection: M365-identity-device-management
 
 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.
+You can review any failed connectivity checks 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)**.
+2. Select a connection in the list > **Overview** > **Performance (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.
+If there is a problem with the Cloud PC's connection due to malfunctioning components, 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.
+When a connectivity check fails, you'll see one of the following messages. 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.
+- **DomainReachable**: This Cloud PC can't connect to the domain. Review your Azure Virtual Network checks. 
+- **DomainTrust**: The domain doesn't trust this Cloud PC. Make sure 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. 
 - **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.
-
+- **UrlsAccesibleCheck**: This Cloud PC is blocking traffic to [these URLs](requirements.md).
 
 <!--
 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.
@@ -84,7 +78,7 @@ The user connectivity history report shows when a user started a connection and
 ### 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**.
+2. Select a connection in the list > **Overview** > **Performance (preview)** > **View connectivity history**.
 
 ### Activities
 
@@ -98,6 +92,8 @@ The report shows of the following activities:
 
 Select any activity to get more information about the event.
 
+The connectivity history report will provide visibility to other activities within a 1-hour period of a connectivity error or failed check.  As an example, if a user attempts to connect to their Cloud PC, and is not able to, the health checks and successful sign-in activity within 1 hour prior/after of the error will show as well.  This allows an admin to evaluate an error, possible cause, and if/when the system became healthy again.
+
 <!-- ########################## -->
 ## Next steps
 

windows-365/enterprise/media/alerts/system-rule.png

@@ -42,8 +42,8 @@ Admins need only provide a few configuration details to set up the provisioning
 At a high level, the full provisioning process looks like this:
 
 1. You [create a provisioning policy](create-provisioning-policy.md) to manage who gets access to Cloud PCs. The provisioning policies are the engines that build, configure, and make Cloud PCs available to end users. Within a policy, you’ll provide details for the network, the [image](device-images.md) used to create each Cloud PC, and an Azure Active Directory (Azure AD) user group.
-2. When a user in the Azure AD user group is assigned a Windows 365 license, Windows 365 automatically provisions a Cloud PC and sends access information to the user. This automation has three stages, which are invisible to the administrator. For more information on this automated process, see the [Details of the automated provisioning process article](automated-provisioning-steps.md).
-3. The end user receives the access information and can then sign in to the Windows Cloud PC from anywhere.
+2. When a user in the Azure AD user group is assigned a Windows 365 license, Windows 365 automatically provisions a Cloud PC for the user. This automation has three stages, which are invisible to the administrator. For more information on this automated process, see the [Details of the automated provisioning process article](automated-provisioning-steps.md).
+3. Once provisioned, the end user can then sign in to the Windows Cloud PC from anywhere.
 
 ## Provisioning policy objects
 

windows-365/enterprise/media/alerts/view-alert-rules.png

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 03/10/2022 
+ms.date: 09/27/2022 
 ms.topic: overview
 ms.service: cloudpc
 ms.subservice:
@@ -59,6 +59,7 @@ You must allow traffic in your Azure network configuration to the following serv
 - rdweb.wvd.microsoft.com
 - rdbroker.wvd.microsoft.com
 - Provisioning and Azure network connection endpoints:
+  - \*.infra.windows365.microsoft.com
   - cpcsaamssa1prodprap01.blob.core.windows.net
   - cpcsaamssa1prodprau01.blob.core.windows.net
   - cpcsaamssa1prodpreu01.blob.core.windows.net