Please Include KB Numbers in the Intune Expedite Policy Update Dropdown

Hi Intune Team,

Currently, it's difficult to identify and differentiate between Out-of-Band (OOB) updates when using the Expedite installation of quality updates feature in Intune.

For example, two OOB updates were recently released to address issues related to the Windows 10 BitLocker recovery screen and the other is related to a Windows 11 issue. However, when reviewing the available updates in the expedite policy dropdown, it becomes challenging for admins to determine which specific patch to deploy, especially when relying only on the OS version listed.

To improve clarity and avoid confusion, I recommend displaying the corresponding KB numbers alongside each update in the dropdown menu. This would make it significantly easier for admins to identify and select the appropriate updates for deployment.

Please find the example below; this is the kind of functionality I'm expecting.

Select the quality update you would like to Expedite:  09/23/2025 - 2025.09 D Update for Windows 10 and later - KB50XXXXX, (KB details needed for OOB updates as well)

Feedback submitted: https://feedbackportal.microsoft.com/feedback/idea/0ef40fc7-503e-f011-a2da-000d3a05d8a6

Intune Admin Center Allowing Duplicate Policy Names - Needs Attention

In the Intune Admin Center, including Configuration Profiles, Compliance Policies, Endpoint Privilege Management (EPM) Policies, PowerShell Scripts and Remediations, Windows Autopilot Device Preparation, and Windows Autopilot Deployment Profiles, etc., I observed that the portal currently allows duplicate names for policies and profiles.

For example, I'm able to create two Settings Catalog profiles with the exact same name, such as "ABC", even when the settings configured were identical or overlapping. This behaviour is consistent across other configuration types as well. This issue is affecting all device platforms (Windows, iOS/iPadOS, macOS, Android).

In my opinion, Intune should prevent duplicate names for better management, clarity, and to reduce the risk of confusion or misconfiguration, especially in environments with multiple administrators. A unique name validation mechanism would enhance usability and help maintain policy hygiene.

Feedback submitted - https://feedbackportal.microsoft.com/feedback/idea/2a8236bf-be55-f011-95f3-7c1e5299279a