Microsoft Entra Verified ID Reviews

I can answer a few questions about Microsoft Dynamics. Our main focus in Microsoft Dynamics products is CRM and the finance side. We are just starting our implementation of Dynamics 365 Sales and finalizing the vendors. Our primary product is Dynamics 365 Sales.

I find Microsoft Dynamics 365 very easy and useful because most of the users on our end are using Microsoft, thus they are very familiar with the Microsoft Office stack, and some of SharePoint and Teams. The main thing is the collaboration which helps us from the start of our client journey—from the lead, to maturing, and then managing their operations. Even if someone is leaving, we can track the whole thing.

I believe there should be an easy provision for the on-premises and for the hybrid environment in Microsoft Entra Verified ID, as there seems to be some difficulty with hybrid implementations, especially in a country like Pakistan where most are transitioning to cloud but not fully migrating, instead opting for hybrid solutions. An ease for hybrid integration would greatly help the technical teams.

I believe the policy implementation is a little bit complex on the Microsoft side; there should be a simpler way to implement policies, utilizing standardized templates for compliance, such as industry-specific templates for the service industry, which would be helpful for HIPAA and other compliances.

I had some small experience with Dynamics 365 Sales, but I worked a lot on the CRM side, such as HubSpot and some other CRMs.

So far, I have not experienced any difficulties in the deployment.

I evaluate the technical support in my region as really good; I have logged a few tickets and they were very supportive, coming online to fix whatever issue there was.

Positive

I was using SAP B1 HANA, and recently, one and a half years ago, I switched jobs and now we are working on different products. We are working on Odoo and Dynamics 365 instead now.

We have Microsoft Azure and are using some Azure services such as Azure Entra, Office 365, and some Power Apps. Overall, I have more than five to eight years of experience with PowerPoint and Microsoft Office 365, and we just implemented Azure Entra in our current organization one and a half years ago. I am familiar with Microsoft Entra and work on the Entra side.

We haven't used Entra Workload ID, but we are purely using Microsoft Entra services for our users and integrating our on-premises AD as well. We are definitely using Microsoft Entra Verified ID and it is important. The main feature I find valuable in Microsoft Entra Verified ID is the authentication and management of users, along with a wide range for user management, especially Microsoft Purview that provides important auditing features for our business.

We are using two-factor authentication and some complex passwords for our identity verification processes right now. Microsoft Entra Verified ID has helped reduce fraud or impersonation attacks in some way because we are using a separate product for this, utilizing a SOC and EDR to protect our infrastructure. I would definitely recommend Microsoft Entra Verified ID to others. I would rate this review as a seven out of ten.

My main use cases for Microsoft Entra Verified ID are verifying the end user saying who they are and being able to back that up with government-issued proof.

What I like the most about Microsoft Entra Verified ID is the fact that it is not all the other features that are available, like self-service password reset, which all require a little bit of human intervention. This is more self-service for the end user.

Because I am a consultant, Microsoft Entra Verified ID actually benefits my customers, empowering them to be more efficient in what they are doing day to day.

Microsoft Entra Verified ID has not affected my organization's identity verification process as we use it in conjunction with different methods.

Microsoft Entra Verified ID has helped reduce fraud or impersonation attacks because if you are using a government-sanctioned ID, what is more secure than that?

It is hard for me to say how Microsoft Entra Verified ID can be improved. I really do not know the extent of how that can benefit everything. I am trying to learn that here at the Ignite conference.

I have been using Microsoft Entra Verified ID for as long as it has been available, which has to be when Entra came out, although it was not Entra when it first came out; it was Azure AD. I cannot remember exactly how long.

I would assess the stability and reliability of Microsoft Entra Verified ID as having no problems thus far, which makes it stable in my opinion.

I have not experienced any downtime, crashes, or performance issues with Microsoft Entra Verified ID.

I will say Microsoft Entra Verified ID has the potential to scale as far and wide as we probably need it to, but the usage of it has not quite spread for us.

I have not really expanded usage at all; it is something we have mostly labbed and tested and made available, but not really utilized further.

I would evaluate customer service and technical support as excellent because it is us. We are a CSP, so understanding how the product works and how the deployment is in our best interest ensures we do that right.

On a scale from one to ten, I would rate customer service and technical support as a ten because we are the support. We have got it down, and if there was a question, we know how to reach out for documentation. We have Microsoft representatives that we can reach out to, and it is a very supportive process. We are doing well with it.

Positive

Prior to adopting Microsoft Entra Verified ID, I was using passkeys, YubiKeys, and other token authentications.

