It's not very easy to configure, in my view. We have to do some work behind the scenes. It's not very simple. We have to do it very carefully, and we need to monitor this enablement as well. But apart from that, I didn't see any kind of challenges. So, in my opinion, configuration is the main trouble for them. It is something that can be done to be better. Not just configuration. You need an expert who knows the ins and outs of these security solutions. In my experience, people struggle with configuration. While configuring, we get this error, we get that error, and then we try to fix those issues. I have seen those. It's not straightforward.
The implementation of Azure DDoS Protection results in a decrease in our bandwidth capacity and should be optimized to reduce resource consumption. I would like to have an analytic dashboard for reporting added in a future release.
Analyst - Security Officer at a non-tech company with 201-500 employees
Real User
2021-08-24T19:21:00Z
Aug 24, 2021
Sometimes, it is hard for our staff to keep track of changes (in the GUI) between different projects, because there are constant changes. As a result, it is hard to manage, recall, and see all the features because they have been moved from one place to another.
Azure DDoS Protection, combined with application design best practices, provides defense against DDoS attacks.
To learn more about our solution, ask questions, and share feedback, join our Microsoft Security, Compliance and Identity Community.
It's not very easy to configure, in my view. We have to do some work behind the scenes. It's not very simple. We have to do it very carefully, and we need to monitor this enablement as well. But apart from that, I didn't see any kind of challenges. So, in my opinion, configuration is the main trouble for them. It is something that can be done to be better. Not just configuration. You need an expert who knows the ins and outs of these security solutions. In my experience, people struggle with configuration. While configuring, we get this error, we get that error, and then we try to fix those issues. I have seen those. It's not straightforward.
The implementation of Azure DDoS Protection results in a decrease in our bandwidth capacity and should be optimized to reduce resource consumption. I would like to have an analytic dashboard for reporting added in a future release.
The visibility could be better. We would like to have better metrics, so we could see all the information in a central place.
The reporting aspect and dashboard management monitoring need improvement.
It's a costly solution, so it should only be used by large organizations where protection is a major priority. The UI needs to be improved.
Azure DDoS Protection could improve on the reporting.
Sometimes, it is hard for our staff to keep track of changes (in the GUI) between different projects, because there are constant changes. As a result, it is hard to manage, recall, and see all the features because they have been moved from one place to another.