Forum Discussion
Solved
Blocked USB file transfer
We are struggling with some user reports about blocked USB file transfer functionality on their Samsung A52 / A54 devices enrolled with corporate-owned work profile.
Microsoft released a blog p...
Be aware also Google changed out the default behaviour of usb when left unconfigured, which aligns with the experience you're describing.
https://bayton.org/android/android-enterprise-faq/usb-data-access-amapi/
Hey everyone,
I hope you've all had a good week.
Just wanted to come back to you. To clarify the change mentioned by jasonbayton above was updated by Microsoft Intune. I know there was a bit of uncertainty mentioned so just wanted to confirm this.
From our own testing, as you mentioned Weberda, it appears toggling the "USB File Transfer" policy setting from "Not Configured" to "block" (save), then back to "Not configured" (save) will enable USB file transfer. I believe Microsoft are working on an update to iron this out.
If you continue to have difficulties though, please do contact Microsoft Intune directly and they can advise you further.
Hope this helps and do keep us posted if you can.
Thanks again,
Lizzie
Hi weberda , I tried on my tenant too and I confirm that the trick worked, but only for devices already enrolled.
I tried factory reset a test device where the trick fixed and after the new enrolling is still not possible to enable USB file transfer.
Unfortunately is not possible to force Intune to "Allow" it, I can only choose between Block or Not Configured
Am I correct or did you find a way for fix it permanently?
I fear we've to wait until Intune will apply a change on their part.
Oh… I did not re-enroll a device yet to see what the results are. I only confirmed with affected users that the usb file transfer is back working a day after our dummy save in Intune.
will go through it tomorrow and see what happens… thanks
weberda I've to change my previous answer, seems like that just after the enrollment the USB file transfer is disabled but after a while it started working, so seems that was just a delay due to the policy sync.
Try if you can but I'm confident that the dummy edit is enough for have it working.
