Microsoft Entra ID Reviews

My main use cases involve daily usage as a system technician, running InTune and Microsoft Entra ID, mainly for endpoint and user management. The main metric demonstrating the impact of the integrations is that we use Microsoft Entra ID for all of our devices. When assigning or removing users, if a user is terminated, or a device is lost or stolen, we use it to remove and manage all endpoints. User migration occurs when we have new hires or terminations, and most of that is what I actively use it for.

The user-friendliness of Microsoft Entra ID is what I appreciate the most. Everything is organized, simple, and straightforward. Even new technicians can come into it and know what they're looking for. The simplicity is a major factor.

Microsoft Entra ID has not had much direct impact on my secure access to apps or resources in my environment since we have been using it from day one, so it has not really changed much, but everything I need is accessible from there.

These features of Microsoft Entra ID have worked and benefited my organization. For my day-to-day role, endpoint management, user management, and policy management within our enrollments for our devices are directly involved between Entra and InTune. It is the main housing unit for everything that I do in my role.

Currently, I don't have any main suggestions for how Microsoft Entra ID can be improved; it has worked for what we needed it to. Since it is already quite simple, I would recommend keeping it as is.

In my current field, I have been working for about five years, and I have been using Microsoft Entra ID for at least four of those five years.

I assess the stability and reliability of Microsoft Entra ID overall as good. If anything does come up, Microsoft is great about notifying us; we get alerts if anything goes down, and we find out before it happens for the most part. We haven't had many issues; most of it is quite stable.

I definitely cannot say we have experienced no downtime, crashes, or performance issues. Recently, we had one issue that lasted for a few hours during the day. We went straight to Microsoft health and notified the issue, and then Microsoft came with a workaround for it quite quickly. Generally, if there are issues, there is a quick turnaround on either a repair or an alternative solution.

Microsoft Entra ID scales well with my organization's growing needs; we use it daily and don't plan on changing it.

I would say we have expanded usage of Microsoft Entra ID. My experience with the expansion has been smooth on my end. I'm not the engineer directing it, but everything has been smooth in my role.

I would rate customer service and technical support as a seven to eight on a scale from one to ten. I give it a seven to eight because most of my interaction is with the end user and managing their system, ensuring everything is up and running for them to do what they need to on their jobs daily. I would evaluate my experience with customer service and technical support as great; I have never had any complaints.

Positive

To my knowledge, Microsoft Entra ID is the only solution we have worked with; I'm not sure of any other alternatives we looked at. That is the only solution I have used to address similar needs prior to adopting Microsoft Entra ID.

My experience with deploying Microsoft Entra ID has been straightforward; everything works well.

Most of my experience with developing Microsoft Entra ID pertains to setting up new policies when we get new features and upgrades, and we are always looking at ways to improve. I do have an engineer who mainly handles that, but as a technician, I go in and maintain and manage it. I haven't seen any specific challenges on my end regarding the deployment.

My experience with the deployment of Microsoft Entra ID has been quite straightforward. Anytime we get new devices in, the new policies are managed through InTune right to the devices, and it all rolls right out. I haven't had any issues.

From what I understand, there has been a return on investment. They have at least spoken to it. I don't have specifics, but I know it's a positive notion.

Unfortunately, I don't have information on the pricing, setup cost, and licensing on my end.

Since implementing Microsoft Entra ID, the most change I have observed in the frequency of identity-related security incidents in my organization has been as policies get updated. A few more features show up in there that we can edit to strengthen the policies as a whole from a security outlook. Most of it is that as they change, we can go in and look again to see if there is any way we can strengthen our current policies. I couldn't think of any specific metrics or data points at the moment regarding the changes I have observed.

My organization's approach to defending against token theft or nation-state attacks hasn't changed much after implementing Microsoft Entra ID. The following features of Microsoft Entra ID—token replay detection, attacker-in-the-middle detection, Verified Threat Actor ID, and Microsoft Entra ID Protection—haven't had a lot of specific impact that I'm aware of for the most part. We could say that there are no specific data points or examples at the moment.

The implementation of device-bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing-resistant authentication by ensuring that we use MFA and the passwordless device token specifically. All access is limited, and we have them set up for specific policies based on certain groups for different access, and it's all managed through there for us.

I would advise another organization considering utilizing Microsoft Entra ID to give it a shot if they're not already. It has been great and smooth; we haven't had many issues, and if we do, they are fixed quite quickly. With the support of Microsoft on our side, it's worth trying out. I would rate this product an overall eight out of ten.

