App Validation Fails in Developer Portal Due to Bot Configuration and URL Issues

[AmrapaliZade93]

Description:
We are trying to validate our Microsoft Teams app, named notification-team-app, in the Developer Portal, but the validation process is failing. We are facing multiple issues that prevent the app from passing the validation. Below are the details:

1. Bot Welcome Message Issues:

• The bot welcome message is received in personal scope but is not triggered in the Teams scope.
• The bot is not responding to commands, such as "Hi", in both personal and Teams scope.
• We suspect these issues are related to the bot configuration, but we are unsure what exactly is causing the problem.

2. URL Issues:

• The URLs provided for Privacy, Terms of Use, and the website are all returning HTTP 502 errors.
• This causes the app validation to fail because the Developer Portal cannot access these URLs.

3.Impact:

• Because of these issues, we are unable to publish our Teams app either to our organization or to the Teams store.
• We need guidance on how to correctly configure the bot and ensure that the URLs work properly for validation.

4.Additional Information:

• We have tried rechecking the bot configuration, but the problem persists.
• Screenshots of the validation errors are attached for reference.

We would really appreciate guidance or suggestions on how to fix these issues so that our app can pass the Developer Portal validation successfully.

[m365-agent-toolkit-assistant]

👋 Hi @AmrapaliZade93,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

You are facing two main issues blocking app validation:

1. Bot Welcome Message & Command Issues

• Welcome message shows only in personal scope: This is often a bot code/configuration issue. For Teams scope messages, ensure your bot logic listens for conversationUpdate activities where the conversation type is channel. Many sample bots only trigger on personal scope.
• Bot not responding to "Hi": Double-check your bot is running, accessible, and registered in the manifest. Make sure the Teams channel is enabled in Azure Bot registration. Refer to this fix guide.

2. Privacy, Terms, and Website URL 502 Errors

• 502 means your URLs are down or unreachable to the Developer Portal: Make sure these endpoints are publicly accessible, use HTTPS, and are not behind corporate firewalls or proxies blocking external requests. Validate URLs with tools like https://httpstatus.io/.

---

To proceed:

• Check/enable the Teams channel on your bot in Azure or Developer Portal.
• Update your privacy/terms URLs to be live and accessible.
• Share your environment (VS Code/VS/CLI), manifest version, and error logs if you need step-by-step help.

Related Issues:

• 502 Errors & Proxy
• Bot Welcome Msg Issues

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!