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."
"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."
"AWS Directory Service is secure."
"The support is very good. I would rate the technical support as a nine out of ten."
"The most valuable feature of AWS Directory Service is cost-cutting features."
"Two-step authentication is very useful and important."
"The most valuable feature is that because it's all in the cloud, you don't need to manage the infrastructure."
"AWS has eliminated the downtime we waste when our on-premises resources go down."
"Personally, I'm a great fan of Azure Active Directory due to the security and compliance features that are there in the classic or default Azure Active Directory."
"The most valuable feature of Azure AD is its ability to connect with services outside of Microsoft, although documentation is necessary to properly implement these connections."
"The user functionality enables us to provide different levels of access, across many applications, for each user. We can customize the access level and set a security level in connection with that access. For instance, we can require MFA. That is a feature that helps enhance our security posture a lot."
"The most valuable feature is Identity and Access Management. As an IT administrator, this feature allows me to manage access for users and groups."
"The security features, such as attack surface rules and conditional access rules, are the most valuable aspects of Azure AD."
"Configuring the domain and setting it up in the Azure portal is just three clicks to be honest."
"Microsoft Authenticator is highly secure."
"Overall the solution functions very well, such as the ability to access it from the cloud."
"The solution lacks certain features."
"AWS could improve the number of regions. Azure has passed them. The ned more consistency, as far as the Northeast is concerned."
"To get CloudWatch to monitor your memory and storage, you have to do some configuration within your server, which sometimes results in errors."
"Can be improved by including on-premises access for services through Identity Access Management."
"I would like to grant partial access to a table contained in a database without having to provide full access to the whole database."
"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."
"Some of the security protocols are difficult to understand."
"AWS Directory Service needs to improve processing."
"Sometimes, the notifications and alerts are not delivered properly, and we end up missing them. Also, the overall graphical user interface needs to be improved."
"They have had a few outages, so stability is a little bit of an issue. It is global. That is the thing. I know some of the other competitors are regionalized ID platforms, but Entra ID is global, so when something goes wrong, it is a problem because it underpins everything, whether you are logging in to M365 or you have single sign-on to Azure, Autopilot, Intune, Exchange mailbox or another application. If there is a problem with Entra ID, all of that falls apart, so its great strength and weakness is the global single tenant for it. Stability is a key area for me. Otherwise, it is generally pretty good."
"In terms of connecting the web application, there is technology for single sign-on. When we use it, the solution opens very slowly. It might be a bandwidth issue, and some content will not work on that portal."
"Transitioning to the cloud is very difficult. They need the training to make it easier."
"The role-based access control can be improved. Normally, the role-based access control has different privileges. Each role, such as administrator or user, has different privileges, and the setup rules for them should be defined automatically rather than doing it manually."
"The solution was difficult to scale because the group's configuration was complex. I would rate the scalability level of Azure Active Directory a five out of ten."
"I would like to see improvements made when it comes to viewing audit logs, sign-in logs, and resource tags."
"There is no documentation about how Microsoft will scale Azure AD for customers. It only mentions that it will scale out if you have a lot of requests but does not mention how in detail."
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.