Our main use case for Microsoft Entra ID is authentication. One of the pilots that we want to try is to allow external authentication into our systems or platform.
The features of Microsoft Entra ID that I like the most are security, ease of management and maintenance, and the ability to integrate with other platforms.
We are realizing those benefits with Microsoft Entra ID. For instance, the idea is to partner with one of our main stakeholders from the company, one of our sister organizations. We are trying to connect both Microsoft Entra ID platforms and include third-party authentication as well. For us, that is going to be easy, and that is what we are targeting.
Microsoft Entra ID's integration capabilities influence our zero trust model by providing reliability to our stakeholders first, and second, all the governance that is behind it.
Our organization's approach to defending against token theft and nation-state attacks has not changed since implementing Microsoft Entra ID, not that I'm aware of.
Of the features token replay detection, attacker-in-the-middle detection, and verified threat actor IP, I think the last one has an impact on defending against threats.
I think that, in our case, it is related to the dedicated security team that we have.
I have been using Microsoft Entra ID for the last two and a half years.
I would assess the stability and reliability of Microsoft Entra ID as a nine on a scale of one to 10.
I have not experienced any downtime, crashes, or performance issues with Microsoft Entra ID.
I think Microsoft Entra ID is aligned with the growing needs of our organization. It is really aligned, and we can grow together.
We have not expanded our usage of Microsoft Entra ID.
On a scale of one to 10, I would rate customer service and technical support for Microsoft Entra ID a seven or an eight. Sometimes it is hard to get into the proper support queue. Once I am there, the response is amazing, but the hard part is reaching the right channel at the right time.
Before adopting Microsoft Entra ID, we tried to implement Azure B2C at the beginning, but then we realized that we were going to move away from it. Microsoft is about to move away from it, so we decided to go for the other option.
I haven't seen ROI with Microsoft Entra ID. Maybe my superiors have.
Before choosing Microsoft Entra ID, we also considered Auth0 from Okta, which we are trying to implement as well.
During the evaluation process, what stood out to me about Microsoft Entra ID was its integration capabilities, one of them, and its single sign-on capabilities as well. Another factor was the possibility to partner with one of our sister companies to integrate both models.
On a scale of one to 10, I would give Microsoft Entra ID a nine overall.
My advice for other organizations considering Microsoft Entra ID is to evaluate and consider everything related to integrations and everything related to a proper business model, so that they can leverage the solution successfully.