Autopilot is a web-based SaaS (software as a service) application, and setup takes just a few minutes. Here’s how to do it:
Setting up the initial Autopilot account
Create an Autopilot account by following these steps:
- Open a private browsing session and log in to portal.office.com with your Global Admin account.
- In a new tab, go to your Autopilot URL.
- Accept the license terms.
- Enter your Global Admin credentials.
- If desired, click Add to set up more service accounts (shown below).
- Click Save.
Setting up additional service accounts
Although you can add multiple service accounts during the initial setup of Autopilot, if you ever need to set up service accounts later, follow these steps.
- In the left menu bar, expand Admin and click Settings.
- Locate the Accounts section and click the edit (pencil) button.
- Click Add.
- Use the fields to configure the account and then click Save to create the service account.
Installing an on-premises agent
The only element you’ll install is the on-premises agent. The on-premises agent allows you to pull in any users and organizational unit structures you have locally within Active Directory. It also provides the ability to update local objects.
Here are requirements for the on-premises agent:
- The Active Directory module for Windows PowerShell must be installed on the machine where you’ll install the on-premises agent. This can be done via PowerShell with Install-WindowsFeature -Name RSAT-AD-PowerShell
- It must have 443 access to the Autopilot URL for the tenant.
- It must be installed on a domain joined server.
- It must have a service account that has Domain Admin rights in Active Directory. This is used for proxied administration.
- The service account must have logon as service rights on the server.
- As far as required software, the agent must have a current .Net framework installed, as well as PowerShell 5.1 or above.
Install an on-premises agent by completing the steps below.
- Go to On-Premises Agent Admin > On-premises Agent and download latest version of installer. Then, run the installer file.
- Review and accept the terms and conditions of the license agreement.
- Enter a web server address. Click Verify, and then click Next.
Note: The Web Server Address should match the URL of the tenant you used when you set up the Autopilot web application.
- Click Request Token and follow the prompts to retrieve an authentication token.
- Verify the token and click Next.
- Verify the paths and click Next.
- Set up a service account that has logon as a service and administrative rights.
- Click Check access and then click Next.
- Click Install and then click Close.
Once you complete the installation process, you’ll see a job within Autopilot that’s collecting on-premises entities, as shown below.
When you set up your Autopilot account, users and groups were pulled into the application from a flat list in Office 365. Once the on-premises agent pulls in your organizational unit structure, users are automatically organized into the appropriate organizational unit if Azure Active Directory Sync is running.