We are hybrid, so we mainly use Microsoft Entra ID for control of users that we've synced out to the cloud.

The features of Microsoft Entra ID that I like the most include the dynamic grouping, which is pretty cool.

The integration capabilities of Microsoft Entra ID have influenced my zero-trust model positively since we can actually tie in single sign-on, which has been nice.

I can't think of any metrics or data points off the top of my head to demonstrate the impact of Microsoft Entra ID integrations, but it's helped simplify logins for the end users, which is good.

Our organization's approach to defending against token theft and phishing attacks has actually changed since implementing Microsoft Entra ID, as we are working on going passwordless using YubiKeys.

The passwordless feature of Microsoft Entra ID has been nice; it's super slick since users don't have to know their password anymore. We are still working on putting it in, but it has helped reduce help desk calls where users would ask about not knowing their password, which has been pretty nice.

The centralized management with the single sign-on feature of Microsoft Entra ID has been huge, and that aspect has been nice as a data point demonstrating the ROI.

The features of Microsoft Entra ID such as token replay detection, attack-in-the-middle detection, or verified threat actor ID protection haven't had a specific impact on defending against threats for us; however, we have worked with companies that have gotten hacked, and if they were on passwordless, that would have stopped that.

I can't think of any improvements for Microsoft Entra ID off the top of my head, but I would like to see more features brought from on-prem Exchange into the cloud, which would be huge, and also with Office, there are features that we just don't have anymore, raising the question of whether we will get these.

I've been using Microsoft Entra ID for about seven or eight years.

I would assess the stability and reliability of Microsoft Entra ID as fair; I've experienced downtime and crashes, especially when trying to use PowerShell, and there have been times where it has crashed as a whole due to something on their end, which sometimes gives us issues.

Microsoft Entra ID scales with my growing needs pretty well.

I have expanded usage of Microsoft Entra ID, and the process has been pretty smooth; we've expanded into using some of the cloud features when it comes to VMs and other resources. Though it's more in the testing phase compared to being in production, so far it's been pretty easy.

On a scale from one being the worst and ten being the best, I would rate my customer service and technical support from Microsoft a three.

I would give that rating of three because the last ticket that I had open with them was open for about seven months, and I messaged them multiple times; it got stuck in a queue waiting for somebody to pick it up. I couldn't open a different ticket because that one was already in, and then after about seven months, they sent me something that said they were sorry and that my ticket got put into the wrong queue, so they went ahead and closed it and asked me to submit a new ticket.

Neutral

Prior to adopting Microsoft Entra ID, I was using another solution to address similar needs that included just on-prem AD and then ADFS for single sign-on.

I would describe my experience with deploying Microsoft Entra ID as pretty seamless for the most part; however, when it goes down, it is a bit of a pain, and we have noticed challenges with the documentation since they're constantly changing information, leading to dead links that don't go anywhere, making it hard to do something when the knowledge base isn't up to spec.

My overall experience with the deployment of Microsoft Entra ID has been pretty good.

An example of my deployment experience includes migrating all mailboxes from on-prem out to the cloud, which was pretty seamless, and the users and setting up the connect piece was honestly pretty easy for the most part.

I've seen a return on investment with Microsoft Entra ID.

Prior to selecting Microsoft Entra ID, I honestly considered staying on-prem; there wasn't really anything else, maybe Google.

What stood out in the evaluation process for Microsoft Entra ID, both positively and negatively, was that we already had on-prem, so it was a no-brainer to just keep going that way with them.

The implementation of device bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing resistant authentication positively, as it's going pretty well, but it has helped us find applications that don't support it, which means we have to either work with the vendor or find a solution for that.

Since implementing Microsoft Entra ID, I haven't observed any changes in the frequency of identity-related security incidents in the organization; one thing that confuses everybody is where they keep changing the name. If they would just stick to one thing, that would be nice, but it is what it is.

My advice to another organization considering Microsoft Entra ID is to make sure that you build it out properly, leverage dynamic grouping as much as you can, and use proper naming schemes so you know what your groups do. I would rate this product a six out of ten overall.

Hybrid Cloud

Microsoft Azure

I have demo tenants where I test lots of features, such as creating test accounts and managing permissions.

Many organizations are shifting to a zero-trust model where nothing is trusted by default, and we explicitly add permissions as needed. Entra has some of those metrics, like risky sign-on. You can set up conditional access policies to ensure users can't access it from unknown locations. 

