Microsoft Entra ID Reviews

Everything for Office, for VPNs, AVD, or all VDIs are my main use cases for Microsoft Entra ID.

Conditional Access is one of the features of Microsoft Entra ID that I like the most. I think it's the one that we use the most.

The implementation of Microsoft Entra ID has made secure access to apps or resources in my environment more secure.

Microsoft Entra ID's integration capabilities have influenced my Zero Trust model significantly.

Microsoft Entra ID as a whole has created a lot of business for us. Since we're doing this every day, the impact is pretty huge.

I don't have any suggestions for improvement at this time.

My experience with the pricing, setup costs, and licensing of Microsoft Entra ID indicates that we need to make it simple. It's way too complicated. Customers are getting confused about what package and everything. It's confusing for them to actually know what features are actually included. Despite the documentation, it's too complex because there are too many add-ons and too many options. The number of options and packaging is too extensive.

I would assess the stability and reliability of Microsoft Entra ID as not really having experienced any downtime, crashes, or performance issues.

Microsoft Entra ID works perfectly and scales with the growing needs of my organization as it's the perfect source to use with perfect tools.

On a scale from one to ten, with one being the worst and ten being the best, I would rate my customer service and technical support as eight.

I give it an eight because sometimes the first support level is pretty basic and it's hard to get expertise right away on our problems. It's time-consuming for our customers. They have to wait for an answer when there's a problem in the back end. It takes longer to get support, so we actually have to subscribe to another service to get faster response from the support team.

The implementation of the device-bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing resistance since we're using it for all admin and users that have privileged roles inside the organization. We're using passkey throughout our organization and trying to implement it to our customers.

My experience with deploying Microsoft Entra ID has been that it's very simple to use. I think it makes sense how it's built.

The deployment process involves following the flow going from on-premises and then getting the users synchronized, using ID, and getting that going.

The usage of Microsoft Entra ID has expanded and is everywhere.

My advice to another organization that's considering Microsoft Entra ID is to go for it. I would rate this review overall as a nine out of ten.

We use Microsoft Entra ID for authentication purposes and are planning to implement additional modules like Mobile Device Management. Our current use is mainly for integrating third-party applications for distributed applications to centralize authentication.

The major feature we utilize is the ability to perform third-party validations. This functionality allows our distributed applications to be integrated with a single authentication system using Microsoft Entra ID. Previously, each application had standalone authentications, but with Microsoft Entra ID, we have consolidated them. After implementing Microsoft Entra ID, secure access to apps has become seamless.

There are a couple of main concerns. Microsoft plans to move away from SMS authentication for Multi-Factor Authentication and only implement application-based authenticator, which will be challenging for retail outlets reliant on Microsoft Active Directory. Additionally, the pricing for Microsoft services is rising. Furthermore, there is a tool to measure resource usage in Power BI, but it is not functioning properly, making it difficult to understand resource consumption.

We have been using Microsoft Entra ID for three and a half years. Initially, it was Azure Active Directory before transitioning to Microsoft Entra ID, and we've mostly used it over the last three years.

The solution is stable without any latency issues. However, in the last two quarters, we experienced three Power BI outages.

There are no current issues with scalability.

Support could be better at times. There was an incident where I couldn’t get help with deleting an unused subscription and another where Power BI support took weeks without providing a solution. Overall, the support incidents mentioned involved delays and inefficiencies.

Neutral

We have been with Microsoft from the start and have not explored other solutions.

The initial setup for Microsoft Entra ID was straightforward.

The setup was done in-house. I personally handled it without needing a full team.

We did not perform a detailed ROI analysis, but using Microsoft Entra ID has saved about fifteen percent of resources since one person used to manage login details, a task now simplified by the integration.

Microsoft's pricing is increasing significantly. The Office suite has undergone multiple licensing changes, driving up costs, and this also applies to Microsoft Entra ID.

We have been with Microsoft since the beginning and did not evaluate alternative solutions.

One additional feedback is that Microsoft plans to discontinue SMS functionality for Multi-Factor Authentication, which poses a challenge for retailers without mobile application authentication. This requires having an authenticator for Windows, so retail operations dependent on Microsoft Entra will not encounter authentication issues. Furthermore, the overall rating I would give this solution is seven due to issues with support. The MFA upcoming changes must be addressed before they cause further complications.

Hybrid Cloud

Microsoft Azure

