From fe4edd0b33c44cd925b17cd6b6ac052c2c0ea4b1 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 11 Feb 2020 17:02:43 -0800 Subject: [PATCH] More updates --- windows/client-management/mdm/policy-csp-bluetooth.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-bluetooth.md b/windows/client-management/mdm/policy-csp-bluetooth.md index 8e384d21f3..2160f0b07a 100644 --- a/windows/client-management/mdm/policy-csp-bluetooth.md +++ b/windows/client-management/mdm/policy-csp-bluetooth.md @@ -448,10 +448,8 @@ There are multiple levels of encryption strength when pairing Bluetooth devices. The following list shows the supported values: - 0 (default) - All Bluetooth traffic is allowed. -- 1-N - A number representing the bytes that must be used in the encryption process. +- N - A number from 1 through 16 representing the bytes that must be used in the encryption process. At this time, 16 is the largest allowed value for N and 16 bytes is the largest key size that Bluetooth supports so far. If you wish to enforce Windows to use Bluetooth encryption at all times, but do not care about the precise encryption key strength, use a value of 1. - >[!Note] - >If you wish to enforce Windows to use Bluetooth encryption at all times, but do not care about the precise encryption key strength, use a value of 1.