Page tree
Skip to end of metadata
Go to start of metadata

Why Wordbee is migrating to Azure

Because many of our corporate customers expressed an interest in Azure, we decided to examine the advantages Azure could offer. As we had already some experience with Azure, we noticed that availability, scalability, reliability and security was enhanced considerably. Most importantly,  Azure has the most comprehensive compliance coverage with more than 70 compliance certificates, and it was the first major cloud provider to contractually commit to the requirements of the General Data Protection Regulation (GDPR).

What else should you know?

Security. The Microsoft Azure data centers have several layers of physical and operational security that ensure the safety and integrity of your data.  It ensures the availability and confidentiality of your files.

Technology. We will always be using the latest technology available on the market.

Scalability. Wordbee can have immediate access to as much storage and computing power as needed by the clients.

Speed. Better connections over the globe. We will be able to deliver results within a few seconds even in China and Australia thanks to the extraordinary network power of Microsoft.

Working on the Microsoft Azure Servers will have a positive impact on your daily work and please share your user experience with us when you can.

Plan your migration

The following page details the steps to be taken on client and Wordbee side to plan the migration process:

Wordbee actions

  • We contact you and prepare all the steps necessary for the migration.
    • We send you the exact date of the change and the new URL of your platform (except for custom domains which remain the same).
    • You prepare the migration on your side thanks to the information below (Client Actions).    
  • A few hours before the migration, a message appears on your platform alerting the logged-in users.
  • Your platform is disabled during the migration time that was communicated prior to you.
  • An email is sent to the Administrator(s) of the platform when the migration is complete, no additional action is necessary on your part (except those listed in the Client Actions below)

In case of an issue, we'll interrupt the migration and reactivate your platform on our servers. No data will be lost and everything will be exactly the same as before. We'll solve the problem and plan a new migration date together with you.

Additional actions on your side



In order to schedule the migration, the following actions need on your side :

Client actions

My platform uses a custom domain 

ACTION MIGHT BE REQUIRED PRE-MIGRATION

Make sure that your domain name is properly configured to the Wordbee DNS servers, as per our Custom domain configuration documentation.

Thanks to the right configuration, Wordbee will be able to update the record of your domain name at the exact moment of the migration and no action will be required on your side.

If your domain name is not managed by Wordbee, it's mandatory that you change the A record of your domain name as a CNAME to azure.wordbee-translator.com.


My platform sends emails with my own domain name

ACTION REQUIRED

Make sure you are compliant with current email settings described in the documentation.

My platform uses Wordbee SSO 

ACTION REQUIRED

If you are not using a custom domain, you might need to add/change your SSO configuration to allow the new callback URL. It is usually https://your-platform-name.eu.wordbee-translator.com. If you are using a custom domain, you're already all good.


My platform uses Beebox hosted 

ACTION NOT REQUIRED

If you are using a Beebox hosted by Wordbee, you are not concerned by this step. Wordbee takes care of these changes for you, you are all good.


My platform uses on-premise Beebox 

ACTION REQUIRED

Once your platform has been migrated to Azure, you need to update your projects configuration to use your new TMS vendor URL. This change can be done without breaking the current work progress.

  1. Stop the Windows service Wordbee Beebox Server.

  2. For all projects in C:\Beebox  (default path), edit the file configuration.json

    If the file contains "tms": null at the line 6, it means the project is not connected to Wordbee-Translator.

    Otherwise, you need to instruct Beebox to use Azure by changing the line 10 as follows: 

    Replace api.wordbee-translator.com by api.eu.wordbee-translator.com.

  3. Once all files are modified and saved properly, start the Windows service Wordbee Beebox Server again.


My platform uses Wordbee System API (API v1) 

ACTION REQUIRED

Once your platform has been migrated to Azure, replace api.wordbee-translator.com by api.eu.wordbee-translator.com in your scripts.


My platform uses Wordbee User API 

ACTION REQUIRED

Once your platform has been migrated to Azure, replace api.wordbee-translator.com by api.eu.wordbee-translator.com in your scripts.


My platform uses Wordbee API v2 

ACTION REQUIRED

If you are not using a custom domain, make sure your scripts use your new platform URL. It should be like https://your-platform-name.eu.wordbee-translator.com/api.


My platform uses Wordbee Office Add-In 

ACTION REQUIRED PRE-MIGRATION

Install the latest version of the Wordbee Office. Since the version X, it is possible to choose on what region your platform is set-up.


I'm using Wordbee API(s) and my company has security settings blocking non-standard outgoing trafic 

ACTION REQUIRED

The new inbound IP address is 40.67.219.162


I'm using external integrated tools (MT, API, Webhooks, ...)

ACTION REQUIRED

Outgoing IP address from Azure environment is now 40.74.60.251






Once you have confirmed the migration date with your Account manger, there is nothing else to worry about!

Remember your platform will be disabled during the migration time that was communicated prior to you and the new URL to access it will be available upon completion.

Remember

No data will be lost and everything will be exactly the same as before.



  • No labels