From 7e68d71ac6d79ed0224cda09e3530c329fdc8d9f Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Thu, 10 Sep 2020 13:50:17 -0700 Subject: [PATCH] Update control-usb-devices-using-intune.md broken link --- .../device-control/control-usb-devices-using-intune.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md b/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md index 6ba1e8c891..4bb1ff6d5b 100644 --- a/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md +++ b/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md @@ -99,7 +99,7 @@ In this example, the following classes needed to be added: HID, Keyboard, and {3 If you want to restrict to certain devices, remove the device setup class of the peripheral that you want to limit. Then add the device ID that you want to add. Device ID is based on the vendor ID and product ID values for a device. For information on device ID formats, see [Standard USB Identifiers](https://docs.microsoft.com/windows-hardware/drivers/install/standard-usb-identifiers). -To find the vendor or product IDs, see [Look up device ID](#look-up-device-vendor-id-or-product-id). +To find the vendor or product IDs, see [Look up device ID](#look-up-device-id). For example: