Configurations will vary across environments, and there is some nuance to what these setting mean. Interactions between 3rd party deployment consoles and device settings as well as managed and personal files can be complex. The following table lists only those features provided by DC Acrobat Reader. Your vendor console may provide a number of configuration options. DO NOT try to consume the XML file.Ĭomplete the policy configuration workflow. Open the XML file, and copy each of the needed values shown below into your vendor’s policy console (see the table below). In both cases, files can either be personal (unmanaged) or work (managed) depending on their origin.ĭownload Acrobat Reader (the latest version is always recommended).ĭownload the latest XML definition file (above).Ĭreate a device or application configuration policy. The settings described here behave differently when applied in MDM or MAM configuration policies. There is no method for an admin to pre-enable this user setting. OneDrive).Įnabling Intune ahead of time is unneccessary. Users can manually enroll via the **Intune MAM* preference or let Acrobat auto-enroll when the user adds the admin has specified as managed (e.g. On iOS, admins also have another option: Adobe preferences allow end user Document Cloud and Dropbox accounts to be individually treated as managed or unmanaged. Admins can still control files (PDF data) across work and personal in the same way as MDM: simply allow or prevent opening unmanaged files in a managed environment. In this context, the enterprise cloud storage account resides in the “managed” category while the personal account resides in the “unmanaged” category. For example, while an organization would be aware of Dropbox and Document Cloud accounts accessed via an enterprise ID, a user may also have personal cloud storage accounts associated with private, personal IDs.
#ADOBE ACROBAT PRO FOR MAC IOS PDF#
Managing data across PDF workflows is more challenging since a user may have personal files and file storage locations in addition to enterprise files and approved locations on a single device. In Mobile Application Management (MAM) scenarios, the organization may choose to control some applications and file locations and not the user personal apps and files on the same device. If the device is not enrolled, there are no restrictions. The high level behavior is simply this: If the device is enrolled, restrictions derive from the admins XML configuration file choices. It is possible for an admin to use both MDM and MAM, in which case the setting may have an effect, but that scenario is less common. The Intune MAM preference in the Acrobat app is not related to MDM and typically will have not effect. If the user’s device is enrolled in Intune, then Acrobat is also enrolled. Users enroll their device via the Microsoft portal app. For example, a user might access their personal email account via the device browser, and whether or not an attached PDF will open in Acrobat Reader may depend on the admin allowing Acrobat to open unmanaged files in a managed environment.
Managing the flow of data in PDF workflows often involves specifying whether operations from an unmanaged source can be moved to a managed source and vice versa.
Organizations that use Mobile Device Management (MDM) can control the device as well as installed applications and file storage locations. Files can either be managed or unmanaged, and you can also control how these files move from one state to another in a way that complies with your organization’s security policies. Acrobat’s support for Intune means you can pro-actively manage files and features on both iOS and Android. As one of Microsoft’s Azure cloud based services, it supports app management via policies, reporting and alerts, and other essential enterprise tasks. Intune is Microsoft’s EMM solution that provides both MDM and MAM.