Microsoft Entra ID Reviews

The main use case for Entra ID is to move from on-premises to the cloud. I have been doing a lot of cloud transformation work, and I have seen that most organizations that move to the cloud see a lot of benefits in terms of monitoring and IAM. In those cases, we move to Entra ID.

Entra ID provides a single pane of glass for access management. Microsoft Identity confirms users and the access management grants access. In terms of IT and access management, Entra ID provides better management and monitoring solutions that can be used effectively. Entra ID can be used by IT administrators and app developers. It offers a wide range of options for onboarding applications to the cloud. For example, enabling single sign-on for an on-premises application can be time-consuming. However, moving the application to Entra ID is straightforward. App developers can use Entra ID APIs to build personalized experiences, set up single sign-on, customize applications, and monitor them.

The single pane of glass consistency for user sign-on experience is very good because Entra ID is a solution from Microsoft that is available in different regions around the globe. This means that we always have better visibility and management of user sign-on, and now Microsoft apps also moved to Microsoft Entra. This provides a unified experience where we can manage access and permissions from a single location.

The consistency of our security policy is excellent. It is very granular, allowing us to scope it to groups or access it via the API. We also have Entra ID PIM, which allows us to granularly control access to resources. This is a very good option for access management.

Active Directory's Admin Center is a very good tool for managing all identity and access tasks in our organization. It provides a single pane of glass for managing users, groups, external identities, and roles. It also allows us to create administrative units, which can be used to scope access to a set of users, groups, and devices. We can also use Admin Center to view licenses, company branding, user settings, security settings, sign-in logs, provisioning logs, usage, and insights. Admin Center also makes it easy for admins to troubleshoot problems. For example, if we need to debug something, we can log into Admin Center and check the sign-in logs.

There were many benefits to moving to Entra ID. The main benefit was that it was a game-changer, especially for monitoring. When we were using Active Directory, everything was local. This meant that we had to build our own monitoring solution for each application that was onboarded into AD. This was a time-consuming and expensive process. With Entra ID, we can use Microsoft Sentinel or Entra ID Monitor to monitor all of our applications from a single location. This is a huge time and cost savings. Another benefit of Entra ID is that it makes it easy to onboard new applications. With AD, we had to deploy the application on-premises and then configure IT and access management. This was a complex and time-consuming process. With Entra ID, we can simply onboard the application and then grant Identity Access Management to the application. This is a much simpler and faster process.

Conditional access is a powerful feature that allows us to define a set of conditions that must be met in order for users to access our applications. This can help us to improve security by ensuring that only authorized users can access our data, regardless of where they are or what device they use. For example, we could create a policy that requires users to be located in a specific country or to use a specific device type in order to access our applications. We could also require users to use multi-factor authentication in order to access our applications. Conditional access policies can be applied to all of our applications, including those in Entra ID and Office 365.

Conditional access policy plays a key role in zero trust security. In the conditional access policy, there is a feature called named locations, which allows us to exclude devices from a condition if they are coming from a trusted location. For example, if we add an exclusion for trusted locations to our conditional access policy, it will directly impact our zero trust policy. The main driver for any organization to move to zero trust security is to reduce the number of named locations in their conditional access policies. By reducing the number of named locations, we can increase the security of our organization by making it more difficult for attackers to gain access to our systems.

I have been using the conditional access feature in conjunction with the endpoint manager for a long time. This is a great feature because it helps us to monitor threats and direct users accordingly. It is a very useful feature for monitoring our endpoints. For example, if a user tries to access a service, the check can be done and the endpoint manager will be able to provide us with all the findings.

Microsoft Defender for Endpoint can identify any PaaS devices that connect to a network. This includes any unpacked devices that are trying to use an application that is onboarded in Entra ID or any persistent Office 365 application, such as Microsoft Teams, Outlook, or OneDrive.

I have been using Entra Verified ID on the proof of concept. It is one of the best ways to onboard a remote employee. Since COVID in 2020, we have all been working remotely. It is better to onboard an employee who is present remotely in a different location than to ask them to come to the office, collect a laptop, and then onboard them. Verified ID makes this process easier by using preset, already-known information that is present in our company directory. For example, when an employee is interviewed, they are given face verification through a government ID. The ID is collected and a photograph is taken, which is then stored in the HR database. With this information, we can onboard employees remotely and grant them access to all of the company's resources. This is a much easier option than asking everyone to come to the office and ask for help from the overloaded service desk team.

