Documentation
Feedback and how to engage
Filing a bug or requesting a feature?
Table of Contents
- Pick the right channel
- GitHub Issues
- GitHub Discussions
- Email and meetings
- Private Teams channel
- Office hours
Pick the right channel
| You want to | Use |
|---|---|
| Report a bug, regression, or unexpected behavior | GitHub Issues: Bug report |
| Request a feature or capability | GitHub Issues: Feature request |
| Ask a “how do I” question | GitHub Discussions: Q&A |
| Share what you built | GitHub Discussions: Show & Tell |
| Suggest a direction or pitch an idea | GitHub Discussions: Ideas |
| Email the team directly | azuresqldb-container@microsoft.com |
| Book live time with the team | Connect with the team |
| Talk to the team in real time | Private Teams channel (link shared via the early-access feedback channel) |
| Demo, ask questions live, hear roadmap updates | Office hours (calendar invite shared via the early-access feedback channel) |
GitHub Issues
Use GitHub Issues for anything that has a reproducible test case or a concrete capability ask.
Before filing, scan the open issues for a duplicate and read the Known limitations page. If your issue is already a known limitation, you can comment with your scenario instead of opening a new issue.
When you file, include:
- Container image tag
- Host OS and architecture
- Container runtime and version
- Driver or ORM and version
- Reproduction steps
- Expected behavior
- Actual behavior
The issue templates ask for all of this. The more complete the report, the faster the triage.
GitHub Discussions
Use Discussions for everything that is not a clean bug or feature request:
- Q&A: how do I, what is the right way to, did anyone else hit
- Show & Tell: here is what I built, here is a pattern that worked
- Ideas: I think the container should, here is a use case we have not seen
- Announcements: updates from the team, posted by maintainers
Discussions move slower than the Teams channel but they are searchable and durable. Questions answered in Discussions help every future participant who runs into the same thing.
Email and meetings
Want to reach the team directly?
- Email: azuresqldb-container@microsoft.com. Good for anything that does not fit a public issue or discussion: onboarding questions, access, or a quick note to the team.
- Book live time: aka.ms/azuresql-container-meet. Grab a slot to talk through your scenario, show what you built, or work through a blocker with the team.
For bugs and feature requests, still file on GitHub so the work is tracked and visible to the whole cohort.
Private Teams channel
Customers in this Private Preview are under NDA. The Teams channel is private, access-controlled, and the right place for:
- Real-time conversation
- Questions you do not yet want to put in a public issue
- Quick polls from the team to the cohort
The Teams channel is not a substitute for filing an issue. If something is a bug or a feature request, please file it on GitHub so it does not get lost in chat.
Office hours
Weekly office hours run for the duration of the Private Preview. The agenda template:
- 5 min: opening, what shipped this week
- 15 min: customer demos (volunteer in the Teams channel ahead of time)
- 15 min: open Q&A
- 10 min: engineering update
Engineering attends. Bring your hardest question.