Setting up and managing device configurations using Intune
Public apps in the Intune admin center only show:
- Microsoft apps that have integrated the Intune SDK
- Partner apps that have integrated the Intune SDK and have been registered with Microsoft as Intune partner apps
Because the app was registered in a different tenant and is already in the public stores, there are two key points:
- Internal (LOB) apps do not need public registration
If the app is internal to an organization and not meant to be publicly listed as an Intune partner app, no registration with Microsoft is required. Intune will detect the SDK and the admin can target it via Custom apps using the bundle ID / package name. This is the expected behavior for LOB apps. - Public store apps must be registered with Microsoft to appear as a Public app
For an app that is in the Apple App Store or Google Play and is intended to show up as a public/partner app in Intune (so admins can pick it from Public apps instead of manually entering bundle IDs), the app must be registered with Microsoft Intune as a partner app and the registration process must be completed and confirmed. Until that registration is finished, Intune admins will not see the app listed as a public app target and must continue using Custom apps with the bundle ID / package name.
So the missing step is:
- For a public store app that should appear under Public apps for all tenants, complete the Microsoft Intune App Partner registration process and wait for confirmation. Only after that will the app be listed as a partner productivity app and selectable as a Public app in Intune.
If the app is only for a specific tenant and not intended to be a global Intune partner app, then targeting it via Selected apps → Custom apps with the bundle ID / package name is the correct and final approach.
References: