Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure DevOps Services | Azure DevOps Server | Azure DevOps Server 2022
This article helps you access support resources and provide feedback for Azure DevOps. Learn how to contact Support, report issues, suggest features, and give feedback on both the product and documentation.
Self-help first
Try these options before opening a support request:
- Collect an HTTP Archive (HAR) trace for sign-in problems through Microsoft Edge or Google Chrome.
- Troubleshoot access and permissions problems.
- See user and permissions management FAQs.
- See Microsoft Entra access FAQs.
Support and feedback channels
Use the following table to choose the right channel quickly.
| If you need to... | Use this channel | Link |
|---|---|---|
| Get help when you're blocked and can't continue work | Contact Support | Create a support request |
| Resolve project-specific access or configuration problems | Project administrator | Contact your project administrator |
| Report a product bug or defect | Developer Community | Azure DevOps Services Azure DevOps Server |
| Suggest a product feature | Developer Community | Azure DevOps Services Azure DevOps Server |
| Ask implementation questions | Stack Overflow | Azure DevOps Services Azure DevOps Server |
| Report a security vulnerability | Microsoft Security Response Center (MSRC) | Report security flaws |
| Review recent product changes | Release notes | View release notes |
Tips for effective feedback
If you want to vent about the product or the documentation, that's okay. It helps the product team know when you're happy or unhappy with an experience. Provide the following details so the team can better understand what they're doing right or wrong:
- Provide context. What problem were you trying to solve? At what point did it go wrong?
- Include your role. Are you a developer, manager, or business owner? Understanding the audience helps the product team create better solutions.
- Include your product version. What other products were you using with it?
- For sign-in issues, include a HAR trace. A HAR trace helps the support team diagnose authentication problems faster.
Give product feedback
Enter clear, precise, detailed feedback when you create a support request.
Important
Don't include credentials, API keys, personal access tokens, or other sensitive information in your feedback.
Example: "I'm a project manager for a small start-up using Azure DevOps. I'm trying to create work item templates through the UI, but my changes don't persist. It's not clear what I'm doing wrong."
Give documentation feedback
All articles on Microsoft Learn have a ratings tool. Select Feedback beneath the title of the article, and in the "Was this page helpful?" pane, select Yes or No based on your experience.
Enter clear, precise, detailed feedback in the Tell us more section. Avoid including sensitive or personal information. Although we can't reply, we regularly review this feedback and use it in our content planning.
Example: "I'm a developer in a large organization working on Java apps. I tried to use Maven with your build system in Azure DevOps Server 2017 Update 1 (15.112.26307.0), but I couldn't get the configuration shown in the documentation to work."
For more information, see the following section of related articles.