To automatically enroll, some settings need to be made on Azure. These settings are as follows:
After you finish the integration on the Swif side, https://help.swif.ai/en/articles/8314271-microsoft-autopilot-automated-enrollment-ade, your application will be created.
Note, for Autopilot to work, the device user will log in via the Entra ID work account you assign to them. It requires an Azure (Entra ID) license to use MDM mobility (You don't need an Intune license.) The minimum license required to enable MDM mobility is the Microsoft Entra ID P1. You can start a free trial of Entra ID P1 at https://portal.azure.com/.
Reference document: Enable MDM automatic enrollment for Windows | Microsoft Learn
Configuring the Application
To configure the application, click on the ‘Swif’ application. On this screen, enter the following information:
MDM user scope: It specifies which users this application will be valid for. If it is valid for all users, use the 'All' option. If it is to be done only for certain users, use the 'Some' option and select the users.
MDM terms of use URL: https://enterpriseenrollment.swifteam.com/ManagementServer/tos
MDM discovery URL: https://enterpriseenrollment.swifteam.com/EnrollmentServer/Discovery.svc
Click 'Save' and you are done. Now, you are ready to do the real testing on a new or wiped Windows device.
Device Enrollment
Wipe the device to see the changes made. Afterward, following the selections for Language, Keyboard, and Network, the Device name screen will appear. Enter a device name here.
Then, a screen appears asking how we want to continue with the setup. Click on the "Set up work and school" option.
On the incoming screen, log in with the user credentials.
On the next screen, accept the Swift Terms.
After these steps, when the device is turned on, the enrollment will be completed.
Offboarding
When a team member is offboarded, you can deactivate the account on Azure.
After one hour, the user won't be able to log in to the Azure web portal anymore.
When the device is rebooted, the team member won't be able to log in anymore. This assumes there is no local user on the device.