Support¶
Monkey365 uses GitHub Issues to track bugs and feature requests. I maintain Monkey365 in my spare time. I answer questions when I can, but I cannot promise a response or resolution date.
Before you file an issue, please search the existing issues to avoid duplicates.
- For new issues, file your bug or feature request as a new issue.
- For help, discussion, and support questions about using this project, join or start a discussion.
Search the open issues, discussions, and documentation before posting.
Bug reports¶
Please include enough detail for me to reproduce the bug.
| Detail | What to provide |
|---|---|
| Monkey365 | Version and installation method |
| PowerShell | $PSVersionTable.PSVersion |
| Host | Operating system, workstation or container, and other relevant runtime details |
| Cloud | Azure Public, Azure China, or Azure US Government |
| Reproduction | The shortest command or script that still fails |
| Result | What happened and what you expected instead |
| Diagnostics | Relevant, sanitized errors or log excerpts |
Redact tenant and subscription identifiers, names, user data, credentials, tokens, certificates, and private keys. Never attach a complete assessment report or a production log.
Reports prepared with AI tools¶
If an AI tool helped prepare the report, name it and explain what it did. Read the report before submitting it, and check every command, claim, and link. Remove placeholder text and anything the tool invented. I may close an issue when it appears to contain unreviewed generated text.
Support for Monkey365 is limited to the resources listed above.