We use a hybrid environment with Active Directory and Microsoft Entra ID along with SCCM. Our hybrid setup with Entra and Azure allows us to use role-based groups for access while keeping our AD environment intact. We sign our automation based on Active Directory and use write-back for populating new groups. We are able to use the enhanced security from Microsoft Entra ID while maintaining our existing environment. Our company has been slow to modernize in the cloud environment and we are on the tail end of the actual conversion. We conduct a lot of pen testing with our existing accounts because we still use Active Directory. We haven't had a lot of incidents with identity management. We are just getting into issuing out cloud PCs, having done that in the last year. Some of the more advanced features on Microsoft Entra ID have not been implemented yet.

The write-back caching of Microsoft Entra ID allows us to keep our existing Active Directory environment while also using Azure services. The write-back caching helped tremendously because we didn't have to do a full conversion from one to the other. We could keep our existing environment and still use the zero-trust platform to build it out.

The return on investment from having an Azure tenant comes from being able to use Microsoft Entra ID with our deployment of cloud PCs and having them auto-join the tenant. We are able to build this into our deployments with SCCM and use the hybrid environment to leverage Microsoft Entra ID for deployment. This has made deployments a lot easier, especially with moving to cloud PCs. We still use physical devices, but moving to a virtual environment is a much better solution overall once we get it fully implemented and move everything over to cloud. We are able to release our lease on physical machines and use virtual machines instead.

We have just recently started implementing write-back caching. We were able to go from AD to cloud, but we were not going from cloud back down to AD. When we created new accounts, they were created in AD and then moved up to cloud, but we are not yet creating accounts in cloud and having them populate down to AD. As far as what can be improved, we haven't gotten that deep into it to know what we are missing or what we could improve on.

I have been using Microsoft Entra ID for about six years.

We have very good uptime, and the only time we have suffered any issues is when Microsoft experiences issues.

Information security would be more knowledgeable about pen testing and security configurations for preventing threats, as that is outside my area of expertise. I would not be knowledgeable on those details. I am rating this review an eight out of ten.

Hybrid Cloud

Microsoft Azure

Our use case focuses on ensuring company security through authentication, two-factor verification, groups, and access management. This includes SSO, SFTP, FTP, to manage access for both internal workers and external users who need to access our system.

The best features include the visually intuitive navigation through the platform, which has been evident since the beginning. It is more stable, and the features that Azure delivers make it easier to work in a hybrid environment since we are working with both environments.

Microsoft Entra ID's conditional access policies are very effective and significantly enhance company security. They are very specific, which is particularly beneficial.

The identity protection features have helped mitigate potential threats through our external systems, which are protected through Defender and firewall and private endpoints. We are primarily concerned with Azure DevOps, ensuring maximum protection as we run systems on the Azure Cloud. This protection is achieved through Defender and private endpoints, ensuring our operations run on-premise in a closed environment.

The subscription costs are quite high, so that area needs consideration. Apart from pricing, the support response time could be improved as ticket resolution sometimes takes longer than desired.

There are approximately six people working with Microsoft Entra ID.

The deployment experience was mediocre overall. As a self-learner who watches videos and reads extensively about necessary work topics, the process was relatively easy for me.

The deployment took between four to five months to complete.

The stability is very good, warranting a solid eight out of ten rating.

The scalability deserves an eight out of ten rating.

The technical support is very good, with most inquiries receiving satisfactory answers. However, the waiting time reduces the overall rating to around seven out of ten.

Positive

While I haven't worked with different products, Microsoft Entra ID stands out because it provides an all-in-one solution. With adequate time and dedication, one can achieve significant results with this platform.

The implementation was done through a partner purchase.

While specific monetary return on investment is unclear, the solution has improved our work efficiency. By eliminating the need for multiple VPN channels and enabling direct work from Azure servers, we have achieved approximately 30% efficiency savings.

The SSO functionality is an excellent feature that simplifies work, especially for users with limited IT experience. Despite a busy period last year when Microsoft implemented single sign-on and authenticator for all users, the system has performed effectively.

Regarding seamless integration with third-party applications, Microsoft Entra ID offers a complete solution, particularly beneficial for medium to large companies. Having worked with Dynamics CRM and implementing systems with API, I can confirm that achieving integrated system functionality creates robust company infrastructure.

The solution requires less maintenance compared to our on-premise solutions. While we perform frequent patching and updating on-premise, cloud server updates are minimal, typically only when our external consultant requires changes.

