%3CLINGO-SUB%20id%3D%22lingo-sub-1503416%22%20slang%3D%22en-US%22%3EHow%20to%20deploy%20DMG%20or%20APP-format%20apps%20to%20Intune-managed%20Macs%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1503416%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EBy%3A%20Arnab%20Biswas%20%7C%26nbsp%3BProgram%20Manager%20-%20Microsoft%20Endpoint%20Manager%20-%20Intune%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20can%20use%20Microsoft%20Endpoint%20Manager%20to%20deploy%20the%20most%20common%20app%20types%20supported%20by%20macOS%20such%20as%20.pkg%2C%20.dmg%20or%20.app.%20Natively%2C%20Mac%20MDM%20only%20supports%20installing%20signed%20.pkg-type%20applications.%20Therefore%2C%20for%20apps%20that%20are%20of%20non-pkg%20types%2C%20it%20requires%20admins%20to%20run%20commands%20on%20macOS%20either%20manually%20or%20as%20a%20script%20to%20create%20a%20signed%20app%20package%20(.intunemac%20file)%20that%20can%20be%20distributed%20using%20Intune.%20The%20rest%20of%20the%20document%20outlines%20the%20recommended%20app%20preparation%20steps.%20These%20steps%20have%20been%20tested%20on%20macOS%2010.15.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1301767061%22%20id%3D%22toc-hId--1301767061%22%20id%3D%22toc-hId--1301767061%22%20id%3D%22toc-hId--1301767061%22%20id%3D%22toc-hId--1301767061%22%3E%3CSTRONG%3EImportant%20notes%20before%20you%20begin%3C%2FSTRONG%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EFor%20apps%20that%20require%20a%20kernel%20or%20system%20extension%2C%20the%20extension%20must%20be%20deployed%20as%20a%20macOS%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Fconfiguration%2Fkernel-extensions-overview-macos%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edevice%20configuration%20profile%20in%20Microsoft%20Endpoint%20Manager%3C%2FA%3E%20before%20the%20app%20is%20deployed.%20The%20app%20deployment%20will%20not%20complete%20successfully%20if%20the%20extension%20is%20included%20in%20the%20app%20package.%3C%2FLI%3E%0A%3CLI%3EFor%20apps%20that%20require%20a%20property%20list%20file%20(plist%20file)%2C%20the%20property%20list%20file%20must%20be%20deployed%20using%20a%20macOS%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Fconfiguration%2Fpreference-file-settings-macos%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edevice%20configuration%20profile%20in%20Microsoft%20Endpoint%20Manager%3C%2FA%3E%20before%20the%20app%20is%20deployed.%20The%20app%20deployment%20will%20not%20complete%20successfully%20if%20the%20property%20list%20files%20are%20included%20in%20the%20app%20package.%3C%2FLI%3E%0A%3CLI%3EThe%20converted%20app%20must%20be%20re-signed%20for%20successful%20MDM-deployment.%20Unsigned%20applications%20are%20rejected%20by%20macOS.%20This%20also%20applies%20to%20DMGs%20containing%20PKG%20files.%3C%2FLI%3E%0A%3CLI%3EIt%20is%20crucial%20that%20the%20PKG%20files%20are%20created%20using%20the%20commands%20below.%20PKG%20files%20that%20are%20packaged%20using%20different%20packaging%20commands%20may%20not%20deploy%20successfully.%3C%2FLI%3E%0A%3CLI%3EDMG%20files%20containing%20more%20than%20one%20APP%20file%20are%20not%20supported.%3C%2FLI%3E%0A%3CLI%3EYou%20will%20need%20the%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmsintuneappsdk%2Fintune-app-wrapping-tool-mac%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20Intune%20App%20Wrapping%20Tool%20for%20macOS%3C%2FA%3E%20to%20complete%20the%20steps%20in%20the%20next%20section.%20Follow%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Fapps%2Flob-apps-macos%23before-your-start%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethese%20instructions%3C%2FA%3E%20to%20set%20up%20the%20App%20Wrapping%20Tool%20correctly.%3C%2FLI%3E%0A%3CLI%3EThis%20is%20not%20an%20exhaustive%20list%20of%20all%20applicable%20conditions.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1185745772%22%20id%3D%22toc-hId-1185745772%22%20id%3D%22toc-hId-1185745772%22%20id%3D%22toc-hId-1185745772%22%20id%3D%22toc-hId-1185745772%22%3E%3CSTRONG%3EApp%20preparation%20steps%3C%2FSTRONG%3E%3C%2FH2%3E%0A%3CP%3EThe%20steps%20below%20require%20that%20you%20initiate%20with%20an%20app%20of%20DMG%20or%20APP%20format%20that%20satisfy%20the%20conditions%20above.%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EMount%20the%20DMG%20file.%3CBR%20%2F%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20Skip%20this%20step%20when%20starting%20with%20APP-format%20apps.%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-bash%22%3E%3CCODE%3Ehdiutil%20attach%20appname.dmg%E2%80%8B%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLI%3E%0A%3CLI%3EMake%20a%20temporary%20folder%20and%20navigate%20to%20it.%3CBR%20%2F%3Emkdir%20.%2FTargetDirectory%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-bash%22%3E%3CCODE%3Emkdir%20.%2FTargetDirectory%E2%80%8B%0Acd%20.%2FTargetDirectory%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLI%3E%0A%3CLI%3EBuild%20an%20intermediate%20PKG%20file.%3CBR%20%2F%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20When%20using%20autocomplete%2C%20delete%20the%20final%20slash%20in%20the%20APP%20path.%20Pass%20the%20install-location%20as%20an%20argument%20to%20the%20pkgbuild%20command.%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-bash%22%3E%3CCODE%3Epkgbuild%20--install-location%20%2FApplications%20--component%20%2FVolumes%2Fpath_to_app%2Fapp_to_convert.app%20.%2FTargetDirectory%2Fintermediate.pkg%E2%80%8B%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLI%3E%0A%3CLI%3ECreate%20the%20distribution%20XML%20file%20for%20the%20intermediate%20PKG%20file.%3CBR%20%2F%3E%3CSTRONG%3ENote%3A%20%3C%2FSTRONG%3EThis%20is%20required%20to%20build%20a%20redistributable%20package.%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-bash%22%3E%3CCODE%3Eproductbuild%20--synthesize%20--package%20%2FTargetDirectory%2Fintermediate.pkg%20%2FTargetDirectory%2Fdistribution.xml%E2%80%8B%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLI%3E%0A%3CLI%3EBuild%20the%20final%20PKG%20file.%20This%20PKG%20file%20is%20not%20signed.%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-bash%22%3E%3CCODE%3Eproductbuild%20--distribution%20.%2Fdistribution.xml%20--package-path%20.%2Fintermediate.pkg%20.%2Funsigned_final.pkg%E2%80%8B%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLI%3E%0A%3CLI%3ESign%20the%20PKG%20file%20using%20a%20Mac%20Developer%20ID%20certificate.%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-bash%22%3E%3CCODE%3Eproductsign%20--sign%20%E2%80%9C3rd%20Party%20Mac%20Developer%20Installer%3A%20Developer%20Name%20(XXXX)%E2%80%9D%20.%2Funsigned_final.pkg%20.%2Fsigned_final.pkg%E2%80%8B%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLI%3E%0A%3CLI%3EUnmount%20the%20DMG%20file.%3CBR%20%2F%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20Skip%20this%20step%20when%20starting%20with%20APP-format%20apps.%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-bash%22%3E%3CCODE%3Ehdiutil%20detach%20%2FVolumes%2Fappname%E2%80%8B%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLI%3E%0A%3CLI%3ECreate%20the%20INTUNEMAC%20file%20from%20the%20signed%20PKG%20file.%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-bash%22%3E%3CCODE%3E.%2FIntuneAppUtil%20-c%20signed_final.pkg%20-o%20%2Ffinalpath%E2%80%8B%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLI%3E%0A%3CLI%3E-ERR%3AREF-NOT-FOUND-Add%20the%20INTUNEMAC%20file%20as%20a%20line-of-business%20application%20for%20macOS%20on%20Microsoft%20Endpoint%20Manager.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E-ERR%3AREF-NOT-FOUND-This%20sample%20script%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3E%20demonstrates%20how%20the%20above%20steps%20can%20convert%20a%20DMG%20file%20to%20INTUNEMAC.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELet%20us%20know%20by%20responding%20to%20this%20post%20if%20you%20have%20any%20questions%20or%20feedback!%20You%20can%20also%20ask%20questions%20by%20tagging%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FIntuneSuppTeam%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%40IntuneSuppTeam%3C%2FA%3E%26nbsp%3Bout%20on%20Twitter%20where%20our%20Support%20as%20a%20Feature%20team%20helps%20answer%20quick%20questions.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBlog%20post%20updates%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E7%2F22%2F20%3A%20With%20an%20update%20to%20the%20IntuneSuppTeam%20URL.%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1503416%22%20slang%3D%22en-US%22%3E%3CP%3ERead%20this%20post%20on%26nbsp%3Bdeploying%20DMG%20or%20APP-format%20apps%20to%20Intune-managed%20macOS%20devices.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1503416%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApp%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDMG%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EmacOS%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMEM%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1780670%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20deploy%20DMG%20or%20APP-format%20apps%20to%20Intune-managed%20Macs%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1780670%22%20slang%3D%22en-US%22%3E%3CP%3E%40%3CSTRONG%3EArnab%20Biswas%26nbsp%3B%3C%2FSTRONG%3EThanks%20for%20the%20post.%20Let%20me%20know%20for%20MacOS%2C%20how%20to%20convert%20the%20DMG%20to%20PKG%20if%20we%20don't%20know%20the%20Developer%20ID.%20Do%20you%20recommend%20any%20tool%20or%20command%20for%20the%20conversion.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20facing%20difficulties%20in%20deploying%20applications%20in%20Intune%20for%20MacOS.%20Also%20I've%20few%20challenges%20in%20deploying%20it%20and%20list%20as%20follows%2C%3C%2FP%3E%3CP%3E1.%20We%20got%20SentinelOne%20Anti-virus%20agent%20and%20I%20don't%20know%20how%20to%20incorporate%20the%20Token%20key%20in%20MacOS%20package%20to%20deploy%20it%20in%20Intune.%20By%20default%2C%20SentinelOne%20agent%20not%20coming%20with%20Token%20Key.%20But%20for%20Windows%2C%20we%20have%20Install%20command%20parameter%20in%20Intune%2C%20which%20helps%20to%20provide%20the%20token%20key%20to%20get%20it%20installed%20silently.%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20Though%20I%20deployed%20Zoom%20package%20in%20Intune%20and%20it%20got%20installed%20in%20MacOS%2010.15.7%2C%20still%20in%20Intune%20portal%20shows%20the%20status%20as%20%22The%20app%20state%20is%20unknown%22%20and%20error%20code%20is%20%22%3CSPAN%3E0x87D13B67%22.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EKindly%20help%20me%20on%20this.%20Thanks%20for%20understanding.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1826329%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20deploy%20DMG%20or%20APP-format%20apps%20to%20Intune-managed%20Macs%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1826329%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F832498%22%20target%3D%22_blank%22%3E%40Karthick2504%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsually%20when%20you%20have%20to%20provide%20tokens%20with%20macOS%20packages%20you%20can%20do%20this%20with%20a%20post-install%20script.%20I%20find%20i%20easiest%20to%20use%20a%20tool%20like%20Packages%20which%20is%20freeware%20to%20re-package%20the%20PKG%20and%20add%20post%2Fpre-install%20scripts.%20Keep%20in%20mind%20that%20regardless%20of%20which%20tool%20you%20use%20to%20repackage%20you%20still%20need%20to%20have%20a%20Developer%20ID%20to%20sign%20the%20package.%20If%20your%20company%20does%20not%20have%20this%20you%20have%20to%20buy%20one%3A%20%3CA%20href%3D%22https%3A%2F%2Fdeveloper.apple.com%2Fprograms%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.apple.com%2Fprograms%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20also%20tested%20depoying%20Zoom%20and%20did%20not%20get%20the%20correct%20install%20status%20of%20the%20application.%20What%20you%20need%20to%20make%20sure%20is%20that%20the%20application%20contains%20the%20correct%20parameters%2C%20specifically%3A%3C%2FP%3E%3CUL%3E%3CLI%3EThe%20package%20version%20and%20CFBundleVersion%20string%20in%20the%20packageinfo%20file.%3C%2FLI%3E%3CLI%3EThe%20correct%20install-location%20in%20the%20pkg-info%20file.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20extract%20the%20package%20information%20using%20this%20command%3A%3C%2FP%3E%3CUL%3E%3CLI%3Exar%20-x%20-f%20%26lt%3B.pkg%20file%20path%26gt%3B%20-C%20%3COUTPUT%20folder%3D%22%22%3E%3C%2FOUTPUT%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESee%20this%20URL%20for%20more%20information%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Ftroubleshoot%2Fmem%2Fintune%2Fmacos-lob-apps-not-deployed%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Ftroubleshoot%2Fmem%2Fintune%2Fmacos-lob-apps-not-deployed%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E