The speed at which we can onboard a remote employee depends on how we define it in the initial planning. If we set the correct standards, such as the type of information we need to verify the employee's identity, we can streamline the process. For example, if we require the employee to provide a government ID and a photograph, the HR department can collect this information in advance and process it in the company's database. This will make it easier for the employee to complete the onboarding process remotely.

When it comes to controlling and prioritizing the privacy of identity data, there are multiple ways to do so. One way is to onboard remote employees with information that is already present in the company directory. This information can be verified by HR, who has already obtained the employee's consent to share their personal information. Another way to onboard remote employees is to ask them to provide a photo and government ID. This information is also stored in the company's database and is not shared with Microsoft. Microsoft only creates a digital identity for the employee and uses this identity to validate the employee's remote onboarding. In both cases, the employee's personal information is not exposed to the Internet. Microsoft and the company have a secure channel for exchanging this information, so there is no problem with data privacy.

The permission manager in Entra ID is very good. Microsoft improved it a lot. Microsoft Entra is the new permission manager solution. It provides comprehensive visibility into the permissions assigned to all identities, such as user identities. It also allows us to check the current permissions that are given to users. This is a better way to manage permissions. Permission management is a really good option that has a lot of benefits and improvements, especially when moving to the Microsoft enterprise.

When it comes to identity and permission management, the risk is relatively low when using a cloud-managed solution. This is because cloud-managed solutions provide full visibility and the option to automate permission management. One of the benefits of cloud-managed identity and permission management is that it allows us to implement the principle of least privileges. This means that we can give users and workloads only the permissions they need to do their jobs. This helps to reduce our attack surface and makes it more difficult for attackers to gain access to our systems. Another benefit of cloud-managed identity and permission management is that it provides us with visibility into our user and workload identities. This allows us to quickly identify and remediate any security issues that may arise.

Entra ID helps our IT administrators and HR department save time. It reduces the custom task of deploying and onboarding any application. This means that administrators can easily onboard applications to Entra ID and provide users with a single sign-on experience. As a result, administrators have more time to focus on improving their skills and deploying new Entra ID features. Entra IDoffers a wide range of features, including artificial intelligence capabilities such as Chat GPT. This frees up a lot of time that was previously spent managing the local active directory. Entra ID has freed up most of my weekends. When I was previously working with on-premises data centers, I had to patch my servers every weekend, which was a time-consuming and tedious task. However, now that all of my applications have been moved to Entra ID, these tasks have been drastically reduced. As a result, I would say that my weekends are now almost free.

Entra ID saved lot of organization money. I see previously organizations investing in expensive solutions for data centers, which required a lot of maintenance and the need to find the right talent to manage them. However, with Microsoft Entra ID, we no longer have to worry about maintaining data centers, as they are completely managed by the cloud. This has made our operations easier and more efficient, as we can now deploy changes quickly and easily, and receive alerts when any issues are found.

Entra ID positively affected our user experience.

Microsoft Entra ID Protection and Microsoft Sentinel are both excellent monitoring features for Microsoft Entra ID.

Beneficial of Entra Monitor and Log Analytics to monitor the secure operation of Entra ID services.

Great improvements in the Modern Authentication Strategy Passwordless FIDO2 improvements & Entra ID verification 

In terms of licensing - being able to pick some premium features without purchasing a package is advantageous.

Increasing the free log retention period might be more beneficial.

Compatibility features for legacy systems integration with new features will be challenging at times.

I have been using Microsoft Entra ID for ten years. Microsoft Entra ID has been a critical component of Microsoft cloud offerings since the time it was introduced.

Entra ID is extremely stable and Microsoft absolutely brings new improvements to this feature.

Entra ID is highly scalable. I have seen multiple organizations over 80,000 people in use Entra ID worldwide.

The technical support is good but sometimes it can be difficult to connect with the right engineer when you are working in a complex enterprise environment.

Out of all my experiences i have seen organizations using  Microsoft Active Directory before switching to Entra ID.

The initial setup is straightforward. I completed most of the deployment myself with excellent support from the Microsoft support Team.

In most of the cases the implementation was completed in-house with support from the Microsoft support Team.

We have seen a return on our investment with Microsoft through improved performance, better management, and enhanced features.

Entra ID's pricing is comprehensive and affordable. The prices are easy to understand, and the licenses include a variety of security monitoring and additional features.

I have evaluated Google Cloud Identity and AWS Directory Service, but I felt more comfortable with Entra ID.

I give Microsoft Entra ID a nine out of ten.

Entra ID does not require maintenance from our end.

For someone evaluating Entra ID, it is important to understand their use case, business requirements, current solution, and expectations. The current solution is important to understand because it will help to identify any gaps that Entra ID could potentially fill.

I usually use Microsoft Entra ID to access our resources and to manage our approvals. It is used to assign roles, set limits, and manage access levels. For specific users, I ensure that nobody else has access. My personal files are protected, and confidential projects are kept secure.

The solution has helped build trust. I trust what I am doing and make sure that my files are protected and safe.

Microsoft Entra ID offers strong security levels, especially with two-step authentication, which confirms that I am the real user. It ensures that nobody can access files or emails without permission. Additionally, it consolidates sign-in requirements across different services, like GitHub, Twitter, and Upwork, in a single application. Microsoft Entra ID changes permissions to role access ID levels, ensuring access to only what is needed.

I do not see any area needing improvement. Perhaps integration with other AI tools, beyond Copilot, could enhance its use, like signing into ChatGPT.

I have been using Microsoft Entra ID for almost more than fifteen years.

I have not experienced any performance or stability issues with Microsoft Entra ID.

Microsoft Entra ID is scalable. It can accommodate many accounts, beyond just a few.

I have not been in contact with Microsoft customer service.

Positive

I evaluated Google Identity and HashiCorp but decided to stay with Microsoft Entra ID because of its user-friendliness and familiarity.

The initial setup of Microsoft Entra ID was very straightforward.

The deployment of Microsoft Entra ID was handled in-house by our department.

I have not thought about return on investment because the company provides Microsoft Entra ID. However, the protection it offers is invaluable.

The cost of Microsoft Entra ID is around $8 per month, which I find very reasonable.

I evaluated Google Identity and HashiCorp.

I rate the solution at ten because it is a great solution for those looking for security and privacy.

We predominantly use Microsoft Entra ID for running our User Directory Service. It integrates with Intune, Exchange, and SharePoint.

Microsoft Entra ID acts as our core directory. It is essential for authentication, VPN authentication, and using onsite RADIUS. It supports our user scopes for various applications. Everything we do revolves around this directory and its authentication.

If I have one criticism, it's regarding processing times. Changes or even inbound email logging tend to take a minimum of fifteen to twenty minutes. There is a need for more real-time processing. Some user updates are instantaneous, while others can take two to three hours. A feature to force manual updates would be beneficial rather than waiting for scheduled updates.

I have been working with Microsoft Entra ID since 2009.

For stability, I wouldn't give it a ten because we have experienced some outages. I would probably rate it around a seven. Generally, it's stable, but when it goes down, the impact is substantial.

From my perspective, we haven't encountered any scaling limits. It meets our needs for user productivity.

I would rate Microsoft's technical support on the lower side. While some responses are quick and satisfactory, there have been occasions where issues took weeks or circles to resolve, sometimes closing and reopening without resolution. I would rate their support around a four.

Neutral

Through acquisitions, we used Google Workspace. We have spent a considerable amount of time with it.

The initial setup of Microsoft Entra ID is not straightforward without training. However, once you are familiar with it, the process is seamless.

We did not use an integrator or consultant for the first deployment. Initially, I did it all myself, although I have a few people working with me now.

Regarding pricing, for the services we receive, it seems within the market range and about average.

Through acquisitions, we have spent considerable time evaluating Google Workspace.

Overall, Microsoft Entra ID does what we need it to do. I would rate it around a seven on a scale of one to ten.

Our primary use case for the solution is building solutions using all Microsoft services, including migration projects, service provider roles, developer solutions, AI solutions, and ETL solutions for all those things, where we will use Microsoft services.

Recently, I did a migration project, which involved migrating from Microsoft Dynamics using ETL, for which I have used Microsoft Entra ID for app registration and API authentication. From Microsoft Dynamics 365, I want to connect to Microsoft services, and I perform the authentication and app registration and user login; I have used all these functions in Microsoft Entra ID.

The implementation of Microsoft Entra ID has impacted my secure access to apps or resources in my environment because it made it easier. For example, if I need to access a Key Vault and don't want to access it directly, I can use Microsoft Entra ID, and I can set all the policies there and use the Key Vault values.

These features are beneficial and valuable because they can be used to connect with third-party services and Microsoft services.

