We performed a comparison between AWS Directory Service and Microsoft Entra ID based on real PeerSpot user reviews.
Find out in this report how the two Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature of AWS Directory Service is cost-cutting features."
"Provides good performance and availability."
"AWS has eliminated the downtime we waste when our on-premises resources go down."
"AWS Directory Service is secure."
"Two-step authentication is very useful and important."
"The support is very good. I would rate the technical support as a nine out of ten."
"We like the fact that it's got such great redundancy."
"AWS handles everything on the backend requiring minimal legwork from our team. We only require a dedicated database administrator while depending on Amazon for RDS."
"The two-step authentication is the most valuable."
"The scalability is quite good."
"It is a central point where we provide the cloud lock-in for our company. We focus the multi-factor authentication within Azure AD before jumping to other clouds or software as a service offerings. So, it is the central point when you need to access something for our company within the cloud. You go to Azure AD and can authenticate there, then you move from there to the target destination or the single sign-on."
"We have the ability to define the email user in the designated field."
"All of the features are amazing, such as identity governance and privileged identity management."
"The most valuable feature is that it is very easy to implement, you don't need a lot of effort to set up the solution. This is the most advantageous point, that you can do anything on Azure without taking too much time."
"The scalability capabilities are quite high."
"We use BitLocker for policy enforcement. And now, because of the Microsoft 365 Business Premium package, we get Intune as a part of it. That's very useful for us for setting policies and managing the systems. The biggest strength of Azure AD is Intune."
"Can be improved by including on-premises access for services through Identity Access Management."
"The group policy can be improved."
"The solution lacks certain features."
"Our only complaint is that you cannot integrate your Exchange server. Or, if you are planning to install an Exchange server on your Amazon EC2 instance, then you need to configure Active Directory on EC2 instance. We would like for this limitation to be lifted."
"AWS Directory Service needs to improve processing."
"The AWS Directory Service should be easier to integrate."
"I would like to grant partial access to a table contained in a database without having to provide full access to the whole database."
"To get CloudWatch to monitor your memory and storage, you have to do some configuration within your server, which sometimes results in errors."
"Documentation I think is always the worst part with what Azure's doing right now across the board."
"Entra ID is not battle-tested or stable enough to support a business of our size. There are some design issues specifically around support for legacy services."
"I think the solution can improve by making the consumption of that data easier for our customers."
"The product takes at least ten minutes to activate privilege identity management roles."
"When you start to deal with legacy applications, provisioning is not as intuitive."
"Four years ago, we had an issue with Azure AD. We wanted to reverse sync from Azure AD to on-prem Active Directory, but we couldn't achieve this. Azure AD could connect only in one way, for example, from your site to Azure. If you needed to do the reverse and connect from Azure to on-prem, there was no way to achieve it. We asked Microsoft, and they told us that they don't support it."
"The solution has not saved costs. While we’ve eliminated some tools, there are some other features that we are dependent on as admin, which are not yet integrated with Azure AD."
"My only pain point in this solution is creating group membership for devices."
AWS Directory Service is ranked 10th in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 12 reviews while Microsoft Entra ID is ranked 1st in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 190 reviews. AWS Directory Service is rated 8.6, while Microsoft Entra ID is rated 8.6. The top reviewer of AWS Directory Service writes "Extends AD identity and management capabilities to AWS resources". On the other hand, the top reviewer of Microsoft Entra ID writes "Saves us time and money and features Conditional Access policies, SSPR, and MFA". AWS Directory Service is most compared with Microsoft Entra External ID, Google Cloud Identity, SailPoint Identity Security Cloud and Okta Workforce Identity, whereas Microsoft Entra ID is most compared with Microsoft Intune, Google Cloud Identity, CyberArk Privileged Access Manager, Ping Identity Platform and Okta Workforce Identity. See our AWS Directory Service vs. Microsoft Entra ID report.
See our list of best Identity and Access Management as a Service (IDaaS) (IAMaaS) vendors.
We monitor all Identity and Access Management as a Service (IDaaS) (IAMaaS) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.