Azure AVD LogAnalytics bug with SessionHostSessionId field?

Question

We are attempting to link AVD UserSessions to WVDConnections records in LogAnalytics.  The _ResourceID + SessionHostSessionId looks like it should be perfect for making this association, however we have observed that the SessionHostSessionId field is only sporadically present, and very rarely set while a session is open.

Is this a known issue - expected behavior - plans to fix?

Answer 1

Hi @Ted Rainey
Welcome to Microsoft Q&A Forum, Thanks for asking question here.
The issue you're facing with the inconsistent appearance of the SessionHostSessionId field when linking AVD UserSessions to WVD Connections in Log Analytics is recognized by the community, but Microsoft has not provided official documentation on this behavior.

Possible Causes:

• Intermittent Availability: The SessionHostSessionId may not always be available due to how sessions are managed and logged in Azure. This can cause the ID to be missing during some active sessions or not recorded consistently.
• Expected Behavior: While Microsoft hasn't confirmed this as a known issue, it might be considered normal under certain conditions, like session timeouts, resource issues, or logging delays.
• Resolution Plans: Microsoft has not provided any updates or timelines for fixing this issue. It’s recommended to monitor Azure updates and community forums for improvements.

Recommendations:

• Provide Feedback to Microsoft: If this issue affects your operations, submit feedback through Azure support or forums to help prioritize fixes.
• Workarounds: Use other fields that are consistently available to correlate sessions with connection records. You can also create custom logging to track session activity.
• Community Engagement: Join Azure forums to get insights from others who may have found workarounds for this issue.

In conclusion, the inconsistent availability of the SessionHostSessionId is likely expected behavior rather than a documented issue. Continuing communication with Microsoft and the community may lead to further solutions. I hope this has been helpful! Your feedback is important so please take a moment to accept answers. If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!Hi @Ted Rainey

Welcome to Microsoft Q&A Forum, Thanks for asking question here.
The issue you're facing with the inconsistent appearance of the SessionHostSessionId field when linking AVD UserSessions to WVD Connections in Log Analytics is recognized by the community, but Microsoft has not provided official documentation on this behavior.

Possible Causes:

• Intermittent Availability: The SessionHostSessionId may not always be available due to how sessions are managed and logged in Azure. This can cause the ID to be missing during some active sessions or not recorded consistently.
• Expected Behavior: While Microsoft hasn't confirmed this as a known issue, it might be considered normal under certain conditions, like session timeouts, resource issues, or logging delays.
• Resolution Plans: Microsoft has not provided any updates or timelines for fixing this issue. It’s recommended to monitor Azure updates and community forums for improvements.

Recommendations:

• Provide Feedback to Microsoft: If this issue affects your operations, submit feedback through Azure support or forums to help prioritize fixes.
• Workarounds: Use other fields that are consistently available to correlate sessions with connection records. You can also create custom logging to track session activity.
• Community Engagement: Join Azure forums to get insights from others who may have found workarounds for this issue.

In conclusion, the inconsistent availability of the SessionHostSessionId is likely expected behavior rather than a documented issue. Continuing communication with Microsoft and the community may lead to further solutions.

I hope this has been helpful! Your feedback is important so please take a moment to accept answers. If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!