A great addition to the new ‘health status' feature in 7.0 is to utilize the Session Host API to display the ‘HealthCheckResult’ key and its values. This could be an on-demand query when someone selects the ‘Healthy’ or ‘Unhealthy’ tag on the session host. Placing results of the ‘Get-AzWvdSessionHost’ cmdlet that provides this detail.
HealthCheckResult: {{
"additionalFailureDetails": {
"message": "SessionHost healthy: is joined to domain
≤domainname≥",
"errorCode": 0,
"lastHealthCheckDateTime": "2025-04-14T14:05:49.1332513Z"
},
"healthCheckName": "DomainJoinedCheck",
"healthCheckResult": "HealthCheckSucceeded"
}, {
"additionalFailureDetails": {
"message": "SessionHost healthy: domain trust check succeeded for domain
≤domainname≥",
"errorCode": 0,
"lastHealthCheckDateTime": "2025-04-14T14:05:49.6650051Z"
},
"healthCheckName": "DomainTrustCheck",
"healthCheckResult": "HealthCheckSucceeded"
}, {
"additionalFailureDetails": {
"message": "SessionHost healthy: SessionHost healthy: SxS stack listener is ready",
"errorCode": 0,
"lastHealthCheckDateTime": "2025-04-14T14:05:49.1588726Z"
},
"healthCheckName": "SxSStackListenerCheck",
"healthCheckResult": "HealthCheckSucceeded"
}, {
"additionalFailureDetails": {
"message": "{\"AccessibleUrls\":[\"77c5c161-4140-4814-adef-1e30399beb46.rdbroker-g-u
s-r1.wvd.microsoft.com\",\"77c5c161-4140-4814-adef-1e30399beb46.rdbroker.wvd.microsoft.c
om\",\"77c5c161-4140-4814-adef-1e30399beb46.rddiagnostics-g-us-r1.wvd.microsoft.com\",\"
mrsglobalsteus2prod.blob.core.windows.net\",\"gcs.prod.monitoring.core.windows.net\",\"e
astus-shared.prod.warm.ingest.monitor.core.windows.net\",\"eastus-qos.prod.warm.ingest.m
onitor.core.windows.net\"],\"NotAccessibleUrls\":null,\"Context\":null}",
"errorCode": 0,
"lastHealthCheckDateTime": "2025-04-11T20:35:43.7521402Z"
},
"healthCheckName": "UrlsAccessibleCheck",
"healthCheckResult": "HealthCheckSucceeded"
}
Comments (0 comments)