Long description | When used together, Entra ID and Conditional Access provide a comprehensive solution for managing identities and access in an organization. Entra ID provides user authentication and authorization, while Conditional Access provides a layer of security by enforcing policies based on specific conditions. |
Active | 1 |
Ask an expert
Description #
Microsoft Entra ID, previously Azure Active Directory, is a suite of cloud-based identity and access management tools that enable organizations to manage their users' identities and access to resources. Entra ID is a component of this suite, providing a secure, cloud-based identity management solution that offers single sign-on (SSO), multi-factor authentication (MFA), and self-service password reset capabilities, and many others.
Conditional access is a feature of Microsoft Entra ID, that allows organizations to control access to resources based on conditions such as location, device type, user risk level or different criteria. Administrators can create policies that require certain conditions to be met before a user can access a specific resource. This feature helps organizations protect their data by ensuring that only authorized users with trusted devices can access sensitive information.
IT Partner responsibilities #
- Identify goals and objectives for Conditional Access Policy implementation.
- Identify use-cases.
- Configure Conditional Access policies and rules.
- License assignment.
- Verification and testing.
Client responsibilities  #
- Coordinate Client resources and staff schedules.
- Provide a dedicated point of contact responsible for working with IT Partner.
- Coordinate any outside vendor resources and schedules.
- Participate in the project discussion and provide all the information necessary to implement the solution.
- Configure all network equipment, such as load balancers, routers, firewalls, and switches.
- Review and approve engagement deliverables in a timely manner.
Prerequisites #
- Entra ID Plan 1 or 2 license.
Plan #
- Kickoff meeting.
- Determination of deployment goals, objectives, and challenges.
- Determination of use-case scenario requirements.
- Design and configuration of the Conditional Access policies.
- Test implementation.
- Testing and validation.
- Production implementation.
- Verification and fixing of issues, if any.
Success criteria #
- Conditional access policies are configured according to client requests, tested and working.