What is our primary use case?
My main use cases for Microsoft Entra ID are security, authorization, and authentication. We use everything that Microsoft Entra ID has to offer.
We haven't run into anything with device-bound passkeys in Microsoft Authenticator, but we use MFA with Microsoft Authenticator.
What is most valuable?
Our organization runs off of Microsoft Entra ID, so authentication and authorization are all in there, and those are crucial. Being able to utilize it with enterprise apps so that we can do SSO makes life so much easier.
Implementing Microsoft Entra ID has had a big impact on secure access to apps and resources in our environment. We do everything through Microsoft Entra ID. For all of the solutions or apps that we purchase from outside, we use SSO, so all the authorization stays in one place.
We have groups that give dynamic access to whatever apps a person in a certain field requires, whether it is accounting, ops, or another department. That really helps and makes things easier.
Microsoft Entra ID's integration capabilities influence our Zero Trust model. SSO is a huge part of that, and it really helps with the Zero Trust model.
We have something set up where if somebody accesses their computer outside of the US, meaning the geographical US area, we get notified or receive an alert about it. We have been able to set up location-based policies and similar controls through Microsoft Entra ID, and that has been really nice.
What needs improvement?
Microsoft Entra ID does what we need it to do right now. I think some things within Microsoft Entra ID could be made a little easier, such as mail-enabled security groups, which take a lot of effort.
Dynamic groups are also a huge thing that we use. We create groups based on job titles, and it would be really helpful if there were an easier way to manage those dynamic group memberships. Right now, it requires a bunch of code and is messy.
For how long have I used the solution?
I have been using Microsoft Entra ID for nine years. It used to be called Active Directory and is now called Microsoft Entra ID.
What do I think about the stability of the solution?
I assess the stability and reliability of Microsoft Entra ID as great. It has been great.
How are customer service and support?
On a scale of 1 through 10, I would rate customer service and technical support for Microsoft Entra ID as subpar, somewhere around 5 or 6. It is Microsoft support. I am not really satisfied because we try to resolve issues before we reach out to them, and the only reason we reach out is that we have gotten to a point where we can't do it anymore. They still ask us the same bunch of questions.
It is similar to calling a helpdesk and being asked, "Have you restarted your computer?" and answering, "Yes, that's why I'm calling you. It's not working."
How was the initial setup?
I wasn't involved in the deployment of Microsoft Entra ID, so I can't speak to it directly, but I have heard that there were no challenges.
What was our ROI?
I have not seen any ROI with Microsoft Entra ID, because there is no data point to compare it against. We have always been a Microsoft shop.
What other advice do I have?
Our approach to token theft and nation-state attacks has not changed since implementing Microsoft Entra ID, because those threats are not applicable to us.
On a scale of 1 through 10, I would rate Microsoft Entra ID an 8 overall. Ease of use is there, and it has been point and click so far.
My advice to other organizations considering Microsoft Entra ID is to do it. It makes life easier. If you're a Microsoft shop, that's what you have to do.