Confluence is a collaboration and content sharing platform used primarily by customers who are already using Atlassian's Jira project tracking product. The product appeals particularly to IT users.
$0
Free for 10 Users
Azure DevOps
Score 8.0 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pricing
Atlassian Confluence
Azure DevOps
Editions & Modules
Free
$0
Free for 10 Users
Standard
$6.40
per month per user
Premium
$12.30
per month per user
Data Center
220,000.00
40,001+ Users - Annually
Enterprise
Contact Sales
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Offerings
Pricing Offerings
Confluence
Azure DevOps
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Prices shown here reflect prices for deployments with 100 users or less. The prices decrease wien the user base surpasses 100.
It has great features like integration and real time collaboration with new features like AI and automation. So it gives an edge over other tools I have used in the past few years. I am sure there are a lot of features which I have not explored yet, but the features I am using …
Atlassian Confluence has a more comprehensive and flexible set of capabilities that stand out and made the decision upfront more straightforward for our team. The tools we evaluated have knowledge management, task management and collaboration capabilities, however Atlassian …
Atlassian Confluence is way popular for a larger team and makes collaboration way easier. The community is strong and you get easier resolution against any request. It's integration with other Atlassian products like JIRA is an icing on the cake.
In my experience, Atlassian Confluence is at the top of these tools. I've had first hand experience with other tools and they are not at par with Atlassian Confluence. The versatility of the tool is very well recognized and utilized. Being a new user is not a probably as all …
Atlassian Confluence is a super handy hub for sharing ideas and keeping all your docs in one place. While Jira Service Management is more about handling tickets and support issues, Atlassian Confluence really makes teamwork easy. I feel Atlassian Confluence is user-friendly, …
We choose Atlassian Confluence because it is the reference for managing a SAAS wiki service. And having such a solution in our company to manage the knowledge and especially the knowledge transfer is crucial.
Confluence has a more robust set of capabilities compared to Dovetail and Trello and also was already approved by our legal and compliance teams, so it tends to keep its stickiness due to that. It's also widely known in the market as a knowledge management tool. I would say it …
Overall, Atlassian Confluence is a user-friendly tool and offers such a vast array of capabilities for project and knowledge management purposes and beyond. Other tools listed above have much more limited capabilities, although they are great tools for very specific needs and …
The main reason for moving to Atlassian Confluence was for: 1) Having 1 space that holds all of the org's documentation and knowledge sharing 2)We already used JSM and Jira so it would an organic move to have Atlassian Confluence as our main documentation hub 3) The cost …
Confluence, since it is part of the overall infrastructure of Atlassian, makes it immensely powerful internally, to build an internal knowledgebase, and is far ahead of its counterparts in Zendesk and Hubspot, which is more centered towards their customers. Confluence is just …
Sharepoint in out organisation was mostly used for collaborating on documents, which to some degree has been moved to Confluence, where the Confluence pages have replaced the specific documents.
Being a company which uses other Atlassian tools, Atlassian Confluence was a great fit; the natural and automatic linking of assets from other platforms made following paper trails seamless. Though the editing options aren't as advanced as some other options out there, it does …
We find Atlassian better for its ease of use, real time editing, integration with Jira for bug tracking, stores our security compliance documents in structured way, it is feature rich and have lots of capabilities.
In the past, I have used MediaWiki hosted locally as well as Microsoft Team Foundation Server. Wiki was simply a nightmare so all the money saved from paying for Atlassian subscriptions was lost in time while trying to use Wiki and format something properly. I haven't used …
Atlassian Confluence is better suited for documenting and acting as a repository for information than the more immediate what is currently being worked on things that are better suited for in Jira. In my opinion, Atlassian Confluence certainly has it's short comings but it is …
We still use Atlassian Confluence only for its integration with Jira and Bitbucket. For everything else, we moved away from it and are using more modern solutions.
We chose Atlassian Confluence over SharePoint because it's much more user-friendly and intuitive. Atlassian Confluence makes collaboration and knowledge sharing easier with its simpler interface and better search. While SharePoint can be powerful, it often feels clunky and …
The alternatives tested are based only on the whiteboarding functionality added by Confluence Whiteboard, and not the core Confluence functionality (documentation).
Again, Atlassian Confluence is efficient when paired with Jira and can do most of what a company needs it to do. But, I thi Spekit is better for "just-in-time" learning, Sharepoint is better for file hosting and organization, Asana is much better for project/task management, …
We were inclined to use Atlassian Confluence for its easy collaboration with Jira which is used for tracking project development tasks and issues. Using Atlassian Confluence, content creation became easy and even applying access control to the created content was possible. It …
This is the first platform our dev team shared to us so I can't really compare but overall its such a great tool to have even if you are not from tech or dev team.
We would use App Center for distributing our app to testers, and we could implement the same functionality as was handled by App Center, and as far as I remember we even had some automatic conversion of our jobs from App Center. After the conversion, we could see that Azure …
We love the multi-tier hierarchy in Azure DevOps for tasks, with epics, features, stories, bugs and tasks all available in a nice nested hierarchy. It's not as pretty as Monday.com and doesn't work as well OOTB as ServiceNow SPM however.
It is a similar tools with its pros and cons but does not really a differential - I would say it does the same but its own way, sometimes better, other times worst. It is a matter of preference or demands that come from superior decisions, so you just have to take it.
Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing …
The moment I have been working with this tool everything has benn operating efficiently. The software development process has borne positive results under scalable environment. The cost of running Azure DevOps Services us much lower as compared to other tools in the market. It …
ADO has better linking than Confluence and is adaptable for a specific need, whereas Confluence might be a bit more rigid, but it's also sort of along the same lines as to what can be done with both tools. ADO also had an ease of use to it and can do a bunch of stuff with it, …
Jira is super clunky and doesn't behave in a modern fashion. monday.com is too flexible and doesn't provide enough feature set. AWS is the most competitive, but it's hard to wrap your brain around all of the features and offerings provided by amazon. ADO does a better job of …
Azure DevOps has a drag and drop editor so that you can quickly drag build steps into a build or release pipeline. This is much faster than looking up the correct yaml syntax. Additionally, its support for Microsoft and Azure is great. If you're on the .net stack or you use …
Azure DevOps has more services and better integration with other tools. When it. Comes to the overall software development process management ecosystem.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or …
Trello is simple to use, but it's only for a Kanban board. Jira might be the same, but I don't really have enough experience with Jira to fully compare them. When I used it, it missed certain functionalities that I was used to in Azure DevOps. Visually it's a lot different too.
Azure DevOps Services have huge functionality and are well supported by Microsoft as well. You will get plenty of features in the marketplace and learning documentation.
Writing the Docker Images, Storing them in Azure Container Registry and then Deploying onto Azure Kubernetes Services is an Easier process which no other software/product is currently providing in the market. Best till date in terms of End to End deployment and maintaining …
Azure DevOps is widely used because of its collaboration and integration with various other tools. Here the assign of the sub task is quite easy compare to Jira. Also Azure Devops can we integrate easily with Git for better code representation and versioning. It reporting is …
Azure DevOps is a completed product and ecosystem. It offers a robust ecosystem that does everything that is needed. The above products do lack features like pipelines tasks, third-party integrations. Besides all cloud benefits, the main advantage of Azure DevOps Services …
Currently, we use both products, however, we use more the Atlassian suite. We have started recently using Azure DevOps for specific implementations and projects. We don't have any plan yet to migrate all our projects to Azure DevOps, we may in the next couple of years. …
We tested alternatives for Azure DevOps over time. We tested GitHub a while ago and back then lack of some features that now hast, like the project boards and private repositories. We will check GitHub next year.
We also tested AWS CodeCommit and found it very cryptic, …
Beside all cloud benefits, the main advantage Azure DevOps Services compared to Azure DevOps Server is the easier remote access for third party team members, and always up to date software. On the other hand, on prem deployment (Azure DevOps Server) makes complex access or …
The greatest strength of Azure DevOps Services (formerly VSTS) is that it's a one-stop solution for all agile project management instead of setting up bits of different software put together for each and every need. Azure DevOps Services (formerly VSTS) has a great ecosystem …
I prefer Azure Devops over all other code repository / ci/cd systems that I've used in the past. All features are integrated into a single service (back log, repo mgmt, deployment pipelines, artifacts, etc.). The tools are easy to use and super powerful.
Our company is already using a lot of Azure services and it makes more sense to start using Azure DevOps Services (formerly VSTS) when we needed a CI/CD tool. We tested different features of Azure DevOps Services (formerly VSTS) and found out that the build and release …
Atlassian Confluence is a great tool for housing important information and resources across the organization, as it's very easy to search and find content across different teams and departments. The search function is mostly very accurate and the additional tagging with keywords also helps in the search experience. It's also good at tagging other team members, which triggers an automated email to them. Atlassian Confluence also has an extensive template library for all kinds of purposes like project management, etc., which saves time overall.
DevOps is much more user friendly than Git itself. There is a more GUI-centric interface, tighter integration with the Azure / Entra architecture. For those of use in the Microsoft-sphere, it really is excellent for code-centric project management. I rate this as an 8 because it does not seem quite as well suited for fully functional / non-code project aspects in implementation. Nor does it have customer / end-user portal / front end for easy reporting and insight.
Its integration with Jira for tracking development and the bugs and work linked to detailed Confluence documentation.
We use it extensively for writing Software Product Requirement Documents, feature specs, architecture designs, and retrospectives.
Our company follows compliance very seriously, so it helps in streamlining all documentation for ISO27001/27017 compliance and security-related information.
Its integration with various tools allows us to create flow diagrams which are often required to make client and customer understand the overall flow of interactions across various modules of the design architecture
Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
It's very intuitive for most things, making it easy to jump in and start creating pages and collaborating. This makes it ideal for onboarding new members to the team. There are a few areas that could be a little smoother, but overall it's a great experience.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
We never worked against the tide while using Confluence. Everything loads considerably fast, even media components like videos (hosted on the platform or embed external videos from Youtube, for example). We are not using heavy media components a lot, but in the rare occasion we happen to use one we have no problems whatsoever.
This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Atlassian Confluence is a super handy hub for sharing ideas and keeping all your docs in one place. While Jira Service Management is more about handling tickets and support issues, Atlassian Confluence really makes teamwork easy. I feel Atlassian Confluence is user-friendly, integrates smoothly with other Atlassian tools, and helps everyone stay in sync. It's great for brainstorming, and project planning as well. Overall, it is a great way to boost collaboration and ensure all team members are on the same page.
We love the multi-tier hierarchy in Azure DevOps for tasks, with epics, features, stories, bugs and tasks all available in a nice nested hierarchy. It's not as pretty as monday.com and doesn't work as well OOTB as ServiceNow SPM however.
Merging instances has saved search time - We used to have several instances of Atlassian Confluence, which means they're separate and so can't communicate with each other. We've since merged into one instance and now with the help of the search feature can find the documents you're looking for in seconds rather than several minutes.
Cross linking product assets streamlines following paper trails - Being able to click on a BitBucket link from a Confluence page which then links to a JIRA ticket means you can follow paper trails really easily; seconds rather than several minutes.