I would recommend this product to other users because I work with clients and my own company exclusively using Azure. It is the only system I recommend due to my expertise and its comprehensive package that allows for expansion.

On a scale of 1-10, I rate Microsoft Entra ID a 9.

Hybrid Cloud

Microsoft Azure

We are using Microsoft Entra ID for multiple purposes, such as managing all authentications and changing passwords online. Previously, we relied on an on-premise network, which required us to be on-site to change passwords. With Microsoft Entra ID, we can synchronize it from anywhere on the network. We have an Azure AD Premium license and utilize features like conditional access policies to control identities. We use it primarily for managing identities inside the organization.

The best feature of Microsoft Entra ID is that it provides more granular control over user identities. The conditional access policy feature is particularly valuable, and it's something we use frequently. Microsoft Entra ID helps us manage identities according to security standards, and it allows us to implement least privilege access effectively. The logging and monitoring capabilities give us insights into activities, offering a single pane of visibility to detect anomalies, ensuring enhanced security.

In terms of improvement, we face issues with latency and responsiveness. Changes take some time to reflect across all users, sometimes up to twenty-four hours, which can be challenging when we need to implement drastic changes. Additionally, Microsoft's documentation can be insufficient. Some technical configuration details are missing, requiring us to consult external sources like forums or communities. They need to improve their documentation to ensure all necessary technical information is covered.

We have been using Microsoft Entra ID for six to seven years. Before that, we had an on-premises Active Directory environment, and then we transitioned to a hybrid setup with Azure connect. This has been our setup for around six to seven years.

Microsoft Entra ID is stable. It functions as it is designed, but improvements regarding the responsiveness of the solution are needed. Sometimes, rolling back changes takes longer than expected, affecting our operations.

Microsoft Entra ID is scalable. It integrates well with third-party tools.

I have experienced mixed results with technical support. Sometimes the support is excellent and technical issues are resolved quickly. However, there are times when complex tickets are assigned to non-technical personnel, which prolongs resolution times. After a delay, we might find out that an issue is out of scope for a particular agent, causing further delays.

We previously used on-premises Active Directory and switched to Microsoft Entra ID to reduce infrastructure. We have a hybrid environment now but maintain some local infrastructure for testing purposes.

The initial setup of Microsoft Entra ID is not straightforward; it sits between easy and tough. Implementing features requires vigilance and certainty before making changes due to its complexity. Microsoft's documentation misses some technical details, creating a need to refer to external resources for certain configurations.

Our deployment was done in-house. We did not use an integrator, reseller, or managed service provider.

Microsoft Entra ID provides visibility for security, such as tracking identity movements. By not relying on an on-premises solution, our infrastructure management is simplified, which aids in disaster recovery planning. We also integrate security features like risky users policies that enhance our security architecture. This contributes to a good ROI.

I rate Microsoft Entra ID at eight to 8.5 out of 10 overall. The solution is mature, with a big community and a strong reputation in the market. It's recommended due to its features and community support, though implementation challenges and documentation issues require attention. Community support and Microsoft's reputation are valuable, but the latency and documentation need improvement.

Hybrid Cloud

Microsoft Azure

My main use cases for Microsoft Entra ID are authentication and access management.

The features of Microsoft Entra ID that I like the most are Conditional Access.

The implementation of Microsoft Entra ID has a significant impact on my secure access to apps or resources in my environment because it ensures that for every SaaS app we have, we can log in with enterprise accounts instead of having to create different accounts. If we disable a user, they get automatically disabled as well in those SaaS apps. That's definitely a big win compared to Active Directory in the past.

I think Microsoft Entra ID can be improved, but that's a broad question, and I'm uncertain about specific areas.

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

I would assess the stability and reliability of Microsoft Entra ID as working fine with good uptime. There was an issue a few years ago, but that's been resolved now.

I haven't experienced any downtime, crashes, or performance issues.

Microsoft Entra ID scales with my growing organizational needs and scales pretty well, supporting up to hundreds of thousands of users.

I haven't expanded usage beyond what we currently have, as we only have as many employees as we have.

When we have to expand usage, the process is smooth because we don't have to do anything; we just add users.

On a scale from one to ten, I would rate my customer service and technical support for Microsoft Entra ID as pretty good, with the support being amazing for identity.

Positive

Prior to adopting Microsoft Entra ID, I couldn't really use another solution to address similar needs because Office 365 can only work with Microsoft Entra ID; it's tied to it.

I would describe my experience with deploying Microsoft Entra ID as working pretty easily.

The deployment of Microsoft Entra ID was easy with just a quick setup, and for Conditional Access, it's well-documented.

I didn't face any challenges during the implementation.

I have seen a return on investment with Microsoft Entra ID, but we didn't have another solution, so when you have Office 365, that's the only thing you can use.

My experience with the pricing, setup cost, and licensing is that we have Microsoft Entra ID Plan 2 licenses, so for us, everything is included, and I don't really work with the other models.

I didn't consider any other solutions before selecting Microsoft Entra ID because it's the only option with Office 365, so you don't have another choice.

Since implementing Microsoft Entra ID, I observe changes in the frequency of identity-related security incidents in my organization, though I'm uncertain about the specific details.

Since implementing Microsoft Entra ID, I definitely see all of the identity risks that are detected for the users now. Before, we didn't have any view on that.

My organization's approach to defending against token theft and nation-state attacks has not changed specifically since implementing Microsoft Entra ID.

The features of Microsoft Entra ID have benefited my organization because we're just more secure. We have less identity theft and no identity compromises since we have MFA now, whereas before, we didn't have MFA.

The integration capabilities of Microsoft Entra ID have influenced my zero-trust model significantly because we didn't have a zero-trust model before.

I don't share any metrics or data points that demonstrate the impact of integrations because before we had nothing.

The implementation of device-bound passkeys and Microsoft Authenticator has affected my organization's approach, and we use phone sign-in with Authenticator.

I would rate my overall experience with Microsoft Entra ID as a nine. The advice I would give to another organization that's considering Microsoft Entra ID is to pursue it because it's included in Office 365.

Microsoft Azure

We primarily use Microsoft Entra ID for application registration, especially for Software as a Service applications, which are prevalent in managing the power grid. These applications support various needs, such as managing contingent workers in our 24/7 operation. While we still utilize some on-premise applications, we prioritize cloud-based solutions for their high availability and accessibility. Furthermore, we are actively exploring B2B collaboration features in Entra ID to manage guest accounts, which offers significant cost savings on licensing and enhances ease of use for external users. Optimizing guest access privileges is a compelling business case for utilizing Entra ID effectively.

Microsoft Entra ID has helped by simplifying our management of permissions for APIs. We are not directly exposing credentials, as we use tokens instead. It has made management easier and more secure, especially in a multi-user environment.

The implementation of Microsoft Entra ID significantly improved secure access to applications and resources in our environment, primarily through the widespread use of single-sign-on. Managing API permissions became much easier, as application registration often involves calling an API to utilize services without directly exposing credentials, relying instead on token-based authentication. This streamlined approach benefits end-users by simplifying access while remaining transparent to them. Ultimately, my role focuses on ensuring a smooth and user-friendly experience, even if the underlying technology remains unseen by the end-users.

Our company strongly emphasizes passwordless authentication, primarily through device-bound passkeys in Microsoft Authenticator. While administrators with high-privileged accounts utilize YubiKeys and passwords for tasks like accessing Microsoft Graph, we are actively transitioning all other users towards passwordless methods such as Windows Hello biometrics. This approach streamlines authentication and enhances security. Though initial deployment in 2022 presented challenges due to hardware limitations and the lingering effects of the COVID-19 pandemic, the technology has significantly improved and provides a simple and effective user experience.

The most valuable feature of Entra ID is having a cloud-based identity, similar to Google's single sign-on. This technology allows for a managed identity in a corporate environment, differentiating between work and personal profiles. Microsoft excels at this distinction, providing a seamless experience akin to signing on with Google across various platforms, streamlining workplace access.

One challenge with Entra ID is its complexity, stemming from integrating many components into a single solution. This complexity can hinder rapid adoption by professionals, suggesting a need for more streamlined, role-specific training to maximize the platform's potential.

I have been using Microsoft Entra ID for four years.

I have used Microsoft Entra ID almost daily for the past few years. Although there have been some minor issues this year, such as with CrowdStrike, it remains a stable platform overall. However, it may not have achieved 99.9 percent availability this year.

Although our company is small, Microsoft Entra ID is a scalable solution that meets our current needs.

Customer service is a mixed bag. Initial responses aren't always great, but once we find the right person, the support can be really good. The initial score is about a six, but with the right assistance, it moves to an eight or nine out of ten.

Positive