I would describe my experience with deploying Microsoft Entra Verified ID as simplistic. Setting it up is just checkboxes and guided setup procedures, which make it simple.

My experience with deployment was fine, as it was a fast and simplistic process. We were able to accurately determine and architect the solution and deploy it to our customers for the benefit of the organization.

I do not think I have had a great way of measuring the time or costs saved from Microsoft Entra Verified ID yet or any KPIs because there is no dashboard I can go to and say thirty percent have used this new feature over how long the other one would take.

I have not really seen return on investment with Microsoft Entra Verified ID.

My experience with pricing, setup cost, or licensing was fine; it was an expected process. We had help and guidance through the entire thing, so it was a very simple process.

I considered none; Microsoft is our all-supreme solution.

My organization has not implemented the Face Check feature yet; we are using YubiKeys.

My organization's trust in digital interactions really has not changed since implementing Microsoft Entra Verified ID; it is just another method, another option. It is empowering the sales folks to be able to authenticate into the Microsoft solutions they use every day, providing another benefit to them and our customers.

There is always going to be reluctance to use a government-issued ID for these sorts of things, as people are already concerned about privacy. But in the workplace, you have already given them your ID and social security number, and now you just have to give it to Microsoft to log in.

Microsoft Entra Verified ID has helped reduce fraud or impersonation attacks because if you are using a government-sanctioned ID, what is more secure than that? What do we have? A Social Security number you want next?

My customers have not said anything that they do not appreciate about Microsoft Entra Verified ID yet; it is just another additional thing they have available to them.

There was not really anything that stood out to me in my evaluation process; I understood what we were getting ourselves into, and it was just a matter of getting it.

I would recommend reaching out to a trusted solution provider, perhaps your CSP or Microsoft directly, if you are considering Microsoft Entra Verified ID. If you do not have one, we can help get you one here at the conference.

On a scale from one to ten, I rate Microsoft Entra Verified ID overall as a seven. It accomplishes the goal that it is meant to and set out to do, but the problem is the fact that users are reluctant to put applications on their phones for authenticator. Our job is to help teach them that it is safe, verified, and maintained. You do not have to worry, but an ID is another step in that process of user adoption, and to grow the confidence is not easy.

My main use case for Microsoft Entra Verified ID is authentication for our users.

The security feature of Microsoft Entra Verified ID is what I appreciate the most.

These features of Microsoft Entra Verified ID have benefited my organization by reducing our costs, as we implemented it so that we don't have to pay for a lot of external MFA methods that are tied directly to our Microsoft services.

Implementing the Face Check feature of Microsoft Entra Verified ID speeds up the login process, so you're not having to remember your password every single time.

Microsoft Entra Verified ID has smoothed out our identity verification process and made it easier for us to authenticate users. Since implementing Microsoft Entra Verified ID, I would say it has made us more confident about our users being who they say they are, so we can trust that we have secure logins for all our users. Microsoft Entra Verified ID has helped reduce fraud or impersonation attacks.

The API that I think Microsoft is still working on could be enhanced.

There is room for improvement in Microsoft Entra Verified ID, particularly in the integration with other platforms, as they could do better with the API, for example.

I have been using Microsoft Entra Verified ID for the last year.

The stability and reliability of Microsoft Entra Verified ID is very stable, as we haven't had any issues so far.

I have not experienced any downtime, crashes, or performance issues with Microsoft Entra Verified ID.

Microsoft Entra Verified ID scales pretty well with the growing needs of our organization, as we're a nonprofit organization with positions in constant rotation, making it a good system for that.

We have not expanded usage of Microsoft Entra Verified ID, as we're just trying to get it rolled out to all of our current users, and it's been a pretty good process.

I haven't actually had to use customer service or technical support for Microsoft Entra Verified ID.

Possibly, someone on my team has had to use technical support, but I've never heard any complaints.

On a scale from one to ten, I would rate customer service and technical support for Microsoft Entra Verified ID a ten because I've never had any issue with technical support or had anyone come back to me with a bad experience.

Positive

Prior to adopting Microsoft Entra Verified ID, we were using two-factor authentication.

My experience with deploying Microsoft Entra Verified ID has been great and easy.

What made my experience with Microsoft Entra Verified ID great and easy is that it smoothed out our user experience and increased our security for all of our users, giving us peace of mind and making things a lot easier.

The deployment model for Microsoft Entra Verified ID is hybrid.

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

We did not consider any other solutions before selecting Microsoft Entra Verified ID.

