What is our primary use case?
Microsoft Defender for Identity is used to protect our on-premises and hybrid Active Directory environment. Our organization has a hybrid infrastructure where people can log in internally and externally via ADFS. The tool focuses on detecting and identifying advanced threats that can impact identities. It utilizes user and entity behavior analytics, machine learning capabilities, and provides security posture assessment for the Active Directory infrastructure.
What is most valuable?
Our Active Directory implementation is a hybrid one. The advanced threat protection is one of the strengths of
Microsoft Defender for Identity, as it utilizes user and entity analytics and can detect indicative attacks. It identifies lateral movements, privilege escalations, and alerts on potential attacks. The tool is also used for security posture assessment. The seamless integration with other Microsoft solutions within our Microsoft-centric environment is also a major advantage.
What needs improvement?
One area that needs improvement is the number of alerts generated, leading to alert fatigue. Reducing false positives is something we've been working on with Microsoft.
For how long have I used the solution?
I have experience using Microsoft Defender for Identity for over four years.
What do I think about the stability of the solution?
Microsoft Defender for Identity is quite robust and built on
Azure hyperscale infrastructure, with a 99% availability. I would rate its stability between a seven and nine.
What do I think about the scalability of the solution?
In a Microsoft-centric organization, especially with
Azure infrastructure and
Office 365, Microsoft Defender for Identity is scalable. Microsoft provides tools and guidance to handle specific deployment needs. However, I do not have firsthand experience with its scalability outside the Microsoft ecosystem.
How are customer service and support?
The quality of support is very good, but troubleshooting can take time due to complex setups and the need to provide many logs. I rate the support as a seven.
Which solution did I use previously and why did I switch?
Before migrating to the Cloud, we only used on-premises solutions without the need for Microsoft Defender for Identity. As we migrated and integrated Active Directory with
Azure AD and acquired
Office 365 licenses, Microsoft Defender for Identity became necessary.
How was the initial setup?
The initial setup was straightforward as Microsoft Defender for Identity is a SaaS solution. A Microsoft administrator simply needs to enable it, and there isn't much complexity in the implementation.
What about the implementation team?
We engaged Microsoft for implementation support, alongside sourcing industry vendor SIs.
What's my experience with pricing, setup cost, and licensing?
Pricing is part of a bundled deal from Microsoft. Various licenses like E3, E5, or separate bundles are used. From an organization perspective, using E5 licenses is value for money, especially if Azure and Office 365 are already in use.
What other advice do I have?
I rate Microsoft Defender for Identity an eight out of ten. Although it can be improved in certain areas like alert management, it provides strong advanced threat protection and integrates well within a Microsoft-focused environment. My overall rating for the solution is an 8.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure