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."We like the fact that it's got such great redundancy."
"The most valuable feature of AWS Directory Service is cost-cutting features."
"Provides good performance and availability."
"I like the manageability. Activate Connect makes it easier to assign information and to manage the resources in the network."
"The most valuable feature is ease of use."
"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."
"AWS Directory Service is secure."
"The single sign-on across multiple platforms is really the true advantage here. That gives you one ID and password for access to all your systems. You don't need to manage a plethora of different user IDs and passwords to all the systems that you're going to access."
"It's very easy to run and it's part of their ecosystem and I don't think it's going anywhere anytime soon."
"Microsoft Authenticator is highly secure."
"Privileged Identity Management (PIM), managed identities, dynamic groups, and extension and security attributes are all great features."
"It has been stable, and we haven't had any issues since we started to use it."
"It is pretty good in terms of stability."
"Don't delay implementing this solution, it's the best thing you can do for your identity protection."
"Two very important features in terms of security are governance and compliance through the Conditional Access policies and Azure Log Analytics."
"AWS could improve the number of regions. Azure has passed them. The ned more consistency, as far as the Northeast is concerned."
"Some of the security protocols are difficult to understand."
"I would like to grant partial access to a table contained in a database without having to provide full access to the whole database."
"Can be improved by including on-premises access for services through Identity Access Management."
"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."
"The solution lacks certain features."
"AWS Directory Service needs to improve processing."
"The group policy can be improved."
"Azure Active Directory could benefit by adding the capability for identity life cycle for the on-premise solution. For example, an HR solution, which is built on-premise or, in general, better on-premise capable solutions."
"The management interface has some areas that need improvement."
"There is no great solution in the cloud for Conditional Access authentication and RADIUS-type authentication."
"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."
"There are some features, where if you want to access them, then you need to make use of PowerShell. If someone is not really versed in PowerShell scripting, then they would definitely have issues using some of those features in Azure Active Directory."
"In a hybrid deployment, when we update a license by changing the UPN or email address of a user, it does not get updated automatically during normal sync. This means that we have to update it manually from Azure, which is something that needs to be corrected."
"Customers should be informed that public review features are not intended for production use."
"There is a lot of room for improvement in terms of its integration with the local Active Directory. There are some gaps in terms of the local Active Directory through which Microsoft is syncing our environment from our data center. There should be the availability of custom attributes on Azure Active Directory. In addition, there should be the availability of security groups and distribution groups that are residing on the local Active Directory. Currently, they are not replicated on Azure Active Directory by default."
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.