Since implementing Microsoft Entra ID, I've observed changes in the frequency and nature of identity-related security incidents. In app registration for a recent project, my Microsoft Dynamics 365 enterprise application is not visible. We need to add that app through client; we need to use AZ client, and there we need to add the ID, and it is not showing in the UI. This could be improved.

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

The Microsoft Entra integration capabilities have not influenced my zero trust model in any way.

I have been dealing with Microsoft Entra ID, which is not as an Azure product, since 2000. So, twenty-five years now. It is now known as Microsoft Entra ID.

Microsoft Entra ID is built on a robust database infrastructure for finding objects with specific capabilities, be they users, computers, members of a company, machines, or whatever else. It historically stems from the X.500 system, developed for efficiently finding specialists, as demonstrated with the Apollo project. This historical foundation underpins its effective directory services in the modern context.

Currently, Microsoft Entra ID is a pretty service. It could benefit from implementing a specific large language model instead of LDAP queries to find resources and implementation details in one comprehensive scoop. This could replace existing document references with AI-driven support for faster implementation.

I have been dealing with Microsoft Entra ID since 2000, which is now rebranded to Entra ID as a Software as a Service product of Active Directory.

The infrastructure of Microsoft Entra ID scales to register and manage various resources, including large-scale directory services for users, computers, machines, etc.

I find the support excellent. If I have an investigation and I am not progressing well, contacting support results in responses within one or two days, usually with competent people. Because it takes some time, I rate it a nine out of ten.

Positive

There are different licenses with various capabilities, as with any service Microsoft offers. Microsoft sets pricing based on customer demand, adjusting to find the optimal balance between sales volume and profit per unit, similar to how Costco manages product prices.

I rate Microsoft Entra ID ten out of ten. It can be improved with large language models for better usability, but currently, it is quite efficient. Microsoft CEO Satya Nadella suggested transitioning all Software as a Service systems to agent-based large language model solutions, which seems promising. I am willing to be a reference for Microsoft and I am open to receiving contact from people with questions about my review. The solution is rated ten out of ten.

We use Microsoft Entra ID to ensure our users have the correct permissions and access. It manages privileged identity and ensures that we have proper MFA for the security of our employees.

Entra ID has made us more agile, enabling us to move faster in our tasks while providing tools for our employees to become more agile and efficient. The solution has improved our security considerably. Entra ID has helped us strengthen security across the board regarding access to apps and resources. It lets us create layers of security that help us prevent significant security issues in the future, such as nation-state attacks and token theft.

The solution helps us envision a future with zero trust, which is one of our goals but challenging to achieve. Entra ID has given us a pathway to achieve it.

Multi-factor authentication is one of the most important features of my work. Verified ID is another feature that is becoming significant. Furthermore, Microsoft Entra ID provides governance over IDs while ensuring people have the correct permissions. We also gain more visibility into security issues, leveraging automation to address them. It's made us more agile and efficient.

There are many new features being added all the time, and Microsoft is advancing at a pace that aligns with our needs. I can't think of anything immediate that needs improvement.

We have been using Entra ID since Microsoft Office 365 was released. I'm unsure of the exact year, but it's been quite a few years—perhaps 10.

The stability of Microsoft Entra ID is fantastic. We rarely encounter any significant issues.

The scalability is great. We are a larger partner, so we're a high-end example, and it's scaled very well for us.

Customer service and technical support have been outstanding. For an organization the size of ours, we have a dedicated team we frequently connect with and escalation paths for larger issues.

Positive

We previously used various solutions, but integrating everything under Microsoft has allowed us to streamline and manage everything in one place.

The setup process is quite streamlined, particularly around cost procedures. However, I don't have any additional details.

We worked with several partners, although I can't recall any names.

I don't have specific metrics but implementing the solution has definitely helped us.

Our experience with pricing, setup cost, and licensing is streamlined and simplified, particularly in cost procedures. I don't have more details beyond that.

I don't recall any specific alternate solutions evaluated before switching.

I'd rate Microsoft Entra ID a 10 out of 10 due to the extensive range and focus on security features.

As a bank in Turkey, we are prohibited from using cloud services for data storage. However, to utilize Microsoft Teams and implement a suitable Data Loss Prevention solution with Entra ID authentication, we adopted Microsoft Entra ID.

Microsoft Entra ID facilitated the implementation of Microsoft Teams as our collaborative platform. To prevent misuse of Teams features, particularly chat, we also integrated Symantec's data leakage prevention solution.

Microsoft Entra ID, integrated with Microsoft Teams, has enhanced the security of access to applications and resources within our environment.

People in the company are happy with Microsoft Teams, and we are quickly adopting it for collaboration. We are excited about the potential introduction of Copilot to Microsoft Teams, which is expected to be beneficial.

The most valuable aspect of Microsoft Entra ID is its ability to integrate with other cloud applications.

The quality of support has declined in recent years.

I have been using Microsoft Entra ID for two years.

Microsoft Entra ID has been stable since we started using it two years ago.

We experienced no scalability issues with Microsoft Entra ID. Our company's approximately 25,000 users were almost all synchronized to the cloud without performance problems.

Microsoft support has always been the best among all big companies. Although there is a general decrease in the quality of support across all companies, Microsoft Entra ID is still the best.

Positive

We previously used a local Microsoft Active Directory and integrated it with Entra ID. We also had other directory solutions like Oracle ID but chose not to switch because we depend on Microsoft solutions. Our desktops are Microsoft endpoints, and nearly half of our data center servers run Windows operating systems. We have existing long-term agreements with Microsoft, which led us to choose them for cloud adoption without considering other vendors.

We implemented Microsoft Entra ID in-house using resources and the help of Microsoft.

I would rate Microsoft Entra ID nine out of ten.

When I started using Microsoft Entra ID I was an identity and access management technical support engineer at an organization that was a Microsoft partner. I use Microsoft Entra ID primarily to reproduce customer scenarios or challenges they are facing to help them resolve issues on their end. 

Microsoft Entra ID offers a single pane of glass for managing user access. This unified interface provides essential notifications and guidance if further actions are needed within Entra ID. While all features can't be displayed simultaneously due to potential clutter making it visually unappealing, the centralized view efficiently directs us toward managing user access and other identity and access management tasks.

The single pane of glass affects the user's experience positively. Microsoft Entra ID makes necessary innovations when it comes to the GUI interface.

In my overall assessment, the admin center seems effective in consolidating all the responsibilities and duties that admins should be able to perform. This centralization makes it efficient for users like us global admins and user administrators to find everything we need to do in one place, adhering to the principle of least privilege. While I appreciate the admin center's functionality, I prefer working with the Entra portal for its more robust view.

Microsoft Entra ID has significantly improved our organization's security posture. One key feature is what we call privilege identity management, specifically designed to manage sensitive administrative credentials. For example, imagine a CEO with an account in Entra ID. We might also have an IT technician or support person with an admin role, like a Security Admin. We call these privileged identity accounts. While the CEO holds the highest position, they don't need admin access. privilege identity management has been instrumental in enhancing our overall security in several ways including, Robustly securing privileged identity accounts: PIM implements stringent controls and access restrictions, minimizing the risk of unauthorized access to sensitive data and systems. Enforcing the principle of least privilege: PIM ensures users have only the minimum permissions necessary to perform their duties, reducing the attack surface and potential for misuse. Adding extra layers of security: Entra ID integrates multi-factor authentication and conditional access policies, further strengthening access control and mitigating security risks.

Entra ID's conditional access feature strengthens the zero-trust principle, which emphasizes continuous verification and never granting automatic trust. This policy has significantly improved our overall security posture by implementing specific controls that grant access only when users meet defined conditions.

The visibility and control provided by Entra ID permission management across Microsoft, Google, and Amazon Cloud is impressive. Microsoft has a long history in the identity and access management space, starting with Active Directory and subsequently adapting to the cloud. Their cloud expertise has served them well in developing Entra ID, a comprehensive IAM solution. I believe Entra ID represents a significant improvement, offering clear visibility and control over permissions. While I haven't used other third-party products for comparison, I feel Microsoft has delivered a top-notch feature within the IAM landscape.

Using permission management has helped reduce risk surfaces regarding identity permissions.

Entra ID has significantly reduced the time burden on our IT administrators and HR department. Take, for example, its built-in self-service password reset feature. Imagine I've forgotten my password and need to reset it. Previously, I'd have to log a request with IT, potentially waiting for assistance if they were unavailable. SSPR empowers users to reset their passwords independently, freeing up valuable time for our IT team. For our HR department, Entra ID offers integrations with third-party apps, also known as user provisioning. This comes in two flavors: outbound and inbound. Outbound provisioning specifically applies here. In this scenario, Entra ID acts as the source system, creating user accounts in the target third-party SaaS app which is like a tag assistant. For example, if an HR employee needs access to Dropbox or G Suite, we can create those accounts automatically in Entra ID and then provision them into the corresponding SaaS apps using user flows. This eliminates the need for manual user creation in each app. Furthermore, we can implement single sign-on, removing the hassle of juggling multiple passwords for different resources.

