Due to a change from Microsoft you may experience issues with opening files when using "Basic Authentication". As a workaround you can set a policy as described here: Basic authentication sign-in prompts blocked. Our Development team is looking into an alternative solution.
Introduction
Most companies already use SharePoint and OneDrive for Business. However, some companies may still not be fully migrate to the cloud yet and are tied to a file server. The Documents app of Workspace 365 allows you to bundle SharePoint, OneDrive and the file servers (which is based on a WebDAV protocol) in one easy-to-use Document app, bringing all your documents together in one digital adaptive workplace, working online or offline from any device, anytime and anywhere.
Requirements & Recommendations
The WebDAV URL must have a valid SSL certificate
We advice to configure the WebDAV SSL file server in IIS: Installing and Configuring WebDAV on IIS 7 and Later.
For more info how you can secure the WebDAV:
To open files with the Online Editors, an Office Online Server (OOS) is required (the OOS is not required when you only want to use local Office applications)
Hosted environments by default use an OOS server provided by us.
End users will need at least Microsoft 365 E3 or Microsoft 365 Business Premium license to use the Online Editors.
We recommend to use the default port 443, because necessary information (headers) may be lost during port forwarding.
Only self-hosted partners can configure and use their own OOS.
Limitations
Please be aware of the following limitations concerning WebDAV file shares:
Files and folders in WebDAV file shares are not included in the Global Search due to WebDAV limitations
When performing a search in a WebDAV file share, only the currently open folder is searched, underlying folders are not searched
For WebDAV, there is an upload limit of 2GB
Configuration
Add the file server to the Documents app
The admin can set the desired file server/WebDAV URL from the admin settings page under 'Integrations'. Fill in the necessary information.
Remove any blank spaces from the name, it needs to be plain text.
Provide the Integration credentials
SSO in the workspace is configured via oAuth2. However, to connect to file servers, we make use of integration credentials instead of oAuth2.
The first time when users open the file server, they will be prompted to fill in their Integration Credentials once. Make sure to link the credentials to the file server.
We now allow non-UPN usernames the credentials linked to file servers.
Note: This does not apply to Clientless RDP or Exchange links. For Clientless RDP and Exchange make sure you are using the correct username syntax "USER@DOMAIN.LOCAL").
Set preference for opening files (Local- vs. Online Editors)
By default, documents are openend in you local Office applications. However, we have made an integration with Office Online. The Office Online Server (OOS) provides browser-based file viewing and editing services for Office files.
We recommend to use O365 or OOS to open files with the Online Editors and remain within the secure connection via IIS. Read more about security here.
To open files locally, user need to sign in to Microsoft to connect to the WebDAV source.
To open files online, the OOS is needed (see: requirements).
We will lock the file on the file server when you start to edit it in the Online Editor. This means that if another user tries to edit the file via the local editor, the local editor should inform the user that the file is already being edited.
Conditional access for local Office applications
Define on which IP range(s) launching local Office apps are available, e.g. restrict users from accessing Office applications locally.
With IP 'Whitelist' or 'Blacklist' you can choose on which IP range(s) launching local Office apps are available. For example, make it only available from trusted IP ranges (e.g. the company network).
When a user doesn't meet the IP standards, only the 'Open in Word Online' option will appear in the Documents app.