By: Arnab Biswas | Program Manager - Microsoft Endpoint Manager - Intune

You can use Microsoft Endpoint Manager to deploy the most common app types supported by macOS such as .pkg, .dmg or .app. Natively, Mac MDM only supports installing signed .pkg-type applications. Therefore, for apps that are of non-pkg types, it requires admins to run commands on macOS either manually or as a script to create a signed app package (.intunemac file) that can be distributed using Intune. The rest of the document outlines the recommended app preparation steps. These steps have been tested on macOS 10.15.

 

Important notes before you begin

  • For apps that require a kernel or system extension, the extension must be deployed as a macOS device configuration profile in Microsoft Endpoint Manager before the app is deployed. The app deployment will not complete successfully if the extension is included in the app package.
  • For apps that require a property list file (plist file), the property list file must be deployed using a macOS device configuration profile in Microsoft Endpoint Manager before the app is deployed. The app deployment will not complete successfully if the property list files are included in the app package.
  • The converted app must be re-signed for successful MDM-deployment. Unsigned applications are rejected by macOS. This also applies to DMGs containing PKG files.
  • It is crucial that the PKG files are created using the commands below. PKG files that are packaged using different packaging commands may not deploy successfully.
  • DMG files containing more than one APP file are not supported.
  • You will need the Microsoft Intune App Wrapping Tool for macOS to complete the steps in the next section. Follow these instructions to set up the App Wrapping Tool correctly.
  • This is not an exhaustive list of all applicable conditions.

 

