The display name for the configuration must be unique. You are redirected to the administrator consent page in Microsoft.Įnter your Microsoft Azure credentials and follow the onscreen instructions to grant the permissions requested by the Jamf Pro Azure AD Connector application.Īfter the request completes, in Jamf Pro configure the settings on the Server Configuration tab. In the top-right corner of the page, click SettingsĬhoose Azure and click Next. To disable the connection, use the switch. This means you can add a different configuration without deleting the current connection. Disabling the connection prevents Jamf Pro from querying data from this server. You can configure multiple connections and choose which configuration to use. When a server connection is added, it is enabled by default. For information on how to configure SSO in Jamf Pro, see Single Sign-On.Ĭonfiguring an Azure AD Identity Provider Connection Single sign-on (SSO) with Azure must be configured in Jamf Pro to use authentication workflows (e.g., user-initiated enrollment and logging in to Jamf Pro). ![]() When working with LDAP-specific workflows, (e.g., adding scope limitations and exclusions), Azure AD cloud identity items are listed under the LDAP headings. Accounts and groups added in Jamf Pro must be the standard type. User groups added in Jamf Pro have the same name as groups configured in Azure. Your Azure AD privileges (e.g., Global Administrator) allow you to manage consent requested by the Jamf Pro Azure AD Connector app. Your Jamf Pro instance needs to be hosted in Jamf Cloud. When integrating Jamf Pro with Azure AD, consider the following: Adding the Azure AD integration prior to migration may break your environment. To ensure your existing LDAP workflows (e.g., scoping or user accounts and groups) continue to work correctly, you will need to migrate your configuration when the migration assistant is available in a future release of Jamf Pro. Important: If Jamf Pro already integrates with an Azure Active Directory Domain Services or Microsoft’s Active Directory LDAP configuration that you plan to migrate to an Azure AD instance, do not add this Azure AD instance as a cloud identity provider in Jamf Pro.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |