Planned Maintenance May 31, 2026: Updates to Viva Glint SFTP Connectivity
To support ongoing security and infrastructure improvements, Viva Glint will perform planned maintenance on May 31, 2026 starting at 1:00am Pacific time (PDT). During this window, the platform will be temporarily unavailable. The maintenance window is expected to last approximately 3–4 hours, during which time customers may experience limited access to both Viva Glint surveys and the platform. What’s changing As part of this update, we are simplifying and strengthening SFTP connectivity used for file transfers: Moving to a single SFTP endpoint and IPv4 address per environment Introducing IPv6 support for improved network compatibility and future readiness Updating DNS behavior so that secondary SFTP records (sftp2) become aliases of the primary endpoint These changes are designed to enhance reliability, simplify configuration, and align with modern network standards. What this means for your organization Most customers will not need to take any action. However, if your organization: uses SFTP integrations with Viva Glint, and restricts access using firewall rules or IP allowlists, you may need to update your configuration to ensure uninterrupted connectivity following the release. In particular: If your infrastructure supports IPv6, ensure that the new IPv6 addresses are included in your allowlists, as network traffic may prioritize IPv6 when available. If your configuration currently references multiple IPs per environment, note that this will be consolidated to a single endpoint and IP address moving forward. As a best practice, Viva Glint recommends allowing access at the domain level where possible, rather than relying on specific IP addresses. Next steps To avoid disruption to SFTP integrations, customers must maintain their existing IP allowlist entries until the May 31, 2026 maintenance window is complete. You may add the new IP addresses in advance of the release, but existing IP addresses should not be removed until after the maintenance window has concluded. Removing existing IP addresses too early may result in connectivity issues before the change takes effect, while failing to add the new IP addresses in time may cause disruptions after the update. For the most up to date allowlist guidance, including domains, ports, and connectivity requirements, please refer to: Allowed List Thank you We recognize that maintenance windows can cause disruption and appreciate your understanding as we continue to improve the reliability, security, and performance of Viva Glint.
Force Maintenance Window Evaluation
I have several hundred clients that, according to ServiceWindowManager.log are still abiding by a Maintenance Window that no longer exists, and are not upgrading to the Client that came with 1910. I lifted the Maintenance Window about a week ago. Am I just being impatient or is there more I can do (tried forcing a Computer Policy evaluation) to get these clients out of the Service Window and upgraded?
