We hear this request a lot, so I'm adding it here.
ConfigMgr integrates with many Microsoft Cloud Services:
* WUFB
* WSFB
* Windows Upgrade Analytics
* OMS
* etc
For each of the above services, sometimes a company may have multiple tenants. Please allow ConfigMgr to manage multiple tenants for each of these services.

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/

Allow the recurrence pattern for maintenance windows to be scheduled with an offset from a base day.

Meaning, if we want a maintenance window on the Wednesday following the Second Tuesday of every month, we could configure a maintenance window for the Second Tuesday with a +1 offset.

(This would be similar to the offset option added to ADRs in 1802.)

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.

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.

The new Software Center in 1511 should also categorize Applications using the user category even if it is not deployed to users but systems instead. It should reflect the user category no matter what.

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.

After a user installs an application that was deployed as "Available", but later uninstalls the application, the user gets a balloon pop-up every time they logon saying "New software is available".

There is NO way to prevent this from happening apart from removing the user from the collection where the application was deployed, and adding them back. This has been the case since CM12 was released but this is not a desirable behavior especially when there's no "valid" way of preventing this.

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.

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.

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

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).

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.

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

There is the ability to specify dependencies for Applications, however the ability to run another Application POST install would be awesome. Often when an application is installed there is a post configuration task that needs to run.

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