Skip to main content
A
Community Manager
Anshul_NautiyalCommunity Manager
Community Manager
April 3, 2025
Question

Deploy Adobe Packages on macOS Using Microsoft Intune

  • April 3, 2025
  • 4 replies
  • 6909 views

We are excited to announce that flat packages created on the Adobe Admin Console can now be deployed on macOS devices using Microsoft Intune! 

You can download the flat package from the Packages section in the Adobe Admin Console. Click here to learn how to create and download macOS packages from the Admin Console.

 

 

Pre-requisites:

Before deploying, ensure the following:

  • Admin access to Microsoft Intune to manage apps and devices.
  • Adobe macOS PKG file downloaded from the Adobe Admin Console (max size: 8GB).
  • Managed macOS devices enrolled in Microsoft Intune.
  • Microsoft Intune Company Portal installed on target devices.

For more, read the Intune app prerequisites.

Deployment Steps:

  • Upload the PKG file to Microsoft Intune via Apps > macOS in the Endpoint Manager.
  • Configure app details, including name, description, publisher, and category.
  • Set detection rules.
  • Assign the app to devices or user groups.
  • Monitor deployment through Microsoft Intune admin center.

For a step-by-step guide, visit our documentation: Deploy Adobe Packages on macOS Using Microsoft Intune.

If you have any feedback or are encountering issues, let us know by posting on this thread below.

Quick Links

 

 If this was helpful, please click the   Upvote icon in the top left corner of this post. Your feedback helps us improve the experience. Thank you! 

Stay Informed! Explore All the Latest Updates & Releases on Our ICYMI Page!

