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

Microsoft Defender for Cloud vs NGINX Ingress Controller comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 25, 2026

Review summaries and opinions

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

ROI

Sentiment score
7.1
Microsoft Defender for Cloud enhances ROI by improving security, productivity, and cost efficiency, despite perceived licensing costs.
Sentiment score
4.3
NGINX Ingress Controller reduces costs, simplifies API management, prevents downtime, and saves engineering hours compared to commercial alternatives.
Defender proactively indexes and analyzes documents, identifying potential threats even when inactive, enhancing preventative security.
Endpoint management at a government with 10,001+ employees
Identifying potential vulnerabilities has helped us avoid costly data losses.
Manager at CBTS
Compared to not having Microsoft Defender for Cloud in place, we definitely saw an advantage by not having downtime due to a security threat.
Principal Microsoft Consultant at MicroAge
I have seen a return on investment with NGINX Ingress Controller because most organizations, especially small organizations or SMBs, don't buy a specific load balancer, such as F5 load balancer or Fortinet ADC.
Network Security Engineer at IIPL
NGINX Ingress Controller improves performance in terms of load balancing, especially in a microservices environment with many APIs.
Ai Engineer at a tech vendor with 11-50 employees
When you weigh the cost of implementing this project against the potential losses from compromised security, its implementation is justified.
Consultor Independiente, Ingeniero De Bots, Ingeniero Cloud, Ai Engineer at Andela
 

Customer Service

Sentiment score
6.3
Microsoft Defender for Cloud support is knowledgeable with effective documentation, but first-tier delays impact overall satisfaction.
Sentiment score
6.0
NGINX Ingress Controller offers reliable customer service with mixed responsiveness, highly rated expertise, and optional paid support for NGINX Plus.
Since security is critical, we prefer a quicker response time.
Manager at CBTS
The support team was very responsive to queries.
Programme Manager- Cyber Fusion- Group CISO at a financial services firm with 10,001+ employees
They understand their product, but much like us, they struggle with the finer details, especially with new features.
Endpoint management at a government with 10,001+ employees
While they have improved their ticketing system, allowing online submissions and status checks, the skill levels of the technical staff seem to have reduced.
Senior Network At Dxc Technology Professional at DXC Technology
When I reported that there was a connection mismatch between a customer's existing environment and their DR, the technician came within fifteen minutes.
Network Security Engineer at IIPL
On NGINX Plus side, there is paid commercial support.
Senior Database Engineer, SRE at Interswitch Group
 

Scalability Issues

Sentiment score
7.5
Microsoft Defender for Cloud is highly scalable, seamlessly integrates across platforms, and efficiently handles growth, with room for feature improvement.
Sentiment score
7.4
NGINX Ingress Controller efficiently scales in Kubernetes, balancing traffic across services with easy configuration but faces minor annotation challenges.
As we have reduced our on-premises infrastructure, it is about how we can migrate workloads to the cloud to make it easier, and then having everything fully encompassed and secured within that area makes it much easier for us to scale as needed and grow.
Principal Microsoft Consultant at MicroAge
We are using infrastructure as a code, so we do not have any scalability issues with Microsoft Defender for Cloud implementation because our cloud automatically does it.
Senior Cloud Platform Engineer at Deutsche Börse
It has multiple licenses and features, covering infrastructures from a hundred to five hundred virtual machines, without any issues.
Snr. Infrastructure Architect (Data Centre) at LogicEra
The optimization is good, with a build on NGINX web binaries leveraging an asynchronous event-driven architecture that handles thousands of concurrent connections.
Senior Dev Ops Engineer at a tech vendor with 1,001-5,000 employees
We can scale it for multiple applications effectively.
Sr cloud engineer at a tech vendor with 201-500 employees
NGINX Ingress Controller is perfect for scaling.
Import Comliance Specialist at silicon21
 

Stability Issues

Sentiment score
7.6
Microsoft Defender for Cloud is stable and reliable, though minor update issues occur with older systems and internet latency.
Sentiment score
8.2
NGINX Ingress Controller is reliable with seamless integration, though traffic spikes may cause bottlenecks, needing resource management.
Defender's stability has been flawless for us.
Engineer at a computer software company with 201-500 employees
I have not experienced any crashes or downtime.
Head Of IT at Cirrus Response
Microsoft Defender for Cloud is very stable.
Cloud architect at a tech vendor with 1,001-5,000 employees
The stability in SSL for NGINX Ingress Controller Plus, which is the commercial one, is better than the open source.
Import Comliance Specialist at silicon21
I have not seen any issues integrating NGINX Ingress Controller with other security products, such as firewalls.
Senior Network At Dxc Technology Professional at DXC Technology
NGINX's data plane is rock solid.
Senior Database Engineer, SRE at Interswitch Group
 

Room For Improvement

