A button of some sort to grab all the drivers that "needs remediation" or after you have reviewed all the drivers right on the DA azure site.

We are trying to migrate from Win 10 1809 to 1909 and while checking compatibility details software like Symantec End Point protection, Cloud Strike and others are showing compatible however while running actual upgrade, we could see SEP and Cloud Strike blocking the deployment.

Same behavior we have observed with Win 10 1909 to Win 10 20H2.

I've noticed, that once certain version of Windows goes out of support, it's marked red in the adoption chart on the whole timeline instead only from date it's support ended.

As if this version was out of support also few months ago.

I would suggest to show such devices as "red" only from date when they are actually out of service.

For the current setup it is only possible to have one pilot collection from DA. It would be cool if you somewhere at the prepare phase could pick number of pilot rings. That way you can have somewhat a more "secure" deployment flow for your updates if anything would go wrong.

Why have you not implemented a search feature in Desktop Analytics?

I want to add a selected device to the pilot group but do not want to manually search for it over 233 pages to find one single device.

When will the Desktop analytics be available for Intune , It was shared in Ignite 2019 that it will be supported however don't see any update

On the main application Identify importance page, add columns with drop downs so that multiple applications can be reviewed at once without needing to open the app blade.

When reviewing applications it is more efficient to leave the App versions details turned off but when an app requires a more in depth look turning this on causes the current view to be reset.

It would be nice if when you are viewing an app in the blade there was a slider that when enabled showed all the versions with their details.

When editing particular apps, you can select maximum all apps displayed in one page which is 15 apps at once (no more). This is very time consuming considering thousands of applications inventoried.

In addition, it would be suggested to clearly described which attributes are mandatory to be filled in before we can move to pilot phase (importance, owner, upgrade decision)?

In addition, it is not possible to add column "upgrade decision". This would help as well as add possibility to search for Owner in Azure AD.

Like in Windows analytics, is it possible to get the information (dashboard) of the device provisioned and authenticated using Windows Hello for Business Framework in Desktop Analytics

Under Plan Assets it may say "there is an alternative version of this app..." but the only place to find which version is under Monitor Health". Please make the information also under Plan Assets, etc.
Adopted version available

"There is an alternative version of this app which is highly adopted or adopted on other commercial devices according to Ready For Windows. You can consider deploying the alternative version if there are any upgrade blockers."

We need the ability to modify lists to show more than 15 items at a time. Allow user to increase that to a set of values (25, 50, 100, all?) so we don't need to scroll through 50+ pages of applications to review for Desktop Analytics Deployments.

DA is able to create pilot collections in MECM for us. However it would be good if DA could break the pilot collections down into smaller collections.

This would mean that we could deploy a FU to a percentage of devices identified for pilot rather than the whole collection (or need to figure out a manual way to break the Pilot collection up into smaller chunks)

Deploying to the entire pilot collection could result in hundreds of machines with a particular application failing and requiring regression. Smaller target collections would help to build confidence

Add the ability to refresh the dashboards of Desktop Analytics manually from the portal.

Under the apps view in addition to version it would be useful to see the bitness of the app versions. For example if your doing a migration from a 64 bit app to be able to track and monitor the cleanup or target for cleanup. For example we have had a lot of Teams 32-bit getting installed and we don't want any 32-bit Teams in our environment and block it via GPO but they keep getting installed.

Under a Deployment plan, in the Identify importance section, The 'App versions details' slider switch, currently seems to hide non-standard versions from being visible. Editing with this option off, does not address all discovered 'Noteworthy Apps'.

I believe this switch should instead group all versions together, and apply the same actions to all versions found, then you can slid the switch on, and change an individual version if needed. instead of just skipping applying any settings to the hidden items, which is the current behavior.

It would be nice to be able to create deployment plans using powershell. The manual process of creating individual deployment plans via the portal is time consuming, and when working with the need for multiple deployment plans targeting different collections this becomes a cumbersome process. I can currently create and populate all of my collections via powershell, but I then have to manually create each individual deployment plan.