Exporting dependencies to Intune
When exporting packages to Intune, associated dependencies will be automatically exported and linked to the parent application. To support this behavior all packages exported to Intune will be exported as Win32 applications.
Dependency packages are only exported if they haven’t already been exported to Intune, and this behavior is not affected by the re-export behavior (see below).
Re-Export to Intune
When exporting packages to Intune you can now choose whether to skip previously exported packages or to re-export the selected packages and create a new app in Intune, even if one already exists.
In the API a new Boolean parameter called “re-export-existing” has been introduced to the “/api/v2/intune-instances/{intuneInstanceId}/export-application/{applicationPackageId}” endpoint to configure this behavior.
The default behavior for both the UI and the API will be to not re-export previously exported packages. This behavior only applies to selected packages, it doesn’t affect dependencies.
Exporting the package icon from SCCM to Intune
When exporting packages to Intune that were imported from SCCM, the icon configured for Software Center is now exported to Intune and will appear in Company Portal.
Other Changes
- The Migration Suitability dashboard has been renamed to Windows Readiness
- The Manage dashboard has been merged into the new Windows Readiness dashboard
- The performance comparison is no longer displayed on the Windows Readiness dashboard, performance data is still visible on the Performance tab of the sequences screen and exportable via the API
- The AVD Suitability dashboard has been renamed to AVD Readiness
