If this is set, the value that it is set to will be used as the Bluetooth device name. Device/Vendor/MSFT/Policy/Config/Bluetooth/LocalDeviceName Allow users on these managed devices to use Swift Pair and other proximity based scenarios. Block users on these managed devices from using Swift Pair and other proximity based scenarios.Īllow. This policy allows the IT admin to block users on these managed devices from using Swift Pair and other proximity based scenarios.ĭisallow. Device/Vendor/MSFT/Policy/Config/Bluetooth/AllowPromptedProximalConnections Specifies whether to allow specific bundled Bluetooth peripherals to automatically pair with the host device. Device/Vendor/MSFT/Policy/Config/Bluetooth/AllowPrepairing Then, go to another Bluetooth-enabled device, open the Bluetooth control panel and verify that you can discover it. To verify, open the Bluetooth control panel on the device. When set to 1, other devices will be able to detect the device. Then, go to another Bluetooth-enabled device, open the Bluetooth control panel, and verify that you cannot see the name of the device.Īllowed.

When set to 0, other devices will not be able to detect the device. If this is not set or it is deleted, the default value of 1 (Allow) is used. Specifies whether other Bluetooth-enabled devices can discover the device. Device/Vendor/MSFT/Policy/Config/Bluetooth/AllowDiscoverableMode Then, verify that the advertisement is received by the peripheral.

To verify, use any Bluetooth LE app and enable it to do advertising. When set to 1, the device will send out advertisements. Then, verify that the advertisement is not received by the peripheral.Īllowed.

When set to 0, the device will not send out advertisements. Most restricted value is 0.ĭescription framework properties: Property name Specifies whether the device can send out Bluetooth advertisements. Device/Vendor/MSFT/Policy/Config/Bluetooth/AllowAdvertising Feedback In this article AllowAdvertising Scope

Bluetooth file transfer