With 1610, the Cloud Management Gateway feature arrived. Although it's a Pre-Release feature, as Cloud Solution Provider we're UNABLE to use/implement this. And so are our customers...!

When you try to set this up from the ConfigMgr console, a prerequisite is the Azure Management Certificate, which can't be configured as CSP-tenant because this needs the Classic Azure Portal (ASM). This is unacceptable for us, as CSP, as we would have to instruct our customers to get an Azure Subscription separately.

https://blogs.msdn.microsoft.com/cie/2016/11/28/azure-management-certificates-and-publishing-setting-file-with-csp-subscriptions/

As more and more devices are shipping without wired network adapters, and more business areas are going "wireless only," the traditional ability to reimage a device in place is getting scarce. This is especially true in primary and secondary education institutions.

Please provide support for adding Wireless drivers to WinPE, and the ability to provision wireless network profiles for the WinPE phase of the task sequence to enable imaging over wireless network connections.

When working with multiple customers and/or in migration scenarios (and also in lab- technical preview environments) it would be great to be able change the color scheme in the ConfigMgr console to clarify which environment the console belongs to.

Would be nice to be able to advertise Task Sequences to specific users or groups. We have some operating system deployments that we would like only certain users to run, support staff for instance.

Add the complete progression status in the progress bar in order to see the current step and remaining steps.

Like in this post http://www.systanddeploy.com/2018/02/add-complete-progression-sta

Please update the software distribution troubleshooting flowcharts. https://technet.microsoft.com/en-us/library/bb932214.aspx?f=255&MSPPError=-2147217396.

Change default "sort by" order from "Most recent" to Alphabetic list (Application name A-Z). Or remember the setting for the client. Or allow a SysAdmin setting for site-wide default setting. It always resets back to Most recent.

Configuration Manager should be able to configure all aspects of a workstation that can be done using other Microsoft tools. Some group policy items already exist such as folder redirection and Firewall Policies. It would be great if Firewall could be expanded to include creation of firewall exceptions. It would also be great if we could configure all group policies from within SCCM perhaps using compliance settings.

We would like the Client Upgrade feature to allow the client to be upgraded outside of maintenance windows but also give the option to only install when no user is logged in, like deploying Applications allow.

Support SUP/ESD/WSUS/update-based packages via the "Upgrade Operating System" task sequence step so that task sequence-driven upgrades can benefit from the smaller size of the ESD files (2.5GB) compared to the full media used today (3.5GB).

ConfigMgr supports .appx deployment, but sometimes we want these on every machine, so our preferred way would be to do this in the Task Sequence.

Currently, the Add Application step in the Task Sequence doesn't let us browse for .appx packages.

Please consider adding support these during OSD.

The ability to exclude a single or multiple updates with a simple Right Click > Exclude or Menu item.

Enable easier integration with partner products or have the ability to pull down 3rd party catalogs.

Add an column to the devices view that would display Active Directory descriptions in console.

Allow packages to be deployed to multiple collections at one time. For instance I need AppX to go to Lab 1, Lab 2 and Lab4. Instead of going into AppX 3 different times to deploy, it would be nice to deploy it to all 3 labs at one time.

I would like to see ADR's support the creation of Available deployments in addition to Required deployments. We have some business cases where a certain subset of servers are aren't allowed to "push" software updates to until the server/app owners have verified the patches.

The issue is that these servers don't have connectivity to the internet so we have to deliver them via ConfigMgr. By creating an Available update using an ADR, it streamlines our ability to "deliver" the updates to all systems, and allow the Patching Team, or App/Server owner to patch according to their own business schedules.

Beginning with 2012SP1, we have the ability to add a CAS to an autonomous primary site. It could be interesting to reverse the proposition by having the ability to remove a CAS above a Primary when a CAS is no longer needed or has been set for a wrong reason.
I know that it could be done through creating another hierarchy and using migration tasks by this is quite difficult for it requires additional hardware.