With more and more devices being connected to azure AD, SCCM should have an option to perform a zti deployment and join the newly deployed Windows 10 to azure AD only. not hybrid where GPO needs to exist, but a native support where the connection to SCCM already exist but the computer will not be connected to the onprem domain.

Add a step or option to a task sequence that will dump any SMS logs to a predefined location, either a network share or USB drive.

It is a total PITA to watch every machine as a TS runs so we cant always copy the logs off before the machine automatically reboots.

Application A and Application B. Application B supersedes Application A. The content is removed off the DPs for Application A.. A task sequence (non-OSD TS) deployment of Application B fails with "The software could not be found on any servers at this time." After reading the logs, it is looking for Application A. BUT a regular application deployment Application B, it works fine, so this issue is ONLY occurring in TS.

It would be great if the created application groups can be added in a task sequence.

Instead of having long lists in a task sequense you could manage default apps in the application groups

I would like to add setting of LayeredDriver (106/109 key, etc.) during OSD (OS deployment).
These settings are "very important topics" for OSD guys in Japan and Korea.
Without this setting, the keyboard will become an English keyboard.

LayeredDriver [Microsoft Docs]
https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-international-core-winpe-layereddriver

We have the possibility to select to "Access content directly from the DP" when deploying a operating System image in a Task Sequence. It would be great to be able to do this for "Run Command Lines" as well.
Example scenario, you want to run a Powershell script from a package before the disk is formatted in a scenario where we use Bitlocker for instance.

Please add support for cloud imaging without a local MP, meaning get all content for OSD, including policies from the CMG.

It would be convenient to have a method to enter/save your volume licensing credentials to have it directly download an iso from the volume licensing site, extract the wim into a designated storage location, and then import it directly into the console. This would especially be nice considering the more frequent release of new Windows 10 builds. I like running my B&C from the newest image available.

Provide Mac Provisioning with CM12.

Other vendors provide the ability to image and fully manage the Mac device, when will Configuration Manager provide this feature? Imaging Windows platforms is only part of a corporation desktop landscape, we also support Mac, having a single solution would make logical sense.

We have many task sequences, sorted into folders for multiple users, when it comes to archiving them, it's tedious, we'd like to archive multiple task sequences by user (or by folder), this would be great, right now you have to export one task sequence at a time which is tedious.

Please make Task Sequence somehow use Global conditions for better usability and experience. This would help tremendously in every situation for TS deployments, especially for using Preflight checks, which is becoming more and more critical for most deployments and upgrade tasks.

Provide a better way to support preflight checks for OS upgrades in terms of success/error being shown to users. Being able to show users a warning sign instead of a hard stop error would give better user experience. Currently, we either get "Installed successful" message, with having continue on error checked, or hard stop or scary error message that's presented to users if requirements aren't met. Everyone uses preflight checks now for OSD, please support it better with better notifications (customized) and error/warning handling.

It would be useful to integrate AD authentication in the WinPE boot image for PXE boot OSD.

When deploying operating systems with MDT and WDS, users are prompted to authenticate against AD when PXE booting. However, in SCCM the only supported way to secure the PXE point is with a DP password that all users share.

There are third party "hacks" which can integrate AD authentication in the WinPE boot image (Johan Arwidmark's ADSI drivers) but it seems like this would be simple to implement within the product itself since it is already done in MDT/WDS.

Use the value from the built-in variable SMSTSRebootDelay for reboots that occur during the 'Install Application - Install applications according to dynamic variable list' step. This would reduce the time for OS deployments.

While a Step for Run Command line can be used for most Windows Installer, if an application uses a EXE it would be nice for the application to be downloaded and the exe used.

Having version control for Task Sequences would be invaluable.

If we could link a GitHub account we could easily monitor Task Sequence changes either in Github or SCCM. The ability to roll versions with Administrator approval (similar to publishing scripts) would be ideal.

Expanding on this idea more, highlighting additions/edits/deletes within the Task Sequence dialog would be the icing on the cake.