Blog

No one, and I mean no one, really wants to manually and individually assign Mobile Apps to Users or Devices in Intune, especially after you’ve happily used a script to Approve Managed Google Play Apps in their 100’s as part of migrating to Microsoft Intune from other below par Mobile Device Management solutions.

I’m not going to go over old ground in too much detail, as I’ve already covered the importance of keeping your Operating System Compliance Policies up to date in line with the release of new updates, as well as a way to update your compliance policies using Graph and PowerShell.

Now that you’ve made the financial sensible decision to migrate to Microsoft Intune for your Apple device management needs, you’ve got your Apple Push Certificate, sorted your Enrolment Token, added Intune as an MDM provider, and now you’ve got all your iOS/iPadOS devices happily sitting synchronised in Intune waiting to be deployed using Apple’s Automated Device Enrolment.

Nothing has really changed in the Hybrid Join Autopilot space when it comes to device names, and we’re still stuck with useless naming conventions for these devices; sometimes a prefix and random characters just isn’t a good enough identification method for Windows devices.

Have you ever had the pleasure of migrating Configuration Manager clients from one domain to another, or maybe between Configuration Manager environments? Tired of manually reinstalling the client from the Console?

So it turns out that Android based MTR (Microsoft Teams Rooms) want to enrol into Microsoft Intune using what we generally term as a legacy enrolment method in Android Device Administrator, one in fact, that is recommended to be disabled for ‘All Users’ as it will take priority over Android Enterprise Personal Device Work Profile enrolment for personal device or BYOD (Bring Your Own Device) scenarios.

With the impending retirement of the Azure AD Graph API and ADAL authentication methods, and by impending, I mean the end of 2022, we should probably look at how we move away from the existing authentication methods I’ve been using in all of my scripts and into the new realms of MSAL (Microsoft Authentication Library).

So one of those rainy days is here, finally, and as I mentioned in a previous post many months ago, I said I’d look at ways to update other update based compliance policies periodically.

We’ve all had to add Managed Google Play Apps in bulk to Microsoft Intune for your Android Enterprise enrolled devices, whether this is just the raft of Microsoft Apps now that all your data is in Office 365, or the hundreds you have in a rival MDM (Mobile Device Management) solution that you’re looking to migrate away from.