I can look at the logs to see how often my users are flagged as risky and fine-tune my policies to balance usability and security. The biggest implementation barrier with many test accounts is ensuring passwords aren't shared. Using MFA has also helped us ensure the test account is mapped to a single person. 

A lot of these features from Entra ID were implemented in our tenants. The biggest issue we've seen is that these passwords are leaked because someone shared them in a group when they were not supposed to. I think a lot of the policies that Entra has introduced lately around condition access for access management have helped us mitigate that.

I like how Entra allows you to upload a CSV file with user details for bulk user creation. This is useful for automation. Entra has made it easy to manage identity and access by integrating with all Microsoft services. Everything is managed in a single place, eliminating the need for another application.

It was super easy to understand how the basic functions work. The documentation on learn.Microsoft.com was sufficient to get most tasks done. 

The device-bound IDs in Microsoft Authenticator help us fight phishing, which is traditionally made possible by individual passwords. With passkeys, we eliminated the need for passwords to be stored and remembered. These test accounts aren't used daily, so people write the passwords down, and it's insecure. These phishing-resistant ensure we mitigate those risks. 

We've become more aware of token theft and state attacks. For example, if the demo tenant can access our internal resources and code still in development, we ensure that all these user IDs are authenticated. Entra can delegate and control access to apps, helping to close those attack vectors. 

Entra could be improved by enhancing self-service options for end users, such as making password reset options more accessible. This would simplify the user experience for end users.

I have used Entra ID for about a year.

For both the stability and scalability, it's pretty good. I've never had any issues with users trying to log in.

Both the stability and scalability of Microsoft Entra ID are pretty good with no reported login issues.

We have not needed to contact customer service due to sufficient public documentation. This suggests good technical support.

Positive

We used Keycloak for access management and single sign-on and some of the AWS native IAM solutions. Keycloak is open-source, so it's vendor-agnostic and can be integrated with any custom app you build, whereas you run into vendor lock-in with Entra. However, Entra is natively integrated with all Microsoft products, and we've migrated to using an exclusively Microsoft ecosystem. 

The documentation on Microsoft's website was sufficient to understand the setup for basic functions, making the initial setup straightforward.

We did everything in-house without involving any integrator, reseller, or consultant.

Entra is bundled with every new tenant you set up on Azure, so we don't need to pay for extra solutions to manage the fundamental aspects of user management and accounts.

I rate Microsoft Entra ID nine out of 10. It fits my purpose perfectly, and I seldom need to search for alternatives due to its comprehensive functionality.

Hybrid Cloud

Other

We primarily use Microsoft Entra ID in hybrid scenarios where we are undergoing digital transformation. We had on-premises Active Directory that we transitioned to Entra on the cloud, enabling users to authenticate with their regular credentials.

We have a complex scenario with several applications, and we're trying to achieve SSO for most of our applications, but some of our legacy applications don't support SSO or modern protocols. Our core applications are ready for SSO or to be federated. We've centralized our authentication process using Entra ID, so we can collect sign-offs from the users and filter using conditional access. 

Our identity solutions are mature because we started with FIDO and YubiKeys. It's easier to implement now that we aren't sticking to a device. We aren't increasing our costs to add another asset to the user that we can use on their mobile phone. Technologically, FIDO is excellent, but Microsoft Authenticator is even better. 

Entra ID is integrated with Sentinel. It's ingesting logs from Entra ID, and we have playbooks to mitigate any identity-based risks. We could figure out our authentication flows and detect any misbehavior through integration with Sentinel. Entra ID enriches this process with logs, sign-outs, and remediation information.

We have an internal strategy for leveraging all Microsoft solutions. We avoid bringing in third-party applications to solve some gaps and try to address everything exclusively within Microsoft. Microsoft is the only vendor that can deliver the full lifecycle in one solution.

We are always working with cutting-edge solutions. For instance, we were struggling with Zoho support for SSO, and now we no longer use this domain. We are selling commercial vehicles, so it matters how reliable and trustworthy we are. No one wants to buy something from a company that doesn't protect customer data. We need something that makes an attacker's life harder. 

With Entra, we can provide a safe environment where we don't need to rely on users to secure their environment. We have plenty of security pillars to protect the company internally and externally. Using a zero-trust strategy, we reduced the differences between users, enabling safe navigation and asset use.

In my opinion, Microsoft sometimes releases products too early without providing enough documentation. Our team works with innovative solutions like verified ID, identity governance ,and lifecycle workflow.

