Thank you for your interest in contributing! We welcome contributions from the community.
Please take a moment to review:
- CODE_OF_CONDUCT.md - Our community standards
- SECURITY.md - Security reporting and expectations
- This file - Guidelines for contributions
Found a bug or have a suggestion?
- Check existing issues to avoid duplicates
- Open a new issue using the appropriate template:
- Include relevant details: environment, steps to reproduce, expected vs. actual behavior
- Fork this repository
- Create a branch for your changes (
git checkout -b feature/your-feature) - Make your changes and test locally
- Commit with clear, descriptive messages
- Push to your fork
- Open a Pull Request and reference any related issues
Before submitting a PR, ensure:
- ✅ No secrets or credentials - No API keys, connection strings, tenant IDs, or subscription IDs
- ✅ No tenant-specific values - All examples use parameterized inputs
- ✅ Documentation updated - If behavioral changes, update relevant docs
- ✅ Code follows conventions - Consistent formatting and naming
- ✅ Tests pass - If applicable, ensure your changes don't break existing functionality
- ✅ License compliance - Your contribution will be licensed under MIT
See .github/PULL_REQUEST_TEMPLATE.md for our PR checklist.
- Pull requests are reviewed by maintainers in good faith
- You may be asked for clarifications or changes
- Reviews may take time; please be patient
- Once approved, your PR will be merged
✅ Infrastructure improvements and bug fixes ✅ Documentation enhancements ✅ Security issues (reported privately via SECURITY.md) ✅ Sample configurations and best practices
❌ Microsoft internal code or proprietary assets ❌ Secrets, credentials, or sensitive configuration ❌ Tenant-specific or customer-identifying information ❌ Code designed for Microsoft internal environments ❌ Changes requiring Microsoft internal dependencies
- No SLA or Production Support: This is a community project, not a Microsoft service. Contributions and responses are provided on a best-effort basis.
- Reference Architecture: This is a starter kit and reference implementation. Production deployments require customer validation and additional controls.
- Your Responsibility: When you deploy resources, you are responsible for their security, compliance, and operational management.
By contributing, you agree that your contributions will be licensed under the MIT License.
If you have questions about contributing:
- Review docs/faq.md
- Check existing issues and discussions
- Open a new discussion or issue
Thank you for helping make this project better!