What is our primary use case?
I have used Microsoft Entra ID on and off in different roles for different projects. My use has been predominantly about creating an app in Azure to get a client ID and client secret. I use that client ID across platforms for Azure, SharePoint, DocuSign, and building custom connectors.
What is most valuable?
The feature of Microsoft Entra ID I like the most is that once you create it, the password and everything can be refreshed. It is a secure way to use this ID instead of hard-coded credentials. It is also the go-to for creating pretty much any app in and around the Microsoft ecosystem.
The benefits my company and I have realized from using Microsoft Entra ID are more around security, adhering to best practices, and making sure that we build apps the right way so they can then be used in SharePoint and across other platforms.
The impact Microsoft Entra ID has had on secure access to apps or resources in our environment is that it makes access secure, so we do not have to worry about additional work or extra processes. Many times in infosec reviews, using Microsoft Entra ID with a client ID and a secret is a clear go-through, as opposed to any other authentication mechanism.
Since implementing Microsoft Entra ID, I have not seen any changes in the frequency and nature of identity-related security incidents in my company. I have always used Microsoft Entra ID, so I have not had any issues.
In general, having Microsoft Authenticator gives you MFA. That is one additional layer of security, and nobody can impersonate or steal your credentials.
What needs improvement?
I would say Microsoft Entra ID could be improved by making it easier to find application IDs. It is just so huge, and it used to be Azure Active Directory earlier. Many times, I have to find the client ID, find which permissions it has, grant admin consent, and make sure whether it is delegated access or application access. I think a lot of that could be simplified. There is still a lot of jargon that has been carried over for decades now. I have seen it for six years, and not much has changed around the simplicity of use. It is powerful, but I feel the learning curve is a little high, especially for troubleshooting. If you cannot find something, it becomes a maze chase of where something is.
For how long have I used the solution?
I have been using Microsoft Entra ID for a little over five or six years now.
What do I think about the stability of the solution?
I do not see any stability issues with Microsoft Entra ID, including crashes or downtimes. My challenges have been more around finding which ID has which permissions and how to change them. Sometimes it takes a little time for those permissions to reflect, but there is nothing in terms of stability.
What do I think about the scalability of the solution?
I have used Microsoft Entra ID mainly for proofs of concept or apps, but I believe it is pretty scalable in terms of maintaining tens of thousands of users and having multiple applications. I do not see an issue.
How are customer service and support?
If I evaluate Microsoft support, very honestly, I would say three on five. I have used it in the past, and it was not the best experience.
I would give them seven and a half on a scale of one to 10. The response times could be better, and it goes back to my earlier point about simplicity around what you want to do, how to do it, or even the UI. Many times, you are logging in somewhere else or seeing something else. The permissions add a little extra learning curve, and the same goes for Microsoft support. You need to start from the beginning and tell them everything, and there are a lot of handoffs. Nothing is super urgent, so it takes two days, and it cannot be resolved right at that minute. It is more of self-service if you want a quick resolution.
Which solution did I use previously and why did I switch?
Before Microsoft Entra ID, I did not use another solution to address similar needs. For POCs, I used hard-coded credentials, but anything that is production-grade or needs to be secure is Microsoft Entra ID.
Which other solutions did I evaluate?
The main difference between similar solutions and Microsoft Entra ID, both pros and cons, is that because it is more enterprise-grade, it is best to implement and get it right the first time. That has been my choice.
What other advice do I have?
I would tell anyone researching Microsoft Entra ID that I am not sure whether we use a zero-trust model in my company. I guess there should be zero-trust for anything around security.
I am not rating Microsoft Entra ID as seven and five based on that. As a product, I would give it an eight.
As for what would make Microsoft Entra ID a 10 for me, my use cases have been different, and I have not used it very extensively.