No more typing reviews! Try our Samantha, our new voice AI agent.

Elastic Observability vs Microsoft Purview Audit comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Elastic Observability
Ranking in Log Management
14th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
29
Ranking in other categories
Application Performance Monitoring (APM) and Observability (10th), IT Infrastructure Monitoring (13th), Container Monitoring (6th), Cloud Monitoring Software (11th)
Microsoft Purview Audit
Ranking in Log Management
27th
Average Rating
8.2
Reviews Sentiment
5.1
Number of Reviews
4
Ranking in other categories
Microsoft Security Suite (30th)
 

Mindshare comparison

As of September 2026, in the Log Management category, the mindshare of Elastic Observability is 1.3%, down from 1.3% compared to the previous year. The mindshare of Microsoft Purview Audit is 1.1%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management Mindshare Distribution
ProductMindshare (%)
Elastic Observability1.3%
Microsoft Purview Audit1.1%
Other97.6%
Log Management
 

Featured Reviews

Stefan Decuypere - PeerSpot reviewer
Technology Consultant at Hybrid software
Real-time dashboards and visual insights have streamlined issue analysis and monitoring
After careful consideration about areas for improvement in Elastic Observability, aspects such as pricing, customization, implementation, and scalability could be improved. As a user of the system, I know what it costs but am not directly involved in cost-benefit evaluations or maintenance, which is handled by another team. I develop the visual representation of the data and frankly, I don't see major gaps in my application or anything I would really miss; I appreciate the fast pace of the developments that have occurred in the last couple of years. Regarding room for improvement in Elastic Observability, I would have preferred built-in tools to manage the indexes on deployment for better visual representation, as the initial feedback regarding system performance and data storage was fairly primitive and lacking.
OK
Cloud Solution Engineer at a computer software company with 51-200 employees
Integrated auditing has strengthened data retention and improved incident investigations
I have seen areas for improvement, specifically in Microsoft Purview Audit or in general about Microsoft. I have had a situation with documentation. I had a customer who wanted to create alerts and they had Microsoft 365 Business Premium. In the documentation, it was noted that this license is enough for creating alerts. When we tried to make them, we noticed they cannot do it with Microsoft 365 E3 because the customer had limited features to manage alerts. The customer had to buy E3. We created Microsoft support requests, and they confirmed that the documentation displayed not the real situation and they have been going to update documentation. The same situation occurred now with implementing Microsoft Purview Audit in the last autumn. eDiscovery was combined with search and content search, and the documentation was not clear at the beginning. It was a little difficult to describe to customers that now it is a part of eDiscovery. Content search is a very simple functionality, while eDiscovery is a little difficult. I am not entirely sure why Microsoft is going in the way of combining these services because they are the same. However, for a customer who has never seen these services, it is difficult to understand quickly. The same situation occurs with litigation holds and some other holds. For any mail, I am trying to keep data. For example, emails are held for a year or two years, ten years, it does not matter. It is difficult to understand where to find this data and where these emails are being held. I need to use eDiscovery to find out all deleted data that was kept somewhere in some hidden folders of the mailbox. Regular customers and regular administrators know that on-premises Exchange, for example, allows them to find the data in some repository and review the list of kept data. However, with this hold, we do not have any functionality to review the list of kept data. It is difficult to understand for customers how to work with this. I had a case where I spent three or four hours working deeply with a customer to explain how to work with eDiscovery, why Content Search is not there when it was before, what is an eDiscovery case, and why we are talking about all of this just to review a list of kept emails. This is difficult.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature of Elastic Observability is the text search."
"The ability to ensure that the data is searchable and maintainable is highly valuable for our purposes."
"Its diverse set of features available on the cloud is of significant importance."
"In addition to the fact that we are more proactive in the detection of incident before they occur, we can on one click see the request path from the customer to the backend."
"The tool's most valuable feature is centralized logging. Elastic Common Search helps us to search for the logs across the organization."
"For full stack observability, Elastic is the best tool compared with any other tool like New Relic or AppDynamics or Dynatrace."
"The architecture and system's stability are simple."
"Machine learning is the most valuable feature of this solution."
"We're easily saving at least one hour per day using this solution."
"The main Microsoft feature is that it offers common integration of services, of data, of identity, meaning user accounts, user access, and privileged access."
"The platform has significantly enhanced our operational insight into the overall Microsoft 365 environment."
"The overall user experience with Microsoft Purview Audit is of higher quality than when it was branded as Compliance Center, and Microsoft consistently updates and evolves functionalities and the overall experience."
 