Microsoft Defender for Cloud needs improved customization, automation, UI performance, policy management, integration, AI functions, and reduced licensing complexities.
Improving NGINX Ingress Controller involves better documentation, enhanced security, monitoring integration, faster deployment, and streamlined traffic and resource management.
Microsoft, in general, could significantly improve its communication and support.
Endpoint management at a government with 10,001+ employees
It would be beneficial to streamline recommendations to avoid unnecessary alerts and to refine the severity of alerts based on specific environments or environmental attributes.
Works at Coca-Cola HBC
The artificial intelligence features could be expanded to allow the system to autonomously manage security issues without needing intervention from admins.
Cloud Consultant at i-Community AG
This lightweight characteristic is a very significant advantage that prevents any overheads on the systems running the applications.
Network Security Engineer at IIPL
A small mistake can break the whole routing policies and structure, making it challenging to debug deployments at large scale, which takes time.
Senior Dev Ops Engineer at a tech vendor with 1,001-5,000 employees
I think NGINX Ingress Controller could be improved by adding many features and functions regarding firewalls, similar to what a professional API gateway offers.
Sr. DevOps Engineer at a tech vendor with 11-50 employees
 

Setup Cost

Microsoft Defender for Cloud offers flexible pricing but gets complex and costly, requiring careful evaluation, especially for advanced plans.
Enterprise buyers value NGINX Ingress Controller's flexible pricing options, despite varied opinions on F5's cost-effectiveness compared to competitors.
Security has essentially no cost when compared to the cost of a breach.
Director, Cloud and Modern Workplace at Informanix Technology Group
Every time we consider expanding usage, we carefully evaluate the necessity due to cost concerns.
Programme Manager- Cyber Fusion- Group CISO at a financial services firm with 10,001+ employees
We appreciate the licensing approach based on employee count rather than a big enterprise license.
Manager, Microsoft Technology Alliance at Silverfort
Regarding licensing costs for NGINX Ingress Controller, if you are talking about costs, F5 is always very costly.
Senior Network At Dxc Technology Professional at DXC Technology
It is basically a license through a subscription model. The subscription renews regularly.
Network Security Engineer at IIPL
The setup cost was also acceptable, and the licensing was straightforward.
Software Engineer at a outsourcing company with 201-500 employees
 

Valuable Features

Microsoft Defender for Cloud enhances security and compliance with AI-powered threat intelligence, automation, and multi-cloud integration for improved protection.
NGINX Ingress Controller enhances Kubernetes management with load balancing, security, and efficient routing, improving performance and cost-effectiveness.
The most valuable feature for me is the variety of APIs available.
Programme Manager- Cyber Fusion- Group CISO at a financial services firm with 10,001+ employees
This feature significantly aids in threat detection and enhances the user experience by streamlining security management.
Cloud Consultant at i-Community AG
The most valuable feature is the recommendations provided on how to improve security.
Cloud architect at a tech vendor with 1,001-5,000 employees
The main benefit is that it is better in performance, provides security with App Protect and WAF and DDoS, and delivers high performance and high stability.
Import Comliance Specialist at silicon21
The best features that NGINX Ingress Controller offers in my experience are that the ingress controller can perform content-based routing and SSL termination, which is usually not available on software-only solutions and typically comes with hardware-based solutions.
Network Security Engineer at IIPL
The annotations that we utilize with NGINX Ingress Controller help our team by allowing us to block or whitelist IPs for certain publicly accessible services, ensuring that only specific public IPs can access those ingress URLs while blocking others.
Sr. DevOps Engineer at a tech vendor with 11-50 employees
 

Categories and Ranking

Microsoft Defender for Cloud
Ranking in Container Management
8th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
89
Ranking in other categories
Vulnerability Management (9th), Container Security (4th), Cloud Workload Protection Platforms (CWPP) (1st), Cloud Security Posture Management (CSPM) (4th), Cloud-Native Application Protection Platforms (CNAPP) (5th), Data Security Posture Management (DSPM) (7th), Microsoft Security Suite (6th), Compliance Management (4th), Cloud Detection and Response (CDR) (3rd)
NGINX Ingress Controller
Ranking in Container Management
9th
Average Rating
8.4
Reviews Sentiment
6.0
Number of Reviews
20
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the Container Management category, the mindshare of Microsoft Defender for Cloud is 4.0%, up from 1.1% compared to the previous year. The mindshare of NGINX Ingress Controller is 1.7%, up from 1.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management Mindshare Distribution
ProductMindshare (%)
Microsoft Defender for Cloud4.0%
NGINX Ingress Controller1.7%
Other94.3%
Container Management
 

Featured Reviews