When we started with lifecycle workflows, we had only two integrated worklows. Still, we couldn't find much of the information we needed in the documentation about our use case or how to leverage IDs in our proof of concept. 

Entra constantly releases new features, and other companies are releasing products at the same pace as Microsoft, so it's trickier. We started implementing a product called Next Identity that provides modern authentication methods like FIDO and push notifications. In 2023, we couldn't see how verified ID would help us. Now, verified ID has been integrated, and we can realize it, but at the time, we couldn't.

I have been using Entra ID for almost three years.

The solution is robust and stable, though we acknowledge the risk of potential backend outages from Microsoft, which could affect us significantly.

The solution is really scalable. We manage more than 100,000 devices and 300,000 user objects in Entra, indicating a high level of scalability in our environment.

We have always worked with Microsoft. Initially, we operated using on-premises Active Directory until we moved to Microsoft 365 and started using Azure AD at that time. Our parent company requires us to use Microsoft, but Entra is a core solution. 

The initial setup involved syncing our identities to the cloud and building a robust tenant as part of the company group. We adhere to a strict blueprint requiring the use of Microsoft solutions.

We have an internal hub in Lisbon focused on innovation and implementing solutions like Verified ID and identity governance.

I rate Microsoft Entra ID nine out of 10. 

Hybrid Cloud

Microsoft Azure

My main use cases for Microsoft Entra ID are identity and using Conditional Access to lock down security measures and ensure people are not engaging in risky activities when signing in from home.

I really love the Conditional Access feature of Microsoft Entra ID because it provides the security controls that we have sorely needed.

The impact of Microsoft Entra ID on my secure access to apps or resources in my environment has been significant. It has been helping us prevent phishing attempts, MFA phishing, password theft through SharePoint links, and similar threats.

Microsoft Entra ID's integration capabilities have had a significant influence on our Zero Trust model because we have been strengthening our security model over the last six months.

I have observed changes in the frequency and nature of identity-related security incidents. We have seen the reduction of risky behavior that is now being mitigated automatically rather than requiring our security team to investigate and determine if the user is legitimate. The system handles it automatically, and then we can investigate at our leisure instead of having to respond immediately.

I believe that Microsoft Entra ID can be improved by adding more granularity in options within Conditional Access specifically, because there are certain scenarios that we cannot address due to insufficient options to set up those rules.

Another area for improvement is IPv6 detection, which needs significant enhancement. I understand the technology is difficult because IPv6 contains billions of IPs, but the location detection for IPv6 is not effective.

I have been using Microsoft Entra ID for five years.

The stability and reliability of Microsoft Entra ID are quite good. There have been only one or two outages in the last two years, and I have not experienced any major issues.

Microsoft Entra ID scales very well to the growing needs of my company and is highly scalable.

Customer service and technical support for Microsoft Entra ID is about average and could definitely use some improvement.

I have not used another identity solution before choosing Microsoft Entra ID. This is the only one we have used, unless you consider Active Directory on its own as another product. Our entire infrastructure is Microsoft.

The experience with deployment of Microsoft Entra ID was straightforward and quite easy.

The biggest return on investment for me when using Microsoft Entra ID comes from its hybrid capability with on-premises Active Directory. Conditional Access, since we rolled it out, has significantly increased our return on investment as this was not something we had available before.

The pricing, setup cost, and licensing of Microsoft Entra ID is reasonable and probably one of the more competitively priced solutions available.

I did not consider other solutions before choosing Microsoft Entra ID.

Microsoft Entra ID has helped us prevent tokenized threats through Conditional Access policies. Since we obtained the P2 license to implement more advanced Conditional Access features, we have been able to prevent those threats much more frequently.

The impact of features from Microsoft Entra ID on defending against threats has been significant. Attacker-in-the-middle attacks have been the most significant help to us.

The reason is because of those phishing attempts. When you click a link, the person types in their username, provides their MFA, and the attacker replays that attack. However, because of Conditional Access, it is mitigated and they get denied access because of the attack.

Since implementing Microsoft Entra ID, my company's approach to defending against token theft and nation-state attacks has changed.

The implementation of device-bound passkeys in Microsoft Authenticator has not yet affected my company's approach to phishing-resistant authentication, but it is on our roadmap.

My advice for other companies that are considering Microsoft Entra ID is to get the higher tier, the P2, because it provides the security features that you really need at that level. I would rate my overall experience with Microsoft Entra ID as an eight out of ten.

Hybrid Cloud

