Microsoft Entra ID Protection Reviews

The primary use case for Entra ID Protection is to have control and proper naming conventions of all assets within my estate. It helps me control access, assign resource groups, better secure production environments, and be compliant.

The valuable features of Entra ID Protection include providing me visibility of my entire estate, managing access, and having a level of control. I use it to control and manage my assets, assign resources, and ensure compliance in my environments.

Just for authentication purposes. To authenticate other services on behalf of Microsoft.

We use Microsoft. Everyone uses Windows, and we collaborate on Teams. So sometimes it's necessary to use Microsoft. The only Microsoft features I use are logging in via Microsoft authentication or Microsoft Active Directory. 

We have a ton of services available, like Jenkins or Outline for documentation. It becomes difficult to manage users across all these services. If new developers are onboarded, someone has to add them to each service individually. So we've aligned with Microsoft Active Directory. We've integrated our other software with Microsoft, and we log into other software using Microsoft. That's very helpful. If someone leaves the company, we just block their Microsoft account. If someone joins, we just create their Microsoft account.

I am a Security Operations Center (SOC) analyst and manage Microsoft Entra ID for four clients. I act as an administrator for accounts, including Microsoft XDR, within my company.

For me, automatization is most valuable. Microsoft Entra ID can detect if a user is at risk and then execute actions based on the risk level. 

Additionally, it has a good scalability potential, allowing for the management of both small and large user bases efficiently.

The most valuable feature of the solution is the granular control of identity and access in terms of giving access based on additional context and authentication context. For example, the tool has conditional access policies, like identity protection, which is time-based access given to the administrators so that they can perform any administrative control or configuration that is time-bound, and it automatically expires according to that flow. There is also identity governance, so the tool has quite interesting identity-related features that are quite robust in protecting many enterprise client decisions.

So far, the tool has been good. I have dealt with our company's clients' technical and functional requirements. So far, the tool has always serviced all our needs, so I don't see any shortcomings in it.

The challenge in the tool was related to hybrid connectivity, like with Azure AD Connect, which I now think is Microsoft Entra ID's predecessor. Azure AD Connect was replaced by Microsoft Entra ID. There were many issues with the tool's sync process. During the configuration of networks, the process was quite resource-intensive. I think Microsoft understood the concerns of the users associated with the tool, and that is why it released a new kit into the block, like Microsoft Entra Cloud Sync, to replace its shortcomings. Microsoft Entra Cloud Sync is for enterprises that would love to have hybrid configurations.

Microsoft Entra ID Protection needs to offer better hybrid connectivity to users. There are two products under Microsoft Entra ID, which are like brothers or cousins, and I feel that matching them up should not be an uphill task for us, like when we have a scenario where we try to integrate with a tool from a different vendor through APIs and so many other configurations that need to be done. The tool can just unify and make the process as quick as possible with a few clicks to deal with the configuration.

I want the tool's licensing model to be made easier.

I primarily use Microsoft Entra ID Protection to manage identities for applications, including single sign-on capabilities for third-party and in-house applications. I leverage its features for conditional access and identity management.

I find the most valuable feature to be conditional access. It allows for comprehensive security controls, network security, and application label security. It enables me to set policies for signing security user sign-in risks and specific application access. 

Additionally, having a single sign-on feature with Entra ID ensures seamless access to various applications, even those with significant security constraints. Microsoft offers extensive use cases, including app security and IP restrictions, enhancing our overall enforcement capabilities.

I have been using Microsoft Entra ID Protection primarily for identity and privileged access management. It provides multifactor authentication and accessor capabilities, managing specific conditional access for applications.

The tool offers multifactor authentication, which provides an additional layer of security for authentication.

We have a lot of applications or workloads leveraging many services. For authentication and authorization, we use Entra Protection.

Multifactor authentication provides an additional layer of security. We also leverage federated identity capability, allowing us to authenticate through external ID providers.

We use the solution for single sign-on.

As an end-user, I find the experience to be quite seamless. My main advantage is that I only need to manage one login and one two-factor authentication method to access all the necessary tools. I don't have to set up separate logins and authentication for each application.

As a user, the tool has improved my operational efficiency. Using it is a big advantage because the login is very stable, and I only need one login method. Normally, when I need to log in to multiple applications, I would have to manage separate passwords for each one, potentially changing them all every 30 days.

I only have to manage a single password and login method, which is much easier and faster for me. I don't have to set and update passwords across all my different applications repeatedly. For the company, it's also a big advantage that they only have to manage the login rather than across multiple applications.