RW
Head Of IT at Cirrus Response
Cloud security has cut investigation time and now reveals threats faster but needs simpler oversight
When deploying AI applications, my key security concerns with Microsoft Defender for Cloud are data loss, leakage of data, and guardrails around the actual AI, and I am hoping that this is going to help me put those guardrails in place and identify data exfiltration. Microsoft Defender for Cloud has not helped me manage and secure multi-cloud environments, as we are 100 percent Microsoft and have not really got it in any other environment at all. I am not yet using the unified AI-powered security feature offered by Microsoft Defender for Cloud, but that is coming. I am not yet using the integrated XDR feature of Microsoft Defender for Cloud, but that is coming. I am not yet utilizing the GenAI threat protection features of Microsoft Defender for Cloud. That is also coming and a lot of that will come from learning it here. I have enabled the agentless scanning in my cloud environment with Microsoft Defender for Cloud. Assessing the impact on my workload protection without needing to install agents with Microsoft Defender for Cloud makes it a lot easier, but it also identifies a lot more, which puts more load on me sometimes. I would advise another organization considering Microsoft Defender for Cloud that it is the most logical route to follow if their whole ecosystem is Microsoft. It is easy to implement and it is very self-explanatory when doing it, making sense to just follow the steps as it is too simple, really. I would rate this review a 7.5 out of 10.
Suleiman  Mohammed - PeerSpot reviewer
Senior Database Engineer, SRE at Interswitch Group
Routing for long-lived data connections has improved but protocol-aware checks still need work
NGINX Ingress Controller can be improved, and my team's concern would be database protocol-aware health checks for Transport Server since that is what NGINX is more focused on. Right now, even on Plus, a Transport Server health check is essentially a TCP connect or maybe a basic send-expect. For a database, that is a weak signal. The listener being up tells you almost nothing about whether Postgres is actually serving, whether a replica is lagging, or whether it is in recovery. I would love a way to define a health check that does something protocol-aware, even something as simple as you open a connection, run a SELECT one, which is the most popular test, and expect a row for Postgres or a PING for Redis. Without that, I am relying on the database's own infrastructure to pull bad replicas, and the ingress will happily continue routing to a replica that answers TCP but is serving stale reads. Better idle connection management for long-lived stream connections can also be improved. A pooled database connection sitting idle between transactions is healthy in my opinion, but the proxy's instinct is to reap idle connections. You can crank timeouts way up, but that is a blunt instrument. I would like to add that specifically for databases, the need for improvement becomes clearer. Every client connection through NGINX becomes a backend connection, one-to-one. A client connection through NGINX and a client connection through a connection pooler are sitting because they are going to get sent to the backend connection. It does not multiplex; it does not understand transaction boundaries. It cannot reuse a connection across clients. If you put it in front of Postgres without a real pooler behind it, you have just built a very efficient way to exhaust the max connection. The architecture is always client, ingress, connection pooler which is either pgBouncer or ProxySQL, then the actual engine which is Postgres or MySQL. Never let it be clients straight to the database. NGINX Ingress Controller's mode is one client connection to one backend connection with no multiplexing and no protocol awareness, which would be an issue for you.
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Computer Software Company
9%
Manufacturing Company
8%
Outsourcing Company
7%
Outsourcing Company
24%
Computer Software Company
13%
Manufacturing Company
8%
Financial Services Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business31
Midsize Enterprise12
Large Enterprise49
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise3
Large Enterprise10
 

Questions from the Community

How is Prisma Cloud vs Azure Security Center for security?
Azure Security Center is very easy to use, integrates well, and gives very good visibility on what is happening across your ecosystem. It also has great remote workforce capabilities and supports a...
What is your experience regarding pricing and costs for Microsoft Defender for Cloud?
My experience with pricing, setup costs, and licensing was that the license cost was the only consideration. Setup and support had no issues.
What needs improvement with Microsoft Defender for Cloud?
To improve Microsoft Defender for Cloud, I think pricing-wise, the license price is a little bit higher from an ingestion cost perspective. Depending on what license you choose, you might have to p...
What is your experience regarding pricing and costs for NGINX Ingress Controller?
NGINX Ingress Controller was used through the Azure Marketplace, allowing control over precious aspects including pricing, setup cost, and licensing for clients. The best cost-effective solution ca...
What needs improvement with NGINX Ingress Controller?
NGINX Ingress Controller can be improved as it has many features that could be further refined.
What is your primary use case for NGINX Ingress Controller?
NGINX Ingress Controller is used to manage traffic, including HTTPS traffic. For containerized-based applications, NGINX Ingress Controller can be enabled as an event-based request that goes to the...
 

Also Known As

Microsoft Azure Security Center, Azure Security Center, Microsoft ASC, Azure Defender
No data available
 

Interactive Demo

Demo not available
 

Overview

 

Sample Customers

Microsoft Defender for Cloud is trusted by companies such as ASOS, Vatenfall, SWC Technology Partners, and more.
Information Not Available
Find out what your peers are saying about Microsoft Defender for Cloud vs. NGINX Ingress Controller and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.