It's a very good solution. You can manage your entity's enterprise identity using Azure Active Directory, and again, you can do several administrative activities. You can also use your Power Shares sorting and interfacing the endpoint.
Senior Analyst - IT Development at a tech company with 10,001+ employees
It is a very straightforward implementation. It helps us with maintaining enterprise identities.
Pros and Cons
- "It is a very straightforward implementation."
- "It helps us with maintaining enterprise identities."
- "We find the Integration accessory integration the most valuable feature; you can have your application integrated with an actual directory, you don't need to do much code, you can use interfaces and it's a direct integration, so there is no need to worry about the requirements of your application."
- "The licensing cost is a bit prohibitive."
What is our primary use case?
How has it helped my organization?
It helps us with maintaining enterprise identities and integrating enterprise in those applications are some of the assignments.
We do have an expanded feature. We have captured video, so that other people can get their hands on getting used to it. That is, they can get used to the platform and implement it from the beginning.
What is most valuable?
We find the Integration accessory integration the most valuable feature. You can have your application integrated with an actual directory. You don't need to do much code, you can use interfaces and it's a direct integration. So, no need to worry about the requirements of your application.
What needs improvement?
The licensing cost is a bit prohibitive.
Buyer's Guide
Microsoft Entra ID
October 2026
Learn what your peers think about Microsoft Entra ID. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,700 professionals have used our research since 2012.
For how long have I used the solution?
Less than one year.
What do I think about the stability of the solution?
I have not encountered any issues of stability with the product.
What do I think about the scalability of the solution?
It scales as far as it depends on the contract. So, it is useful, with plenty of management capabilities. It is pretty flexible, scaling, you can scale in or out as per your requirements.
How are customer service and support?
I have not contacted tech support.
How was the initial setup?
It is a very straightforward implementation, and you pay as you go. It depends on your number of users, number of applications integrated, and how you prepare your topologies (the arrangements of the network). So, it is pretty much flexible. You can custom tailor it as per your business and target , business implementation and requirement.
Which other solutions did I evaluate?
I have some prior experience with Oracle Unified Directory, as well. It is a less compliant directory service.
In comparison, Azure Active Directory is mostly used with tighter integration. In most of the cases, enterprises are using Office 365 for the communication site online. If you have a requirement like integration with Office 365, then Azure Active Directory is a perfect solution. If you want to integrate other applications or workstations, you can use any compliant directory that works.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Director General
The most important feature is the factor identification.
Pros and Cons
- "The most valuable feature is the factor identification; I find that it is a natural integration and it is just a natural step, and I do not need to do anything else."
- "I think there is room for improvement with actually discussing, and advertising Microsoft as a an authenticator. Many people just get confused and use Google, and I think if Microsoft would make more of an effort to penetrate the market, that would be key."
What is our primary use case?
We primarily use this solution for tracking authentication.
How has it helped my organization?
The quantum we are using is probably the authentication The security-based factor of authentication.
What is most valuable?
The most valuable feature is the factor identification. I find that it is natural integration, and it is just a natural step. I do not need to do anything else.
What needs improvement?
I think there is room for improvement with actually discussing, and advertising Microsoft as a an authenticator. Many people just get confused and use Google. It's weird because it's exactly the same way that it works. But it's there, it's definite region to start the people is more used to use their the Google authenticator instead of the Microsoft authentication. I think if Microsoft would make more of an effort to penetrate the market, that would be key.
In addition, it would be nice to have a biometric authentication like voice ID, or any of your medical ID. This would be a nice additional feature for Azure to have.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
We experienced the aset surge that happened a month or so ago. There was a storm that broke one of the data centers in south-central. The functionality of active directive for Microsoft support was in shortage. It took a day to return back to functional use.
What do I think about the scalability of the solution?
The solution is scalable for our needs.
How are customer service and technical support?
I have not needed to request technical support. All of the Microsoft guides are really good and are very helpful.
Which solution did I use previously and why did I switch?
I know more about Microsoft than any other technology, that's why I didn't look for any other competitors.
How was the initial setup?
It was a very straightforward initial setup. To be honest, we are a pretty small company so for us it's one portal and everything is there. It's not that complicated.
What other advice do I have?
I like it, I love it and it works fine.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Microsoft Entra ID
October 2026
Learn what your peers think about Microsoft Entra ID. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,700 professionals have used our research since 2012.
Domain Admin at a government with 1,001-5,000 employees
Enhanced user and multifactor authentication experience with a straightforward setup
Pros and Cons
- "The most valuable feature is the ability to authenticate users using Microsoft Entra ID."
- "I would like to see some additional attributes for user objects in Microsoft Entra, especially for tasks such as users and account validation, including guest users and guest accounts."
What is our primary use case?
We are using Microsoft Entra ID for Microsoft services and cloud services such as email and Teams.
How has it helped my organization?
We have seen benefits like user authentication and multifactor authentication, which are advantageous for us.
What is most valuable?
The most valuable feature is the ability to authenticate users using Microsoft Entra ID.
What needs improvement?
I would like to see some additional attributes for user objects in Microsoft Entra, especially for tasks such as users and account validation, including guest users and guest accounts.
For how long have I used the solution?
I have been using the solution for approximately three years.
What do I think about the stability of the solution?
We experienced some performance issues with the solution.
How are customer service and support?
Technical support experiences can vary. Sometimes the support is good, and sometimes it requires escalation of the problem. Usually, we have a good experience. I would rate their technical support seven out of ten.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We did not have any similar solutions before Microsoft Entra ID.
How was the initial setup?
Starting to work with it was straightforward, and the deployment process was okay.
What about the implementation team?
I am not aware of the details regarding the implementation strategy as I need to ask our security engineers.
What other advice do I have?
I'd rate the solution nine out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Tech Services Asst at a insurance company with 501-1,000 employees
Single sign-on has unified identity management and provides reliable daily access control
Pros and Cons
- "I'm happy to use it."
What is our primary use case?
Our main use case for Microsoft Entra ID is essentially Active Directory.
What is most valuable?
From what I understand, Microsoft Entra ID allows our Active Directory to communicate with Intune, which verifies the user. I could be totally wrong about that.
Since implementing Microsoft Entra ID, I don't think we've had any incidents. We're a smaller organization, though.
What needs improvement?
I don't think Microsoft Entra ID needs anything further for the next release.
For how long have I used the solution?
I have been using Microsoft Entra ID for a year and a half, since I've been in my current role. I don't believe we used Intune at my last job.
Which solution did I use previously and why did I switch?
Prior to adopting Microsoft Entra ID, we did not use another solution to address a similar need.
What other advice do I have?
Our approach to defending against token theft and nation-state attacks since implementing Microsoft Entra ID predates my time at the organization. Since I've been there, we use a different company for security.
We don't use passkeys yet, so device-bound passkeys in Microsoft Authenticator haven't affected our organization's approach. We're very behind on everything.
Overall, I'd rate Microsoft Entra ID a 10 on a scale of 1 to 10, with 1 being the worst and 10 being the best. I don't have any issues with it. I'm happy to use it.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Nov 20, 2026
Flag as inappropriateFunctional Architect at a computer software company with 51-200 employees
Centralized access control has improved secure user management across all organizational apps
Pros and Cons
- "Microsoft Entra ID is an easy way to manage users across every application the organization uses."
- "Because I scale up IT, I feel that a better user experience, especially for beginners, would be beneficial when deploying Microsoft Entra ID, because it is the key for the whole organization."
What is our primary use case?
My main use cases for Microsoft Entra ID are managing users and managing security organization-wide.
What is most valuable?
The features of Microsoft Entra ID that I appreciate the most are the connectivity with all software and databases and having one location for everything.
Microsoft Entra ID is an easy way to manage users across every application the organization uses.
Microsoft Entra ID has an impact on secure access to apps and resources in my environment. It provides security by managing security access in one place, for example, to Dynamics 365. Those are the applications that I work on.
What needs improvement?
In my opinion, Microsoft Entra ID can be improved. I will think about what could be improved and come back to that.
For how long have I used the solution?
I have been using Microsoft Entra ID for four years.
What do I think about the stability of the solution?
I have never had any issues with the stability and reliability of Microsoft Entra ID, so I cannot speak to that, but I am a fan of it.
How was the initial setup?
Because I scale up IT, I feel that a better user experience, especially for beginners, would be beneficial when deploying Microsoft Entra ID, because it is the key for the whole organization.
What other advice do I have?
My organization's approach to defending against token theft and nation-state attacks has not changed since implementing Microsoft Entra ID.
On a scale of 1 through 10, I would rate Microsoft Entra ID overall as eight.
My advice to others is that it is a great way to manage all your users and all your access from one place in a very secure way. It integrates well with the whole Microsoft ecosystem.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Nov 20, 2026
Flag as inappropriateIT Solutions Consultant at a comms service provider with 10,001+ employees
Centralized identity has strengthened secure access and protected sensitive resources
Pros and Cons
- "Microsoft Entra ID is the center of identity and management, and we find it very helpful for connecting to every application easily."
- "Microsoft Entra ID is the center of identity and management, and we find it very helpful for connecting to every application easily."
- "My experience with pricing, setup cost, and licensing is not so bad, but one thing is that the Microsoft license is getting higher and higher every year."
- "My experience with pricing, setup cost, and licensing is not so bad, but one thing is that the Microsoft license is getting higher and higher every year."
What is our primary use case?
My main use case for Microsoft Entra ID is to control our identities.
What is most valuable?
The feature of Microsoft Entra ID that I like the most is the control of administrators and members, among other things.
Microsoft Entra ID benefits our organization because security incidents have recently occurred frequently in Japan. In that case, we have to block anonymous accounts, and Microsoft Entra ID helps protect us from attackers and similar threats.
Implementing Microsoft Entra ID affects our secure access to apps and resources in our environment. It is easy to connect to other SaaS services. Normally, our users want to connect to other services at one point. Microsoft Entra ID is the center of identity and management, and we find it very helpful for connecting to every application easily.
Microsoft Entra ID's integration capabilities influence our Zero Trust model. When we connect to other sites, especially the internet and the internal network, Microsoft Entra ID selects which person is correct to connect to specific resources and so on. That is very helpful and protects our environment.
The account service is very important for implementing our security for the file server and SharePoint because no one can access that file server easily. If we want to access the file server, we have to have the right account. That is the most important thing, and it implements our security.
Since implementing Microsoft Entra ID, I think our organization's approach to defending against token theft and nation-state attacks has changed. Our company has its own product for a single sign-on service, but we dramatically changed everything to Microsoft Entra ID.
Token replay detection, attacker-in-the-Middle detection, and Verified Threat Actor IP in Microsoft Entra ID Protection have an impact on defending against these threats. I think Microsoft Entra ID Protection is very important, especially attacker-in-the-Middle detection.
The implementation of device-bound passkeys in Microsoft Authenticator has strengthened our organization's security. Our devices are highly protected, although sometimes the strong security measures can make it a little difficult to sign in. If we forget our credentials or get locked out, we may need to contact our IT support team to regain access. However, I think this security measures are very important because if we lose our PC or leave it somewhere, it is difficult for someone else to access it.
What needs improvement?
I think the cloud service is one of the important areas where Microsoft Entra ID can be improved. Maybe 10 or 20 years ago, the AD service was only local, and we could not access Microsoft Entra ID easily. It is a little challenging to access internal divisions through Microsoft Entra ID. However, now Microsoft Entra ID is on the cloud, and we can manage our network service easily. My company is a network company, so we consult our clients on moving from the MPLS service to an open internet service because Microsoft Entra ID is on the cloud. That is a very improved thing.
For how long have I used the solution?
I have been using Microsoft Entra ID for almost five or six years in my company.
What do I think about the scalability of the solution?
Microsoft Entra ID scales well with the growing needs of our organization. It is very good. Our company sometimes does M&A of other companies, and in that case, we have to add other accounts and connect them to Microsoft Entra ID. In that case, we are expanding the environment.
The process of expanding usage of Microsoft Entra ID is very easy because the GUI is very beautiful. If I do not know the details of the selection, I can easily get the meaning of the option.
How are customer service and support?
On a scale of 1 to 10, I rate customer service and technical support at eight or nine.
Which solution did I use previously and why did I switch?
Prior to adopting Microsoft Entra ID, I was not using another solution to address similar needs. I love Microsoft Entra ID. In my company, if I ask someone what the best solution is for a single sign-on service and so on, we definitely approach Microsoft Entra ID.
What was our ROI?
I have not seen a return on investment with Microsoft Entra ID.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is not so bad, but one thing is that the Microsoft license is getting higher and higher every year. It is a little challenging for us to decide the budget, so that is a little challenging.
Which other solutions did I evaluate?
I considered other solutions before selecting Microsoft Entra ID. I forgot the name, but we were thinking about another product. However, Microsoft connects easily with other Microsoft services, and that is one of the big reasons why we selected Microsoft Entra ID.
What other advice do I have?
On a scale of 1 to 10, I also rate Microsoft Entra ID overall at eight or nine.
My advice for other organizations considering Microsoft Entra ID is that if a customer uses Microsoft products such as Office 365 or Azure, they should use Microsoft Entra ID, because every product is related and I believe Microsoft Entra ID is the center of the Microsoft products. They should use it even if they use another accounting service. Microsoft is the center for Microsoft.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Last updated: Nov 20, 2026
Flag as inappropriateIdentity Management Specialist at Cal State Univ Long Beach
Identity management has become smoother while attribute control still needs improvement
Pros and Cons
- "When identities already have a certain tag, they get into the group, they are assigned to the applications, and I never have to do anything."
- "For the next release, Microsoft Entra ID should expand the schema so that it is more similar to on-prem Active Directory."
What is our primary use case?
My main use cases for Microsoft Entra ID are identity management, single sign-on, self-service password requests, and app assignments.
What is most valuable?
The feature I like most about Microsoft Entra ID is that it is pretty good overall. It is flexible, although not extremely flexible, and I like that we are able to sync our identities from on-prem to Microsoft Entra ID. That helps us a lot.
These features have helped our organization a lot, especially for app assignment. It makes assignment really easy because we can use dynamic groups. When identities already have a certain tag, they get into the group, they are assigned to the applications, and I never have to do anything. I also like that it reduces the help desk's time when resetting passwords because users can reset them themselves.
The implementation of Microsoft Entra ID has a positive impact on our secure access to apps and resources. It is positive because we are able to manage more applications. Before, everything was manual and we did it all on-prem, but now with the cloud, it is much easier and we can have a greater variety of apps.
Our organization's approach to defending against token theft and nation-state attacks has changed since implementing Microsoft Entra ID.
The impact on defending against these threats comes from the last two features: Verified Threat Actor IP and Microsoft Entra ID Protection.
What needs improvement?
For the next release, Microsoft Entra ID should expand the schema so that it is more similar to on-prem Active Directory. It should also provide a way to avoid having all the attributes visible on the portal, so that some are hidden and visible only to admins.
For how long have I used the solution?
I have been using Microsoft Entra ID for at least 10 years.
What do I think about the stability of the solution?
The stability and reliability of Microsoft Entra ID are good. I have not experienced any downtime, crashes, or performance issues. Sometimes I see that loading sign-in logs is a little bit slower, but I have not noticed anything else. The issue that occurred last week was not really related to Microsoft Entra ID.
What do I think about the scalability of the solution?
Microsoft Entra ID scales well with our growing needs as an organization.
We have expanded our usage of Microsoft Entra ID, and the expansion process is smooth. Every time we try something, it is pretty smooth. We are trying to expand even more because what we currently use for identity and access management is Microsoft Identity Manager, which reaches end of life in January 2029. We expect to move everything that system does into Microsoft Entra ID, possibly in combination with a fabric or something similar. We will expand.
How are customer service and support?
Our customer service and technical support are great. Once in a while, I get a technician who does not have all the expertise we expect, but once we explain what we are looking for, we get reassigned.
On a scale from one to ten, I would rate customer service an eight.
Which solution did I use previously and why did I switch?
We use another solution to address similar needs. For example, for self-service password requests, we use a homegrown application, so we have to use other tools.
Scalability is the factor that leads us to consider change.
How was the initial setup?
Deploying Microsoft Entra ID is easy.
What was our ROI?
I see a return on investment with Microsoft Entra ID, personally.
One example is that I am a one-person team for identity management, and my work is greatly simplified. It is still a lot of work, but I can do a lot because of the features that Microsoft Entra ID has.
What's my experience with pricing, setup cost, and licensing?
My experience with the pricing, setup cost, and licensing is that it is confusing. It is usually very confusing, and right now we are a little concerned because Microsoft is changing the student benefit, which is not going to be free anymore. Everybody is concerned.
Which other solutions did I evaluate?
Before selecting Microsoft Entra ID, I think they considered Okta.
What stands out in the evaluation process is that it is changing, but Microsoft already gives universities free licenses for every faculty or staff license that they buy, so you get a student benefit with it. Because we already have those licenses, it was an easier decision to go with Microsoft Entra ID.
What other advice do I have?
Microsoft Entra ID's integration capabilities influence our zero trust model in that we already have a lot of identities, and having Microsoft Entra ID has added even more identities that we have to manage. We have to work a little harder to manage all of them.
Device-bound passkeys in Microsoft Authenticator have affected our approach to phishing resistance. Since we are a university, there is some resistance to using tokens, mainly because the claim is that many of the students would not have access to getting one. I guess it comes down to cost.
Overall, I would rate Microsoft Entra ID a seven.
My advice to another organization considering Microsoft Entra ID is to go for it.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Nov 20, 2026
Flag as inappropriateDirector Ai Engg. at Cotiviti
Centralized identity has strengthened zero trust and simplified conditional access management
Pros and Cons
- "Microsoft Entra ID as a whole is amazing, and the feature I like most is the app registration and the Microsoft Graph API concept."
- "Some of the features on the MFA policies and the IP restrictions need improvement."
What is our primary use case?
During the migration, we adopted Microsoft Entra ID. From day one, we have used it for all of our MFA, Intune, and Conditional Access policies. Everything is managed by Microsoft Entra ID. We have an Azure subscription, which is also integrated with Microsoft Entra ID, and we actively use it to manage role-based access for our Azure environment through Microsoft Entra ID groups and permissions.
How has it helped my organization?
Microsoft Entra ID makes user management easy, and that is one of the big benefits I see. I don't need to jump between different platforms. For example, if you have an on-prem AD with groups, you can sync those groups to Microsoft Entra ID and manage them. If you start creating Microsoft Entra ID groups, you get a variety of group types: security groups and Microsoft 365 groups for Teams and SharePoint channels. You can also create distribution lists and dynamic distribution lists. In addition, the role-based access group is managed through our Azure platform. The good thing is that Microsoft Entra ID sits in the center. It manages our entire Microsoft 365 ecosystem and all the security tools. It manages our Copilot and our Foundry. It also manages our entire Power Platform, including Fabric and Power BI. That is one of the best things and the benefit I get from Microsoft Entra ID on a daily basis. From an administration standpoint, I think it is one of the best tools.
The biggest impact that Microsoft Entra ID has had on our secure access to apps and resources is the Conditional Access policy with Multi-Factor Authentication, which is also managed by Microsoft Entra ID. We have a very custom setup that I don't think any other organization generally uses. We have device restriction and IP restriction policies, which are also managed by Microsoft Entra ID. We created the Conditional Access policy in such a way that if anybody is going to get into a specific application, it doesn't matter whether it's Office 365 or a third-party application hosted in Azure. We always have all those applications authenticated through Microsoft Entra ID and have Conditional Access policies applied. If anybody is trying to do something from their personal device, everyone will get it. Recently, we have started adding our AI-registered agent registration as well, which is amazing. I can control the restrictions and policies, including what access the agents have and what access they don't. All these features are amazing.
Microsoft Entra ID integration capabilities have 100% influenced our Zero Trust model. Microsoft Entra ID has full integration with Purview and our Defender ecosystem, and they play the key role in our Zero Trust implementation. If anything goes wrong, Defender provides us the information and we can correct it. Automatically, 100%, it plays a role. It manages all the security. All the policies we created in Purview and Defender for Zero Trust are managed by Microsoft Entra ID rules.
Since implementing Microsoft Entra ID, we definitely see an improvement and we feel more confident, but we have never encountered any security challenges or issues specific to identity theft. That may be our luck. After moving to Microsoft Entra ID, we feel more secure because it provides us an additional layer of security with Multi-Factor Authentication, Conditional Access policies, and all the delegated permissions using Microsoft Graph API and registration. We definitely feel more confident, but we have never encountered a specific scenario where I could say, "Okay, this makes the difference," or "This incident is not going to happen because we are in Microsoft Entra ID now." We have never encountered that.
Our company's approach to defending against token theft and nation-state attacks has definitely changed since implementing Microsoft Entra ID, and we are exploring some of the options with Microsoft to advance our Microsoft Entra ID integration. Our goal is to get Intune in place. Right now, we have Intune just for personal device management. With Microsoft Entra ID integrations through MDM and Intune, if we start working on corporate device management, that is going to be a game changer, and we are planning to do that with Microsoft.
Token replay detection, attacker-in-the-middle detection, and verified threat actor IP all have an impact on our environment. All of them do.
The implementation of device-bound passkeys and Microsoft Authenticator has 100% affected our company's approach to phishing-resistant authentication.
What is most valuable?
Microsoft Entra ID as a whole is amazing, and the feature I like most is the app registration and the Microsoft Graph API concept. Many people reach out to us saying, "I want to do this integration, that integration. I need this application to be integrated." When we do those configurations and integrations using Microsoft Graph delegated permission, it restricts and controls what an app can do. The security level of control we get from Microsoft Graph API is amazing.
Second, Conditional Access policy is my personal favorite for MFA for a lot of internal applications. You can handle things elsewhere, but when it comes to security controls, I always trust Conditional Access policies, whether they involve device policies, IP restrictions, or something else.
What needs improvement?
Microsoft Entra ID can be improved in a few ways, and I definitely want to provide some recommendations. The UI for app registration and Enterprise Applications is separate. Those should be combined so that people can understand them more easily. I think Microsoft made some enhancements, such as being able to do the app registration within the Enterprise Application, but it is still very confusing when a new administrator joins my team. I always need to explain the difference between the two, so it definitely needs some work.
Some of the features on the MFA policies and the IP restrictions need improvement. In Microsoft Defender for Cloud Apps (Cloud App Security), which is a feature of Defender at security.microsoft.com, there is a connection where, if I select Zscaler, it automatically whitelists the Zscaler IP. In Microsoft Entra ID, that feature is missing. I'm surprised that one Microsoft product provides this while another product does not give me a list of companies whose IPs I can whitelist. I need to go and manually whitelist those IPs, and I don't like that at all. I think that fix is 100% needed. If it exists in Defender for Cloud Apps, how hard is it to bring it into Azure?
The only other feedback I will give is on Microsoft Entra Connect. When I do hybrid configurations from AD to Microsoft Entra ID, the biggest problem I see is that I always need to wait for the syncs, and the sync intervals do not give clear visibility of what is happening and what is not. There should be a mechanism where the administrator gets visibility of what is going on, because sometimes we have priority actions to take, and we need a way to make those syncs happen immediately so the replication happens faster. Our organization is very big, and one sync cycle takes more than one hour. We cannot wait one hour to resolve an issue when something needs to be synced from AD to the cloud.
For how long have I used the solution?
We have been using Microsoft Entra ID since 2019, when we started the merging of two different companies. We are on Office 365 for our entire organization, and both companies are on Microsoft 365.
What do I think about the stability of the solution?
In my assessment of the stability and reliability of Microsoft Entra ID, I have never seen any specific outage. There are different products integrated with Microsoft Entra ID that have had outages.
How are customer service and support?
If I evaluate Microsoft support, I would rate them four out of five.
On a scale of one to ten, I would rate Microsoft support an eight. I am taking two points off because a couple of incidents happened with us in the past where we received very poor support. It has improved. If I contact my client engagement person, he helps me a lot, and he is amazing. However, if I don't contact anybody in Microsoft directly and instead open a general ticket, I don't like the support. I always like the support when I reach out to somebody else, such as my account rep, and then get support in a different way. There should not be a difference between an engineer directly raising a ticket and me, as a manager, reaching out to people in Microsoft. There should not be a difference, and I don't like that.
Which solution did I use previously and why did I switch?
Before Microsoft Entra ID, we relied on Active Directory and ADFS for application authentication management. We also had the RSA MFA token. We have eliminated RSA and ADFS after moving everything to Microsoft Entra ID.
How was the initial setup?
My experience deploying Microsoft Entra ID is good. It is not the first time I have done an Office 365 and Microsoft Entra ID implementation. In my career, I have done it at least four to five times. Every time, I get a different experience because Microsoft makes it more automated, with a more single-click implementation instead of doing manual work. I like that. Every year, it is improving.
What about the implementation team?
I was involved in the deployment of Microsoft Entra ID, and I personally deployed it in 2019.
What was our ROI?
In terms of return on investment, I will not say Microsoft Entra ID reduced the cost, because ADFS and Active Directory are an on-premise Microsoft ecosystem. We just eliminated the administration of the servers. We eliminated a lot of servers that required patching and a lot of manual work. That was eliminated because everything is now managed through Microsoft Entra ID.
Our user base is very high. We have close to 25,000 accounts within Microsoft Entra ID. From that point of view, a lot of administration would be required if we had it on AD and ADFS with application management. We have at least 600+ applications that were earlier integrated with ADFS, and we have moved them to Microsoft Entra ID.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup costs, and licensing for Microsoft Entra ID has been positive. I never felt anything bad about the pricing because we are always on Microsoft 365 E3 for other reasons, and that includes the Microsoft Entra Premium P1 license. I never have the conversation, "Why do we need Microsoft Entra ID?" It is always there, and we are just using it.
Which other solutions did I evaluate?
We have considered other solutions, including Okta. In federation, we reviewed a couple of solutions, but the only reason we went with Microsoft Entra ID is that we are already on Microsoft 365 and have the Entra Premium P1 license for the entire company. It makes more sense within the environment. Why have an additional authentication layer instead of keeping the same one?
What other advice do I have?
On a scale of one to ten, I would rate Microsoft Entra ID 100%, a ten, because it solves your identity problem. It solves your administration challenges. You have the most automation you can get. You know you are 100% secure if you are dealing within Microsoft Entra ID. There are other tools, such as Okta or other identity platforms, that you can use to be secure, but Microsoft Entra ID is part of your Microsoft ecosystem. If any organization is on Microsoft 365, it should not think about any product other than Microsoft Entra ID. It should only choose Microsoft Entra ID as its product. That is what I feel, and that is why I feel it is one of the best.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Nov 20, 2026
Flag as inappropriateTechnology Devops Senior Engineer at Navanta
Identity platform has strengthened conditional access and secured single sign-on across apps
Pros and Cons
- "Conditional Access policies act as the firewall of an identity."
- "Sometimes it has performance issues. Sometimes it is super slow trying to grab user sign-ins."
What is our primary use case?
My main use cases for Microsoft Entra ID are as an identity platform, including single sign-on, user identity, device identity, conditional access, and role-based access controls.
How has it helped my organization?
These benefit my organization in multiple ways, but the number one benefit is security. Conditional Access policies act as the firewall of an identity. That has to be the top benefit.
Implementing Microsoft Entra ID has had a ton of impact on secure access to apps and resources in our environment. It pulls in Conditional Access and the SSO capability, along with those integrations. When we do SSO through Microsoft Entra ID, we can pull applications right into scope with our Conditional Access policies. As we protect our users at large, we also protect the apps that they access through Single Sign-On.
Since implementing Microsoft Entra ID, I have not really observed changes in the frequency and nature of identity-related security incidents in our organization, but maybe that proves the effectiveness of the security controls.
I agree that no news is good news. I do not have any wood to knock on, but if I did, I would knock on it.
Our organization’s approach to defending against token theft and nation-state attacks has changed since implementing Microsoft Entra ID. It folds right in. I know that Microsoft Entra ID is already trying to protect us with Continuous Access Evaluation. The Conditional Access policies are getting even more granular in targeting token theft, so it does play a part in that.
The implementation of device-bound passkeys in Microsoft Authenticator affects our organization’s approach to phishing-resistant authentication. We are always on the rise, always on the lookout for the latest and greatest technology for multi-factor authentication, so it does play a big part in our approach.
What is most valuable?
I value the integrations that Microsoft Entra ID allows the most. Those are super important, and it is a very extensible platform because of that. Setting up Single Sign-On, for example, is a really easy use case, and Microsoft Entra ID is really great about it. Connectivity points are another strength, because you can set up applications and have lots of connectivity points. That is really great. The Conditional Access policies are a foundation for security for an identity, and I think that they do a really good job with that.
With great power comes great responsibility. The integration capabilities of Microsoft Entra ID give me the ability to build integrations at a large scale. Those integrations can also be used maliciously. If you have applications that are asking to manage your entire tenant, that could be beneficial, or it could be something an attacker could leverage. It is both sides of the coin.
What needs improvement?
There are features I would want to see in the future, but when put on the spot, I cannot think of them. I know that in the past, I have thought, "I wish that was a little bit better." One way would be when I am looking at integrations for enterprise applications and registered applications. I want to be able to see all the permissions in a single pane instead of having to fish around with PowerShell or something similar. It would be nice if it were built right in where I could see it.
For how long have I used the solution?
I have been using Microsoft Entra ID for about the same amount of time. It used to be known as Azure AD.
What do I think about the stability of the solution?
I assess the stability and reliability of Microsoft Entra ID as pretty reliable. Microsoft had a huge outage last week, but Microsoft Entra ID did not go down. A couple of other Microsoft services went down. Microsoft Entra ID is still going strong.
I have not experienced any downtime or crashes with Microsoft Entra ID. Sometimes it has performance issues. Sometimes it is super slow trying to grab user sign-ins. Our organization is not super large, so I cannot even imagine what it would be at 50,000 users or something similar. It must be incredibly slow.
What do I think about the scalability of the solution?
Microsoft Entra ID scales pretty well with the growing needs of our organization. You are allowed 50,000 users under a single tenant, so it definitely gives us plenty of room to grow.
We have expanded usage only through a user increase.
The process has been smooth. You add users, with no problem at all. You license them, with no problem at all. As we have grown, we have also expanded our use of Microsoft Entra ID technologies and more features along the way.
How are customer service and support?
When it comes to customer service and technical support, we typically do not work with Microsoft directly since we buy from a CSP. We go through our CSP into Microsoft. We usually end up in the right place when we do that, after we get past Microsoft’s tier-one support. It just takes a little bit to get past that. Once we actually get to talking with the Microsoft experts, the tickets usually get resolved pretty quickly.
Which solution did I use previously and why did I switch?
Microsoft Entra ID has been the identity platform for a long time. Even before it was Microsoft Entra ID, it was Azure AD. It has been around for so long.
How was the initial setup?
Our experience with deploying Microsoft Entra ID is that it performed pretty well according to Microsoft documentation. If you follow the documentation, you get the architecture that you are looking for and you are able to implement it.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that Microsoft Entra ID is pretty good in that it only has two license levels, so it is not super crazy when it comes to licensing complexity. That is always nice. However, Microsoft Entra ID licensing does have some unforeseen complexity when it comes to what a user is, because you might have a shared mailbox or something similar. A shared mailbox is not a person, and you would not think of it as a person, but it is still a user and it can still sign in. The licensing gets really complex. I have to ask how many shared mailboxes I have, and whether each one of them needs to be licensed as a regular user. It does not really make sense.
Which other solutions did I evaluate?
I did not consider any other solutions before selecting Microsoft Entra ID, just because it was a natural point for M365 connectivity, which was Office 365 back then, more or less. It has been one and the same. If you are in that space already, it just makes sense to go with that one. We do work with other identity providers such as Duo, for example. We have integrations with them, and Microsoft Entra ID has the capability to integrate with those providers. It helps.
What other advice do I have?
Overall, for performance or just any of it, I rate Microsoft Entra ID a 10 as far as identity platforms go.
My advice for other organizations considering Microsoft Entra ID is to make sure you understand your Conditional Access policies. Those are super important, and they have a level of complexity to them that you want to make sure you get right. That is the most important point above all.
Disclosure: My company has a business relationship with this vendor other than being a customer. Reseller
Last updated: Nov 20, 2026
Flag as inappropriateDigital Workplace Engineer at Shawmut Design and Construction
Identity automation has supported secure pipelines but unified governance still needs improvement
Pros and Cons
- "Microsoft Entra ID benefits my organization because it works, and because of the ease of setting up identities and connecting the dots."
- "In my opinion, Microsoft Entra ID could be improved with increased observability and governance across Microsoft Defender, Microsoft Purview, and Microsoft Entra."
What is our primary use case?
My main use case for Microsoft Entra ID is helping build identities for CI/CD pipelines. I am a software developer, so I build a lot of automation in the background.
What is most valuable?
The feature of Microsoft Entra ID I appreciate the most is that it works.
Microsoft Entra ID benefits my organization because it works, and because of the ease of setting up identities and connecting the dots.
The implementation of Microsoft Entra ID affects our secure access to apps and resources by enabling least‐privilege permissioning, so that we do not give admin credentials to automated tools and agents.
Microsoft Entra ID's integration capabilities influence our zero trust model in the same way as described in the previous answer.
What needs improvement?
In my opinion, Microsoft Entra ID could be improved with increased observability and governance across Microsoft Defender, Microsoft Purview, and Microsoft Entra. A single pane of glass connecting the dots between everything would help. This might be my lack of knowledge, and it might not be an Entra issue.
For how long have I used the solution?
I have been using Microsoft Entra ID for probably the past two to three years.
What do I think about the stability of the solution?
I would assess the stability and reliability of Microsoft Entra ID as solid. I have experienced no downtime, even during last week's fun.
Microsoft Entra ID was still up during that time. Outlook had fun, but Entra was fine. That is crazy.
What do I think about the scalability of the solution?
Microsoft Entra ID scales with a growing team, and I have not seen any growing pains yet. We are not as large as we would be if, for example, Anthropic dumped it on 100,000 people. It works well for my company.
How are customer service and support?
On a scale of one through 10, I would rate customer service and technical support at probably seven to eight. They are quick to respond, and the types of questions I ask do not require quick follow‐ups and deep dives.
What other advice do I have?
The implementation of device-bound passkeys and Microsoft Authenticator affects our organization's approach to phishing-resistant authentication in that we have always used them since I joined the company.
On a scale of one through 10, I would rate Microsoft Entra ID overall at seven to eight. It does everything I need it to do, but the overall view could be improved a little. That might just be my lack of knowledge.
My recommendation to others is that Microsoft Entra ID works, so go for it.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Nov 20, 2026
Flag as inappropriateBuyer's Guide
Download our free Microsoft Entra ID Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2026
Product Categories
Single Sign-On (SSO) Authentication Systems Identity Management (IM) Identity and Access Management as a Service (IDaaS) (IAMaaS) Access Management Microsoft Security SuitePopular Comparisons
Microsoft Intune
Microsoft Defender for Endpoint
Cloudflare One
Microsoft Defender for Cloud
Okta Platform
SailPoint Identity Security Cloud
Microsoft Sentinel
Microsoft Defender for Office 365
Microsoft Purview Data Governance
Workspace ONE UEM
Microsoft Defender XDR
Ping Identity Platform
Cisco Duo
Azure Key Vault
Google Cloud Identity
Buyer's Guide
Download our free Microsoft Entra ID Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What do you think of the integration of Azure AD Services, Defender for Endpoint, and Intune as comprehensive security solutions?
- What are the biggest differences between Google Cloud Identity and Microsoft Azure Active Directory?
- How does Duo Security compare with Microsoft Authenticator?
- How does Microsoft Authenticator compare with Forinet FortiToken?
- When evaluating Single Sign-On, what aspect do you think is the most important to look for?
- CA SiteMinder vs IBM Tivoli Access Manager
- What single sign-on platform do you recommend?
- How much time does SSO save?
- Why is SSO needed?
- Why is Single Sign-On (SSO) important for companies?











