Hi CaseyB , There is a list of improvements that we are investigating to improve many aspects of the Company Portal including what you've characterized above. At this time, these have not yet been prioritized though and thus there's nothing additional to share on this. Please submit feedback on this item directly in the Intune console or using the Microsoft Feedback portal at Microsoft Intune · Community. 

If you are using Intune for Feature Updates, our Autopatch documentation will guide you through creating Feature Update phased rollouts, Windows feature updates overview | Microsoft Learn  In terms of what's not working, it will be difficult for us to diagnose through this forum. But some things you can check - if the devices are in scope of the policy but do not report any status back, it's possible the devices current have a safeguard hold in place that prevents the feature update from being offered to them. If the feature update should encounter an error while processing, that should show up in reporting in Intune in the Feature Update Policies with Alerts. 

Hi there, so if you are trying to update to the latest feature update version via Intune there are a few reasons this may not be working: 

1. Policy conflict (make sure you have no leftover policies from Configuration Manager, Group Policy, etc. that could be causing conflict)
2. Safeguard holds Safeguard holds for Windows | Microsoft Learn which should go away automatically 
3. If moving from Windows 10 to Windows11, in addition to the deferrals, you will need to select target product version = 11, you can do this via the "Windows 11" toggle on the rings page or via Settings Catalog. 

Hope this helps, let me know if you have any additional questions! :)

Windows Autopilot device preparation is not a set of policies, it is a whole new profile type that changes the nature of Autopilot. It is separate and distinct from the original Windows Autopilot profiles (user driven, pre-provisioning, and self-provisioning). It is not a full replacement for the original Windows Autopilot profiles (today at least) but can be useful for certain scenarios including GCCH/US Government and assigning Autopilot to users instead of devices without pre-registering the devices. Windows Autopilot device preparation is a work in progress though and we plan on adding a lot of new capabilities to it in the near future. Check out Skilling snack: Windows Autopilot device preparation | Windows IT Pro Blog for a lot more info.

Note that today, you cannot use a custom name for devices with Windows Autopilot device preparation but this is something we've investigated adding.

You should be able to apply a template: https://learn.microsoft.com/en-us/autopilot/profiles 
(requires Microsoft Entra join type): Select Yes to create a template to use when naming a device during enrollment. Names must be 15 characters or less, and can have letters, numbers, and hyphens. Names can't be all numbers. Use the %SERIAL% macro to add a hardware-specific serial number. Or, use the %RAND:x% macro to add a random string of numbers, where x equals the number of digits to add. Only a prefix can be provided for hybrid devices in a domain join profile.

The advantage is essentially saving time and automating deployment processes.

BenYasika You should work with your Microsoft account team, the device may need a device license. Here is the guide Overview for Windows Autopilot self-deploying mode in Intune | Microsoft Learn

The additional resources section at the bottom of the Learn docs at Get started with Intune for Education - M365 Education | Microsoft Learn offer a lot of great guidance that should get you going.

The guide at Require MFA for all users with Conditional Access - Microsoft Entra ID | Microsoft Learn should get you going. Additional, make sure that you leverage the templates that we created and detailed at Simplify Conditional Access policy deployment with templates - Microsoft Entra ID | Microsoft Learn.

HeyHey16K If you can confirm you are not seeing the request in Intune it would best to contact Microsoft support.

There is device-based licensing available for both Intune and Windows. Also, if needed, there are several ways to license Entra ID P1 (for the auto logged in account). It's best to work with your Microsoft or partner account team to validate the appropriate combination of licenses for your specific scenario.

For the Intune Connector for Active Directory, round robin is always used to attempt to "proxy" the ODJ blob properly to the proper domain. Whether a specific instance of the connector can successfully do this or not depends on the permissions of the MSA account. This is effectively no different than the behavior of the old connector.

Ultimately, our recommendation and guidance here remains the same though: Entra join should be used with Autopilot to provision new devices and hybrid join with Autopilot is best avoided.