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.

We as a company are working on security compliance using Microsoft's tools, including Purview, Defender XDR, Entra, and Azure AD. Our wider company perspective also includes Intune, MBM, Data Lake, and the Azure infrastructure itself. It's a comprehensive list of services we offer.

I did some implementations and workshops for Microsoft Entra ID Protection.

Microsoft Entra ID Protection is used for identity, authentication, authorization, and other connection solutions, especially within hybrid environments. It provides a comprehensive setup for cloud-only or mainly cloud environments, although hybrid setups can still encounter challenges.

Microsoft is doing a good job with their adaptive machine learning algorithms for anomaly detection. These algorithms are effective at identifying unfamiliar sign-ins or malicious IP activities, which help protect our customers. Although results can take some time, being proactive with these tools yields beneficial results.

Conditional access is a powerful solution for Microsoft Entra ID Protection. Our company has developed a framework with conditional access policies which we update when Microsoft releases new information. This framework assists in beginning with conditional access and expanding as you mature in adopting it. We guide customers in their journey toward adopting and understanding the product.

The push for passwordless operation is successful with Microsoft Entra ID Protection. I haven't used a password for about a year, signifying the safety and effectiveness of this feature for protecting online identities.

Microsoft is connecting capabilities within Microsoft Entra ID Protection in conjunction with Azure, Purview, and security solutions. They have improved clarity in their approach by positioning Entra ID between these pillars, enhancing integration.

Microsoft's support is commendable. Their response time is quick, and they handle inquiries effectively, ensuring ongoing support processes.

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.