In the past, we used Okta and more on-premise solutions. In manufacturing, I used Duo as well.

The initial setup of Entra ID is manageable, especially for those familiar with domain controllers and Active Directory functionality. The straightforward process involves installing an agent on our server, after which Microsoft handles the propagation of information to the cloud.

Regarding my work, the managed identity with consistent feature updates that provide access, ease of use, and security comprises the most significant return on investment for us from Entra ID. While keeping up with updates can be challenging, ensuring security and ease of use makes it worthwhile.

Licensing costs for Microsoft Entra ID remain a concern, especially with the price increases in 2023. While these increases are often attributed to global supply issues or inflation, they still impact everyone. To address this, we are exploring guest accounts to reduce costs. Although many new features are still in preview, we are utilizing them with the understanding that once they are finalized and priced, they will be ready for widespread use. For example, we are implementing Microsoft Copilot, which carries a significant licensing cost. However, beyond the cost, data governance and role-based access control are crucial considerations. AI introduces complexities beyond traditional RBAC, requiring data labelling and different access management strategies.

I rate Microsoft Entra ID an eight out of ten.

Microsoft Entra ID is a great tool, but we face challenges working with numerous vendors and Microsoft Gold partners. Since we manage the power grid, we must proceed cautiously while ensuring effective solutions. Our 24/7 operations necessitate collaboration with other power companies that rely heavily on Microsoft products. To facilitate this, we aim to create a platform for seamless intercompany cooperation, especially since many are establishing data centers.

While I'm not as focused on cybersecurity these days, I believe the zero-trust principle should always prioritize security in its design. This foundational approach applies to everything, from individual tenants to startups. Microsoft, for example, uses default settings, which, while not always ideal, aim to avoid disruptions. I understand their approach, but security should always be paramount.

Our adoption of Entra ID has been slow, particularly with bulk electric management systems. While we desire control over our data center, incidents like the CrowdStrike outage highlight the risks of relying solely on cloud providers. This event sparked discussions among my coworkers and me about Microsoft's ambition to be the World's Computer, as proclaimed at Ignite Keystone. Such aspirations demand greater accountability, especially when outages disrupt global operations. Although Microsoft wasn't directly responsible for the CrowdStrike issue, the perception of their service reliability is still impacted. Ultimately, users will focus on the outcome, regardless of fault.

Hybrid Cloud

Microsoft Azure

Microsoft Entra ID is mostly integrated with Microsoft 365, and it serves as the backbone of the 365 services. Microsoft Entra ID identity platform is feature-rich, allowing for a lot of integration as a single identity model. As an identity provider, you can get a lot of external SaaS applications to identify and be authenticated via Microsoft Entra ID, which is very useful, allowing you to secure your identity in one central place as opposed to trying to secure it in multiple different environments or needing to authenticate users individually on different platforms. Authentication happens once through one identity platform. The Conditional Access policies that you can drive and control the identity flow through are also very useful.

Microsoft Entra ID becomes the central point of authentication for identities, and it has a big impact, a very large impact.

I cannot really think of any specific way where Microsoft Entra ID can improve.

I have been using Microsoft Entra ID for many years, probably at least ten years.

Microsoft Entra ID is very stable. Regarding reliability, there have been instances here and there, but nothing noteworthy.

I was not involved in instances where customer support was used, but I would imagine the teams would have reached out to Microsoft customer support for that.

Neutral

I did not use other solutions before Microsoft Entra ID, but the other solution would be predominantly on-premises Active Directory, which is a different identity management model.

I have definitely seen a return on investment for Microsoft Entra ID.

I do not monitor the frequency or nature of identity-related security incidents since my role is not to look after that; I do not work on the IT team for an organization where I control or monitor that. I used to many years ago, but I have since transitioned into more of a solution architect role which I do not really get involved with.

Since organizations have been using Microsoft Entra ID platform, you would need to change your approach in terms of how you authenticate users, which involves a lot of hardware tokens-based authentication, especially MFA. A lot of companies that I have worked with have implemented phishing-resistant MFA deployments, such as YubiKeys, and the interoperability between Microsoft Entra ID and YubiKey has been quite successful.

We predominantly use two solutions that are phishing-resistant, which are Windows Hello, for which we have done quite a few implementations of both the hybrid and cloud-native versions, which also integrate with Microsoft Entra ID. I would rate this review nine out of ten.

Hybrid Cloud

Microsoft Azure