Forum Discussion
MAM - failing uploads to cloud / OneDrive
Hi!
I have a MAM/ MDM setup with user enrolled mobiles. Standard MS apps are deployed to these devices, and the apps are protected with protection policies. One of the apps is the Microsoft 365 (Office) app, and it has a voice capture feature with transcription that auto uploads the capture to OneDrive. Now suddenly this has stopped working. The uploads worked fine just as few weeks ago, but now it fails with the message "transcribing has been paused for this session due to technical reasons", and a could not upload' status. One thing is that it doesnt transcribe, but this means it doesnt upload the capture to OneDrive either. Creating other types of content in the Microsoft 365 app like a scan works fine, and it uploads to OneDrive.
At first i just thought it was the service that was experiencing some downtime or that it was some other temporary issue, but the problem seems to be persistent. So i am now wondering if its something to do with the MS service endpoints, like *cloud.microsoft.com, and that my app preotection policies are perhaps in the way. I have the app in both a work and a personal profile on a Android device, and the app in the personal profile uploads files just fine.
I'll have a go at excluding myself from the protection policy and see if that changes anything, but while i wait for things to get updated, has anyone had any similar experiences, or have any pointers as where i should be looking?
br
S
- ShadyKhorshedIron Contributor
Hi stiangu500,
Good issue description. What is your Android Version? As this might impact the M365 services.
if the AppPP worked last week, then I highly doubt it would be the cause of the problem. But check out the options in App Configuration policy for M365 as well.
let me know if it didn’t work out, maybe I can test it out in my intune tenant.best regards
shady
- stiangu500Copper Contributor
Thanks for the reply! I had to do some more testing before I got back to you here. Its actually the same scenario on both Android (v13, patch level june 23) and iPhone (v15.7.7). I have tested across networks, and with AppPP turned off(excluded using group with user), but its the same story - i get the same error as descibed in my inital post.
Since it works in my personal profile, i can exclude that the service is down. It was working last month, so something must have changed. My policies have not been changed, but i guess both the tenant and apps possibly have had new updates (apps set to auto update). I havent enrolled a new unit from scratch yet, without AppPP from the start, to see if that changes anything.
br
S- ShadyKhorshedIron Contributor
Hallo stiangu500
I have tested on my test environment as well and it works, so we can exclude the ''Service down''. But I would suggest that you check what are the ''Device Compliance and Device Config'' that are hitting the device and start excluding one by one policy.
I would strongly assume that one policy is causing this conflict.