Hi,
​

As our service continues to grow and evolve, we are always searching for ways to optimize both our product and our hosting facilities. As a next step for our hosting facilities, we have implemented a new frontend cluster for Workspace 365 in Azure which further improves our scalability.

Starting Thursday the 2nd of December, we will gradually migrate all of our customers during a regular maintenance window (every Thursday from 22:00 p.m. to 06:00 a.m.).

We have taken all possible precautions to minimize the impact this has on you, but based on your setup this may require action on your end due to our changing IP ranges.

Please note that this migration only affects Workspace 365 environments, not Clientless RDP.

Please note that with this migration the default branding will be replaced with the default Workspace 365 branding. If you have previously set a default branding at the partner level, you will need to check if all your customer environments have environment branding configured. Since this is standard procedure, we don’t expect any issues. To apply non-default branding for your customers, apply them at the environment level as described in this support article.

When using a custom URL for our service, we strongly advise using a CNAME DNS record to refer visitors to your partner URL (yourcompanyname.partner.workspace365.net). If your DNS is already set up in this manner, there is no action required on your end. However, if you are using A records to refer to our servers you will need to change them to CNAME records to avoid additional downtime or working outside of office hours.

Please be aware that including a CNAME record at the root of your domain is usually not allowed as it is in violation of the DNS specification as described in RFC 1035. This means that if you are using an apex domain for Workspace 365 (example.com instead of www.example.com) you will need to check with your DNS provider if they support alternative techniques such as ALIAS/ANAME records, CNAME flattening or top-level redirection. Should this not be possible then please contact our Support department for a custom solution. This might negatively impact the security and availability of your service.

As previously announced, outgoing traffic will also be routed from a new IP range. This only affects you if you are using IP whitelisting to limit access to applications from your Workspace. You will need to add our new IP range:

20.103.81.112/28

If none of these conditions apply to you, the migration will not impair your Workspace 365 environment in any way.

Once your Workspace 365 environment is migrated to the new cluster and with the advised DNS configuration as described above, we will be able to provide you with a valid SSL certificate that is renewed automatically.

You will no longer need to provide your own SSL certificate or worry about expiration. This service is provided to you without any added cost.

If your custom domain uses CAA records to limit the domains from which your SSL certificates can be requested, these records need to include at least one of the following:

Since the hosting migration, additional options to get reporting as described in the article 'How to get reporting', are not available anymore for hosted partners. On a monthly basis we invoice based on the usage. Only active users (users marked as 'Active' under User management) will be billed.