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.
"Provides good performance and availability."
"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 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."
"The most valuable feature of AWS Directory Service is cost-cutting features."
"AWS has eliminated the downtime we waste when our on-premises resources go down."
"I like the manageability. Activate Connect makes it easier to assign information and to manage the resources in the network."
"Two-step authentication is very useful and important."
"This solution serves as the basis to understand the MS SSO and MFA capabilities."
"The portal version of the Azure active directory is pretty robust."
"We have the ability to define the email user in the designated field."
"It's multi-tenant, residing in multiple locations. The authentication happens quickly. Irrespective of whether I'm in Australia, the US, India, or Africa, I don't see any latency. Those are the good features that I rely on."
"We have a history of all our authentications and excellent integration with the Microsoft solutions we use at our company. It runs smoothly in Windows and macOS."
"It has things like conditional access. For example, if someone is accessing sensitive information, then we could force them to do multi-factor authentication. Therefore, we can stop access if it is coming from a location that we did not expect."
"Azure Active Directory has useful policy assigning and management."
"The scalability is good now, and I find it to be more stable and faster since scaling up to ESX."
"The AWS Directory Service should be easier to integrate."
"Can be improved by including on-premises access for services through Identity Access Management."
"The group policy can be improved."
"Some of the security protocols are difficult to understand."
"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."
"We had a problem with the schema uploading and setting up the directory when we are migrating our users from on-premises to cloud infrastructure."
"AWS could improve the number of regions. Azure has passed them. The ned more consistency, as far as the Northeast is concerned."
"The synchronization with the local Active Directory and synchronization with all of the users on the local and cloud could be better."
"I would like to see Microsoft communicate how they intend to manage legacy applications. Right now, you still have to deploy a hosted domain server (which comes at an extra cost) if you have a legacy application that cannot sync properly with the enterprise applications and the modern applications."
"The security policy of Azure Active Directory should be based on a matrix so that we can easily visualize which users have access to what."
"When we add some user groups, at times they will not be properly configured. Also, sometimes Azure AD is not aware of the group policy, like the control, device functions, and settings, in detail. For example, you cannot configure these settings through mobile devices. It doesn't provide the flexibility to do that. The other challenge is that a third-party application may provide access without authorization."
"Microsoft needs to make improvements in this regard and extend its services to other operating systems as well, especially when considering their widespread usage."
"I faced difficulties from Micorosft's end and during the transition from Microsoft Active Directory to Microsoft Entra ID. Sometimes, some of Microsoft's documentation could be a little outdated."
"I think the documentation and configuration are both areas that need improvement."
"The product takes at least ten minutes to activate privilege identity management roles."
AWS Directory Service is ranked 6th 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 "Allows users to authenticate from home and has excellent integrations in a simple, stable solution". AWS Directory Service is most compared with Microsoft Entra External ID, Google Cloud Identity, Okta Workforce Identity, Omada Identity and SailPoint IdentityIQ, whereas Microsoft Entra ID is most compared with Microsoft Intune, Google Cloud Identity, CyberArk Privileged Access Manager, Yubico YubiKey and Cisco Duo. 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.
