Provide support Configuration Manager(CM) with Azure AD DS, which is no require patch management than AD in Azure IaaS. This simplifies our cloud operations. As described on following site, the managed domain of Azure AD DS is listed as compatible with Windows Server Active Directory.

https://docs.microsoft.com/en-us/azure/active-directory-domain-services/join-windows-vm

As MEMCM supports a number of virtualized environment namely Hyper-V, it would be ideal if support is extended to Azure Stack Infrastructure.

We recently had a scenario where someone at customer end deleted the Client/Native App from Azure AD stopping Azure AD Token Authentication from working. Clients were not on VPN and no PKI Certificates for Authentication.
It seems like there is an unsupported way to manually edit SQL DB to re-import a new Client App, but it would be nice to have a supported option with so much CMG adoption lately and the dependency it creates for remote management.

After enabling the collection of 3 attributes from the win32_process WMI class from our PCs, the database blew in size, as all other (30+) attributes of that class take up as much disk space as if they had data in them.

It would be lovely to not rely on SMB for inbox and outbox operations since these are very fragile in high latency environments. Changing this to a webservice would be so much like year 2020 technology.

When enabling Maintenance Mode on a DP it would be handy to specify a "end date" for it to automatically come out of MM on.

In addition, if there was a way to put a comment when setting MM to record why it was set.

The support for Dedup for the content library is fantastic. It would be great to extend this support for content sources as well.

It would be nice to have a checkbox like we have for deployments to pause SCOM agent on DPs when setting them to maintenance mode.

Technically, all DP configurations are done by DistMgr, so it should be possible to update it with re-used code from the client functionality.

Rename Software Inventory to Software File Inventory or something related to File Inventory

The current MEM evaluation lab kit expired on February 7, 2021. When will it be updated? I downloaded and installed it just days before its expiration. So how much longer can I keep evaluating it? This isn't documented very well.

https://www.microsoft.com/en-us/evalcenter/evaluate-mem-evaluation-lab-kit

During the BitLocker user portals setup, the database server name is supplied which the portals use to connect to for key recovery. BitLocker portals do not have a fallback mechanism. If you have an SQL AO configuration, you need to install a second portal so you can still use the recovery functionality bur you also need to notify every admin user to switch...Not really convenient.

Whenever a user deletes a status message, there is no record of this within SCCM (SMSProv.log file gets overwritten fairly quickly). I would like to see a new audit status message get created, whenever a status message gets deleted (showing who deleted the status message). This will leave some sort of trace whenever someone deletes a status message.

Standardize releases of SCCM Versions to twice a year instead of the current frequency of three times a year 2002, 2006 and 2010 and so on.

Please review the pattern of windows feature releases and a clear timeline on supportability for SCCM.

Please give a road map of supportability whether or not the customer has moved to co-management or not

SCCM Client Version supportability in line with Server Version. All these three may be clearly documented please.

Currently it is rather cumbersome to use PKI-issued certificates in many places of ConfigMgr infrastructure (especially DPs), and aoutomate them. ConfigMgr acts as a CA and issues its own certs without any admin control - maybe letting us set it up as a subordinate (to the one probably existing in many companies) CA would solve the issue? Any other ideas?

Bring back the option to change the retention period. The retention days will revert back to the default of 1095. We are not aware of separating a retention date for a cloned CAS database from the actual production CAS database.

Modify the Configuration Manager prerequisites checker to look for supported Windows ADK version

currently all file system operations only accept filepaths with maximum length of 256 chars which is related to the used .NET Framework within CM.
Starting with .NET 4.6 this limitation is now raised to 32.767 chars which is very usueful if you for eample manage driver and driver packs, applications and so on per script and file systems within a domain network. (Servernames FQDN could be longer than 8 chars in our case at minumum 30 chars)