Concerns about Jamf Pro Azure AD Connector Permissions

New Contributor

We recently began looking into configuring Azure AD as the Cloud Identity Provider for our Jamf Pro environment. The setup went smoothly in our dev environment and we've successfully been able to read user and group information, but we have some concerns because we noticed that the Jamf Pro Azure AD Connector application has a delegated permission to Microsoft Graph to access our Azure AD "as the signed in user", in addition to the expected "Read user profile" and "Read directory data" permissions. My understanding is that Jamf only ever needs to read data from Azure, why is this permission needed, which would theoretically allow Jamf to make changes to our Azure environment? 17fd9eb0d08b41f984b9b69ca48d6556