This disclaimer governs your use of the Agents League public GitHub repository. By submitting content, code, or materials to this repository, you acknowledge and agree to these terms.
The Agents League is a high-energy developer challenge showcasing agentic AI across GitHub Copilot, Microsoft Foundry, and M365 Agents Toolkit. Submissions are made to a public repository accessible worldwide. Contributors must ensure compliance with all applicable policies, protect confidential information, and understand their responsibilities regarding intellectual property and liability.
Failure to comply may result in content removal, disqualification from the challenge, or other appropriate actions. Please read this disclaimer carefully before making any submissions.
Contributors must never upload confidential, proprietary, or sensitive information to the Agents League public repository.
- Company Confidential or Highly Confidential information
- Company Internal engineering projects not approved for open source
- Customer data or personally identifiable information (PII)
- Credentials, API keys, passwords, tokens, or secrets
- Proprietary algorithms or trade secrets
- Pre-release product information under NDA
GitHub Secret Protection scans repositories for over 300 token types and provides push protection to prevent secret commits.
All submissions must contain only General-level information suitable for public release. Contributors are responsible for reviewing their code and removing any sensitive data before submission. Organizations should implement secret scanning and establish review processes before allowing public repository contributions.
| Content Type | Risk Level | Description |
|---|---|---|
| Credentials & Secrets | Critical | Immediate security breach risk if exposed |
| Customer PII | High | Compliance violations and privacy concerns |
| Proprietary Code | High | Intellectual property and competitive risks |
| Pre-release Information | Medium | NDA violations and competitive disadvantage |
| Internal Documentation | Medium | Confidentiality breach concerns |
By submitting content to the Agents League repository, contributors grant Microsoft and the community specific rights while retaining certain protections.
- All submissions must be the contributor's original work or properly licensed for public use
- Contributors represent and warrant they have all necessary rights, licenses, and permissions for submitted materials
- Submissions become subject to the repository's open source license as specified in the LICENSE file
- Contributors retain ownership of their original work but grant Microsoft a perpetual, worldwide, non-exclusive, royalty-free license to use, reproduce, modify, and distribute submissions for operating the Agents League program
The repository follows Microsoft's Contributor License Agreement (CLA) process to protect both contributors and Microsoft.
Contributors must not submit content that:
- Infringes third-party intellectual property rights
- Violates patents or copyrights
- Contains proprietary information belonging to employers or other entities without authorization
| Rights Category | Contributor Retains | Microsoft Receives | Community Receives |
|---|---|---|---|
| Ownership | Original work copyright and authorship | Non-exclusive usage rights | Access under open source license |
| Usage Rights | Right to reuse in other projects | Right to operate Agents League program | Right to fork, modify, and distribute |
| License Grant | Can license elsewhere independently | Perpetual, worldwide, royalty-free license | Rights per repository LICENSE file |
| Modification Rights | Can modify own original work | Can adapt submissions for platform needs | Can create derivative works per license |
| Distribution | Can distribute original independently | Can distribute as part of Agents League | Can redistribute per license terms |
Contributors must implement security best practices before submitting to the Agents League repository:
- ✅ Enable two-factor authentication (2FA) on GitHub accounts
- ✅ Store recovery codes securely
- ✅ Use GitHub Personal Access Tokens instead of passwords
- ✅ Revoke tokens when no longer needed
- ✅ Never commit credentials, keys, or secrets to any Git repository
- ✅ Use environment variables or secure vaults instead
- ✅ Review Git commit history to ensure no sensitive information was accidentally included
- ✅ Scan code with secret detection tools before pushing to public repositories
- ✅ Configure Git clients to use appropriate email addresses for commits
- ✅ Follow the Open Source Code of Conduct
GitHub Secret Protection provides push protection that blocks commits containing detected secrets and offers delegated bypass approvals for false positives. Organizations can enforce secret protection across all repositories through customizable policies and API integrations.
Contributors must fulfill specific responsibilities when submitting to the Agents League repository:
- ☐ Verify all submissions comply with Microsoft Open Source GitHub Guidelines and these disclaimer terms
- ☐ Ensure submissions contain only General-level, non-confidential information approved for public release
- ☐ Review and remove any sensitive data, credentials, internal references, or proprietary information before submission
- ☐ Provide accurate and complete information when creating accounts
- ☐ Maintain professional GitHub profiles
- ☐ Accept and sign the Microsoft Contributor License Agreement (CLA) as required
- ☐ Follow the repository's Code of Conduct
- ☐ Engage respectfully with the community
- ☐ Maintain security of GitHub accounts through 2FA and secure password practices
- ☐ Respond promptly to any security concerns or content removal requests from repository maintainers
- ☐ Understand that submissions may be used to evaluate projects using criteria including accuracy, reasoning, creativity, user experience, and reliability
- ☐ Acknowledge that Microsoft may delete, modify, or remove submissions that violate these terms without prior notice
- ☐ Contributors remain responsible for all activity under their accounts
Microsoft reserves the right to monitor, review, and remove content from the Agents League repository to ensure compliance with these terms.
Repository maintainers may remove content that:
- Contains confidential information
- Violates intellectual property rights
- Includes prohibited materials
- Poses security risks
- Breaches the Code of Conduct
Contributors found violating these terms may face:
⚠️ Immediate content removal without notice⚠️ Disqualification from Agents League evaluation and prizes⚠️ Revocation of repository access and organization membership⚠️ Reporting to appropriate authorities for serious violations
GitHub Secret Protection partner program enables automated notifications to service providers when their credentials are exposed, allowing partners to validate and revoke compromised secrets.
- Microsoft may comply with governmental, court, and law enforcement requests relating to repository content
- Microsoft reserves the right to report information to law enforcement
- Organization administrators can remove collaborators at any time to enforce security recommendations or guidelines
- Private repositories created for Agents League preparation must be made public within 90 days or risk deactivation
The enforcement process prioritizes transparency while protecting the security and integrity of the repository and broader community.
If you have questions about this disclaimer or need to report a security concern:
- Security Issues: Please report via GitHub Security Advisories
- General Questions: Open an issue or contact us on Discord
- Content Removal Requests: Open an issue with the
content-removallabel
This disclaimer is subject to change. Contributors are responsible for reviewing the latest version before each submission.
Last updated: February 2026