1. Microsoft Intune App Deployment
2. Intune Mac App Deployment
3. Deploy Software To Mac Intune

Adobe delivers updates, features, and new versions of apps as they become available. Decide how to deploy and deliver these apps and updates to your end users. There are several options available, and you can choose one or more that best suits your requirements. It must be noted that each method has its own pros and cons. Weigh the benefits against the requirements of your organization or group.

May 29, 2019  One of the most frequently asked questions from customers is whether it is possible to publish Win32 applications with Microsoft Intune. The answer is Yes. It is possible to deploy Windows 10 Store Apps, MSI files and even.EXE files. Although.EXE files cannot be published directly. You need to “wrap” the.EXE file (and other required source files if applicable) to an.INTUNEWIN file. Jan 13, 2020  Deploying Apps to Mac’s using Microsoft Intune Published by scott on May 11, 2018 If you’ve been watching the Intune Whats New page closely, you may have noticed you can now use Intune to push down applications to MacOS devices. I have not been able to find documentation on this anywhere for InTune. I tried installing Powershell Core on a test Mac, but I have not been able to find any commands related to local account creation for macOS. Company Portal. I have iOS apps that I would like to make available, but not required to users. I was hoping the CP would solve this. Jan 16, 2017  In this post we will see the steps for deploying Android applications using Microsoft Intune. In case you want to read my previous posts, here are the Intune guides. To deploy an app you must first add it to Microsoft Intune. The devices should also be enrolled in Intune. The android devices should be installed with Intune Company Portal app.

As the administrator of the Adobe enterprise organization, you can make Creative Cloud and Document Cloud applications available to your end users in two ways:

Like millions of Adobe users, you can allow your creatives to install applications and updates via the Creative Cloud Desktop application. Self-service packages reduce IT overhead and ensure that your creatives have access to all the tools they need and receive updates when they are released.

If you want to enable self-service but your end users do not have administrative privileges, you can do one of the following:

• Create a Self-Service package
• Create a Managed Package with elevated privileges turned on
• Create a package based on an Adobe Template with elevated privileges turned on

Self-service workflows enable users to download and install apps as and when required. Apps that a user is entitled to get, are provisioned when the user signs in. Other apps can be used as a trial for a limited time. This also frees up admins from creating and deploying multiple packages and updates. For example, self-service workflows are efficient in the following scenarios:

• You have diverse and changing requirements of apps by different users.
• Your users have several hardware and operating system combinations.
• You have remote workers in your organization.
• Different teams and users upgrade at different times, because of ongoing projects.
• You want to reduce the initial footprint on a machine by allowing a user to install only the applications they require, and for as long as they require.
  

As a first step, end users download the Creative Cloud desktop app from the Creative Cloud website. In addition to downloading and installing the software, the app also provides access to Creative Cloud services such as File Sync, Font Sync, and Behance.

Self-service workflows require the following:

• Named licensing
• Complete access to Creative Cloud web services
• Admin privileges on the client computers

For end-user documentation, see Creative Cloud desktop app.

Using Managed packages, you can decide what get’s deployed and when it gets updated. You can create the packages that contain the latest or archived versions of Adobe products. These packages can then be deployed to the user's computers in your organization. You can even perform silent and custom deployment where no inputs are required from your users during installation.

For example, you can use managed delivery of apps for the following:

• To exercise strict control over installed apps on client machines.
• To reduce Internet bandwidth consumption, by preventing multiple self-service downloads.
• When there is no Internet access on client computers.
• To strictly control the versions of installed apps across your organization.
• To modify the update behavior in installed applications.

To create Managed packages using the Adobe Admin Console, you can do either of the following:

• Create pre-configured packages by using Adobe Templates.
• Create customized packages with the configuration and applications you want your end users to have.

At this stage, you must design the packages, make a list of packages, determine package counts, and decide upon a naming scheme for the packages. For information, see Planning packages.

There are several mechanisms to deliver app updates available to end users. Choose one of the following based on your organization's need.

Self-service

Users can download and install updates directly from Adobe. This method ensures that your end users have access to the latest updates when they become available. Updates can be downloaded and installed using the Creative Cloud desktop app or using the Adobe Updater included with the apps. For these workflows, the client machines require access to the Adobe servers and admin privileges.

This option is available for both self-service and managed app delivery.

Managed delivery

When you create packages, you can choose a managed update delivery mechanism.

• Have client machines install updates via an internal update server.
• Trigger updates remotely using Remote Update Manager. Use this option when client machines don't have admin privileges.
• Create and deploy Update only packages using Creative Cloud Packager.

For more information on managed delivery, see Applying updates.

After you've added an app to Microsoft Intune, you can assign the app to users and devices. It is important to note that you can assign an app to a device whether or not the device is managed by Intune.

Note

The Available deployment intent is not supported for device groups, only user groups are supported.

The following table lists the various options for assigning apps to users and devices:

Note

Currently, you can assign iOS/iPadOS and Android apps (line-of-business and store-purchased apps) to devices that aren't enrolled with Intune.

To receive app updates on devices that aren't enrolled with Intune, device users must go to their organization's Company Portal and manually install app updates.

Assign an app

1. Sign in to the Microsoft Endpoint Manager admin center.

2. Select Apps > All apps.

3. In the Apps pane, select the app you want to assign.

4. In the Manage section of the menu, select Assignments.

5. Select Add Group to open the Add group pane that is related to the app.