Microsoft Entra ID has significantly impacted the employee user experience, particularly through its single sign-on functionality. SSO eliminates the need for multiple passwords to access different resources. Previously, when a user was created in Entra ID, accessing other applications developed outside of Microsoft required separate credentials and logins for each platform. This created a fragmented and cumbersome experience. However, with Entra ID's SSO, user authentication and authorization for these third-party applications now seamlessly occur through a single sign-on process. This grants secure access to all integrated applications without the need for additional logins, streamlining the user experience and enhancing security.

Every feature in Microsoft Entra ID plays a crucial role in overall security. It's like the human body – we might underestimate the importance of seemingly insignificant parts. They might appear small or seemingly irrelevant, but their absence can have significant consequences. When a fingernail breaks or a hair falls out, we suddenly appreciate their role in the body's function. Similarly, with Entra ID, I wouldn't prioritize one feature over another. Each contributes significantly to the platform's robust security posture. They all work together to provide the best possible approach to cloud security. Therefore, highlighting a single feature as more valuable wouldn't be accurate.

Microsoft Entra ID can make improvements in two key areas. The first is to upgrade Workday and SuccessFactors integration to OAuth 2.0. Currently, these HR applications use basic authentication for inbound provisioning to Entra ID, while integration with other IDPs utilizes OAuth 2.0. Many organizations request the adoption of OAuth 2.0 for Entra ID as well, considering its enhanced security. The second is to provide clearer communication about features under public review. Features under public review should have comprehensive documentation outlining their capabilities and limitations. While user feedback is crucial, deploying incomplete features in production environments can lead to frustration and blame. Customers should be informed that public review features are not intended for production use.

I have been using Microsoft Entra ID for three years. 

The technical support team is always readily available 24/7. Regardless of when we raise a support ticket, someone will promptly reach out and try to resolve our specific issue. I understand that the support experience can vary depending on the agent we connect with. Some may not have extensive product knowledge, while others have hands-on experience and offer quick, helpful solutions. Overall, I'd give them a solid ten out of ten. Their constant availability and dedication to resolving our problems are commendable. Even with agents new to our organization, we can feel their effort to assist us. They escalate issues if needed, consistently check back with us for satisfaction, and demonstrate empathy while reassuring us that any limitations or problems we face will be addressed.

Positive

With the rise of cloud computing, Microsoft's exceptional hybrid identity capabilities proved invaluable for our organization. We were able to seamlessly integrate our on-premises users with the cloud through Entra ID. This implementation involved leveraging both Entra ID Connect and the cloud sync agent. While I'm unsure of their identity management setup before Entra ID, I can confidently say that the organization already relied on Active Directory on-premises before I joined.

Deploying Entra ID is generally straightforward. Once we create our Entra tenant, we gain access to Entra ID. Similarly, if we subscribe to Office 365, Entra ID is automatically created for us. This default setup meets most basic operational needs. Therefore, we don't typically need to make any further configuration unless we want to adjust security settings based on our specific organizational needs. Overall, using Entra ID is seamless and can be started directly from our tenant or Office 365 site.

The cost of Entra ID depends entirely on our organization's specific needs and use cases. For smaller organizations, like a local supermarket, it might be quite affordable with the basic free tier or a lower-tiered license. However, larger, multi-national companies with complex requirements may incur higher costs due to the need for additional features and advanced licensing tiers like P1 or P2. Instead of simply labeling it as cheap or expensive, it's important to consider our specific scenario and what functionalities we require. Different models and licenses cater to different needs, so the best approach is to carefully evaluate our organization's specific situation and choose the most suitable option.

I would rate Microsoft Entra ID a ten out of ten.

In the global identity management space, roughly 70 percent of organizations, in my experience, utilize Entra ID. One key reason for this adoption stems from the prevalence of on-premises Active Directory. Many organizations have long relied on this on-premises solution, and Microsoft's decision to replicate its functionality in the cloud, resulting in Entra ID, made the transition seamless for existing users. This familiar interface and consistent experience significantly eased adoption, leading to the 80 percent user utilization rate for Entra ID within my organization.