Requirements for M-Files Cloud Connections

Before you connect to M-Files Cloud, read these requirements and restrictions.


You must have an internet connection.
  • For the best performance, the latency between the client and the M-Files Cloud server must be less than 50 milliseconds. You can use the connection status tool in M-Files Desktop to analyze the connection quality.
  • For more information about network performance, refer to Monitoring and Optimizing M-Files Performance.
Connections from the local network to M-Files Cloud vaults must be allowed by the firewall.
  • Allowed protocol: gRPC or HTTPS
  • Allowed port: 443
  • There is no restriction for the IP range. Contact M-Files customer support or your M-Files reseller to determine your static IP address or check the IP range here: Azure IP Ranges and Service Tags.
Connections from the local network to M-Files Cloud vaults must support the TLS 1.2 protocol.
  • This includes Microsoft Windows operating systems, Microsoft SQL Server, API solutions, client computers, and integration systems.
    Note: TLS 1.2 must be used in on-premises environments if replication with cloud storage is used.
  • Refer to How to Enable TLS 1.2.


Site-to-site, point-to-site, Azure Express Route, and other VPN solutions are not supported in M-Files Cloud. You can use Ground Link when secure connection to local data is necessary. Ground Link supports external repository connectors and external object types.

Pre-shared keys are not supported in M-Files Cloud.