App preparation steps

The steps below require that you initiate with an app of DMG or APP format that satisfy the conditions above.

  1. Mount the DMG file.
    Note: Skip this step when starting with APP-format apps.
    hdiutil attach appname.dmg​
  2. Make a temporary folder and navigate to it.
    mkdir ./TargetDirectory
    mkdir ./TargetDirectory​
    cd ./TargetDirectory
  3. Build an intermediate PKG file.
    Note: When using autocomplete, delete the final slash in the APP path. Pass the install-location as an argument to the pkgbuild command.
    pkgbuild --install-location /Applications --component /Volumes/path_to_app/app_to_convert.app ./TargetDirectory/intermediate.pkg​
  4. Create the distribution XML file for the intermediate PKG file.
    Note: This is required to build a redistributable package.
    productbuild --synthesize --package /TargetDirectory/intermediate.pkg /TargetDirectory/distribution.xml​
  5. Build the final PKG file. This PKG file is not signed.
    productbuild --distribution ./distribution.xml --package-path ./intermediate.pkg ./unsigned_final.pkg​
  6. Sign the PKG file using a Mac Developer ID certificate.
    productsign --sign “3rd Party Mac Developer Installer: Developer Name (XXXX)” ./unsigned_final.pkg ./signed_final.pkg​
  7. Unmount the DMG file.
    Note: Skip this step when starting with APP-format apps.
    hdiutil detach /Volumes/appname​
  8. Create the INTUNEMAC file from the signed PKG file.
    ./IntuneAppUtil -c signed_final.pkg -o /finalpath​
  9. Add the INTUNEMAC file as a line-of-business application for macOS on Microsoft Endpoint Manager.

This sample script demonstrates how the above steps can convert a DMG file to INTUNEMAC.

 

Let us know by responding to this post if you have any questions or feedback! You can also ask questions by tagging @IntuneSuppTeam out on Twitter where our Support as a Feature team helps answer quick questions.

 

Blog post updates:

  • 7/22/20: With an update to the IntuneSuppTeam URL.
2 Comments
Occasional Visitor

@Arnab Biswas Thanks for the post. Let me know for MacOS, how to convert the DMG to PKG if we don't know the Developer ID. Do you recommend any tool or command for the conversion. 

 

I'm facing difficulties in deploying applications in Intune for MacOS. Also I've few challenges in deploying it and list as follows,

1. We got SentinelOne Anti-virus agent and I don't know how to incorporate the Token key in MacOS package to deploy it in Intune. By default, SentinelOne agent not coming with Token Key. But for Windows, we have Install command parameter in Intune, which helps to provide the token key to get it installed silently. 

2. Though I deployed Zoom package in Intune and it got installed in MacOS 10.15.7, still in Intune portal shows the status as "The app state is unknown" and error code is "0x87D13B67". 

 

Kindly help me on this. Thanks for understanding.

Contributor

Hi @Karthick2504,

 

Usually when you have to provide tokens with macOS packages you can do this with a post-install script. I find i easiest to use a tool like Packages which is freeware to re-package the PKG and add post/pre-install scripts. Keep in mind that regardless of which tool you use to repackage you still need to have a Developer ID to sign the package. If your company does not have this you have to buy one: https://developer.apple.com/programs/

 

I've also tested depoying Zoom and did not get the correct install status of the application. What you need to make sure is that the application contains the correct parameters, specifically:

  • The package version and CFBundleVersion string in the packageinfo file.
  • The correct install-location in the pkg-info file.

 

You can extract the package information using this command:

  • xar -x -f <.pkg file path> -C <Output folder>

 

See this URL for more information: https://docs.microsoft.com/en-us/troubleshoot/mem/intune/macos-lob-apps-not-deployed