Have questions? Click 'Reply' below to ask.

    4 replies

    H
    HH-TT-0211
    Participant
    March 26, 2026

    As we haven’t received any feedback from our previous post, here is our experience after following the documentation for deploying Adobe apps in a macOS environment managed with Intune.

    The general outlined steps for creating Adobe apps, uploading them to Intune, and deploying them to macOS devices are, depending on experience and interpretation, mostly correct. However, we followed the detailed instructions here:
    https://helpx.adobe.com/enterprise/kb/deploy-macos-packages-using-ms-intune.html

    Following these steps caused an endless reinstall loop for all our locally deployed Adobe apps. Each macOS machine downloaded around 150 GB per day, and across three shared macOS labs this led to a network meltdown.

    We first noticed a complete slowdown of our network and extremely high inbound traffic. After isolating the problem, it became clear that our macOS labs were responsible — specifically the interaction between Intune and the Adobe PKG detection logic.

    We opened a ticket with Adobe support regarding the published documentation (linked above). Their support team stated that Adobe macOS PKGs are “not supported” and “not validated” for Intune. Only Windows 64‑bit packages are officially supported.

    It was also acknowledged that the documented macOS/Intune workflow does "...not reflect current product limitations" and may set incorrect expectations. We asked Adobe to update the documentation with a clear warning to prevent other admins from running into similar issues.

    They mentioned that they are working on improvements for Intune/macOS/Adobe compatibility, but there is no timeline at present.

    Just wanted to share this so other admins don’t encounter the same problems.

    A
    Community Manager
    Anshul_NautiyalCommunity ManagerAuthor
    Community Manager
    March 26, 2026

    Hi ​@HH-TT-0211 

    Thank you for taking the time to share such a detailed account of your experience—this is extremely helpful for the community. I’m really sorry to hear about your issue and the experience you’ve had, especially the reinstall loop and the significant network load across your macOS labs.

    Could you please confirm if, under detection rules, the “Ignore App version” option is set to Yes?

    If this is not selected as Yes, it can contribute to the issue. In such cases, Intune attempts to match the exact app version, and any variation in the installed Adobe app version may cause it to be detected as not installed, leading to repeated reinstall attempts. We recommend ensuring that under detection rules, “Ignore App version” is set to Yes.

    Additionally, I would suggest creating a flat package and testing the installation on a single macOS device to validate whether the detection logic is working as expected before deploying it broadly. This can help isolate whether the behavior is related to detection configuration or deployment scale.

    You may also consider:

    Using a custom detection method (e.g., checking the installed app path) instead of relying solely on default PKG detection
    Testing with smaller, single-app packages to reduce repeated download impact
    Validating deployment behavior with a limited pilot group before wider rollout

    If you have an active support ticket open, could you please share the details with me? You can send it via a personal message by clicking on my profile, and I’ll be happy to check and assist you further.

    Hope this helps, and please let us know if you need any further assistance.

    Regards,
    ^AN
     

    H
    HH-TT-0211
    Participant
    March 26, 2026

    Hello Anshul,

    Thanks for your quick response.

     

    To answer a few of your questions:

     

    Could you please confirm if, under detection rules, the “Ignore App version” option is set to Yes?

    Yes, the option was set to yes “ignore”.  This did not have any effect, however.

     

    Additionally, I would suggest creating a flat package and testing the installation on a single macOS device to validate whether the detection logic is working as expected before deploying it broadly. This can help isolate whether the behavior is related to detection configuration or deployment scale.

    We also did this initially last year without any major problems.  We experienced this new problem with the detection logic only starting with our updates around four weeks ago.

     

    You may also consider:

    Using a custom detection method (e.g., checking the installed app path) instead of relying solely 

    on default PKG detection

    OK, we’ll look into this.
     

    Testing with smaller, single-app packages to reduce repeated download impact

    We don’t always have a lot of time for this, but we will take it into consideration.  The process of generating multiple Adobe packages, preparing them for upload into Intune is already  massively time-consuming.

     

    And ultimately as we followed the documentation to the letter, we were not expecting any major problems.

     

    If you have an active support ticket open, could you please share the details with me? You can send it via a personal message by clicking on my profile, and I’ll be happy to check and assist you further.

     

    Thanks! The ticket has been closed only today, but I can send the details over to you via PM.

    H
    HH-TT-0211
    Participant
    May 28, 2025

    We are managing macOS computers in a shared lab environment with Intune.  The separate creation of Adobe Apps (maximum 8GB) for deployment in Intune, then downloading, then signing separately with our Apple Dev Certificate, and then uploading to Intune is massively time consuming.  Is there a more streamlined method being planned?

     

    We have spent many hours testing our Intune/macOS environment and have discovered a great deal of problems relating to Adobe App deployment.  The most recent problem is that although our Adobe Packages generated in the Adobe Admin Console are set to DE (German language), they are installing with the default language of English.  This is both with local macOS installs and through the MDM Intune.

    We will contact Adobe support with a more detailed outline of our setup and see what happens.  In the meantime, we are hoping that the packaging and deployment process for our Adobe products becomes much more efficient and reliable.

    Bani Verma
    Bani Verma
    Legend
    May 28, 2025

    Hi there, 

     

    Thank you for sharing your feedback with us. We have made a note of it and will share it with the relevant team. 

    For the deployment issue regarding the language getting changed, give me some time to test it at our end and check if we can duplicate this issue. 

     

    I will get back to you as soon as possible. 

     

    Thanks, 
    ^BS

      I
      ITMel
      Participant
      April 29, 2025

      Premiere Pro is way over the .PKG size limit. How do we deploy this app?

      Bani Verma
      Bani Verma
      Legend
      April 30, 2025

      Hi @Shah_126,

       

      Sorry to hear that you are having trouble deploying your package via Intune due to file size. 

       

      In this case, instead of downloading pre-generated packages, you can try creating a Named user licensing package for Premiere Pro without including any additional Premiere Pro add-ons.
      Please refer to the following document for detailed instructions on creating an NUL package: How to Create NUL Packages.

      Kindly try this approach and let us know if you have any further questions.

      Regards,

      ^BS

      Shah_126
      Shah_126
      Participant
      April 24, 2025

      Am very thankful to you for providing this precious information. 

      Thanks Regards 

      Shah Baig

      Bani Verma
      Bani Verma
      Legend
      April 24, 2025

      Hi @Shah_126

       

      Thank you for sharing your feedback. 

      Please reach out if you have any questions.


      ^BS

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices