Manifest Validation via CLI tool does not check RSC permissions

[joshuamckenty]

CLI tool validate does not check the RSC permissions
When using the CLI tool to confirm the validity of your app package, it performs no checking of the RSC permissions. Thus, it is possible to have a package that passes CLI validation, but will be rejected by the Microsoft Marketplace Teams Submission Team.

To Reproduce
Steps to reproduce the behavior:

1. Create a manifest.json file with nonexistent RSC permissions.
2. Create an app package zip file with this manifest.
3. Run teamsapp validate --package-file ./appPackage.zip
4. No errors will be found.

Expected behavior
The erroneous RSC permissions should be flagged.

CLI Information (please complete the following information):

• OS: MacOS 15.6
• Version 3.1.0

[m365-agent-toolkit-assistant]

👋 Hi @joshuamckenty,

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:

Thanks for your detailed report! This is a known limitation: the Teams CLI validation (even in newer Microsoft 365 Agents Toolkit/Teams Toolkit versions) does not fully validate RSC (Resource-Specific Consent) permissions in the manifest. This causes invalid RSC permissions to pass validate, but be rejected during Teams app submission—exactly as you described.

References & Similar Issues:

• GitHub #362: Confirms schema changes and need to correctly structure RSC permissions.
• Stack Overflow: Insufficient RSC permission: RSC-permission errors despite manifest validation.

Workaround/Recommendations:

• Double-check your RSC permissions against official docs.
• Validate your manifest in the Teams Developer Portal or during submission for a more rigorous check.
• For CI/CD pipelines, supplement CLI validation with manual or API-based manifest linting if RSC is involved.

Apology:
Sorry for the inconvenience—feature parity between CLI validation and real-world submission is a frequent community request.

Let me know if you want guidance on valid RSC permissions or schema upgrades!

✨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!

[wh-alice]

Thanks for reporting the issue. @summzhan, looks there is validation gap between us and marketplace. Let us discuss how to mitigate this gap internally.

[wh-alice]

The issue is in-active for at least 3 months. If this is still relevant or cared in latest ATK release, please comment to provide updated repro details. Otherwise it will be marked as close-candidate after 7 days.