![]() ![]() This is something you’d need to do if you had a requirement to link two or more Jamf Cloud instances to the same Azure AD tenant.Īfter some calls with Jamf Support, it’s as simple as hitting the edit option under “Settings” > “Global Management” > “Conditional Access”, selecting the “Cloud Connector” option, and following the rest of the steps to set this up (don’t forget the documentation here). Lastly little snippet of things to share is regarding migrating from the previous manual Intune* connection, to the new Cloud Connector. Migrating from the Manual Intune Connector to the Jamf Cloud Connector ![]() I tweeted about this shortly after seeing it, but realised how difficult it would be to explain in a Tweet! I can only imagine that the first Jamf Pro server (instance “A”) was still sending data into Intune* and this was holding some sort of partial record in Azure I couldn’t get access to. After a few minutes, the registration worked fine. In the end, the resolution was to remove the old device record from the first Jamf Pro server (Jamf Pro instance “A” above). This same behaviour was repeated when I re-ran registration, wiped and re-deployed the device, and also after removing the device from Azure AD (and waiting the 30-60 minutes for things to settle down). Shortly after which Self Service / Jamf AAD popped up a message to say that device registration failed due to the user closing Company Portal too soon. I selected the “done” button and Company Portal closed. The Company Portal launched as normal, but showed the “This device is already registered” message. All worked fine, until it came to the Intune* registration. I then wiped the test device, and enrolled and deployed this on Jamf Pro instance “B”. I enrolled and deployed the test device on Jamf Pro instance “A”, and registered this with Intune* – no problems. I was using the same physical device when testing the Intune* connection on both Jamf instances. The next thing I came across was in testing enrolments between multiple instances. Work side by side with your Azure GA to enter their credentials at the Azure screen/s as required (not always ideal in a COVID world!).Apply to get (temporary) Azure GA for your Jamf administrator, and set everything up.Give your Azure GA admin access to the Jamf instance/s to set everything up. ![]() With this new Jamf Cloud Connector method, there’s less manual tasks, however there is a number of browser redirects back and forth meaning you can’t just send the Consent URL to be approved (or at least I haven’t found a simple way). This method was handy if you were in a situation where your Jamf administrator wasn’t an Azure GA, and your Azure GA wasn’t a Jamf administrator. They could approve this, complete the setup their side and all worked well. ![]() What do I mean by that? Well, with the previous manual setup, you could configure the Jamf Pro side, then grab the Consent URL for your Azure Global Administrator (GA) to approve. With the background out the way, I’ll share some of the odd bits and pieces I’ve seen in testing so far.įirst thing I noticed with the Jamf Cloud Connector method, is it’s no longer possible to ‘just’ pass over the Consent URL to your Global Administrator (or equivalent) as before. It’s also worth noting at this point that the previous manual method is still an option (and the only option if you are not hosted with Jamf Cloud). The initial setup process (the Jamf Pro to Intune* connection) is also a little easier than the previous manual method. Jamf documentation on this can be found here. This is the only method to link multiple Jamf Pro instances to a single Azure AD tenant! This is limited to Jamf Cloud customers only (no on-premise or 3rd party hosted options at this time I’m afraid) and, amongst other things, allows you to connect multiple Jamf Pro instances to a single Azure AD tenant for the Jamf Pro / Intune* device compliance solution. The Jamf Cloud Connector is a new feature added to Jamf Pro a few months back. This is a mixture of a few smaller things I’ve seen in testing that I’d not seen written up anywhere and thought it’d be worth sharing.įirst up, What is the Jamf Cloud Connector? Migrating macOS Devi… on Migrating macOS Devices from o…ĭazwallace on Moving devices from Adobe Shar…įor this post, I thought I’d share a mixture of things in and around Jamf Pro, the Intune* integration, and the new Jamf Cloud Connector. Richard Glaser on Changes to Docker Desktop for… Stephan Peterson on Submit Jamf inventory update o… Submit Jamf inventory update on OS changesĭeploying Docker Des… on Changes to Docker Desktop for….Speaking at London Apple Admins for Beginners.Re-homing your Mac Admin – MacAD.UK 2023. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |