SCCM to Intune device - Company portal failed

For co-managed devices where workloads are being shifted from Configuration Manager to Intune, Company Portal deployment and behavior depend on both the app deployment method and the co-management workload configuration.

Key points and checks to fix the failure and avoid it on other devices:

1. Confirm the co-management workload state
   • For the Client apps workload:
     • If set to Configuration Manager: devices will only see Configuration Manager client apps in Company Portal.
     • If set to Pilot Intune or Intune: devices will see both Configuration Manager and Intune client apps in Company Portal.
   • For Office Click-to-run apps:
     • Configuration Manager: only Configuration Manager Office C2R apps are visible.
     • Pilot Intune or Intune: only Intune Office C2R apps are visible.
   • If the workload is not aligned with how Company Portal is being deployed (ConfigMgr vs Intune), the app may not appear or behave as expected even if deployment technically succeeds.
2. Verify Company Portal is the selected user portal on the device
   • In Configuration Manager client settings, under Software Center device settings, ensure Select the user portal is set to Company Portal for the collection that includes the affected devices.
   • If this is not set, users may still see Software Center behavior or mixed behavior, which can cause confusion when testing app installs.
3. Validate how Company Portal is deployed
   • For co-managed devices, the deployment path depends on the Client apps workload:
     • If Client apps workload is with Configuration Manager:
       • Deploy Company Portal as a ConfigMgr application using standard application deployment (create and deploy an application with Configuration Manager).
     • If Client apps workload is with Intune (Pilot or full):
       • Either continue to deploy via Configuration Manager, or
       • Add and deploy the Company Portal app from the Microsoft Store using Intune (add the Company Portal app by using Microsoft Intune).
   • Ensure that the app you deployed from the “Microsoft New Store” is indeed the Company Portal package and not a different Store app with a similar name.
4. Check targeting and availability in Company Portal
   • If Company Portal is being deployed as an Intune app:
     • Confirm the app is assigned with Available intent to the correct user or device group.
     • Confirm the affected user is signing into Company Portal on a supported device type for that app.
   • If the app does not display in Company Portal at all, verify:
     • Assignment is correct.
     • The device is properly enrolled and associated with the user.
5. Check for enrollment and device-cap issues
   • If Company Portal is failing with generic or “temporarily unavailable” type errors on some devices, validate:
     • The device is correctly enrolled into Intune.
     • The user is not over the Maximum devices per user limit in Microsoft Entra ID. If over the limit, remove stale device records and retry.
6. Use Company Portal-specific troubleshooting if the client shows errors
   • If users see Company Portal Temporarily Unavailable or similar errors on the device:
     • Uninstall the Intune Company Portal app from the device.
     • From the device browser, go to https://portal.manage.microsoft.com and sign in.
       • If sign-in fails, test another network and verify the user’s credentials and sync with Microsoft Entra ID.
       • If sign-in succeeds, reinstall Company Portal (prompted on iOS/iPadOS; manually from Store on Android/Windows) and retry enrollment/launch.
7. Interpret the 0x0 “unknown” status
   • A status of 0x0 typically indicates a generic success/unknown state rather than a specific failure code. In this context, it often means:
     • The Store/Intune/ConfigMgr deployment pipeline did not receive a clear error from the client, or
     • The app did not fully install or register as expected, but no explicit error was returned.
   • Focus on:
     • Verifying that the correct Company Portal package is deployed and targeted.
     • Ensuring co-management workloads and client settings are aligned so that Company Portal is the active portal and can surface apps correctly.
8. Recommended remediation pattern for other devices
   • Before shifting workloads for a batch of devices:
     1. Set Select the user portal to Company Portal in ConfigMgr client settings for the target collection.
     2. Decide where Client apps workload will live (ConfigMgr vs Intune) and keep the Company Portal deployment method consistent with that decision.
     3. Deploy Company Portal either:
        • As a ConfigMgr application (if Client apps workload is still ConfigMgr), or
        • As an Intune Store app (if Client apps workload is Pilot Intune/Intune), ensuring correct assignments.
     4. Validate on a pilot device that Company Portal installs and shows both ConfigMgr and Intune apps as expected after the workload shift.

If, after aligning workloads and deployment method, Company Portal still fails on specific devices, remove the app, confirm enrollment and device limits, then redeploy Company Portal using the appropriate channel (ConfigMgr or Intune) based on the current Client apps workload.

References:

• Use the Company Portal app on co-managed devices
• Troubleshooting device enrollment in Intune
• Troubleshooting Intune app installation issues