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.
Get support and give feedback
| Action | More info |
|---|---|
| Contact Support | In the Microsoft Azure portal, create a support request. Briefly describe the issue to get to solutions and support, and then follow the prompts for additional details.
|
| Get Virtual Agent support | Chat with the Virtual Agent to get help with common issues, including user management, organization-level configuration and management, sign-in problems, geography moves, and more. |
| Troubleshoot access problems | - Collect an HTTP Archive (HAR) trace for sign-in problems via Microsoft Edge or Google Chrome. - Troubleshoot access and permissions problems. - View user and permissions management FAQs. - View Microsoft Entra access FAQs. |
| Report a bug or problem | Report a problem via the Developer Community, which is an open channel to Microsoft engineering teams: - Azure DevOps Services - Azure DevOps Server |
| Suggest a feature | Submit your suggestion via the Developer Community, which is an open channel to Microsoft engineering teams: - Azure DevOps Services - Azure DevOps Server |
| Contact your project administrator | Contact your project administrator for assistance with access problems, permission changes, project configuration, resource allocation, or troubleshooting. |
| Get advice | Get advice from developers via Stack Overflow: - Azure DevOps Services - Azure DevOps Server |
| Report security flaws | Report potential security problems to ensure the safety and integrity of the system. |
| View Release Notes | Check out what's new in Azure DevOps Release Notes, which get updated every three weeks. |
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?
Give product feedback
Enter clear, precise, detailed feedback when you create a support request.
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.