#Jamf and azure ad install
#Jamf and azure ad manual
#Jamf and azure ad pro
#Jamf and azure ad software

Remove a manually configured Jamf Pro integration If you have not previously set up a connection between Jamf Pro and Intune, or if you've one or more connections that already use the Cloud Connector, skip this procedure and begin with Configure the Cloud Connector for a new tenant. Use the following procedure to remove a manually configured integration of Jamf Pro from your Azure tenant before you can configure the Cloud Connector. Remove the Jamf Pro integration for a previously configured tenant

Microsoft Intune admin center: Global Administrator.

Jamf Pro console: An account with permissions to manage Jamf Pro.

Procedures in this article require use of accounts with the following permissions:

#Jamf and azure ad software

TCP and UDP ports used by Apple software products on.Intune network configuration requirements and bandwidth.The Apple 17.0.0.0/8 block over TCP ports 5223 and 443 from all client networks.įor more information about these ports, see the following articles:.The following ports and endpoints must be accessible for Jamf and Intune to integrate correctly:Īpple: Ports 2195, 2196, and 5223 (push notifications to Intune)įor APNS to function correctly on the network, you must enable outgoing connections to, and redirects from the following ports:

macOS devices with OS X 10.12 Yosemite or later.A Jamf Pro user account with Conditional Access privileges.

#Jamf and azure ad manual

Be sure to configure the Cloud Connector within 24 hours of removing your manual integration to ensure your registered devices can continue to report their status.įor more information about the Jamf Cloud Connector, see Configuring the macOS Intune Integration using the Cloud Connector on.Devices that are already registered can use the Cloud Connector without further configuration. You won't need to re-register devices.Then you can use the procedure to configure the Cloud Connector. Use the procedure to remove your current configuration, which includes deleting the Enterprise apps for Jamf Pro and disabling the manual integration.If you plan to replace your previous integration with the Jamf Cloud Connector: Both the removal of an existing integration and setup of the Cloud Connector are described in this article. For tenants that already have a manual configuration, you can choose to remove that integration, and then set up the Cloud Connector.Or you can manually configure integration as described in Integrate Jamf Pro with Intune for compliance For new tenants that don't yet integrate with Jamf, you can choose to configure the Cloud Connector as described in this article.When you use a manually configured connection, only a single instance of Jamf can integrate with an Azure tenant. You can integrate multiple instances of Jamf Pro with the same Azure tenant that hosts your Intune subscription.Ĭonnecting multiple instances of Jamf Pro with a single Azure tenant is supported only when you use the Cloud Connector.

Set up automatically creates the Jamf Pro applications in Azure, replacing the need to manually configure them.

We recommend use of the Jamf Cloud Connector as it automates many of the steps that are required when you manually configure integration as documented in Integrate Jamf Pro with Intune for compliance. Resource access is controlled by your Azure Active Directory (Azure AD) Conditional Access policies in the same way as for devices managed through Intune. Through integration, you can require that your macOS devices that are managed by Jamf Pro meet your Intune device compliance requirements before those devices are allowed to access your organization's resources.

#Jamf and azure ad install

This article can help you install the Jamf Cloud Connector to integrate Jamf Pro with Microsoft Intune.