On-premises Active Directory to Microsoft Entra ID Transition — Cloud Identity Migration
IT Partner’s On-premises Active Directory to Microsoft Entra ID Transition service, SKU ITPWW360MIGOT, helps organizations move identity management from on-premises Active Directory to Microsoft Entra ID, formerly Azure AD. Microsoft Entra ID enables cloud-based identity capabilities described in the source page, including secure single sign-on, cloud credential management, and user reporting and control. The service is priced at $4,550, has a duration of 3 weeks, and is managed by Roman Sotnik.
What this engagement is
This service supports the transition from on-premises Active Directory to Microsoft Entra ID. The goal is to modernize identity management by moving it to the cloud. The source page describes Microsoft Entra ID benefits such as secure single sign-on for various devices and applications, managing and storing credentials in the cloud, and user reporting and controlling without using servers in the office. IT Partner provides migration support from planning and execution through troubleshooting and documentation.
Success criteria
What you receive
How the work unfolds
Create a customized migration plan to fit the organization’s needs.
Support the transition from on-premises Active Directory to Microsoft Entra ID.
Provide troubleshooting support as part of the transition.
Provide documentation as part of the transition support.
Confirm project scope, schedule, stakeholders, communication channels, administrative access, and any tenant or licensing prerequisites before technical work begins.
Review the existing on-premises Active Directory structure, users, groups, domains, device join state, identity dependencies, Microsoft Entra ID tenant configuration, and current Microsoft 365 or Azure services that rely on identity.
Identify blockers such as unsupported devices, stale user objects, duplicate UPNs, invalid domains, missing licenses, DNS issues, legacy authentication dependencies, or applications that may require additional configuration.
Define the agreed identity model, sign-in method, naming and UPN approach, administrator roles, device transition approach, and validation process for Microsoft Entra ID.
Transition and validate a limited pilot group, confirm sign-in, access to key Microsoft cloud services, device behavior, and user-impact items before wider rollout.
Execute the approved transition plan for in-scope users and devices, coordinate customer communications, and monitor sign-in and identity-related issues during the transition window.
Validate Microsoft Entra ID sign-in, administrative access, key user scenarios, and any agreed reporting or control checkpoints. Document exceptions and remaining actions.
Provide documentation, review the completed configuration with the customer, confirm known limitations or optional follow-on work, and close the engagement.
Prerequisites
Who does what
IT Partner
- Ensure a smooth and secure migration of your identity management system to the cloud.
- Provide customized migration plans to fit your organization’s needs.
- Support the transition from planning and execution to troubleshooting and documentation.
- Ensure a seamless transition with minimal impact on daily operations.
- Lead project kickoff, confirm scope, and identify technical dependencies and risks.
- Review the existing Active Directory and Microsoft Entra ID environment at a practical level required for the transition.
- Prepare the transition plan, validation checklist, and recommended cutover sequence.
- Configure in-scope Microsoft Entra ID identity settings required for the agreed transition approach.
- Support pilot and production transition activities for in-scope users and devices.
- Troubleshoot identity-related issues encountered during the engagement within the agreed scope.
- Provide post-transition documentation and handoff guidance.
Your team
- Provide required administrative access, tenant access, domain access, and environment information in a timely manner.
- Confirm licensing availability and purchase any required Microsoft licenses not already in place.
- Identify in-scope users, devices, groups, administrators, applications, and business-critical authentication scenarios.
- Provide knowledgeable technical and business contacts for discovery, approvals, testing, and user communications.
- Approve the migration plan, pilot group, transition schedule, and any change windows.
- Communicate expected sign-in, profile, and device changes to users.
- Ensure in-scope devices are available, powered on, connected, and accessible when transition activities are scheduled.
- Participate in pilot and post-transition validation, including confirming that users can access key services.
- Maintain backups and recovery readiness for customer-managed systems, user data, and on-premises infrastructure.
- Own remediation of issues outside the agreed scope, such as application modernization, endpoint repair, cabling, network outages, or unsupported operating systems.
What's not included
Limitations & technical notes
Frequently asked questions
What is IT Partner’s On-premises Active Directory to Microsoft Entra ID Transition service?
IT Partner’s On-premises Active Directory to Microsoft Entra ID Transition service helps organizations move identity management from on-premises Active Directory to Microsoft Entra ID, formerly Azure AD. The service is designed to modernize identity management by moving it to the cloud, including support for planning, execution, troubleshooting, and documentation.
What is included in the On-premises Active Directory to Microsoft Entra ID Transition service?
The service includes a customized migration plan, execution support for the transition from on-premises Active Directory to Microsoft Entra ID, troubleshooting support during the transition, and documentation. IT Partner’s stated responsibility is to help make the migration smooth and secure with minimal impact on daily operations. A standard delivery approach would also include discovery, readiness review, pilot validation, production transition support, and handoff documentation for the agreed scope.
What is not included in this Microsoft Entra ID transition service?
Data transfer from existing local user profiles, such as Documents, Desktop, and Favorites, to OneDrive for Business or SharePoint Online is not included in the base service. IT Partner identifies that profile data transfer as an optional add-on, so buyers should confirm add-on scope and pricing if they need user files migrated. Other typical exclusions include application modernization, advanced security configuration, Intune deployment, file/mail migration, endpoint repair, and ongoing managed support, 24/7 support, continuous monitoring, and ongoing maintenance unless purchased as optional extra-cost add-ons delivered through IT Partner's NOC, third-party support partnerships, and a Microsoft Premier Support agreement.
How much does the On-premises Active Directory to Microsoft Entra ID Transition service cost?
The listed price for IT Partner’s On-premises Active Directory to Microsoft Entra ID Transition service is $4,550. Buyers should confirm whether any optional add-ons, environment-specific needs, or out-of-scope work would affect the final quote.
How long does the transition from on-premises Active Directory to Microsoft Entra ID take?
The stated duration for this service is 3 weeks. The engagement is structured around planning, execution, troubleshooting, and documentation, but exact scheduling should be confirmed with IT Partner based on the customer environment and readiness.
What happens during the Microsoft Entra ID transition engagement?
IT Partner begins by creating a customized migration plan for the organization’s needs, then supports execution of the transition from on-premises Active Directory to Microsoft Entra ID. The engagement also includes troubleshooting during the transition and documentation as part of the project closeout. A standard delivery sequence would include kickoff, environment discovery, readiness review, target-state design, pilot transition, production transition, post-transition validation, and handoff.
Will the migration affect daily business operations?
The service is intended to complete the transition with minimal impact on daily operations. However, the service description does not guarantee zero downtime or specify exact interruption windows, so any timing, user impact, and cutover expectations should be confirmed during planning.
What are the success criteria for this service?
The stated success criteria are that the identity management system is migrated to the cloud smoothly and securely, and that the transition is completed with minimal impact on daily operations. Practical acceptance criteria should include successful Microsoft Entra ID sign-in for the agreed pilot and production users, completion of in-scope identity configuration, validation of key user scenarios, delivery of documentation, and documentation of any exceptions or follow-on work.
Does this service configure Microsoft Entra ID single sign-on?
The source content describes Microsoft Entra ID as enabling secure single sign-on for devices and applications. However, the service scope specifically states migration planning, execution support, troubleshooting, and documentation, so buyers should confirm whether configuring or validating specific single sign-on scenarios is included for their environment.
Does this service move credentials from local servers to the cloud?
The service supports moving identity management from on-premises Active Directory to Microsoft Entra ID, and Microsoft Entra ID is described as supporting cloud credential management and storage. The exact credential migration or synchronization approach is not specified in the service content, so IT Partner should confirm the technical method during planning.
Will users get new Windows profiles after connecting to Microsoft Entra ID?
Yes, the service notes that when users connect to Entra ID, a new user profile is created on their devices. Because of that, existing profile content such as Desktop, Documents, and Favorites may need separate handling, and transferring that data to OneDrive for Business or SharePoint Online is an optional add-on.
Does the service migrate user files, Desktop, Documents, or Favorites?
No, migration of existing profile data such as Documents, Desktop, and Favorites is not included in the base service. IT Partner states that transferring this data to OneDrive for Business or SharePoint Online is available as an optional add-on.
What prerequisites are required before the transition starts?
Standard prerequisites include an active Microsoft Entra ID tenant, appropriate Microsoft licenses, required administrative access, DNS/domain access where needed, a healthy enough on-premises Active Directory environment, an agreed inventory of in-scope users and devices, a pilot group, available test users, and customer approval of the transition plan and change windows.
What is IT Partner responsible for during the engagement?
IT Partner is responsible for providing a customized migration plan, supporting the transition from planning through execution, delivering troubleshooting support, and providing documentation. IT Partner also states that it will work to ensure a smooth and secure migration with minimal impact on daily operations. IT Partner would typically also lead discovery, readiness review, transition planning, pilot support, production transition support, validation, and administrator handoff for the agreed scope.
What is the client responsible for during the engagement?
The client is typically responsible for providing administrative access, licensing, accurate environment information, pilot users, approvals, user communications, available devices, participation in testing, and timely decisions. The client also owns customer-managed backups, business application owners, and remediation of items outside the agreed project scope.
Who manages this Microsoft Entra ID transition service?
The service is managed by Roman Sotnik. The listed service SKU is ITPWW360MIGOT, which can help buyers identify the correct IT Partner offering when requesting details or a quote.
What documentation is provided after the transition?
Documentation is included as part of the transition support. Typical documentation would include configuration notes, transition summary, validation results, known issues or exceptions, and recommended next steps. The exact format and contents should be confirmed during project planning.
What happens after the Microsoft Entra ID transition is completed?
After completion, the organization should have its identity management transitioned to Microsoft Entra ID according to the project scope, with documentation provided by IT Partner. Any additional configuration, profile data migration, broader Microsoft 365 adoption work, or ongoing support such as 24/7 support, continuous monitoring, and ongoing maintenance should be confirmed separately because it is not part of the base service. 24/7 support, continuous monitoring, and ongoing maintenance are available as optional extra-cost add-ons delivered through IT Partner's NOC, third-party support partnerships, and a Microsoft Premier Support agreement.