There are always challenges when you're rolling out something new and introducing it to new users, but the challenges with Microsoft Entra Verified ID were not bad overall.

The deployment of Microsoft Entra Verified ID was rolled out in stages, starting with our IT team first, testing to make sure it works properly, and then deploying it to all the other users in our organization.

I highly recommend Microsoft Entra Verified ID for a business of our size, which is around forty employees, as it works really well for that. I gave this review an overall rating of ten.

We deal with the Microsoft Entra Verified ID as a dictionary where we put all the users. We use it more for internal purposes, but we do have a lot of guest accounts there. We are in the non-profit sector.

One of the valuable features of the Microsoft Entra Verified ID is that it's cloud-based. The importance of having the Microsoft Entra Verified ID being cloud-based is because we don't need to maintain the server.

I don't think there are areas that could be improved with the product. It looks pretty good already. AI could be an area for continuous improvement or even pricing. The Microsoft Entra Verified ID doesn't currently utilize AI.

I have experience with the Microsoft Entra Verified ID for five years now.

Please keep it anonymous. I don't want to disclose my name to avoid receiving strange emails.

On a scale of 1 to 10, I rate their support as pretty bad. Microsoft products basically have no support other than the knowledge base, so I would give it a two out of 10. It takes too long, which is the downside of their support. They have a good product but a very bad support team.

Negative

The initial setup for the Microsoft Entra Verified ID is straightforward. On a scale of 1 to 10, where 10 is the easiest, I would place it at nine. It took a few hours to deploy it.

The solution works as a Verified ID system. I would recommend this solution to others because it's simple enough to deploy. Overall, I rate the Microsoft Entra Verified ID an eight out of ten.

We have many use cases. We're an MSP that provides security solutions, and we deployed Entra ID for various clients, primarily for authentication to Office 365 or Azure. We also integrate it with on-prem environments using Azure AD Connect, now called Entra Server, to push identities into Azure Active Directory or Entra ID.

Entra allows us and our customers to access workloads on Azure and Office 365 securely. We've integrated it with other applications to provide a single pane of glass for user identification, eliminating the need for multiple IDs.

Our clients trust Entra ID as an identity service. We have deployed it in many places and always push it to our customers. We tell them that if they have a built-in application identity, they should change it to Entra ID and create application registrations and one identity.

MFA can do number matching, and the attacker can't get past it. We have lots of cases like that. Unfortunately, it's really hard to eliminate phishing completely

The MFA number matching feature effectively prevents unauthorized access by phishing bad actors who might obtain email credentials. This feature requires users to verify a number on their screen, ensuring they only approve genuine requests. 

MFA has improved our anti-phishing efforts. If a bad guy makes a request from a phished credential, they won't be able to log in unless they have my mobile phone and my biometric information.

While Microsoft continues to improve the solution, integrating the ID with biometric features could be enhanced, especially in terms of standard B2C flows for multi-factor authentication. Improvements in remembering devices and the timing of MFA triggers could also be beneficial.

I've been using Entra ID since around 2014 or 2015 and have continued through its updates and name changes.

Microsoft Entra is very stable. For as long as I've been using it, there's only been one global failure during an upgrade, which was resolved within an hour.

Entra ID is easy to scale. You can have as many users as needed. Scalability is managed through licenses, making it straightforward to adjust to our needs.

I rate Microsoft support seven out of 10. The support can be inconsistent. Verified Support, which used to be Premier Support, is much quicker but comes at a higher cost. Standard support could be improved, as it's often not as responsive.

Neutral

The initial setup is straightforward for those who understand the process.

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

The pricing and setup are standard. With Entra, you choose between P1 and P2 licenses. We recommend having at least one P2 license in a company for better alert management, even though P2 is more expensive.

We've had clients using Duo, but we often advise against it since they pay for similar features with Entra ID.

I rate Microsoft Entra Verified ID nine out of 10. While the solution might need improvement in some areas, the stability and core functionality are exceptionally robust, delivering great value.

We started using Microsoft Entra Verified ID when the Active Directory was changed, and we needed to onboard customers from on-premises to Azure Cloud. For instance, we started using the solution when we did a significant migration from VMware Horizon VDI to Azure VDI. This was our first introduction to it for Azure VDI customers.

Microsoft Entra Verified ID helped us with single sign-on and logging. It organized everything, allowing a single sign-on process for our cloud customers. We no longer manage multiple domain controllers because Microsoft handles everything, improving our efficiency.