6. For the specific app, select an assignment type:

   • Available for enrolled devices: Assign the app to groups of users who can install the app from the Company Portal app or website.

   • Available with or without enrollment: Assign this app to groups of users whose devices are not enrolled with Intune. Users must be assigned an Intune license, see Intune Licenses.

   • Required: The app is installed on devices in the selected groups. Some platforms may have additional prompts for the end user to acknowledge before app installation begins.

   • Uninstall: The app is uninstalled from devices in the selected groups if Intune has previously installed the application onto the device via an 'Available for enrolled devices' or 'Required' assignment using the same deployment. Web links cannot be removed after deployment.

     May 26, 2020  Paintbrush: A one-to-one Paint alternative for Mac Of course, some people might find Preview’s hidden photo editor to be too complex.

     Note

     For iOS/iPadOS apps only:

     • To configure what happens to managed apps when devices are no longer managed, you can select the intended setting under Uninstall on device removal. For more information, see App uninstall setting for iOS/iPadOS managed apps.
     • If you have created an iOS/iPadOS VPN profile that contains per-app VPN settings, you can select the VPN profile under VPN. When the app is run, the VPN connection is opened. For more information, see VPN settings for iOS/iPadOS devices.

     For Android apps only: If you deploy an Android app as Available with or without enrollment, reporting status will only be available on enrolled devices.

     For Available for enrolled devices: The app is only displayed as available if the user logged into the Company Portal is the primary user who enrolled the device and the app is applicable to the device.

7. To select the groups of users that are affected by this app assignment, select Included Groups.

8. After you have selected one or more groups to include, select Select.

9. In the Assign pane, select OK to complete the included groups selection.

10. If you want to exclude any groups of users from being affected by this app assignment, select Exclude Groups.

11. If you have chosen to exclude any groups, in Select groups, select Select.

12. In the Add group pane, select OK.

13. In the app Assignments pane, select Save.

The app is now assigned to the groups that you selected. For more information about including and excluding app assignments, see Include and exclude app assignments.

How conflicts between app intents are resolved

A single group is prevented from being targeted for multiple app assignment intents, however if a user or a device is a member of multiple groups that are each assigned with different intents it will result in a conflict. Creating assignment conflicts for applications is not recommended.The information in the following table can help you understand the resulting intent when a conflict occurs:

Note

Microsoft Intune App Deployment

For managed iOS store apps only, when you add these apps to Microsoft Intune and assign them as Required, the apps are automatically created with both Required and Available intents.
iOS Store apps (not iOS/iPadOS VPP apps) that are targeted with required intent will be enforced on the device at the time of the device check-in and will also show in the Company Portal app.
When conflicts occur in Uninstall on device removal setting, the app is not removed from the device when the device is no longer managed.

Managed Google Play app deployment to unmanaged devices

For Android devices in a non-enrolled App Protection Policy Without Enrollment (APP-WE) deployment scenario, you can use Managed Google Play to deploy store apps and line-of-business (LOB) apps to users. Managed Google Play apps targeted as Available with or without enrollment will appear in the Play Store app on the end user's device, and not in the Company Portal app. End user will browse and install apps deployed in this manner from the Play app. Because the apps are being installed from managed Google Play, the end user will not need to alter their device settings to allow app installation from unknown sources, which means the devices will be more secure. If the app developer publishes a new version of an app to Play that was installed on a user's device, the app will be automatically updated by Play.

Steps to assign a Managed Google Play app to unmanaged devices:

1. Connect your Intune tenant to managed Google Play. If you have already done this in order to manage Android Enterprise work profile, dedicated, or fully managed devices, you do not need to do it again.
2. Add apps from managed Google Play to your Intune console.
3. Target managed Google Play apps as Available with or without enrollment to the desired user group. Required and Uninstall app targeting are not supported for non-enrolled devices.
4. Assign an App Protection Policy to the user group.
5. The next time the end user opens the Company Portal app, they will see a message indicating that there are apps available for them in the Play Store app. The user can tap this notification to be brought directly to the Play app to see corporate apps, or they can navigate to the Play Store app separately.
6. The end user can expand the context menu within the Play Store app and switch between their personal Google account (where they see their personal apps), and their work account (where they will see store and LOB apps targeted to them). End users install the apps by tapping Install in the Play Store app.

When an APP selective wipe is issued in the Intune console, the work account will be automatically removed from the Play Store app and the end user will from that point no longer see work apps in the Play Store app catalog. When the work account is removed from a device, apps installed from the Play Store will remain installed on the device and will not uninstall.

App uninstall setting for iOS managed apps

For iOS/iPadOS devices, you can choose what happens to managed apps on unenrolling the device from Intune or removing the management profile using Uninstall on device removal setting. This setting only applies to apps after the device is enrolled and apps are installed as managed. The setting cannot be configured for web apps or web links. Only data protected by Mobile Application Management (MAM) is removed after retirement by an App Selective Wipe.

Default values for the setting are prepopulated for new assignments as follows:

Note

'Available' assignment types: If you're updating this setting for 'available for enrolled devices' or 'available with or without enrollment' groups, users who already have the managed app won't get the updated setting until they sync the device with Intune and re-install the app.

Pre-existing assignments: Assignments that existed prior to the introduction of this setting are unmodified and all managed apps will be removed on device removal from management.

Intune Mac App Deployment

Next steps

Deploy Software To Mac Intune

To learn more about monitoring app assignments, see How to monitor apps.