This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 71%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECK%3C/text%3E%3C/svg%3E)
The Niimbot app does not discover my Niimbot B1 bluetooth printer inside the android Intune work profile.
If I use the Niimbot app outside of the Intune work profile, it discovers and connects just fine. When using the Niimbot app inside the work profile however, it doesn't discover the printer at all.
Any ideas?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 30%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
@Colby Kehler, Thanks for posting in Q%A. For the printer issue, please check if any device policy applied to this device which may block it. You can check if the Bluetooth is blocked.
https://learn.microsoft.com/en-us/mem/intune/configuration/device-restrictions-android-for-work
Unassign these policies to the devices and see if it will work.
If there's any update, feel free to let us know.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I tested exempting the phone from the only Android device config policy we have. No luck unfortunately. I've also tested with another app that can scan for bluetooth devices and confirmed it has the same problem. So, it seems to be something with work profile restrictions. I also confirmed that using a bluetooth headset with the Teams app in the work profile works fine. So, it seems related to just scanning and connecting to new devices within a work profile app.
@Colby Kehler, Thanks for the reply. From your description, I know when there's no policy applied. It also has the issue. So it seems to be work profile limitation. To dig into the issue, you can open case to analysis logs to get more finding: