Microsoft Configuration Manager
App managementExtending Application Management Overview
In brief
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
What Intune admins need to know
No administrator action is required; this updates documentation classification metadata only.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Extending Application Management Overview
By default, Application Management supports creating numerous deployment types such as Windows Installer, Script Installer, Microsoft Application Virtualization, Nokia SIS files and Windows Mobile Cabinet file deployment technologies. Partners that must continue to use a specific deployment technology not natively supported by Configuration Manager, can extend the Application Management model to support a custom deployment type.
@@ -5,7 +5,7 @@ ms.date: 09/20/2016 ms.subservice: sdk ms.topic: article ms.collection: tier3-ms.service: microsoft-endpoint-configuration-manager+ms.service: configuration-manager --- # Extending Application Management Overview By default, Application Management supports creating numerous deployment types such as Windows Installer, Script Installer, Microsoft Application Virtualization, Nokia SIS files and Windows Mobile Cabinet file deployment technologies. Partners that must continue to use a specific deployment technology not natively supported by Configuration Manager, can extend the Application Management model to support a custom deployment type.