Microsoft Azure

I am currently using Microsoft Entra ID and have been working as a user and administrator for nearly two years. It serves as an ID management tool which used to be called Active Directory on on-prem servers. With the transition to the cloud, it became Microsoft Entra ID.

The features I find most useful in Microsoft Entra ID include sign-in logs, device management, and application registration. With the Entra ID dashboard, I can access logs easily without needing to remote into servers. This tool is excellent for integrating third-party applications through application registration, making it easy to configure for single sign-on seamlessly. It supports conditional access across various Microsoft applications, enhancing secure access.

There should be guidance on features, especially security features, in Entra ID and whether they are sufficient on their own. The solution could become expensive when paying extra for enhanced security features, so Microsoft needs to offer better clarity on this matter.

I have been using Microsoft Entra ID for almost two years.

In terms of stability, I can say it is ninety-nine percent stable. The remaining one percent instability is mainly due to the hybrid setup.

I have no complaints regarding scalability for Microsoft Entra ID.

The customer service and support are excellent. I experienced a fast resolution within half an hour for an issue by the first line engineer on a Severity A case, which shows support is very good even with minimal licenses.

Neutral

I am not aware of the solutions used prior to Microsoft Entra ID, as I have been involved for the last two years only.

Since it is a SaaS model, everything is set up, and I just need to configure it according to my needs.

We did not require any integrator, reseller, or consultant for the deployment as we managed it internally, using Microsoft's extensive documentation for guidance.

Microsoft Entra ID is reportedly quite expensive for each user regarding security features. The renewal cost is particularly high according to the teams managing purchases.

I have only been involved with Microsoft Entra ID and am aware of another identity management solution called NetIQ, but Microsoft Entra ID is prioritized.

Users should prepare technically before using Microsoft Entra ID, especially in understanding ID management and security integration with applications. Microsoft Entra ID is regarded as the best ID management suite for integrating applications using SAML 2.0 for single sign-on. My total rating for Microsoft Entra ID is nine out of 10.

Hybrid Cloud

Other

Our main use cases for Microsoft Entra ID are for governance while we're transitioning off of on-prem Active Directory.

I appreciate Microsoft Entra ID's ease of use for the identity governance aspect of it, and I also appreciate the app registrations and the enterprise applications.

The implementation of Microsoft Entra ID has definitely made it much easier to access apps or resources in my environment, eliminating the need to use VPN to get into things, providing conditional access, managing client secrets and tokens.

Microsoft Entra ID's integration capabilities have definitely made it easier for my zero-trust model; we can set up the secrets, we can set up the conditional access, and we have functionality for lockouts if we have any suspicious activity, such as logging in with a suspicious IP or from an unusual area.

Since implementing Microsoft Entra ID, I've observed real-time analytics, receiving alerts whenever there's suspicious behavior, being able to quickly review the logs, and identify issues with users or applications authenticating; it's been excellent.

The features of Microsoft Entra ID such as token replay detection, attack-in-the-middle detection, and verified threat actor IP protection have all had an impact on defending against these threats, with the last one being particularly significant.

With Microsoft Entra ID, the alerts and being able to have trusted domains and trusted areas, making sure we have ranges of IPs that have been identified as bad actors, have benefited my organization by making the entire process much more simplistic.

I don't know how Microsoft Entra ID can be improved; I think it works really well right now. I appreciate the breadcrumbs when I move through the different blades, and most of the functionality is fairly easy to figure out. My recommendation is to continue doing things that work, pay attention to customer feedback, and provide good ways for us to give feedback through user voice.

I have been using Microsoft Entra ID for the last six or seven years.

The only downtime I remember is the major one when AWS went down a month ago.

We have expanded usage of Microsoft Entra ID by approximately 15% since implementation, and that process has gone really well.

On a scale from one to ten, I would rate customer service and technical support a decent score, with no concerns.

Positive

Prior to adopting Microsoft Entra ID, we were using another solution to address similar needs; we had physical authentication keys, VPN access, and a secure client set up, so it was a combination of multiple different things.

The implementation of device-bound passkey in Microsoft Authenticator had significant resistance when we rolled it out, but now that people are used to it, it's made things much easier for our approach to phishing-resistant authentication.

I would describe my experience with deploying Microsoft Entra ID as intermediate.

I wouldn't say I'm a pro with Microsoft Entra ID; I don't think I could just run with it and conduct a full implementation on my own, but I don't think it would be a struggle to assist other people if I had a team to help me out.

What worked well with Microsoft Entra ID deployment was the training we provided, although change is hard for people and new technology; we have to get a grasp on it before we can expect anyone else in our organization to understand what's going on and why we're doing it.

My experience with the deployment of Microsoft Entra ID went well; I don't recall any major issues, and we stayed within our timeframe of when we wanted the project concluded.

I'm not certain about the return on investment with Microsoft Entra ID.

I'm not a procurement person, so I don't have to deal with any of that regarding pricing, setup costs, and licensing.

I honestly don't know what other solutions we considered before selecting Microsoft Entra ID.

I wasn't really a part of the evaluation process for Microsoft Entra ID; I gave my insights on having used it at previous companies, and they had already had it on the shortlist of things they wanted to move forward with, so I think it was an easy choice.

I think our organization's approach to defending against token theft and nation-state attacks has changed since implementing Microsoft Entra ID; we're much more diligent about expirations, who has access to it, conducting certificate renewals for shorter periods of time, and making sure that it has only the access it needs, so it's definitely caused us to be more holistic in our approach to it.

The factors that led me to consider a change included needing to modernize, keeping up with new technology, continuing trends in security, and making it easier to administrate.

My advice to other organizations considering Microsoft Entra ID is to carefully evaluate its capabilities and how it aligns with your needs. I gave this review a rating of ten.

Hybrid Cloud

Microsoft Azure

Our main use cases for Microsoft Entra ID include single sign-on into every application, even third-party.

The feature I like most about Microsoft Entra ID is the single source of truth for the data.

Microsoft Entra ID integration capabilities have influenced our zero-trust model heavily. We are also passwordless and we use PIM as well.

Since implementing Microsoft Entra ID, I don't think we have any identity-related security incidents because you have to have a fingerprint to even log in.

The implementation of Microsoft Entra ID has hardened our approach to defending against token theft and nation-state attacks. You have to be on a hybrid-joined device to access the system, so basically if you're not on a company device, it doesn't matter where you are in the world; you can't even get on anyhow.

Microsoft Entra ID protection has had the most impact on defending against threats such as token replay detection, attack on the middle detection, and verified threat actor IP. The features have had an impact on defending against all of the ones that I listed.

The verified threat actor IP and Microsoft Entra ID protection features have benefited our organization by helping secure our edge and preventing any type of data breaches.

Improvement for Microsoft Entra ID is a hard one; I don't necessarily have one.

I can't think of anything that immediately comes to mind.

I have been using Microsoft Entra ID for 25 years, even though Entra has only been around for a short time. It used to be called Active Directory.

I assess the stability and reliability of Microsoft Entra ID as being up 98% of the time.

I have experienced downtime. We've had instances of downtime.

Microsoft Entra ID scales well with the growing needs of the organization.

I can't expand anymore unless we hire more people; everyone in our company has an ID.

Since we have expanded, the process was easy.

On a scale from one being the worst and 10 being the best, I rate my customer service and technical support as an eight.

I rate it an eight because it depends on the engineer you get. Sometimes you don't get great engineers, but if you get the right engineer, it's good. Sometimes I'll just put in another ticket if I get the wrong engineer.

I evaluate my customer service and technical support as an eight for the same reason. Sometimes they have engineers that don't perform as well.

Positive

I would describe my experience deploying Microsoft Entra ID as definitely a challenge. We use SailPoint to manage it, and we actually have a third-party tool to help with it for the workflow of it.

What worked well with deploying Microsoft Entra ID is that it's already integrated into the Microsoft landscape. It just works with everything that's already Microsoft.

My experience with the deployment was good.

My experience with the deployment involves still using the on-prem integration. We push from on-prem to Entra, so we're not fully offloaded off the on-prem, but that's in case our network goes down and we can still work. The deployment was pretty seamless.

We use SailPoint to manage it, and we actually have a third-party tool to help with it for the workflow of it.

I have seen a return on investment with Microsoft Entra ID.

Before selecting Microsoft Entra ID, I don't think we considered any other solutions. We're a Microsoft shop, and we do everything Microsoft.

Since we don't have the premium licensing, just the regular E3 licensing, and we've been licensing it for where I'm at for over a decade for sure.

My advice to another organization considering Microsoft Entra ID is that it's a hard one to give. I think most people are already on Microsoft Entra ID, at least in the Fortune 500 companies. Literally everybody uses that, so I don't know anybody that would be doing a new deployment.

I rate this review a 9.

Hybrid Cloud

Microsoft Azure