Skip to content

Commit f77daeb

Browse files
committed
healch check connect
1 parent 0315217 commit f77daeb

1 file changed

Lines changed: 75 additions & 0 deletions

File tree

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
# required metadata
3+
title: Connectivity health checks in Windows 365
4+
titleSuffix:
5+
description: Learn about the health checks that are automatically run on Azure network connections.
6+
keywords:
7+
author: ErikjeMS
8+
ms.author: erikje
9+
manager: dougeby
10+
ms.date: 08/31/2022
11+
ms.topic: how-to
12+
ms.service: cloudpc
13+
ms.subservice:
14+
ms.localizationpriority: high
15+
ms.technology:
16+
ms.assetid:
17+
18+
# optional metadata
19+
20+
#ROBOTS:
21+
#audience:
22+
23+
ms.reviewer: abpineda
24+
ms.suite: ems
25+
search.appverid: MET150
26+
#ms.tgt_pltfrm:
27+
ms.custom: intune-azure; get-started
28+
ms.collection: M365-identity-device-management
29+
---
30+
31+
# Connectivity health checks
32+
33+
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.
34+
35+
Connectivity errors can occur even when all connectivity health checks have successfully passed.
36+
37+
## View connectivity checks
38+
39+
1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **Azure network connections**.
40+
2. Select a connection in the list > **Overview** > **Connectivity and usage (preview)**.
41+
42+
43+
An admin is also able to look at the connectivity history of a user to see if user might have experience failed connectivity check, or connectivity error in the last 14 days.
44+
45+
## Connectivity checks
46+
47+
| Check | Failure description | Troubleshooting |
48+
| --- | --- | --- |
49+
| Azure Resource Availability Check | Azure resources are not up and running. | If this persists, contact Microsoft support. |
50+
| DomainJoin | This Cloud PC isn't joined to a domain. | Try reprovisioning the Cloud PC or join it to a domain. |
51+
| 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). |
52+
| DomainTrust | The domain doesn't trust this Cloud PC. | Make sure that the local device password matches the device password in the domain. |
53+
| SxSStackListener | The side-by-side stack installed on the Cloud PC is malfunctioning or blocked. | Run the troubleshooting tool to fix this issue. |
54+
| 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. |
55+
| UrlsAccesible | This Cloud PC is blocking traffic to [these URLs](requirements.md). | Unblock the URLs this Cloud PC uses to connect to Windows 365. |
56+
| 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. |
57+
58+
If any of these issues persist, contact Microsoft support.
59+
60+
## User connectivity history report
61+
62+
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. The report shows of the following activities:
63+
64+
| Activity | Description |
65+
| --- | --- | --- |
66+
| Connection started | The user successfully connected to their Cloud PC. |
67+
| 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.|
68+
| Connectivity check | If the connection fails because of a failed connectivity check, the failed check is listed. |
69+
70+
Select any activity to get more information about the event.
71+
72+
<!-- ########################## -->
73+
## Next steps
74+
75+
[Learn more about Azure network connections](azure-network-connections.md).

0 commit comments

Comments
 (0)