We need to provide guidance to identify the user interacting with the agent

[Sunil-Garg]

Description

Agents need a way to identify the A365 user they are interactive with so that they can perform housekeeping activities on their side. This information is available in the activity payload. We need to show how the dev can get this information and also show what can they do to get additional information about this user which is not directly available in the activity payload. We must update our samples and the doc accordingly.

Expected behavior

the dev is able to retrieve the information.

SDK Version

1.0.0

Language/Runtime

all

OS

all

How to Reproduce

send a message to the agent in Teams and see if you can get the user info in the agent

Output

No response

Screenshots

No response

Code of Conduct

• I agree to follow the Microsoft Open Source Code of Conduct.

[github-actions]

[AUTO-TRIAGE] Team Assistant Triage

This issue has been automatically analyzed and triaged.

AI Decision Reasoning: Type: Classified as 'documentation' because the issue focuses on providing guidance and updating samples and documentation to help developers retrieve user information.
Priority: Elevated to P1 due to security concern: The issue discusses exposing user information to agents and developers, which could lead to potential data exposure or privacy concerns if not handled securely, especially when retrieving additional user information not directly available in the activity payload.
Copilot: Security issues require human review and should not be auto-fixed
Assignment: Security issue assigned to security lead. The issue discusses exposing user information to agents and developers, which could lead to potential data exposure or privacy concerns if not handled securely, especially when retrieving additional user information not directly available in the activity payload.
Labels: Applied labels documentation, P1, security based on issue type and priority

Labels and assignee have been applied based on this analysis.

[github-actions]

[AUTO-TRIAGE] Results

Classification: documentation
Priority: P1
Confidence: 95.0%

Recommended Assignee: @pontemonti

Analysis:
type rationale: Classified as 'documentation' because the issue focuses on providing guidance and updating samples and documentation to help developers retrieve user information.

priority rationale: Elevated to P1 due to security concern: The issue discusses exposing user information to agents and developers, which could lead to potential data exposure or privacy concerns if not handled securely, especially when retrieving additional user information not directly available in the activity payload.

copilot rationale: Security issues require human review and should not be auto-fixed

assignment rationale: Security issue assigned to security lead. The issue discusses exposing user information to agents and developers, which could lead to potential data exposure or privacy concerns if not handled securely, especially when retrieving additional user information not directly available in the activity payload.

labels rationale: Applied labels documentation, P1, security based on issue type and priority

[SUGGESTION] Suggested Approach

1. Update the documentation in the docs directory to include a new section titled 'Retrieving User Information from Activity Payload'. Provide step-by-step instructions on how to access the user details from the activity payload, including code snippets in C# for parsing the payload and extracting user-specific fields.
2. Enhance the sample code in src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests/Commands by adding a new example command that demonstrates how to retrieve user information from the activity payload. Include logic for accessing additional user details via the Microsoft Graph API or Azure AD if necessary.
3. Add a unit test in src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests/Helpers to validate the extraction of user information from the activity payload. Ensure the test covers edge cases, such as missing or malformed user data in the payload.
4. Include a reference to the Microsoft Graph API in the documentation and provide guidance on how developers can use it to fetch additional user details. Update the autoTriage/requirements.txt file to include relevant Python libraries (e.g., msal) if Python scripts are used for this purpose.
5. Create a troubleshooting section in the documentation to address common issues developers might face when retrieving user information, such as permissions errors or incomplete payloads. Provide links to relevant Microsoft documentation for resolving these issues.

---

Generated by TeamAssistant Auto-Triage powered by GitHub Models

[github-actions]

SLA Escalation Alert

This P1 issue has exceeded its SLA threshold.

Metric	Value
Priority	P1
SLA Threshold	48 hours
Time Since Update	58.6 hours
Current Assignees	@sellakumaran

Action: This issue is already assigned to a Tech Lead but remains unresolved.

Escalating to Engineering Manager @ajmfehr for visibility.

Tech Leads: @sellakumaran

---

Generated by AutoTriage SLA Escalation