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 is ease of use."
"The support is very good. I would rate the technical support as a nine out of ten."
"We can provide specific access to people based on what they need from our accounts."
"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."
"Provides good performance and availability."
"The most valuable feature of AWS Directory Service is cost-cutting features."
"AWS Directory Service is secure."
"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."
"The solution allows users to authenticate from home, and the Office 360 integration is advantageous."
"The most valuable feature is the authentication platform."
"We have the ability to define the email user in the designated field."
"The most valuable feature of this solution is that is easy to use."
"Microsoft Entra ID's valuable features include integration capabilities, a simplified Active Directory approach, scalability, conditional access, and privileged identity management."
"Being able to use Azure AD means that you can use some of the Azure AD security features like Advanced Password Protection. As well as querying your normal password requirements like lengths and complexity, Azure AD has a feature in which you can put specific words. It can be words to do with your company, words to do with your company location, or words that a lot of your employees would otherwise use. You can disallow them. It's very good at making more obvious passwords, ones they're not allowed to use anymore. That's a good feature."
"It is a very straightforward implementation."
"Can be improved by including on-premises access for services through Identity Access Management."
"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."
"AWS could improve the number of regions. Azure has passed them. The ned more consistency, as far as the Northeast is concerned."
"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."
"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."
"I would like to see better integration with other business solutions."
"I would like to see improvements made when it comes to viewing audit logs, sign-in logs, and resource tags."
"Microsoft has so many different requirements and priorities that sometimes they don't invest all their energy into the products that you have expectations to investigate."
"At first, it was a bit challenging to come up with a workaround that would get authentication to work."
"Initially, we wanted to exclude specific users from MSA. So, we had a condition policy, which forces MSA for all the users. So we wanted to exclude users who are using an NPS extension. So it was not listed, as a NPS extension was not listed outside an application, in actual, so, we go back and were not able to exclude users using NPS extension from MSA. So that was one limitation that we found and we had to work around that."
"Whatever business requirements we needed in the past three years, users were created, with the name of the user and they were not connected with the Active Directory. We were trying to in house in three years and with directory, but we were not able to achieve it."
"Transitioning to the cloud is very difficult. They need the training to make it easier."
"If your organization requires additional security then the subscription will be more expensive."
"Something that can be improved is their user interface"
AWS Directory Service is ranked 9th 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, SailPoint IdentityIQ, Okta Workforce Identity and Omada Identity, whereas Microsoft Entra ID is most compared with Microsoft Intune, Google Cloud Identity, CyberArk Privileged Access Manager, Cisco Duo 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.