Updated 10/21/20 - This is now resolved with the latest iOS and iPadOS 14.1 update.
We were recently alerted to a scenario whereby after an end user updated to iOS/iPadOS 14, they experienced the inability to import any file from an MDM-managed File Provider such as importing a file from OneDrive to another MDM-managed app, and the error: "Content Unavailable. The folder contents could not be displayed because of an unknown error. Try again" is presented. This issue can occur when the iOS/iPadOS 14 device is enrolled and managed in an MDM solution such as Intune, and has an MDM-managed File Provider app like OneDrive targeted as a "Required" or "Available" app.
Working with Apple, we discovered that this is a regression in iOS/iPadOS 14. Apple is working on a resolution and we’ll update this post when new information is available.
Here’s the steps we took to replicate this experience:
Make OneDrive and Teams a “Required” or “Available” app targeting the user.
Enroll an iOS or iPadOS 14 device with the targeted user account via the Intune Company Portal.
Install OneDrive and Teams via the Company Portal.
Launch OneDrive to login.
Launch Teams to login and start a new chat.
Tap on the paper clip button to add an attachment.
Select "Browse" and if needed, enable OneDrive under "More Locations".
Expected: Able to access OneDrive content.
Actual: Error above is shown.
Note: The scenario above was tested with the Microsoft Teams app and may not be the only way to reproduce this issue. Any app which integrates the File Provider extension can hit this issue, including the native Mail app, Outlook, OneNote, native Files app, and more. So specific repro steps may vary based on specific app.
In the interim, here is a potential workaround:
Note: If you’re testing on the iOS/iPadOS 14 Beta, we've validated that this has been fixed with the iOS 14.2 Beta 2 update.
Again, we'll keep this post updated as we receive additional information.
Blog post updates:
10/3/20: With an update to the scenarios on when this issue can occur, and clarification that this issue has been fixed with the iOS 14.2 Beta 2 update.
10/21/20: With an update that we've received reports that this has been resolved with the latest release of iOS and iPadOS 14.1.