We are still deep involved in the use of Microsoft technology for databases and business intelligence, and in the last three years with Power Apps and Power Automate, all that means Azure services, because it is a very performant ecosystem to develop digital services or cloud solutions for our clients.We use Azure Blob storage intensely for our applications and to develop custom APIs and similar solutions. For connection, it is important for us to make a performant connection to integrate data sources from heterogeneous technologies. We now use Dataverse, which is much easier to use. It's more friendly because the no-code, low-code technology has become really performant at this moment. We can solve many problems without deep knowledge of coding, and it's very quick to solve problems with the no-code, low-code solution of Microsoft for us. We use Microsoft Entra ID Protection because this is the foundation of our application. We use it to authorize access into the application. We previously used Active Directory, not the Entra version, but now it's known as Entra. It solved our problems related to access, identity, and access in the application, user identity, and access. We do not tend to use something else because that solution satisfies our needs. At our level, we do not act at a very high level; we use a normal level of security. Our needs are not very sophisticated, which is why we are not users with very high expectations.
Senior Solution Architect DataCenter & Cloud at a tech services company with 11-50 employees
Real User
Top 10
Aug 26, 2025
I mainly use Microsoft Entra ID Protection for several integrations, including the hybrid AD architecture and the Azure Cloud. Users and on-premises AD synchronize to Azure or Microsoft Entra ID Protection. This includes Mailbox integration with Office 365. In Microsoft Entra ID Protection, we generally use the user's group and Enterprise applications. We also handle integration with other third-party applications for SSO or third-party SSO. The system handles log injection from Microsoft Entra ID Protection to the SIEM. Enterprise application is the main use case, apart from the users and groups.
Technical Consultant Security and Compliance at inSpark
Consultant
Top 5
Jun 11, 2025
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.
Security Operations Team Leader at Yalla Security Srl
Real User
Top 5
Feb 6, 2025
I enforce policies to manage the access of users, focusing on their activity, login positions, and security audit logs. It is always based on security and the enforcement of security policies.
AI Solution Architect at Bitscape Infotech Pvt. Ltd.
MSP
Top 5
Dec 16, 2024
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.
Learn what your peers think about Microsoft Entra ID Protection. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
We use the product for various purposes, such as implementing conditional access policies and access reviews. These features are available with specific licenses, such as the E3 and E5 licenses, including privileged identity management features.
Azure Active Directory Identity Protection enables synchronization between my on-premises user accounts and the cloud. By using Azure Active Directory, I can enforce restrictions and create policy rules. I can also identify the devices connected to Azure Directory and apply policies accordingly. The usage of this feature is extensive, with a large number of users utilizing its capabilities. I feel that it forms the core of Microsoft's security infrastructure, acting as a central portal for managing the security of Microsoft solutions.
Microsoft Entra ID Protection enhances security through features like conditional access and multifactor authentication, optimizing identity management for enterprises. This robust solution ensures efficient control over access policies, supporting seamless integration and operational efficiency.Microsoft Entra ID Protection provides advanced identity management, authentication, and authorization capabilities, supporting multifactor authentication and single sign-on to control digital...
We are still deep involved in the use of Microsoft technology for databases and business intelligence, and in the last three years with Power Apps and Power Automate, all that means Azure services, because it is a very performant ecosystem to develop digital services or cloud solutions for our clients.We use Azure Blob storage intensely for our applications and to develop custom APIs and similar solutions. For connection, it is important for us to make a performant connection to integrate data sources from heterogeneous technologies. We now use Dataverse, which is much easier to use. It's more friendly because the no-code, low-code technology has become really performant at this moment. We can solve many problems without deep knowledge of coding, and it's very quick to solve problems with the no-code, low-code solution of Microsoft for us. We use Microsoft Entra ID Protection because this is the foundation of our application. We use it to authorize access into the application. We previously used Active Directory, not the Entra version, but now it's known as Entra. It solved our problems related to access, identity, and access in the application, user identity, and access. We do not tend to use something else because that solution satisfies our needs. At our level, we do not act at a very high level; we use a normal level of security. Our needs are not very sophisticated, which is why we are not users with very high expectations.
I mainly use Microsoft Entra ID Protection for several integrations, including the hybrid AD architecture and the Azure Cloud. Users and on-premises AD synchronize to Azure or Microsoft Entra ID Protection. This includes Mailbox integration with Office 365. In Microsoft Entra ID Protection, we generally use the user's group and Enterprise applications. We also handle integration with other third-party applications for SSO or third-party SSO. The system handles log injection from Microsoft Entra ID Protection to the SIEM. Enterprise application is the main use case, apart from the users and groups.
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.
I enforce policies to manage the access of users, focusing on their activity, login positions, and security audit logs. It is always based on security and the enforcement of security policies.
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.
We have a lot of applications or workloads leveraging many services. For authentication and authorization, we use Entra Protection.
We use the product for various purposes, such as implementing conditional access policies and access reviews. These features are available with specific licenses, such as the E3 and E5 licenses, including privileged identity management features.
We use the solution for single sign-on.
Azure Active Directory Identity Protection enables synchronization between my on-premises user accounts and the cloud. By using Azure Active Directory, I can enforce restrictions and create policy rules. I can also identify the devices connected to Azure Directory and apply policies accordingly. The usage of this feature is extensive, with a large number of users utilizing its capabilities. I feel that it forms the core of Microsoft's security infrastructure, acting as a central portal for managing the security of Microsoft solutions.
The solution helps us with authentication.
I use the solution to manage users, groups, access, and license.
Our company uses the solution to provide identity protection services to customers. We currently have fifteen developers on our team.