Microsoft Entra deployment plans
Use the following guidance to help deploy Microsoft Entra ID. Learn about business value, planning considerations, and operational procedures. You can use a browser Print to PDF function to create offline documentation.
When beginning your deployment plans, include your key stakeholders. Identify and document stakeholders, roles, responsibilities. Titles and roles can differ from one organization to another, however the ownership areas are similar.
|Sponsor||An enterprise senior leader with authority to approve and/or assign budget and resources. The sponsor is the connection between managers and the executive team.|
|End user||The people for whom the service is implemented. Users can participate in a pilot program.|
|IT Support Manager||Provides input on the supportability of proposed changes|
|Identity architect or Azure Global Administrator||Defines how the change aligns with identity management infrastructure|
|Application business owner||Owns the affected application(s), which might include access management. Provides input on the user experience.|
|Security owner||Confirms the change plan meets security requirements|
|Compliance manager||Ensures compliance with corporate, industry, or governmental requirements|
RACI is an acronym derived from four key responsibilities:
Use these terms to clarify and define roles and responsibilities in your project, and for other cross-functional or departmental projects and processes.
Use the following list to plan for authentication deployment.
- Microsoft Entra multifactor authentication - Using admin-approved authentication methods, Microsoft Entra multifactor authentication helps safeguard access to your data and applications while meeting the demand for a simple sign-in process:
- Conditional Access - Implement automated access-control decisions for users to access cloud apps, based on conditions:
- Microsoft Entra self-service password reset (SSPR) - Help users reset a password without administrator intervention:
- Passwordless authentication - Implement passwordless authentication using the Microsoft Authenticator app or FIDO2 Security keys:
Applications and devices
Use the following list to help deploy applications and devices.
- Single sign-on (SSO) - Enable user access to apps and resources while signing in once, without being required to enter credentials again:
- My Apps portal - A web-based portal to discover and access applications. Enable user productivity with self-service, for instance requesting access to groups, or managing access to resources on behalf of others.
- Devices - Evaluate device integration methods with Microsoft Entra ID, choose the implementation plan, and more.
The following list describes features and services for productivity gains in hybrid scenarios.
- Active Directory Federation Services (AD FS) - Migrate user authentication from federation to cloud with pass-through authentication or password hash sync:
- Microsoft Entra application proxy - Enable employees to be productive at any place or time, and from a device. Learn about software as a service (SaaS) apps in the cloud and corporate apps on-premises. Microsoft Entra application proxy enables access without virtual private networks (VPNs) or demilitarized zones (DMZs):
- Seamless single sign-on (Seamless SSO) - Use Seamless SSO for user sign-in, on corporate devices connected to a corporate network. Users don't need to enter passwords to sign in to Microsoft Entra ID, and usually don't need to enter usernames. Authorized users access cloud-based apps without extra on-premises components:
- User identities - Learn about automation to create, maintain, and remove user identities in cloud apps, such as Dropbox, Salesforce, ServiceNow, and more.
- Identity governance - Create identity governance and enhance business processes that rely on identity data. With HR products, such as Workday or Successfactors, manage employee and contingent-staff identity lifecycle with rules. These rules map Joiner-Mover-Leaver processes, such as New Hire, Terminate, Transfer, to IT actions such as Create, Enable, Disable.
- Microsoft Entra B2B collaboration - Improve external-user collaboration with secure access to applications:
Identity Governance and reporting
Use the following list to learn about identity governance and reporting. Items in the list refer to Microsoft Entra.
- Privileged identity management (PIM) - Manage privileged administrative roles across Microsoft Entra ID, Azure resources, and other Microsoft Online Services. Use it for just-in-time access, request approval workflows, and fully integrated access reviews to help prevent malicious activities:
- Reporting and monitoring - Your Microsoft Entra reporting and monitoring solution design has dependencies and constraints: legal, security, operations, environment, and processes.
- Access reviews - Understand and manage access to resources:
- Identity governance - Meet your compliance and risk management objectives for access to critical applications. Learn how to enforce accurate access.
Best practices for a pilot
Use pilots to test with a small group, before making a change for larger groups, or everyone. Ensure each use case in your organization is tested.
Pilot: Phase 1
In your first phase, target IT, usability, and other users who can test and provide feedback. Use this feedback to gain insights on potential issues for support staff, and to develop communications and instructions you send to all users.
Pilot: Phase 2
Widen the pilot to larger groups of users by using dynamic membership, or by manually adding users to the targeted group(s).