@Steve, Thanks for posting in Q&A. For MDM only enrollment device, this enrollment method isn't recommended because: It doesn't register the device into Azure Active Directory (AD). Users might not get access to organization resources, And Azure AD features will be prevented to use.
Based as i know, Expedite Windows quality updates, Feature update policy and some new windows update policy needs Azure AD join or Hybrid Azure AD join. And it will not support on the devices with MDM only enrollment.
https://learn.microsoft.com/en-us/mem/intune/protect/windows-10-feature-updates
https://learn.microsoft.com/en-us/mem/intune/protect/windows-10-expedite-updates
For application, win32 needs the device in Azure AD as well: So it is not supported on this enrollmetn method either
https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-app-management
I also find some other feature like Powershell script is also not supported
https://learn.microsoft.com/en-us/mem/intune/apps/intune-management-extension
For configuration policy, most can apply. And we will assign it to the device group.
https://learn.microsoft.com/en-us/mem/intune/configuration/device-profile-create
For compliance policy, it can be used.
https://learn.microsoft.com/en-us/mem/intune/protect/create-compliance-policy
When the AD connection is lost, but the Internet connection is OK, the device can still contact Intune, the device will still check in to receive policy, I think. This is not related with the AD user profile on the device.
Hope it can help.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.