General info

We will plan, design, and implement a Windows Autopilot, the future of device deployment designed to allow you to set up, pre-configure, and repurpose the devices for your environment, with little or no infrastructure in place. You will be able to deploy Windows automatically, without an image, to PCs anywhere in the world at any time.

Useful links

Related files

Related products

Long description We will plan, design, and implement a Windows Autopilot, the future of device deployment designed to allow you to set up, pre-configure, and repurpose the devices for your environment, with little or no infrastructure in place. You will be able to deploy Windows automatically, without an image, to PCs anywhere in the world at any time.
Active 1

Windows Autopilot is a cloud-based deployment technology available in Windows 10. It allows you to deploy and configure devices over the internet with no interaction as an administrator or IT specialist. It is built on existing modern management technologies like Azure Active Directory and Mobile Device Management to manage and configure devices by automatically enrolling in these solutions at their first bootup, right out of the box.

Deployment of devices with Windows Autopilot enables a number of capabilities for the deployment process and configuration of the devices deployed. These features transform the way devices are deployed by enabling customization of the first boot experience and providing automated configuration of deployed devices. Windows Autopilot also enables benefits from modern management solutions, such as:

  • presenting organization branding to users at the first prompt to log in via organization branding configured in AAD
  • automatic enrollment in Microsoft Intune or an alternate MDM solution with the configuration of automatic enrollment in AAD
  • Device configuration, policies, and apps defined by Intune or an alternate MDM solution begin applying to a device immediately upon the first logon, setting up the device for the user to begin working with and using the device

Our objective is that devices are configured and ready to work for your users without requiring reconfiguration of the devices, access to on-network resources, or even physical presence in your organization's buildings or offices.

IT Partner responsibilities #

[Please note: We do not require administrative access to the customer's AAD or MDM environment to register devices.]{.mark}

  1. Kickoff meeting
  2. Create a project plan and schedule
  3. Communicate with hardware provider to obtain the necessary information
  4. One-time purchase or DaaS model
  5. Collect the hardware IDs from the existing devices
  6. Configure Autopilot profiles and profile settings
  7. User assignment to the specific Autopilot-enabled devices
  8. Escalate issues to Microsoft support, if needed
  9. Offer advice on implementation issues, if any
  10. Project closure and acceptance

Client responsibilities #

  1. Coordinate Client resources and staff schedules
  2. Provide a dedicated point of contact responsible for working with IT Partner
  3. Coordinate any outside vendor resources and schedules
  4. Configure all network equipment, if necessary, such as load balancers, routers, firewalls, and switches
  5. Review and approve engagement deliverables in a timely manner
  6. Request and approve all change management tickets (if applicable) in the client environment
  7. Provide access to physical and virtual servers as needed; provide necessary remote and/or physical access to the facility and systems needed in order to complete the work
  8. Unbox new devices, plug them in and turn them on, and connect them to a wireless or wired network with internet access
  9. Provide information about PC setup requirements and software requirements
  10. Resolution of basic tickets, which may be resolved by following end user adoption instructions provided by Microsoft
  11. End user support

Prerequisites #

  1. One of the following subscriptions provisioned into your Entra ID tenant: a. Enterprise Management and Security (EM+S) (E3 or E5) -- includes Azure Active Directory Premium and Microsoft Intune or b. Microsoft 365 Enterprise (E3 or E5) -- includes Enterprise Management and Security, Azure Active Directory Premium, Microsoft Intune, and Microsoft 365 Apps for enterprise or c. Microsoft 365 Business -- (excluding Office 365 Business, which can't be configured by Windows Autopilot -- Microsoft 365 Apps for enterprise is required for that) and a select set of Azure Active Directory Premium and Microsoft Intune features

  2. Sufficient rights to the Azure portal

  3. Intune service (or another MDM solution) to manage devices

  4. Sufficient rights for the Windows Store for Business

  5. The devices used for Autopilot should be supported by Microsoft for Windows Autopilot

  6. Windows 10 version 1809 or higher is required

  7. The following editions are supported:

    • Windows 10 Pro
    • Windows 10 Pro Education
    • Windows 10 Pro for Workstations
    • Windows 10 Enterprise
    • Windows 10 Education
    • Windows 10 Enterprise 2019 LTSC
  8. Network configuration must match the requirements listed on the Microsoft Website -- https://learn.microsoft.com/en-us/mem/autopilot/software-requirements

Additional cost items not provided by this project #

  • Microsoft Intune implementation -- please check this service: Microsoft Intune -- Initial Setup
  • Migration of local documents and data from current devices (migration to OneDrive or SharePoint may be included in addition to this project, if desired)
  • Windows 10 upgrade is outside of the scope and could be performed as a separate project
  • Support for existing Windows 7 and Windows 8 devices
  • Installation of firmware on desktops or network hardware devices
  • End user teams training
  • The IT Partner team will perform all the work remotely. An on-site presence may be arranged by request and will be invoiced separately at the rate of $1,900 per business day
  • Hardware, software, and Office 365/Azure subscription costs that may be required to complete this engagement
  • Any items not specifically mentioned in the scope of work

Upon completion of the project, we will provide a project closeout report. This document will indicate the final project status, including evidence of matching acceptance criteria, outstanding issues (if any), and the final budget. If you require more extensive documentation, it can be provided for an additional fee.

Plan #

The plan may vary depending on your needs.

  1. Kickoff meeting
  2. Project schedule review and revisions
  3. Planning and development
  4. Interaction with hardware provider
  5. Collect existing device information
  6. Create and manage Autopilot profiles
  7. Test device deployment and lifecycle
  8. Production deployment monitoring
  9. Possible problem-solving
  10. Provide the use case documentation

Success criteria #

  1. Implementation plan is developed and approved
  2. Client's Microsoft 365 tenant and Azure services are configured to support Windows Autopilot functionality
  3. Windows Autopilot can be used to deploy, repurpose, break-fix, and retire all the supported devices configured for the Autopilot service
  4. One month of post-implementation consulting and support period has started


Manufacturer IT Partner
Licensing SRV
Duration 21 days
Add to cart
- +
$ 1,300.00 per project
To top