The authentication features of Microsoft Entra Verified ID are valuable. As an infrastructure professional, I appreciate the exceptional integration between on-premises Active Directory features and Entra ID. 

We were an on-premises organization. When we moved to the cloud, Entra gave us more clarity regarding logins and log collections and helped us see what succeeded or failed. When we were on-premises, we had to do a lot of log digging that we don't need to do on the cloud. We get fraud detections and can act immediately. 

There are issues with the integration of Microsoft Entra Verified ID and MFA. Sometimes, the MFA process doesn't succeed, requiring users to sign out and log back in.

I have used Microsoft Entra Verified ID for over two years.

The stability of Microsoft Entra Verified ID is very good.

Scalability is also good as it is a cloud product.

I rate Microsoft support six out of 10. Occasionally, the support we receive from Microsoft isn't great.

Neutral

We previously did not use a different solution that performed the same functions. We are onboarding only customers who are already Azure tenants.

The initial setup process, guided by Microsoft, was verified for efficiency and ease.

We used an integrator for the first deployment, Ingram, and the experience was satisfactory.

The biggest return on investment when using Microsoft Entra Verified ID is the single sign-on (SSO) feature. Security is a benefit we get regardless of the license we pay. The number of attacks has gone down. We rarely face any threats.

I still feel the pricing is on the higher side for larger customers. They don't pay anything for on-prem Active Directory. Although we receive additional features with Microsoft’s SSO, pricing is an area Microsoft can work on. 

We are only offering this solution to customers who are on Azure, so there is no point in evaluating other solutions.

I rate Microsoft Entra Verified ID eight out of 10 because there are still some issues when reporting to Microsoft, with customer support needing improvement.

In our company, Microsoft Entra Verified ID is not used in a full-fledged capacity. I would say that the product is used partially, specifically when employees are being moved around.

The most valuable features of the solution are mainly in the areas of security and auditing.

Honestly, I cannot comment on what needs improvement because we don't have any requirements. All our requirements are met with the tool. The tool's expensive nature is an area of concern where improvements are required.

I have been using Microsoft Entra Verified ID for three years. I am an end user of the solution.

It is a stable solution. Stability-wise, I rate the solution a nine out of ten.

It is a highly scalable solution. Scalability-wise, I rate the solution a nine out of ten.

There are 150 users of the solution in my company.

The tool is used daily for our day-to-day operations.

I never had an experience with the solution's technical support. We never had any requirements to contact them.

I have used Active Directory for my company's in-house purposes. I started to use Microsoft Entra Verified ID due to COVID-19, which caused people to move around a lot in our company.

The product's initial setup phase is really easy.

The solution is deployed on the cloud.

The solution can be deployed in a few hours since we don't have many users.

The product was deployed with the help of our company's in-house team.

If one is cheap and ten is very expensive, I rate the product price as seven. The tool is not very expensive, but it is priced in a higher range.

The decentralized aspect of Microsoft Entra Verified ID enhances security measures. My company has full control and visibility of our users and their logins. If users make any wrong login attempts, the tool offers full visibility. If there are any malpractices, we can easily identify them with the tool.

The tool has improved our company's operational efficiency.

I have not encountered any issues while integrating or using Microsoft Entra Verified ID. Actually, we have a strong internal team. Once we plan out something, we never have an issue with that. There are challenges in moving or migrating from an existing older system to a new system, and it is because we are moving users, and getting hold of their new devices can be quite difficult. The issue is not related to Microsoft Entra Verified ID. It is a practical limitation of equipment availability.

Microsoft Entra Verified ID supports our company's initiatives in AI-driven security solutions.

I recommend the tool to others because it is a really good tool to have visibility on your users.

I rate the tool a nine out of ten.

We use the product as a single sign-on for our business applications. 

Microsoft Entra Verified ID is our primary way of authenticating into ServiceNow apps. It helps us to stay connected in the company. 

I like the Microsoft Authenticator app since it comes with two-factor authentication. 

I must do two-factor authentication when I sign in from a different location. It creates friction. It's not personalized for the end user. I would like to see specific insights. 

I have been using the product for four and a half years. 

Microsoft Entra Verified ID is stable. 

The product is scalable and works across different geographies. 

The tool's support is straightforward. It has good documentation. 

Neutral

Microsoft Entra Verified ID has saved time for IT admins. The product helps us save money from the cost of security breaches. It is a more cost-effective solution than others in the market. It comes in a Microsoft suite. You can manage permission and access the products without buying anything additional. I rate it a six out of ten.