The Microsoft Company Portal app is a critical component of the Microsoft Intune device management ecosystem. It provides users with a self-service portal to install approved applications, manage their devices, and access company resources. When combined with Windows Autopilot and the Enrollment Status Page (ESP), you can create a seamless deployment experience that ensures devices are properly configured before users can access them.
This tutorial will guide you through the process of deploying the Company Portal app from the Windows App Store and integrating it with Windows Autopilot ESP, including the White Glove pre-provisioning mode.
Before you begin, ensure you have:
- Microsoft Intune subscription with administrative access
- Windows 10/11 devices registered for Windows Autopilot
- Appropriate licenses for users
- Access to the Microsoft Intune admin center
- Basic understanding of Windows Autopilot and Intune app deployment
The Company Portal app serves several important functions in the Intune ecosystem:
- Application Management: Allows users to install company-approved applications
- Device Management: Enables users to enroll and manage their devices
- Resource Access: Provides access to company resources and support
- Compliance Status: Shows users their device compliance status
When deployed as part of the Windows Autopilot process, the Company Portal app can be installed before the user even signs in, ensuring it's available immediately after setup.
- Sign in to the Microsoft Intune admin center with your admin account.
- Select Apps from the left navigation menu.
- In the Apps page, select All apps.
- In the All apps page, select Add.
- In the Select app type pane, under Store app, select Microsoft Store app (new).
- Click Select at the bottom of the page.
- Select Search the Microsoft Store app (new).
- In the search box, enter Company Portal.
- Select Company Portal from the search results.
- Click Select at the bottom of the page.
- In the App information tab, review the app details:
- Name: Company Portal
- Publisher: Microsoft Corporation
- Category: Business
- Change Install behavior to System to ensure the app is installed in the system context rather than per-user.
- Set Show this as a featured app in the Company Portal to Yes if you want it to be prominently displayed.
- Click Next to continue.
- Add any scope tags if you use them to organize your Intune resources.
- Click Next to continue.
- In the Assignments tab, under Required, select Add group.
- Select the groups to which you want to assign the Company Portal app.
- For Autopilot deployment, assign it to your Autopilot device groups.
- Consider creating a dynamic device group that includes all your Windows 10/11 devices.
- Click Select to add the groups.
- Click Next to continue.
- Review all the settings you've configured.
- Click Create to add the Company Portal app to Intune.
The Enrollment Status Page (ESP) displays the provisioning status to users during device setup and can be configured to block device use until all required policies and applications, including the Company Portal, are installed.
- Sign in to the Microsoft Intune admin center.
- Navigate to Devices > Enrollment > Windows enrollment.
- Select the Windows tab.
- Under Windows Autopilot, select Enrollment Status Page.
- Click Create to create a new ESP profile.
- In the Basics tab:
- Enter a descriptive Name for the profile (e.g., "Standard ESP with Company Portal").
- Add an optional Description.
- Click Next to continue.
-
In the Settings tab, configure the following:
- Show app and profile configuration progress: Set to Yes to display installation progress.
- Show an error when installation takes longer than specified number of minutes: Set an appropriate timeout (e.g., 60 minutes).
- Show custom message when time limit or error occur: Optionally set to Yes and provide a custom message.
- Turn on log collection and diagnostics page for end users: Set to Yes for troubleshooting purposes.
- Only show page to devices provisioned by out-of-box experience (OOBE): Choose based on your requirements.
- Block device use until all apps and profiles are installed: Set to Yes to ensure all required apps are installed.
- Allow users to reset device if installation error occurs: Set based on your organization's policies.
- Allow users to use device if installation error occurs: Set based on your organization's policies.
-
For Block device use until these required apps are installed if they are assigned to the user/device:
- Select Selected.
- Click Select apps.
- In the app list, select Company Portal and any other critical apps.
- Click Select to add the apps to the blocking list.
-
If you're using pre-provisioning (White Glove), set Only fail selected blocking apps in technician phase based on your requirements:
- No: All apps must be installed during pre-provisioning.
- Yes: Only blocking apps must be installed during pre-provisioning.
-
Click Next to continue.
- In the Assignments tab, select Add groups.
- Select the groups that should receive this ESP profile.
- For Autopilot deployment, assign it to your Autopilot device groups.
- Consider creating a dynamic device group that includes all your Windows 10/11 devices.
- Click Select to add the groups.
- Click Next to continue.
- Add any scope tags if you use them to organize your Intune resources.
- Click Next to continue.
- Review all the settings you've configured.
- Click Create to create the ESP profile.
Now that you've added the Company Portal app and configured the ESP, you need to ensure they're properly integrated with your Windows Autopilot deployment.
- In the Microsoft Intune admin center, navigate to Devices > Enrollment > Windows enrollment.
- Under Windows Autopilot, select Deployment Profiles.
- Select an existing profile or create a new one.
- Ensure the profile is configured for your desired deployment scenario:
- User-driven mode (standard)
- Self-deploying mode
- Pre-provisioning (White Glove)
- Make sure the profile is assigned to the appropriate device groups.
- In the deployment profile, ensure that Show the Enrollment Status Page is set to Yes.
- Verify that the ESP profile you created is assigned to the same groups as your Autopilot deployment profile.
White Glove (pre-provisioning) allows IT staff, partners, or OEMs to pre-configure devices before delivering them to end users. This process installs device-targeted apps and policies, including the Company Portal, before the user receives the device.
- Ensure your devices are registered for Windows Autopilot.
- Verify that your Autopilot deployment profile is configured correctly.
- Make sure the Company Portal app is assigned as a required app to your Autopilot device groups.
- Confirm that your ESP profile is properly configured and assigned.
- Boot the device to be provisioned.
- At the first OOBE screen, press Windows key + Shift + F10 to access the pre-provisioning options.
- Press the Windows key five times to open the Windows Autopilot pre-provisioning screen.
- Select Windows Autopilot provisioning.
- On the authentication screen, sign in with a technician account that has appropriate permissions.
- Select Pre-provision to begin the process.
- The device will connect to your tenant and begin downloading and applying policies and apps.
- The ESP will display the progress of app installations, including the Company Portal.
- Once all required apps and policies are installed, the pre-provisioning process will complete.
- The device will be ready to be shipped to the end user.
When the end user receives the device:
- They will power on the device and begin the OOBE process.
- They will sign in with their credentials.
- The ESP will display, showing the progress of user-specific configurations.
- Once complete, the user will have access to the desktop with the Company Portal already installed.
- The user can open the Company Portal to access additional apps and resources.
Before rolling out to all users, it's important to test the deployment process to ensure everything works as expected.
- Select a test device that is registered for Windows Autopilot.
- Assign it to your Autopilot deployment profile and ESP profile.
- Reset the device to begin the Autopilot process.
- Monitor the deployment to ensure:
- The ESP displays correctly
- The Company Portal app installs successfully
- The device is properly configured before the user gains access
- After the device setup is complete, sign in as a test user.
- Locate and open the Company Portal app.
- Verify that the app launches correctly and displays the expected content.
- Test installing an app from the Company Portal to ensure it works properly.
- Collect feedback from test users about the deployment experience.
- Make any necessary adjustments to your ESP profile or app assignments.
- Test again with the updated configuration before rolling out to all users.
- In the Microsoft Intune admin center, navigate to Apps > Monitor > App install status.
- Select the Company Portal app to view its installation status across your devices.
- Review the status to identify any devices where installation failed.
- Verify that the Company Portal app is assigned as a required app to the device group.
- Check that the app is included in the blocking apps list in your ESP profile.
- Ensure the ESP timeout is long enough to allow for app installation.
- Review the device's enrollment status in Intune to identify any issues.
- Increase the timeout value in your ESP profile if installations are taking too long.
- Enable log collection in the ESP profile to gather diagnostic information.
- Review the logs to identify the specific issue causing the failure.
- Check network connectivity and ensure the device can reach all required endpoints.
- Ensure the technician account has appropriate permissions.
- Verify that the device meets the hardware requirements for pre-provisioning.
- Check network connectivity during the pre-provisioning process.
- Review the ESP logs to identify any specific issues.
-
Assign the Company Portal as a System App: Always set the install behavior to "System" to ensure it's installed for all users on the device.
-
Include in ESP Blocking Apps: Add the Company Portal to your ESP blocking apps list to ensure it's installed before the user can access the device.
-
Test Thoroughly: Always test your deployment process with a small group of devices before rolling out to all users.
-
Monitor Deployment: Regularly check the installation status of the Company Portal app to identify and address any issues.
-
Update Regularly: Keep the Company Portal app updated to ensure users have access to the latest features and security improvements.
-
Document Your Configuration: Maintain documentation of your ESP and Autopilot configurations for future reference and troubleshooting.
-
Use Dynamic Groups: Create dynamic device groups based on device properties to automatically assign profiles and apps to new devices.
-
Optimize Pre-Provisioning: For White Glove scenarios, carefully select which apps are critical to install during pre-provisioning to minimize provisioning time.
Deploying the Company Portal app through Windows Autopilot with ESP integration provides a seamless and controlled deployment experience for your users. By ensuring the Company Portal is installed during the device setup process, you give users immediate access to the tools and resources they need to be productive.
The White Glove pre-provisioning option further enhances this experience by allowing IT staff to prepare devices before they reach end users, reducing the time users spend waiting for device setup to complete.
By following the steps and best practices outlined in this tutorial, you can successfully deploy the Company Portal app as part of your Windows Autopilot process, creating a consistent and efficient deployment experience for your organization.