Cons

"The only challenging aspect for new users is often writing the query language."
"One example is the inability to monitor very old databases with the newest version."
"I would have preferred built-in tools to manage the indexes on deployment for better visual representation, as the initial feedback regarding system performance and data storage was fairly primitive and lacking."
"With Elastic, you need to code and program more things compared to Dynatrace."
"If we had some pre-defined templates for observability that we could start using right away after deploying it – instead of having to build or to change some of the dashboards – that would be helpful."
"Improving code insight related to infrastructure and network, particularly focusing on aspects such as firewalls, switches, routers, and testing would be beneficial."
"The solution needs to use more AI. Once the product onboards AI, users would more effectively be able to track endpoints for specific messages."
"Simplifying the parsing of logs and manual efforts would also be beneficial."
"I had a case where I spent three or four hours working deeply with a customer to explain how to work with eDiscovery, why Content Search is not there when it was before, what is an eDiscovery case, and why we are talking about all of this just to review a list of kept emails."
"We do have a Denial of Access happening."
"Areas for product improvement include enhancing customization options and integrating more comprehensive compliance features."
"We are still in the early stages of leveraging Microsoft Purview Audit. Currently, it's primarily used for the audit function."
 

Pricing and Cost Advice

"One needs to pay for the licenses, and it is an annual subscription model right now."
"Elastic Observability is cheaper than other similar solutions, such as Dynatrace. Its license calculation is based on various factors like data volume and physical infrastructure, particularly related to RAM capacity."
"We have been using the open-source version."
"There are two types: cloud and SaaS. They charge based on data ingestion, ingest rate, hard retention, and warm retention. I believe it costs around $25,000 annually to ingest 30GB of data daily. That is the SaaS version. There is also a self-managed license where the customer manages their own infrastructure on-prem. In such cases, there are three license tiers that respectively cost $5,000 annually per node, $7,000 per node, and $12,500 per node."
"The product is not that cheap."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
"So far, there are just the standard licensing fees. Several of the components are embedded in the license or are even open source. They're even free depending on what you use, which makes it even more appealing to someone that is discussing pricing of the solution."
"Elastic Observability's pricing could be better for small-scale users."
Information not available
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
9%
Comms Service Provider
7%
Manufacturing Company
7%
Financial Services Firm
12%
Computer Software Company
11%
Comms Service Provider
9%
Construction Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise16
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Elastic Observability?
The problem is their licensing model, which is a bit confusing. Many customers struggle to understand their total cost of ownership because Elastic licensing is not dependent on easy, quantifiable ...
What needs improvement with Elastic Observability?
After careful consideration about areas for improvement in Elastic Observability, aspects such as pricing, customization, implementation, and scalability could be improved. As a user of the system,...
What is your primary use case for Elastic Observability?
My use case for Elastic Observability is observability, as we upload our customers' data, including logs, and when there is an issue, we can analyze what went wrong.
What is your experience regarding pricing and costs for Microsoft Purview Audit?
It is not so expensive in comparison with other products, but I can tell you about an example.
What needs improvement with Microsoft Purview Audit?
I have seen areas for improvement, specifically in Microsoft Purview Audit or in general about Microsoft. I have had a situation with documentation. I had a customer who wanted to create alerts and...
What is your primary use case for Microsoft Purview Audit?
I work with Defender for IoT by chance because I see that we have enough reviews for Defender for Office 365 today, and we need reviews for some Azure products. I work with Azure products such as L...
 

Overview

 

Sample Customers

PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
Information Not Available
Find out what your peers are saying about Elastic Observability vs. Microsoft Purview Audit and other solutions. Updated: September 2026.
913,806 professionals have used our research since 2012.