microsoftgraph / microsoftgraph/msgraph-beta-sdk-dotnet
[Bug] CloudPC ConnectivityResult is empty for some hosts
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 112
- Forks
- 37
- Avg merge
- 14h 57m
- Merged PRs (30d)
- 3
Description
I'm trying to get a list of cloud PC hosts and select the ConnectivityResult for each host.
Unfortunately, the response does not include a ConnectivityResult for all hosts.
GET https://graph.microsoft.com/beta/deviceManagement/virtualEndpoint/cloudPCs?$select=id,displayName,connectivityResult
response:
{
"@odata.context": "https://graph.microsoft.com/beta/$metadata#deviceManagement/virtualEndpoint/cloudPCs(displayName,connectivityResult)",
"value": [
{
"id": "a33fffc8-1dee-4743-8598-37f9850824d2",
"displayName": "",
"connectivityResult": {
"status": "available",
"updatedDateTime": "0001-01-01T00:00:00Z",
"lastModifiedDateTime": "2026-01-23T12:36:14.4934096Z",
"failedHealthCheckItems": []
}
},
{
"id": "c3cd2780-e00f-498c-a674-1398a33487a1",
"displayName": "frontline-dedicated-2 - Cpc User 1",
"connectivityResult": null
}
]
}
On the other hand, I can get the same connectivity results for a single host:
GET https://graph.microsoft.com/beta/deviceManagement/virtualEndpoint/cloudPCs/c3cd2780-e00f-498c-a674-1398a33487a1?$select=id,displayName,connectivityResult
response
{
"@odata.context": "https://graph.microsoft.com/beta/$metadata#deviceManagement/virtualEndpoint/cloudPCs(id,displayName,connectivityResult)/$entity",
"id": "c3cd2780-e00f-498c-a674-1398a33487a1",
"displayName": "frontline-dedicated-2 - Cpc User 1",
"connectivityResult": {
"status": "available",
"updatedDateTime": "0001-01-01T00:00:00Z",
"lastModifiedDateTime": "2026-01-27T13:17:45Z",
"failedHealthCheckItems": []
}
}
Could you please clarify the API behavior?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the collection endpoint GET /deviceManagement/virtualEndpoint/cloudPCs?$select=id,displayName,connectivityResult with the single-host endpoint shown in the report. Start by examining the two response payloads and the reported timestamps; done means the differing ConnectivityResult behavior is explained and any required API or SDK follow-up is clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100