App Validation Issue - Bot must send a proactive welcome message in personal scope

Hello @ParamZ - Thanks for bringing this issue to our attention. 

1.Graph API queries may generate unexpected conversationUpdate events.
Recommended Solution: Use event deduplication based on activity ID and conversation ID to avoid sending duplicate welcome messages.

2.Reading Chat History – Suggested Method:

Best Practice: Save conversation references when the bot is installed, rather than polling the Graph API.
Alternative: Opt for webhooks or change notifications instead of using /me/chats queries.

3.App Validation – Proper Procedure:

Primary Method: Utilize on_installation_update for sending welcome messages to meet validation requirements.
Fallback: Apply on_members_added_activity with deduplication as needed for special cases.

References:

Design and control conversation flow - Bot Service | Microsoft Learn

Teams Store Validation Guidelines - Teams | Microsoft Learn

Please let us know if you have any further query here.