Files.com's integration with Sharepoint allows you to integrate with SharePoint in several different ways.
Files.com's Remote Server Mount feature gives you the ability connect a specific folder on Files.com to the remote server in a real time manner.
That folder then becomes a client, or window, accessing the files stored in your remote server or cloud.
Once you configure a Mount, any operation you perform on or inside that folder will act directly on the remote in real time. Whether you are dropping a file into that folder, deleting a file, creating a subfolder, or performing any other file/folder operations your Files.com user has permissions for, those operations will "pass through" to the remote in real time.
This powerful feature enables a wide variety of use cases such as:
- accessing files on a counterparty (client or vendor)'s cloud without provisioning individual access to individual users.
- reducing storage costs by leveraging on-premise or bulk storage solutions
- enabling applications to access 3rd party clouds via Files.com API, FTP, SFTP, or Files.com Apps
- and many more
Alternatively, Files.com's Remote Server Sync feature give you the ability to push or pull files to or from remote servers. This means that the files will exist in both places at the end of the sync process.
A remote sync can be a "push", where files from your Files.com site are transferred to the remote server, a "pull" where files are transferred from the remote server to your Files.com site, or a two-way "sync" where files that are new or changed in either location are pushed and pulled to maintain a synchronized state between the folder on your Files.com site and that on the remote server.
This integration requires Files.com's Enterprise Connectivity Addon, which is included for free on the Premier or Enterprise plan.
Type Remote servers in the search box at the top of every page, and then click on the matching result. Click the Add new remote server button and select SharePoint.
Enter a descriptive name for the "Internal name for this connection" field, and Save.
A popup will display with the Microsoft login form. By logging in, you are connecting your Files.com site with your Microsoft account.
Once your Remote Server is added, now you need to integrate it to Files.com as either a Remote Server Mount or Remote Server Sync.
You can create as many SharePoint Remote Servers as required. Repeat the above instructions and enter different credentials each time the Microsoft login page is presented.
However, if you are using Single-Sign-On (SSO) with Microsoft then your web browser will always try and log you in using your currently logged-in credentials. The popup Microsoft login page will automatically log you in without giving you the option to enter different credentials. This is normal web SSO behavior. If you have this issue, you can try to circumvent the Single-Sign-On by:
- Logging out of Microsoft within your web browser prior to connecting the new Remote Server.
- Use an incognito web browser window.
- Use a different computer and web browser that hasn't logged into Microsoft yet.
Remote Server Mounts are created by mounting them onto an empty folder in Files.com. This folder should ideally not be the Root of your site, although that is supported if you need it.
From the Files icon on the left, navigate to the location where you want the mounted folder to be and create a new folder. Navigate into the newly created folder and click the Folder Settings button on the top right.
Select Remote Server Mount from the list and click Add new remote server mount button. Select the remote server.
Choose the Remote folder, which is the portion of the remote file system that will be mounted into this folder on Files.com. You can either by leave the default "/" (i.e., the remote server's root directory) or click on Choose a different folder link and navigate to the remote folder you want to this folder to connect to.
Click the Save button. The folder will reload and immediately list the remote folders/files from the selected remote path.
If you instead prefer to do a Sync with the remote, follow these directions.
- From Files, navigate into the folder where you would like to add the remote server sync and click Folder settings > Sync to/from remote server.
- Click the Add new remote server sync button to reveal the form.
- Select the server you would like to transfer to or from by clicking on the Remote server menu.
Next choose your Sync direction. You have three choices:
- Push to the remote server: This option uploads files and folders from your designated folder in your Files.com site to the remote server.
- Pull from the remote server: This option downloads files from the remote server and saves them in your designated folder in your Files.com site.
- Two-way sync: this option checks for new files, deleted files, and changed modification dates on both servers and then pushes and pulls as needed to keep the folders synchronized on both servers.
You have the option to delete files on the source server after a push or pull. Use the After copying menu to select whether you would like files that are successfully transferred to be deleted from or kept on the source server.
Enter the remote path to or from which you would like files and folders transferred, starting after the folder/directory your remote user lands in upon authentication.
For example: if the remote server has a folder structure folderA/folderB/folderC, and the user credentials that you have configured your sync server to log in with automatically land that user inside folderA, then to properly configure your sync folder behavior to transfer files to or from folderC, you would enter the path as folderB/folderC.
Be aware of case sensitivity differences when copying, moving, or syncing files and folders between SharePoint and other storage locations. Sharepoint is a case insensitive system whereas other systems may be case sensitive. This can cause files to be overwritten, and folders to have their contents merged, if their case insensitive names are a match.
Certain remotes that use OAuth for authentication may require regular rotation of your credentials. When this is needed, you will see an alert in the top left of the web interface. You can click the link in that alert to re-authenticate and re-establish the connection to the remote.
Because SharePoint uses the oAuth authorization protocol, there may be future errors with the authentication even after your remote server is configured and running smoothly for some time. When one of those errors happens, Files.com will disable your SharePoint remote server connection and record the error in your External Events log.
When you've resolved the problem that caused the authentication error, you can re-enable your remote server by saving its configuration. Even if you don't make any changes to the configuration, saving the record will cause Files.com to re-enable the connection so that any associated mounts and syncs will begin working again.
Files.com implements OAuth for access delegation to Sharepoint.
When configuring a connection to Sharepoint you will be redirected to your SharePoint server login page to authenticate.
Access controls and permissions are restricted to those of the SharePoint userID used to authenticate.
If you require Files.com to access and retrieve files from SharePoint then the SharePoint userID used should have at least Read and List permissions to the relevant SharePoint sites, folders, and files.
If you require Files.com to transfer or upload files to SharePoint then the SharePoint userID used should have at least Create, Read, Update, Delete and List permissions to the relevant SharePoint sites, folders, and files.
When connecting to SharePoint, Files.com will act in the context of the SharePoint userID used to authenticate the connection.
As a best practice, we recommend that you create a SharePoint userID specifically for Files.com and use this to authenticate the connection.
However, there may be times when you need to access the SharePoint content of specific users and so you can authenticate using those SharePoint user credentials instead.
You can configure as many connections to SharePoint as you require, each with different SharePoint credentials if needed, allowing you to restrict access to specific parts of SharePoint to specific users.
SharePoint connection and connectivity issues can be caused by the following:
- Incorrect Sharepoint access permissions
- Incorrect SharePoint configuration
- Firewall permissions (when the SharePoint server is hosted on premises or hosted in a private cloud.)
When connecting to SharePoint, Files.com will only be able to access those SharePoint resources that have been granted to the credentials being used to connect.
Make sure that the SharePoint account that is being used to authenticate for the Remote Server connection has been granted permission to access the SharePoint resources that you are trying to access. Check that the SharePoint permissions for the account are correct. Log in directly to SharePoint with the same account and verify that you can access the required resources. Contact your SharePoint administrator if you cannot access the required resources successfully.
SharePoint can be configured to present and arrange data in multiple ways. Verify the exact configuration of your SharePoint server determine the exact location of the resource that you are trying to connect to.
For example, SharePoint can present folders as "sites", "libraries", "shared documents", and "pages". Sometimes these terms are used interchangeably even though they represent very different resources within SharePoint.
When setting up a Remote Mount to SharePoint, leave the Remote folder setting blank and select the Choose a different folder option. This will present you with the available resources on the SharePoint server and allow you to navigate to, and select, the exact resource folder that you want to connect to.
When manually entering the Remote folder path, make sure that it is valid and that it can be accessed by the credentials used in the Remote Server configuration.
SharePoint resource paths typically look something like this: companyname.sharepoint.com/resource/resource_name, where resource can be "sites", "Shared Documents", or the name of a Library.
Make sure you use the correct resource path for the resource type that you are trying to access. For example, a SharePoint site resource path should look something like companyname.sharepoint.com/sites/MySite whereas a Library resource path should look something like companyname.sharepoint.com/MyLibrary instead.
If in doubt, start by leaving the Remote folder setting blank and select the Choose a different folder option to navigate to the required resource. Contact your SharePoint administrator if you cannot access the required resources.
If your SharePoint server is located on premises, or is hosted in a private cloud, then check that location's firewall configuration to make sure that connections from Files.com are allowed.
Get Instant Access to Files.com
The button below will take you to our Free Trial signup page. Click on the white "Start My Free Trial" button, then fill out the short form on the next page. Your account will be activated instantly. You can dive in and start yourself or let us help. The choice is yours.Start My Free Trial