Skip to content

Commit dd16eaf

Browse files
author
Angela Fleischmann
authored
Merge pull request #8550 from abrahamp91/patch-26
Update health-checks-connectivity.md
2 parents 695118e + 2365c80 commit dd16eaf

1 file changed

Lines changed: 10 additions & 14 deletions

File tree

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

Lines changed: 10 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -32,45 +32,39 @@ ms.collection: M365-identity-device-management
3232

3333
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.
3434

35-
You can review any connectivity errors and use the **Troubleshoot this connection** button to troubleshoot.
35+
You can review any failed connectivity checks and use the **Troubleshoot this connection** button to troubleshoot.
3636

3737
## View Cloud PC connectivity status
3838

3939
1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **All Cloud PCs**.
40-
2. Select a connection in the list > **Overview** > **Connectivity and usage (preview)**.
40+
2. Select a connection in the list > **Overview** > **Performance (preview)**.
4141

4242
If the Cloud PC is connected, the status will show as **Available**.
4343

44-
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.
44+
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.
4545

4646
## Connectivity errors
4747

48-
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.
48+
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.
4949

50-
- **Azure Resource Availability Check**: Azure resources are not up and running.
5150
- **DomainJoin**: This Cloud PC isn't joined to a domain.
52-
- **omainReachable**: This Cloud PC can't connect to the domain.
53-
- **DomainTrust**: The domain doesn't trust this Cloud PC.
51+
- **DomainReachable**: This Cloud PC can't connect to the domain. Review your Azure Virtual Network checks.
52+
- **DomainTrust**: The domain doesn't trust this Cloud PC. Make sure the local device password matches the device password in the domain.
5453
- **SxSStackListener**: The side-by-side stack installed on the Cloud PC is malfunctioning or blocked.
5554
- **Unknown**: This Cloud PC might not be running or the network isn't connected to the public Internet.
56-
- **UrlsAccesible**: This Cloud PC is blocking traffic to [these URLs](requirements.md).
57-
- **VM Power Status Check**: This Cloud PC is powered off and an issue is preventing it from turning back on.
58-
55+
- **UrlsAccesibleCheck**: This Cloud PC is blocking traffic to [these URLs](requirements.md).
5956

6057
<!--
6158
Possible different view of this data:
6259
6360
| Check | Failure description | Troubleshooting |
6461
| --- | --- | --- |
65-
| Azure Resource Availability Check | Azure resources are not up and running. | If this persists, contact Microsoft support. |
6662
| DomainJoin | This Cloud PC isn't joined to a domain. | Try reprovisioning the Cloud PC or join it to a domain. |
6763
| 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). |
6864
| DomainTrust | The domain doesn't trust this Cloud PC. | Make sure that the local device password matches the device password in the domain. |
6965
| SxSStackListener | The side-by-side stack installed on the Cloud PC is malfunctioning or blocked. | Run the troubleshooting tool to fix this issue. |
7066
| 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. |
7167
| UrlsAccesible | This Cloud PC is blocking traffic to [these URLs](requirements.md). | Unblock the URLs this Cloud PC uses to connect to Windows 365. |
72-
| 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. |
73-
7468
7569
-->
7670
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
8478
### View Connectivity history report
8579

8680
1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **All Cloud PCs**.
87-
2. Select a connection in the list > **Overview** > **Connectivity and usage (preview)** > **View connectivity history**.
81+
2. Select a connection in the list > **Overview** > **Performance (preview)** > **View connectivity history**.
8882

8983
### Activities
9084

@@ -98,6 +92,8 @@ The report shows of the following activities:
9892

9993
Select any activity to get more information about the event.
10094

95+
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.
96+
10197
<!-- ########################## -->
10298
## Next steps
10399

0 commit comments

Comments
 (0)