diff --git a/links/hosted-private-cloud/onprem-cloud-platform b/links/hosted-private-cloud/onprem-cloud-platform
new file mode 100644
index 00000000000..d5598ae6d93
--- /dev/null
+++ b/links/hosted-private-cloud/onprem-cloud-platform
@@ -0,0 +1,10 @@
+- [en-asia](https://www.ovhcloud.com/asia/hosted-private-cloud/onprem-cloud-platform/)
+- [en-au](https://www.ovhcloud.com/en-au/hosted-private-cloud/onprem-cloud-platform/)
+- [en-ca](https://www.ovhcloud.com/en-ca/hosted-private-cloud/onprem-cloud-platform/)
+- [en-gb](https://www.ovhcloud.com/en-gb/hosted-private-cloud/onprem-cloud-platform/)
+- [en-ie](https://www.ovhcloud.com/en-ie/hosted-private-cloud/onprem-cloud-platform//)
+- [en-in](https://www.ovhcloud.com/en-in/hosted-private-cloud/onprem-cloud-platform/)
+- [en-sg](https://www.ovhcloud.com/en-sg/hosted-private-cloud/onprem-cloud-platform/)
+- [en-us](https://www.ovhcloud.com/en/hosted-private-cloud/onprem-cloud-platform/)
+- [fr-ca](https://www.ovhcloud.com/fr-ca/hosted-private-cloud/onprem-cloud-platform/)
+- [fr-fr](https://www.ovhcloud.com/fr/hosted-private-cloud/onprem-cloud-platform/)
\ No newline at end of file
diff --git a/links/transversal/marketplace b/links/transversal/marketplace
new file mode 100644
index 00000000000..07263338b49
--- /dev/null
+++ b/links/transversal/marketplace
@@ -0,0 +1 @@
+- [fr-fr](https://marketplace.ovhcloud.com/)
\ No newline at end of file
diff --git a/links/transversal/marketplace-support-collaboration b/links/transversal/marketplace-support-collaboration
new file mode 100644
index 00000000000..5ed94cac6f7
--- /dev/null
+++ b/links/transversal/marketplace-support-collaboration
@@ -0,0 +1 @@
+- [fr-fr](https://marketplace.ovhcloud.com/c/support-collaboration)
\ No newline at end of file
diff --git a/pages/account_and_service_management/account_information/new-control-panel-navigation/guide.fr-ca.md b/pages/account_and_service_management/account_information/new-control-panel-navigation/guide.fr-ca.md
index 51f3a9fb2c4..af301093118 100644
--- a/pages/account_and_service_management/account_information/new-control-panel-navigation/guide.fr-ca.md
+++ b/pages/account_and_service_management/account_information/new-control-panel-navigation/guide.fr-ca.md
@@ -75,7 +75,7 @@ En bas à gauche de l'espace client, des raccourcis vous permettent de découvri
 /// details | Liens utiles
 
 - [Le Centre d'aide OVHcloud](https://help.ovhcloud.com/csm?id=csm_get_help)
-- [OVHcloud Marketplace](https://marketplace.ovhcloud.com/)
+- [OVHcloud Partners](/links/partner)
 - [OVHcloud Status](https://www.status-ovhcloud.com/)
 - [Comment obtenir l'empreinte carbone de vos services OVHcloud](/pages/account_and_service_management/managing_billing_payments_and_services/carbon_footprint)
 
diff --git a/pages/account_and_service_management/account_information/new-control-panel-navigation/guide.fr-fr.md b/pages/account_and_service_management/account_information/new-control-panel-navigation/guide.fr-fr.md
index 51f3a9fb2c4..c403acbc09e 100644
--- a/pages/account_and_service_management/account_information/new-control-panel-navigation/guide.fr-fr.md
+++ b/pages/account_and_service_management/account_information/new-control-panel-navigation/guide.fr-fr.md
@@ -75,7 +75,7 @@ En bas à gauche de l'espace client, des raccourcis vous permettent de découvri
 /// details | Liens utiles
 
 - [Le Centre d'aide OVHcloud](https://help.ovhcloud.com/csm?id=csm_get_help)
-- [OVHcloud Marketplace](https://marketplace.ovhcloud.com/)
+- [OVHcloud Marketplace](/links/transversal/marketplace)
 - [OVHcloud Status](https://www.status-ovhcloud.com/)
 - [Comment obtenir l'empreinte carbone de vos services OVHcloud](/pages/account_and_service_management/managing_billing_payments_and_services/carbon_footprint)
 
diff --git a/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/multisite/modify-a-domain-step-1-all-disabled-git-message.png b/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/multisite/modify-a-domain-step-1-all-disabled-git-message.png
index 25c613a6188..d5896e68ba9 100644
Binary files a/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/multisite/modify-a-domain-step-1-all-disabled-git-message.png and b/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/multisite/modify-a-domain-step-1-all-disabled-git-message.png differ
diff --git a/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/multisite/modify-a-domain-step-1-all-disabled.png b/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/multisite/modify-a-domain-step-1-all-disabled.png
index 9614ff0cc5b..8ebff6ad175 100644
Binary files a/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/multisite/modify-a-domain-step-1-all-disabled.png and b/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/multisite/modify-a-domain-step-1-all-disabled.png differ
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-fr.md
index 61bf4916112..e514fdb92eb 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-fr.md
@@ -14,7 +14,7 @@ L'alias d'IP (*IP aliasing* en anglais) est une configuration spéciale du rése
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. En effet, n’ayant aucun accès à ces machines, nous n’en sommes pas les administrateurs et nous ne pourrons pas vous fournir d'assistance. Il vous appartient de ce fait d’en assurer la gestion logicielle et la sécurisation au quotidien.
 > 
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [prestataire spécialisé](https://marketplace.ovhcloud.com/) si vous éprouvez des difficultés ou des doutes concernant l’administration, l’utilisation ou la sécurisation d’un serveur. Plus d’informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [prestataire spécialisé](/links/transversal/marketplace) si vous éprouvez des difficultés ou des doutes concernant l’administration, l’utilisation ou la sécurisation d’un serveur. Plus d’informations dans la section « Aller plus loin » de ce guide.
 >
 
 ## Prérequis
@@ -482,7 +482,7 @@ Pour tester la connexion, envoyez un ping à votre adresse Additional IP depuis
 
 [Activer le mode rescue sur un VPS](/pages/bare_metal_cloud/virtual_private_servers/rescue)
 
-[OVHcloud Marketplace](https://marketplace.ovhcloud.com/)
+[OVHcloud Marketplace](/links/transversal/marketplace)
 
 Si vous souhaitez bénéficier d'une assistance à l'usage et à la configuration de vos solutions OVHcloud, nous vous proposons de consulter nos différentes [offres de support](/links/support).
 
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.de-de.md
index 3275d50db0c..6ba5321d44f 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: "Einen VPS absichern"
 excerpt: "Erfahren Sie hier, wie Sie grundsätzliche Sicherheitsmaßnahmen anwenden, um Ihren VPS vor Angriffen und unbefugtem Zugriff zu schützen"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 > [!primary]
@@ -101,7 +101,13 @@ Sie sollten diese oder ähnliche Zeilen vorfinden:
 ```
 
 Ersetzen Sie die Nummer **22** mit der Port-Nummer Ihrer Wahl.<br>
-**Geben Sie keine bereits auf Ihrem System verwendete Port-Nummer ein**. Um sicher zu gehen, verwenden Sie eine Zahl zwischen 49152 und 65535. <br>Speichern und schließen Sie die Konfigurationsdatei.
+**Geben Sie keine bereits auf Ihrem System verwendete Port-Nummer ein**. Um sicher zu gehen, verwenden Sie eine Zahl zwischen 49152 und 65535.
+
+Sie können die Ihrem System zugewiesenen Ports auch mit dem folgenden Befehl anzeigen:
+
+```bash
+sudo cat /etc/services
+```
 
 Wenn die Zeile "auskommentiert" ist (d. h. wenn ihr ein "#" vorangestellt ist) wie im Beispiel oben zu sehen, achten Sie darauf, das "#" vor dem Speichern der Datei zu entfernen, damit die Änderung wirksam wird. Beispiel:
 
@@ -111,37 +117,68 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> [!warning]
+> Wenn auf Ihrem Betriebssystem eine Firewall konfiguriert ist (UFW oder iptables), müssen Sie deren Einstellungen anpassen, um den Datenverkehr auf dem neuen Port zuzulassen, bevor Sie den Dienst neu starten. Wenn Sie iptables verwenden, lesen Sie diese Anleitung: [Konfiguration der Linux Firewall mit iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). Wenn standardmäßig keine Firewall konfiguriert ist, starten Sie den Dienst neu.
+>
+
+Speichern und schließen Sie die Konfigurationsdatei.
+
 Starten Sie den Dienst neu:
 
 ```bash
-systemctl restart sshd
+sudo systemctl restart sshd
 ```
 
 Dies sollte ausreichen, um die Änderungen umzusetzen. Sie können alternativ den VPS neu starten (`sudo reboot`).
 
-**Für Ubuntu 23.04 und höher**
+**Für Ubuntu 24.04 und höher**
 
 Für die neuesten Ubuntu Versionen wird die SSH-Konfiguration nun in der Datei `ssh.socket` verwaltet.
 
 Um den SSH-Port zu aktualisieren, bearbeiten Sie die Zeile `ListenStream` in der Konfigurationsdatei mit einem Texteditor Ihrer Wahl (`nano` in diesem Beispiel verwendet):
 
+```bash
+sudo nano /lib/systemd/system/ssh.socket
+```
+
+Ihre Datei sollte je nach der von Ihnen installierten Ubuntu-Version wie in den folgenden Beispielen aussehen:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+oder
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Speichern Sie die Änderungen, und führen Sie die folgenden Befehle aus:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Starten Sie den Dienst neu:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-Wenn Sie die Betriebssystemfirewall aktiviert haben, stellen Sie sicher, dass der neue Port in den Firewallregeln zugelassen ist.
+**Ubuntu 25.04**
+
+Starten Sie den Dienst neu:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Denken Sie daran, dass Sie nun den neuen Port immer angeben müssen, wenn Sie eine [SSH-Verbindung mit Ihrem Server aufbauen](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -155,6 +192,8 @@ Beispiel:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+Wenn Sie aus Ihrem System ausgesperrt sind, können Sie unsere [Rescue-Modus](/pages/bare_metal_cloud/virtual_private_servers/rescue/) verwenden, um Ihre Änderungen wiederherzustellen.
+
 ### Erstellen eines Benutzers mit eingeschränkten Rechten <a name="createuser"></a>
 
 Im Allgemeinen sollten Aufgaben, die keine Root-Rechte erfordern, über einen Standardbenutzer ausgeführt werden. Weitere Informationen finden Sie in [dieser Anleitung](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-asia.md
index 0e82b3ff349..a3e3986b4d1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-asia.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: "How to secure a VPS"
 excerpt: "Find out how to apply basic security measures to protect your VPS against attacks and unauthorised access"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -94,8 +94,13 @@ Find the following or similar lines:
 #ListenAddress 0.0.0.0
 ```
 
-Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535.  
-Save and exit the configuration file.
+Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535. 
+
+Alternatively, you can view the ports assigned on your system with the following command:
+
+```bash
+sudo cat /etc/services
+```
 
 If the line is "commented out" (i.e. if it is preceded by a "#") as shown in the example above, make sure to remove the "#" before saving the file so that the change takes effect. Example:
 
@@ -105,6 +110,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> ![warning]
+> If a firewall is configured on your operating system (UFW or iptables), you must adjust its settings to allow traffic on the new port before restarting the service. If you are using iptables, refer to this guide: [Configuring the firewall on Linux with iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). If no firewall is configured by default, restart the service.
+>
+
+Save and exit the configuration file.
+
 Restart the service:
 
 ```bash
@@ -113,7 +124,7 @@ sudo systemctl restart sshd
 
 This should be sufficient to apply the changes. Alternatively, reboot the VPS (`sudo reboot`).
 
-**For Ubuntu 23.04 and later**
+**For Ubuntu 24.04 and later**
 
 For the latest Ubuntu versions, the SSH configuration is now managed in the `ssh.socket` file.
 
@@ -123,23 +134,44 @@ To update the SSH port, edit the `Listenstream` line in the configuration file w
 sudo nano /lib/systemd/system/ssh.socket
 ```
 
+Your file should resemble the following examples, depending on the version of Ubuntu you have installed:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+or
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Save your changes and run the following commands:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Restart the service:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-If you have enabled your operating system's firewall, make sure you allow the new port in your firewall rules.
+**Ubuntu 25.04**
+
+Restart the service:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Remember that you will have to indicate the new port any time you [establish an SSH connection to your server](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -153,6 +185,8 @@ Example:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+If you are locked out of your system, you can use our [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue/) environment to revert your changes.
+
 ### Creating a user with restricted rights <a name="createuser"></a>
 
 In general, tasks that do not require root privileges should be performed via a standard user. Please refer to the information in [this guide](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds) for details.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-au.md
index 0e82b3ff349..a3e3986b4d1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-au.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: "How to secure a VPS"
 excerpt: "Find out how to apply basic security measures to protect your VPS against attacks and unauthorised access"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -94,8 +94,13 @@ Find the following or similar lines:
 #ListenAddress 0.0.0.0
 ```
 
-Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535.  
-Save and exit the configuration file.
+Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535. 
+
+Alternatively, you can view the ports assigned on your system with the following command:
+
+```bash
+sudo cat /etc/services
+```
 
 If the line is "commented out" (i.e. if it is preceded by a "#") as shown in the example above, make sure to remove the "#" before saving the file so that the change takes effect. Example:
 
@@ -105,6 +110,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> ![warning]
+> If a firewall is configured on your operating system (UFW or iptables), you must adjust its settings to allow traffic on the new port before restarting the service. If you are using iptables, refer to this guide: [Configuring the firewall on Linux with iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). If no firewall is configured by default, restart the service.
+>
+
+Save and exit the configuration file.
+
 Restart the service:
 
 ```bash
@@ -113,7 +124,7 @@ sudo systemctl restart sshd
 
 This should be sufficient to apply the changes. Alternatively, reboot the VPS (`sudo reboot`).
 
-**For Ubuntu 23.04 and later**
+**For Ubuntu 24.04 and later**
 
 For the latest Ubuntu versions, the SSH configuration is now managed in the `ssh.socket` file.
 
@@ -123,23 +134,44 @@ To update the SSH port, edit the `Listenstream` line in the configuration file w
 sudo nano /lib/systemd/system/ssh.socket
 ```
 
+Your file should resemble the following examples, depending on the version of Ubuntu you have installed:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+or
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Save your changes and run the following commands:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Restart the service:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-If you have enabled your operating system's firewall, make sure you allow the new port in your firewall rules.
+**Ubuntu 25.04**
+
+Restart the service:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Remember that you will have to indicate the new port any time you [establish an SSH connection to your server](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -153,6 +185,8 @@ Example:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+If you are locked out of your system, you can use our [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue/) environment to revert your changes.
+
 ### Creating a user with restricted rights <a name="createuser"></a>
 
 In general, tasks that do not require root privileges should be performed via a standard user. Please refer to the information in [this guide](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds) for details.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-ca.md
index 0e82b3ff349..a3e3986b4d1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "How to secure a VPS"
 excerpt: "Find out how to apply basic security measures to protect your VPS against attacks and unauthorised access"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -94,8 +94,13 @@ Find the following or similar lines:
 #ListenAddress 0.0.0.0
 ```
 
-Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535.  
-Save and exit the configuration file.
+Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535. 
+
+Alternatively, you can view the ports assigned on your system with the following command:
+
+```bash
+sudo cat /etc/services
+```
 
 If the line is "commented out" (i.e. if it is preceded by a "#") as shown in the example above, make sure to remove the "#" before saving the file so that the change takes effect. Example:
 
@@ -105,6 +110,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> ![warning]
+> If a firewall is configured on your operating system (UFW or iptables), you must adjust its settings to allow traffic on the new port before restarting the service. If you are using iptables, refer to this guide: [Configuring the firewall on Linux with iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). If no firewall is configured by default, restart the service.
+>
+
+Save and exit the configuration file.
+
 Restart the service:
 
 ```bash
@@ -113,7 +124,7 @@ sudo systemctl restart sshd
 
 This should be sufficient to apply the changes. Alternatively, reboot the VPS (`sudo reboot`).
 
-**For Ubuntu 23.04 and later**
+**For Ubuntu 24.04 and later**
 
 For the latest Ubuntu versions, the SSH configuration is now managed in the `ssh.socket` file.
 
@@ -123,23 +134,44 @@ To update the SSH port, edit the `Listenstream` line in the configuration file w
 sudo nano /lib/systemd/system/ssh.socket
 ```
 
+Your file should resemble the following examples, depending on the version of Ubuntu you have installed:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+or
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Save your changes and run the following commands:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Restart the service:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-If you have enabled your operating system's firewall, make sure you allow the new port in your firewall rules.
+**Ubuntu 25.04**
+
+Restart the service:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Remember that you will have to indicate the new port any time you [establish an SSH connection to your server](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -153,6 +185,8 @@ Example:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+If you are locked out of your system, you can use our [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue/) environment to revert your changes.
+
 ### Creating a user with restricted rights <a name="createuser"></a>
 
 In general, tasks that do not require root privileges should be performed via a standard user. Please refer to the information in [this guide](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds) for details.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-gb.md
index 0e82b3ff349..a3e3986b4d1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: "How to secure a VPS"
 excerpt: "Find out how to apply basic security measures to protect your VPS against attacks and unauthorised access"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -94,8 +94,13 @@ Find the following or similar lines:
 #ListenAddress 0.0.0.0
 ```
 
-Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535.  
-Save and exit the configuration file.
+Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535. 
+
+Alternatively, you can view the ports assigned on your system with the following command:
+
+```bash
+sudo cat /etc/services
+```
 
 If the line is "commented out" (i.e. if it is preceded by a "#") as shown in the example above, make sure to remove the "#" before saving the file so that the change takes effect. Example:
 
@@ -105,6 +110,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> ![warning]
+> If a firewall is configured on your operating system (UFW or iptables), you must adjust its settings to allow traffic on the new port before restarting the service. If you are using iptables, refer to this guide: [Configuring the firewall on Linux with iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). If no firewall is configured by default, restart the service.
+>
+
+Save and exit the configuration file.
+
 Restart the service:
 
 ```bash
@@ -113,7 +124,7 @@ sudo systemctl restart sshd
 
 This should be sufficient to apply the changes. Alternatively, reboot the VPS (`sudo reboot`).
 
-**For Ubuntu 23.04 and later**
+**For Ubuntu 24.04 and later**
 
 For the latest Ubuntu versions, the SSH configuration is now managed in the `ssh.socket` file.
 
@@ -123,23 +134,44 @@ To update the SSH port, edit the `Listenstream` line in the configuration file w
 sudo nano /lib/systemd/system/ssh.socket
 ```
 
+Your file should resemble the following examples, depending on the version of Ubuntu you have installed:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+or
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Save your changes and run the following commands:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Restart the service:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-If you have enabled your operating system's firewall, make sure you allow the new port in your firewall rules.
+**Ubuntu 25.04**
+
+Restart the service:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Remember that you will have to indicate the new port any time you [establish an SSH connection to your server](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -153,6 +185,8 @@ Example:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+If you are locked out of your system, you can use our [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue/) environment to revert your changes.
+
 ### Creating a user with restricted rights <a name="createuser"></a>
 
 In general, tasks that do not require root privileges should be performed via a standard user. Please refer to the information in [this guide](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds) for details.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-ie.md
index 0e82b3ff349..a3e3986b4d1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-ie.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: "How to secure a VPS"
 excerpt: "Find out how to apply basic security measures to protect your VPS against attacks and unauthorised access"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -94,8 +94,13 @@ Find the following or similar lines:
 #ListenAddress 0.0.0.0
 ```
 
-Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535.  
-Save and exit the configuration file.
+Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535. 
+
+Alternatively, you can view the ports assigned on your system with the following command:
+
+```bash
+sudo cat /etc/services
+```
 
 If the line is "commented out" (i.e. if it is preceded by a "#") as shown in the example above, make sure to remove the "#" before saving the file so that the change takes effect. Example:
 
@@ -105,6 +110,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> ![warning]
+> If a firewall is configured on your operating system (UFW or iptables), you must adjust its settings to allow traffic on the new port before restarting the service. If you are using iptables, refer to this guide: [Configuring the firewall on Linux with iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). If no firewall is configured by default, restart the service.
+>
+
+Save and exit the configuration file.
+
 Restart the service:
 
 ```bash
@@ -113,7 +124,7 @@ sudo systemctl restart sshd
 
 This should be sufficient to apply the changes. Alternatively, reboot the VPS (`sudo reboot`).
 
-**For Ubuntu 23.04 and later**
+**For Ubuntu 24.04 and later**
 
 For the latest Ubuntu versions, the SSH configuration is now managed in the `ssh.socket` file.
 
@@ -123,23 +134,44 @@ To update the SSH port, edit the `Listenstream` line in the configuration file w
 sudo nano /lib/systemd/system/ssh.socket
 ```
 
+Your file should resemble the following examples, depending on the version of Ubuntu you have installed:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+or
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Save your changes and run the following commands:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Restart the service:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-If you have enabled your operating system's firewall, make sure you allow the new port in your firewall rules.
+**Ubuntu 25.04**
+
+Restart the service:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Remember that you will have to indicate the new port any time you [establish an SSH connection to your server](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -153,6 +185,8 @@ Example:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+If you are locked out of your system, you can use our [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue/) environment to revert your changes.
+
 ### Creating a user with restricted rights <a name="createuser"></a>
 
 In general, tasks that do not require root privileges should be performed via a standard user. Please refer to the information in [this guide](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds) for details.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-sg.md
index 0e82b3ff349..a3e3986b4d1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-sg.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: "How to secure a VPS"
 excerpt: "Find out how to apply basic security measures to protect your VPS against attacks and unauthorised access"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -94,8 +94,13 @@ Find the following or similar lines:
 #ListenAddress 0.0.0.0
 ```
 
-Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535.  
-Save and exit the configuration file.
+Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535. 
+
+Alternatively, you can view the ports assigned on your system with the following command:
+
+```bash
+sudo cat /etc/services
+```
 
 If the line is "commented out" (i.e. if it is preceded by a "#") as shown in the example above, make sure to remove the "#" before saving the file so that the change takes effect. Example:
 
@@ -105,6 +110,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> ![warning]
+> If a firewall is configured on your operating system (UFW or iptables), you must adjust its settings to allow traffic on the new port before restarting the service. If you are using iptables, refer to this guide: [Configuring the firewall on Linux with iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). If no firewall is configured by default, restart the service.
+>
+
+Save and exit the configuration file.
+
 Restart the service:
 
 ```bash
@@ -113,7 +124,7 @@ sudo systemctl restart sshd
 
 This should be sufficient to apply the changes. Alternatively, reboot the VPS (`sudo reboot`).
 
-**For Ubuntu 23.04 and later**
+**For Ubuntu 24.04 and later**
 
 For the latest Ubuntu versions, the SSH configuration is now managed in the `ssh.socket` file.
 
@@ -123,23 +134,44 @@ To update the SSH port, edit the `Listenstream` line in the configuration file w
 sudo nano /lib/systemd/system/ssh.socket
 ```
 
+Your file should resemble the following examples, depending on the version of Ubuntu you have installed:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+or
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Save your changes and run the following commands:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Restart the service:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-If you have enabled your operating system's firewall, make sure you allow the new port in your firewall rules.
+**Ubuntu 25.04**
+
+Restart the service:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Remember that you will have to indicate the new port any time you [establish an SSH connection to your server](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -153,6 +185,8 @@ Example:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+If you are locked out of your system, you can use our [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue/) environment to revert your changes.
+
 ### Creating a user with restricted rights <a name="createuser"></a>
 
 In general, tasks that do not require root privileges should be performed via a standard user. Please refer to the information in [this guide](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds) for details.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-us.md
index 0e82b3ff349..a3e3986b4d1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-us.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: "How to secure a VPS"
 excerpt: "Find out how to apply basic security measures to protect your VPS against attacks and unauthorised access"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -94,8 +94,13 @@ Find the following or similar lines:
 #ListenAddress 0.0.0.0
 ```
 
-Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535.  
-Save and exit the configuration file.
+Replace the number **22** with the port number of your choice. **Please do not enter a port number already used on your system**. To be safe, use a number between 49152 and 65535. 
+
+Alternatively, you can view the ports assigned on your system with the following command:
+
+```bash
+sudo cat /etc/services
+```
 
 If the line is "commented out" (i.e. if it is preceded by a "#") as shown in the example above, make sure to remove the "#" before saving the file so that the change takes effect. Example:
 
@@ -105,6 +110,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> ![warning]
+> If a firewall is configured on your operating system (UFW or iptables), you must adjust its settings to allow traffic on the new port before restarting the service. If you are using iptables, refer to this guide: [Configuring the firewall on Linux with iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). If no firewall is configured by default, restart the service.
+>
+
+Save and exit the configuration file.
+
 Restart the service:
 
 ```bash
@@ -113,7 +124,7 @@ sudo systemctl restart sshd
 
 This should be sufficient to apply the changes. Alternatively, reboot the VPS (`sudo reboot`).
 
-**For Ubuntu 23.04 and later**
+**For Ubuntu 24.04 and later**
 
 For the latest Ubuntu versions, the SSH configuration is now managed in the `ssh.socket` file.
 
@@ -123,23 +134,44 @@ To update the SSH port, edit the `Listenstream` line in the configuration file w
 sudo nano /lib/systemd/system/ssh.socket
 ```
 
+Your file should resemble the following examples, depending on the version of Ubuntu you have installed:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+or
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Save your changes and run the following commands:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Restart the service:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-If you have enabled your operating system's firewall, make sure you allow the new port in your firewall rules.
+**Ubuntu 25.04**
+
+Restart the service:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Remember that you will have to indicate the new port any time you [establish an SSH connection to your server](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -153,6 +185,8 @@ Example:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+If you are locked out of your system, you can use our [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue/) environment to revert your changes.
+
 ### Creating a user with restricted rights <a name="createuser"></a>
 
 In general, tasks that do not require root privileges should be performed via a standard user. Please refer to the information in [this guide](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds) for details.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.es-es.md
index 3e91f1b5160..77cfe9b5583 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "Proteger un VPS"
 excerpt: "Esta guía explica cómo aplicar medidas de seguridad básicas para proteger su VPS de ataques y accesos no autorizados"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 > [!primary]
@@ -96,14 +96,19 @@ sudo nano /etc/ssh/sshd_config
 Encontrará las siguientes líneas o equivalentes:
 
 ```console
-#Port 49152
+#Port 22
 #AddressFamily any
 #ListenAddress 0.0.0.0
 ```
 
 Sustituya el número **22** por el número de puerto que desee.  
-**Recuerde que no debe indicar un número de puerto que ya esté en uso en su sistema**. Para mayor seguridad, utilice un número entre 49152 y 65535.  
-Guarde y cierre el archivo de configuración.
+**Recuerde que no debe indicar un número de puerto que ya esté en uso en su sistema**. Para mayor seguridad, utilice un número entre 49152 y 65535.
+
+También puede ver los puertos asignados a su sistema con el siguiente comando:
+
+```bash
+sudo cat /etc/services
+```
 
 Si la línea está "comentada" (es decir, precedida de un "#") como en el ejemplo anterior, asegúrese de eliminar el "#" antes de guardar el archivo para que se tenga en cuenta el cambio. Ejemplo:
 
@@ -113,6 +118,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> [!warning]
+> Si hay un cortafuegos configurado en su sistema operativo (UFW o iptables), debe ajustar su configuración para permitir el tráfico en el nuevo puerto antes de reiniciar el servicio. Si utiliza iptables, consulte esta guía: [Configurar el firewall de Linux con iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). Si no hay ningún cortafuegos configurado por defecto, reinicie el servicio.
+>
+
+Guarde y cierre el archivo de configuración.
+
 Reinicie el servicio:
 
 ```bash
@@ -121,29 +132,54 @@ sudo systemctl restart sshd
 
 Esto debería ser suficiente para aplicar los cambios. En caso contrario, reinicie el VPS (`sudo reboot`).
 
-**Para Ubuntu 23.04 y versiones posteriores**
+**Para Ubuntu 24.04 y versiones posteriores**
 
 Para las últimas versiones de Ubuntu, la configuración SSH se gestiona ahora en el archivo /ssh.socket`.
 
 Para actualizar el puerto SSH, edite la línea `ListenStream` en el archivo de configuración con un editor de texto de su elección (`nano` utilizado en este ejemplo):
 
+```bash
+sudo nano /lib/systemd/system/ssh.socket
+```
+
+Su archivo debería parecerse a los siguientes ejemplos, dependiendo de la versión de Ubuntu que tenga instalada:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+o
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Guarde los cambios y ejecute los siguientes comandos:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Reinicie el servicio:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-Si ha activado el cortafuegos del sistema operativo, asegúrese de autorizar el nuevo puerto en las reglas del cortafuegos.
+**Ubuntu 25.04**
+
+Reinicie el servicio:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Recuerde que deberá indicar el nuevo puerto en cada solicitud de [conexión SSH al servidor](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -157,6 +193,8 @@ Ejemplo:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+Si no puede acceder a su sistema, puede utilizar nuestro entorno [modo de rescate](/pages/bare_metal_cloud/virtual_private_servers/rescue/) para cancelar los cambios.
+
 ### Crear un usuario con permisos restringidos <a name="createuser"></a>
 
 Por lo general, las tareas que no requieran privilegios root deben realizarse a través de un usuario estándar. Para más información, consulte [esta guía](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds).
@@ -294,4 +332,4 @@ En la [página de producto](/links/bare-metal/vps-options) y en las [respectivas
 
 [Configurar el firewall de red](/pages/bare_metal_cloud/dedicated_servers/firewall_network)
 
-Interactúe con nuestra [comunidad de usuarios](/links/community).
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.es-us.md
index 3e91f1b5160..77cfe9b5583 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.es-us.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Proteger un VPS"
 excerpt: "Esta guía explica cómo aplicar medidas de seguridad básicas para proteger su VPS de ataques y accesos no autorizados"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 > [!primary]
@@ -96,14 +96,19 @@ sudo nano /etc/ssh/sshd_config
 Encontrará las siguientes líneas o equivalentes:
 
 ```console
-#Port 49152
+#Port 22
 #AddressFamily any
 #ListenAddress 0.0.0.0
 ```
 
 Sustituya el número **22** por el número de puerto que desee.  
-**Recuerde que no debe indicar un número de puerto que ya esté en uso en su sistema**. Para mayor seguridad, utilice un número entre 49152 y 65535.  
-Guarde y cierre el archivo de configuración.
+**Recuerde que no debe indicar un número de puerto que ya esté en uso en su sistema**. Para mayor seguridad, utilice un número entre 49152 y 65535.
+
+También puede ver los puertos asignados a su sistema con el siguiente comando:
+
+```bash
+sudo cat /etc/services
+```
 
 Si la línea está "comentada" (es decir, precedida de un "#") como en el ejemplo anterior, asegúrese de eliminar el "#" antes de guardar el archivo para que se tenga en cuenta el cambio. Ejemplo:
 
@@ -113,6 +118,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> [!warning]
+> Si hay un cortafuegos configurado en su sistema operativo (UFW o iptables), debe ajustar su configuración para permitir el tráfico en el nuevo puerto antes de reiniciar el servicio. Si utiliza iptables, consulte esta guía: [Configurar el firewall de Linux con iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). Si no hay ningún cortafuegos configurado por defecto, reinicie el servicio.
+>
+
+Guarde y cierre el archivo de configuración.
+
 Reinicie el servicio:
 
 ```bash
@@ -121,29 +132,54 @@ sudo systemctl restart sshd
 
 Esto debería ser suficiente para aplicar los cambios. En caso contrario, reinicie el VPS (`sudo reboot`).
 
-**Para Ubuntu 23.04 y versiones posteriores**
+**Para Ubuntu 24.04 y versiones posteriores**
 
 Para las últimas versiones de Ubuntu, la configuración SSH se gestiona ahora en el archivo /ssh.socket`.
 
 Para actualizar el puerto SSH, edite la línea `ListenStream` en el archivo de configuración con un editor de texto de su elección (`nano` utilizado en este ejemplo):
 
+```bash
+sudo nano /lib/systemd/system/ssh.socket
+```
+
+Su archivo debería parecerse a los siguientes ejemplos, dependiendo de la versión de Ubuntu que tenga instalada:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+o
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Guarde los cambios y ejecute los siguientes comandos:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Reinicie el servicio:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-Si ha activado el cortafuegos del sistema operativo, asegúrese de autorizar el nuevo puerto en las reglas del cortafuegos.
+**Ubuntu 25.04**
+
+Reinicie el servicio:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Recuerde que deberá indicar el nuevo puerto en cada solicitud de [conexión SSH al servidor](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -157,6 +193,8 @@ Ejemplo:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+Si no puede acceder a su sistema, puede utilizar nuestro entorno [modo de rescate](/pages/bare_metal_cloud/virtual_private_servers/rescue/) para cancelar los cambios.
+
 ### Crear un usuario con permisos restringidos <a name="createuser"></a>
 
 Por lo general, las tareas que no requieran privilegios root deben realizarse a través de un usuario estándar. Para más información, consulte [esta guía](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds).
@@ -294,4 +332,4 @@ En la [página de producto](/links/bare-metal/vps-options) y en las [respectivas
 
 [Configurar el firewall de red](/pages/bare_metal_cloud/dedicated_servers/firewall_network)
 
-Interactúe con nuestra [comunidad de usuarios](/links/community).
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.fr-ca.md
index 0688ce7f076..3b5fa75088a 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "Sécuriser un VPS"
 excerpt: "Découvrez comment mettre en place des mesures de sécurité basiques pour protéger votre VPS des attaques et des accès non autorisés"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 ## Objectif
@@ -92,15 +92,20 @@ sudo nano /etc/ssh/sshd_config
 Vous devriez trouver les lignes suivantes ou équivalentes :
 
 ```console
-#Port 49152
+#Port 22
 #AddressFamily any
 #ListenAddress 0.0.0.0
 ```
 
 Remplacez le nombre **22** par le numéro de port de votre choix.<br>
 **Veillez toutefois à ne pas renseigner un numéro de port déjà utilisé sur votre système**. 
-Pour plus de sécurité, utilisez un numéro entre 49152 et 65535.<br>Enregistrez et quittez le fichier de configuration.
+Pour plus de sécurité, utilisez un numéro entre 49152 et 65535.
 
+Vous pouvez également afficher les ports attribués à votre système à l'aide de la commande suivante :
+
+```bash
+sudo cat /etc/services
+```
 
 Si la ligne est "commentée" (c'est-à-dire si elle est précédée d'un "#") comme dans l'exemple ci-dessus, veillez à supprimer le "#" avant d'enregistrer le fichier pour que la modification soit prise en compte. Exemple :
 
@@ -110,6 +115,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> [!warning]
+> Si un pare-feu est configuré sur votre système d'exploitation (UFW ou iptables), vous devez ajuster ses paramètres pour autoriser le trafic sur le nouveau port avant de redémarrer le service. Si vous utilisez iptables, consultez ce guide : [Configurer le pare-feu sous Linux avec Iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). Si aucun pare-feu n'est configuré par défaut, redémarrez le service.
+>
+
+Enregistrez et quittez le fichier de configuration.
+
 Redémarrez le service :
 
 ```bash
@@ -118,29 +129,54 @@ sudo systemctl restart sshd
 
 Cela devrait être suffisant pour appliquer les changements. Dans le cas contraire, redémarrez le VPS (`sudo reboot`).
 
-**Pour Ubuntu 23.04 et versions ultérieures**
+**Pour Ubuntu 24.04 et versions ultérieures**
 
 Pour les dernières versions d'Ubuntu, la configuration SSH est désormais gérée dans le fichier `ssh.socket`.
 
 Pour mettre à jour le port SSH, éditez la ligne `Listenstream` dans le fichier de configuration avec un éditeur de texte de votre choix (`nano` utilisé dans cet exemple) :
 
+```bash
+sudo nano /lib/systemd/system/ssh.socket
+```
+
+Votre fichier devrait ressembler aux exemples suivants, en fonction de la version d'Ubuntu que vous avez installée :
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+ou
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Enregistrez vos modifications et exécutez les commandes suivantes :
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Redémarrez le service :
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-Si vous avez activé le pare-feu de votre système d'exploitation, assurez-vous d'autoriser le nouveau port dans les règles du pare-feu.
+**Ubuntu 25.04**
+
+Redémarrez le service :
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 N'oubliez pas que vous devrez indiquer le nouveau port à chaque demande de [connexion SSH à votre serveur](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) :
 
@@ -154,6 +190,8 @@ Exemple :
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+Si vous êtes bloqué hors de votre système, vous pouvez utiliser notre [mode rescue](/pages/bare_metal_cloud/virtual_private_servers/rescue/) pour annuler vos modifications.
+
 ### Créer un utilisateur avec des droits restreints <a name="createuser"></a>
 
 En général, les tâches qui ne requièrent pas de privilèges root doivent être effectuées via un utilisateur standard. Pour plus d'informations, consultez [ce guide](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.fr-fr.md
index 3923ae822cb..5f9b4636312 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: "Sécuriser un VPS"
-excerpt: "Découvrez comment mettre en place des mesures de sécurité basiques pour protéger votre VPS contre les attaques et les accès non autorisés"
-updated: 2024-10-07
+excerpt: "Découvrez comment mettre en place des mesures de sécurité basiques pour protéger votre VPS des attaques et des accès non autorisés"
+updated: 2025-11-04
 ---
 
 ## Objectif
@@ -92,15 +92,20 @@ sudo nano /etc/ssh/sshd_config
 Vous devriez trouver les lignes suivantes ou équivalentes :
 
 ```console
-#Port 49152
+#Port 22
 #AddressFamily any
 #ListenAddress 0.0.0.0
 ```
 
 Remplacez le nombre **22** par le numéro de port de votre choix.<br>
 **Veillez toutefois à ne pas renseigner un numéro de port déjà utilisé sur votre système**. 
-Pour plus de sécurité, utilisez un numéro entre 49152 et 65535.<br>Enregistrez et quittez le fichier de configuration.
+Pour plus de sécurité, utilisez un numéro entre 49152 et 65535.
 
+Vous pouvez également afficher les ports attribués à votre système à l'aide de la commande suivante :
+
+```bash
+sudo cat /etc/services
+```
 
 Si la ligne est "commentée" (c'est-à-dire si elle est précédée d'un "#") comme dans l'exemple ci-dessus, veillez à supprimer le "#" avant d'enregistrer le fichier pour que la modification soit prise en compte. Exemple :
 
@@ -110,6 +115,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> [!warning]
+> Si un pare-feu est configuré sur votre système d'exploitation (UFW ou iptables), vous devez ajuster ses paramètres pour autoriser le trafic sur le nouveau port avant de redémarrer le service. Si vous utilisez iptables, consultez ce guide : [Configurer le pare-feu sous Linux avec Iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). Si aucun pare-feu n'est configuré par défaut, redémarrez le service.
+>
+
+Enregistrez et quittez le fichier de configuration.
+
 Redémarrez le service :
 
 ```bash
@@ -118,29 +129,54 @@ sudo systemctl restart sshd
 
 Cela devrait être suffisant pour appliquer les changements. Dans le cas contraire, redémarrez le VPS (`sudo reboot`).
 
-**Pour Ubuntu 23.04 et versions ultérieures**
+**Pour Ubuntu 24.04 et versions ultérieures**
 
 Pour les dernières versions d'Ubuntu, la configuration SSH est désormais gérée dans le fichier `ssh.socket`.
 
 Pour mettre à jour le port SSH, éditez la ligne `Listenstream` dans le fichier de configuration avec un éditeur de texte de votre choix (`nano` utilisé dans cet exemple) :
 
+```bash
+sudo nano /lib/systemd/system/ssh.socket
+```
+
+Votre fichier devrait ressembler aux exemples suivants, en fonction de la version d'Ubuntu que vous avez installée :
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+ou
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Enregistrez vos modifications et exécutez les commandes suivantes :
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Redémarrez le service :
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-Si vous avez activé le pare-feu de votre système d'exploitation, assurez-vous d'autoriser le nouveau port dans les règles du pare-feu.
+**Ubuntu 25.04**
+
+Redémarrez le service :
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 N'oubliez pas que vous devrez indiquer le nouveau port à chaque demande de [connexion SSH à votre serveur](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) :
 
@@ -154,6 +190,8 @@ Exemple :
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+Si vous êtes bloqué hors de votre système, vous pouvez utiliser notre [mode rescue](/pages/bare_metal_cloud/virtual_private_servers/rescue/) pour annuler vos modifications.
+
 ### Créer un utilisateur avec des droits restreints <a name="createuser"></a>
 
 En général, les tâches qui ne requièrent pas de privilèges root doivent être effectuées via un utilisateur standard. Pour plus d'informations, consultez [ce guide](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds).
@@ -291,4 +329,4 @@ Vous trouverez toutes les informations sur les solutions de sauvegarde disponibl
 
 [Configurer le Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network)
 
-Échangez avec notre [communauté d'utilisateurs](/links/community).
+Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.it-it.md
index 8f483a473a6..e6dc1bd311f 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "Mettere in sicurezza un VPS"
 excerpt: "Come impostare misure di sicurezza di base per proteggere il VPS da attacchi e accessi non autorizzati"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 > [!primary]
@@ -94,15 +94,20 @@ sudo nano /etc/ssh/sshd_config
 Dovrai trovare queste linee o equivalenti:
 
 ```console
-#Port 49152
+#Port 22
 #AddressFamily any
 #ListenAddress 0.0.0.0
 ```
 
 Sostituisci il numero **22** con il numero di porta che preferisci.<br>
 **Ricordati di non inserire un numero di porta già utilizzato sul tuo sistema**.
-Per una maggiore sicurezza, utilizza un numero tra 49152 e 65535.<br>Salva e lascia il file di configurazione.
+Per una maggiore sicurezza, utilizza un numero tra 49152 e 65535.
 
+È inoltre possibile visualizzare le porte assegnate al proprio sistema utilizzando il seguente comando:
+
+```bash
+sudo cat /etc/services
+```
 
 Se la riga è "commentata" (cioè preceduta da un "#") come nell'esempio precedente, assicurarsi di rimuovere il "#" prima di salvare il file, in modo che la modifica venga presa in considerazione. Esempio:
 
@@ -112,6 +117,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> [!warning]
+>  Se sul sistema operativo è configurato un firewall (UFW o iptables), è necessario modificarne le impostazioni per consentire il traffico sulla nuova porta prima di riavviare il servizio. Se si utilizza iptables, consultare questa guida: [Configura il firewall su Linux con iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). Se non è configurato alcun firewall predefinito, riavviare il servizio.
+>
+
+Salva e lascia il file di configurazione.
+
 Riavvia il servizio:
 
 ```bash
@@ -120,29 +131,54 @@ sudo systemctl restart sshd
 
 Ciò dovrebbe essere sufficiente per attuare le modifiche. In caso contrario, riavvia il VPS (`sudo reboot`).
 
-**Per Ubuntu 23.04 e versioni successive**
+**Per Ubuntu 24.04 e versioni successive**
 
 Per le ultime versioni di Ubuntu, la configurazione SSH viene gestita nel file `ssh.socket`.
 
 Per aggiornare la porta SSH, modifica la riga `ListenStream` nel file di configurazione con un editor di testo a tua scelta (`nano` utilizzato in questo esempio):
 
+```bash
+sudo nano /lib/systemd/system/ssh.socket
+```
+
+Il tuo file dovrebbe essere simile ai seguenti esempi, a seconda della versione di Ubuntu che hai installato:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+oppure
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Salvare le modifiche ed eseguire i comandi seguenti:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Riavvia il servizio:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-Se è stato attivato il firewall del sistema operativo, assicurarsi di consentire la nuova porta secondo le regole del firewall.
+**Ubuntu 25.04**
+
+Riavvia il servizio:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Ricordati di indicare la nuova porta ad ogni richiesta di [connessione SSH al tuo server](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -156,6 +192,8 @@ Esempio:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+Se sei bloccato fuori dal tuo sistema, puoi utilizzare il nostro ambiente [Rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue/) per annullare le modifiche apportate.
+
 ### Crea un account con diritti utente limitati <a name="createuser"></a>
 
 In genere, i compiti che non richiedono privilegi root devono essere eseguiti tramite un utente standard. Per maggiori informazioni, consulta [questa guida](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.pl-pl.md
index 38e9f422279..4f3eb339e33 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "Zabezpieczenie serwera VPS"
 excerpt: "Dowiedz się, jak wdrożyć podstawowe środki bezpieczeństwa, aby chronić Twój serwer VPS przed atakami i nieautoryzowanym dostępem"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 > [!primary]
@@ -17,7 +17,7 @@ Kiedy zamawiasz serwer VPS, możesz wybrać dystrybucję lub system operacyjny d
 > [!warning]
 > OVHcloud świadczy usługi, za które jesteś odpowiedzialny w związku z ich konfiguracją i zarządzaniem. Jesteś więc odpowiedzialny za ich prawidłowe funkcjonowanie.
 >
->Jeśli napotkasz trudności z przeprowadzeniem tych operacji, skontaktuj się z wyspecjalizowanym dostawcą usług i/lub przedyskutuj problem z naszą społecznością użytkowników na stronie https://community.ovh.com/en/. OVHcloud nie może udzielić Ci wsparcia technicznego w tym zakresie.
+> Jeśli napotkasz trudności z przeprowadzeniem tych operacji, skontaktuj się z wyspecjalizowanym dostawcą usług i/lub przedyskutuj problem z naszą społecznością użytkowników na stronie https://community.ovh.com/en/. OVHcloud nie może udzielić Ci wsparcia technicznego w tym zakresie.
 >
 
 ## Wymagania początkowe
@@ -95,14 +95,20 @@ sudo nano /etc/ssh/sshd_config
 Należy znaleźć następujące lub równoważne linie:
 
 ```console
-#Port 49152
+#Port 22
 #AddressFamily any
 #ListenAddress 0.0.0.0
 ```
 
 Zamień liczbę **22** na wybrany numer portu.<br>
 **Pamiętaj, aby nie wpisywać numeru portu już używanego w systemie**.
-Aby zwiększyć bezpieczeństwo, wprowadź numer 49152 i 65535.<br>Zapisz i wyjdź z pliku konfiguracyjnego.
+Aby zwiększyć bezpieczeństwo, wprowadź numer 49152 i 65535.
+
+Możesz również wyświetlić porty przypisane do Twojego systemu za pomocą następującego polecenia:
+
+```bash
+sudo cat /etc/services
+```
 
 Jeśli linia jest "zakomentowana" (tj. poprzedzona znakiem "#"), jak w powyższym przykładzie, należy usunąć znak "#" przed zapisaniem pliku, aby zmiana została uwzględniona. Przykład:
 
@@ -112,6 +118,12 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
+> [!warning]
+> Jeśli w systemie operacyjnym skonfigurowano zaporę ogniową (UFW lub iptables), przed ponownym uruchomieniem usługi należy dostosować jej ustawienia, aby zezwolić na ruch w nowym porcie. Jeśli używasz iptables, zapoznaj się z tym przewodnikiem: [Konfiguracja firewalla w systemie Linux z systemem iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). Jeśli domyślnie nie skonfigurowano żadnej zapory ogniowej, uruchom ponownie usługę.
+>
+
+Zapisz i wyjdź z pliku konfiguracyjnego.
+
 Zrestartuj usługę:
 
 ```bash
@@ -120,29 +132,54 @@ sudo systemctl restart sshd
 
 Powinno to wystarczyć do wdrożenia zmian. W przeciwnym razie zrestartuj serwer VPS (`sudo reboot`).
 
-**Dla systemu Ubuntu 23.04 i nowszych wersji**
+**Dla systemu Ubuntu 24.04 i nowszych wersji**
 
 W przypadku najnowszych wersji Ubuntu, konfiguracja SSH jest zarządzana w pliku `ssh.socket`.
 
 Aby zaktualizować port SSH, edytuj wiersz `ListenStream` w pliku konfiguracyjnym za pomocą wybranego edytora tekstu (`nano` użyty w tym przykładzie):
 
+```bash
+sudo nano /lib/systemd/system/ssh.socket
+```
+
+Twój plik powinien wyglądać podobnie do poniższych przykładów, w zależności od zainstalowanej wersji Ubuntu:
+
 ```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+lub
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Zapisz zmiany i wykonaj następujące polecenia:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Uruchom ponownie usługę:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-Jeśli włączona jest zapora systemu operacyjnego, upewnij się, że zezwalasz na nowy port w regułach zapory.
+**Ubuntu 25.04**
+
+Uruchom ponownie usługę:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Pamiętaj, że podczas każdego zlecenia [połączenia SSH z Twoim serwerem](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) należy wskazać nowy port:
 
@@ -156,6 +193,8 @@ Przykład:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+Jeśli nie masz dostępu do swojego systemu, możesz skorzystać z naszego środowiska [trybu Rescue](/pages/bare_metal_cloud/virtual_private_servers/rescue/), aby anulować wprowadzone zmiany.
+
 ### Utworzenie użytkownika z ograniczonymi prawami <a name="createuser"></a>
 
 Zadania, które nie wymagają uprawnień root, powinny być wykonywane za pomocą standardowego użytkownika. Więcej informacji znajdziesz w [tym przewodniku](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.pt-pt.md
index f18264e724f..f0df6c6bbb9 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "Proteger um VPS"
 excerpt: "Saiba como implementar medidas básicas de segurança para proteger o seu VPS de ataques e acessos não autorizados"
-updated: 2024-10-07
+updated: 2025-11-04
 ---
 
 > [!primary]
@@ -95,7 +95,7 @@ sudo nano /etc/ssh/sshd_config
 Deve encontrar as seguintes linhas ou equivalentes:
 
 ```console
-#Port 49152
+#Port 22
 #AddressFamily any
 #ListenAddress 0.0.0.0
 ```
@@ -104,6 +104,12 @@ Substitua o número **22** pelo número de porta à sua escolha.<br>
 **No entanto, certifique-se de que não indica um número de porta já utilizado no seu sistema**.
 Para uma maior segurança, utilize um número entre 49152 e 65535.<br>
 
+Você também pode visualizar as portas atribuídas ao seu sistema usando o seguinte comando:
+
+```bash
+sudo cat /etc/services
+```
+
 Se a linha estiver "comentada" (ou seja, precedida por um "#") como no exemplo acima, certifique-se de que remove o "#" antes de guardar o ficheiro para que a alteração seja tida em conta. Exemplo:
 
 ```console
@@ -112,7 +118,11 @@ Port 49152
 #ListenAddress 0.0.0.0
 ```
 
-Registe e saia do ficheiro de configuração.
+> [!warning]
+> Se estiver configurado um firewall no seu sistema operativo (UFW ou iptables), terá de ajustar as suas definições para autorizar o tráfego na nova porta antes de reiniciar o serviço. Se estiver a utilizar o iptables, consulte este guia: [Configurar a firewall em Linux com iptables](/pages/bare_metal_cloud/dedicated_servers/firewall-Linux-iptable/). Se não estiver configurado nenhum firewall por predefinição, reinicie o serviço.
+>
+
+Guarde e saia do ficheiro de configuração.
 
 Reinicie o serviço:
 
@@ -122,29 +132,55 @@ sudo systemctl restart sshd
 
 Isto deveria ser suficiente para aplicar as alterações. Caso contrário, reinicie o VPS (`sudo reboot`).
 
-**Para Ubuntu 23.04 e versões posteriores**
+**Para Ubuntu 24.04 e versões posteriores**
 
 Para as últimas versões de Ubuntu, a configuração SSH é agora gerida no ficheiro `ssh.socket`.
 
 Para atualizar a porta SSH, edite a linha `Listenstream` no ficheiro de configuração com um editor de texto à sua escolha (`nano` utilizado neste exemplo):
 
-```consola
+
+```bash
+sudo nano /lib/systemd/system/ssh.socket
+```
+
+O seu ficheiro deve ser semelhante aos exemplos a seguir, dependendo da versão do Ubuntu que você instalou:
+
+```console
 [Socket]
 ListenStream=49152
 Accept=no
 ```
 
+ou
+
+```console
+[Socket]
+ListenStream=0.0.0.0:49152
+ListenStream=[::]:22
+BindIPv6Only=ipv6-only
+Accept=no
+FreeBind=yes
+```
+
 Guarde as alterações e execute os seguintes comandos:
 
 ```bash
 sudo systemctl daemon-reload
 ```
 
+Reinicie o serviço:
+
 ```bash
 sudo systemctl restart ssh.service
 ```
 
-Se tiver ativado a firewall do sistema operativo, certifique-se de que a nova porta está autorizada nas regras da firewall.
+**Ubuntu 25.04**
+
+Reinicie o serviço:
+
+```bash
+sudo systemctl restart ssh.socket
+```
 
 Lembre-se de que deve indicar a nova porta a cada pedido de [ligação SSH ao seu servidor](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction):
 
@@ -158,6 +194,8 @@ Exemplo:
 ssh ubuntu@203.0.113.100 -p 49152
 ```
 
+Se você estiver bloqueado fora do seu sistema, pode usar o nosso ambiente [modo rescue](/pages/bare_metal_cloud/virtual_private_servers/rescue/) para anular as suas alterações.
+
 ### Criar um utilizador com direitos restritos <a name="createuser"></a>
 
 Em geral, as tarefas que não exijam privilégios root devem ser realizadas através de um utilizador standard. Para mais informações consulte [este guia](/pages/bare_metal_cloud/dedicated_servers/changing_root_password_linux_ds).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.de-de.md
index 7fe2ff53463..8c14bc454f4 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: VPS-Partitionierung nach einem Storage-Upgrade
 excerpt: Erfahren Sie hier, wie Sie den verwendbaren Speicherplatz nach einem Upgrade vergrößern
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 > [!primary]
@@ -172,6 +172,18 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 Vergewissern Sie sich, dass der Standardwert in der Zeile `First sector` mit dem Wert übereinstimmt, den Sie zuvor notiert haben. Stimmt er nicht überein, verwenden Sie den von Ihnen aufgeschriebenen Wert.
 
+Wenn die folgende Meldung angezeigt wird:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Geben Sie `n` ein und fahren Sie fort.
+
+Die Antwort `y` bewirkt, dass das vorhandene ext4-Dateisystem auf Partition 1 überschrieben und die darin enthaltenen Daten gelöscht werden.
+
 ### Die Partition bootfähig machen
 
 Jetzt muss sichergestellt werden, dass die Partition bootfähig ist. Das ist über den Befehl `a`{.action} möglich.
@@ -209,7 +221,7 @@ The filesystem on /dev/sdb1 is now 5242624 blocks long.
 
 ### Überprüfung der Ergebnisse
 
-Um zu überprüfen, ob das Erweitern funktioniert hat, können Sie die neu erstellte Partition einhängen und sich die Größe ansehen.
+Um zu überprüfen, ob das Erweitern funktioniert hat, können Sie die neu erstellte Partition mounten und sich die Größe ansehen.
 
 ```sh
 mount /dev/sdb1 /mnt
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-asia.md
index c96e8f74342..90338edecd9 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-asia.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Repartitioning a VPS after a storage upgrade
 excerpt: Find out how to increase the usable disk space following an upgrade
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -162,6 +162,18 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 On the `First sector` line, check that the default value is the same as the one you have previously written down. If it is different, use the value you have written down.
 
+If you see the following message:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Enter `n` and proceed.
+
+Answering `y` would mean overwriting the existing ext4 file system on Partition 1 and agreeing to destroy the data on it.
+
 #### Make the partition bootable
 
 You now need to ensure that the partition is bootable. You can do this using the command `a`{.action}.
@@ -274,4 +286,4 @@ Enter your desired size and click `OK`{.action}. Your volume will now be extende
 
 ## Go further
 
-Join our community of users at <https://community.ovh.com/en/> .
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-au.md
index c198d6ecba9..90338edecd9 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-au.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Repartitioning a VPS after a storage upgrade
 excerpt: Find out how to increase the usable disk space following an upgrade
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -145,7 +145,7 @@ Selected partition 1
 
 The single partition will automatically be deleted.
 
-### Create a new partition
+#### Create a new partition
 
 You now need to create a new partition with the command `n`{.action}. It is recommended that you use the default values.
 
@@ -162,7 +162,19 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 On the `First sector` line, check that the default value is the same as the one you have previously written down. If it is different, use the value you have written down.
 
-### Make the partition bootable
+If you see the following message:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Enter `n` and proceed.
+
+Answering `y` would mean overwriting the existing ext4 file system on Partition 1 and agreeing to destroy the data on it.
+
+#### Make the partition bootable
 
 You now need to ensure that the partition is bootable. You can do this using the command `a`{.action}.
 
@@ -274,4 +286,4 @@ Enter your desired size and click `OK`{.action}. Your volume will now be extende
 
 ## Go further
 
-Join our community of users at <https://community.ovh.com/en/> .
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-ca.md
index c96e8f74342..90338edecd9 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Repartitioning a VPS after a storage upgrade
 excerpt: Find out how to increase the usable disk space following an upgrade
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -162,6 +162,18 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 On the `First sector` line, check that the default value is the same as the one you have previously written down. If it is different, use the value you have written down.
 
+If you see the following message:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Enter `n` and proceed.
+
+Answering `y` would mean overwriting the existing ext4 file system on Partition 1 and agreeing to destroy the data on it.
+
 #### Make the partition bootable
 
 You now need to ensure that the partition is bootable. You can do this using the command `a`{.action}.
@@ -274,4 +286,4 @@ Enter your desired size and click `OK`{.action}. Your volume will now be extende
 
 ## Go further
 
-Join our community of users at <https://community.ovh.com/en/> .
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-gb.md
index 06ce1d4ffdb..a99b84bba04 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Repartitioning a VPS after a storage upgrade
 excerpt: Find out how to increase the usable disk space following an upgrade
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -162,6 +162,18 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 On the `First sector` line, check that the default value is the same as the one you have previously written down. If it is different, use the value you have written down.
 
+If you see the following message:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Enter `n` and proceed.
+
+Answering `y` would mean overwriting the existing ext4 file system on Partition 1 and agreeing to destroy the data on it.
+
 #### Make the partition bootable
 
 You now need to ensure that the partition is bootable. You can do this using the command `a`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-ie.md
index 6d7a9f8b93f..90338edecd9 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-ie.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Repartitioning a VPS after a storage upgrade
 excerpt: Find out how to increase the usable disk space following an upgrade
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -160,7 +160,19 @@ First sector (2048-41943039, default 2048): 2048
 Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 41943039.
 ```
 
-On the `First sector` line, check that the default value is the same as the one you have previously written down. If it is different, use the value you have written down instead.
+On the `First sector` line, check that the default value is the same as the one you have previously written down. If it is different, use the value you have written down.
+
+If you see the following message:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Enter `n` and proceed.
+
+Answering `y` would mean overwriting the existing ext4 file system on Partition 1 and agreeing to destroy the data on it.
 
 #### Make the partition bootable
 
@@ -274,4 +286,4 @@ Enter your desired size and click `OK`{.action}. Your volume will now be extende
 
 ## Go further
 
-Join our community of users at <https://community.ovh.com/en/> .
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-sg.md
index c96e8f74342..90338edecd9 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-sg.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Repartitioning a VPS after a storage upgrade
 excerpt: Find out how to increase the usable disk space following an upgrade
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -162,6 +162,18 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 On the `First sector` line, check that the default value is the same as the one you have previously written down. If it is different, use the value you have written down.
 
+If you see the following message:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Enter `n` and proceed.
+
+Answering `y` would mean overwriting the existing ext4 file system on Partition 1 and agreeing to destroy the data on it.
+
 #### Make the partition bootable
 
 You now need to ensure that the partition is bootable. You can do this using the command `a`{.action}.
@@ -274,4 +286,4 @@ Enter your desired size and click `OK`{.action}. Your volume will now be extende
 
 ## Go further
 
-Join our community of users at <https://community.ovh.com/en/> .
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-us.md
index c96e8f74342..90338edecd9 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-us.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Repartitioning a VPS after a storage upgrade
 excerpt: Find out how to increase the usable disk space following an upgrade
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -162,6 +162,18 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 On the `First sector` line, check that the default value is the same as the one you have previously written down. If it is different, use the value you have written down.
 
+If you see the following message:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Enter `n` and proceed.
+
+Answering `y` would mean overwriting the existing ext4 file system on Partition 1 and agreeing to destroy the data on it.
+
 #### Make the partition bootable
 
 You now need to ensure that the partition is bootable. You can do this using the command `a`{.action}.
@@ -274,4 +286,4 @@ Enter your desired size and click `OK`{.action}. Your volume will now be extende
 
 ## Go further
 
-Join our community of users at <https://community.ovh.com/en/> .
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.es-es.md
index 21fe97a89bf..188bfff9d2e 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: Reparticionar un VPS tras un upgrade de almacenamiento
 excerpt: "Cómo aumentar el espacio en disco útil después de una actualización"
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objetivo
@@ -163,7 +163,19 @@ First sector (2048-41943039, default 2048): 2048
 Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 41943039
 ```
 
-En la línea «First sector», asegúrese de que el valor por defecto coincide con el que ha anotado anteriormente. Si es diferente, utilice el valor anotado.
+En la línea `First sector`, asegúrese de que el valor por defecto coincide con el que ha anotado anteriormente. Si es diferente, utilice el valor anotado.
+
+Si aparece el siguiente mensaje:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Introduzca `n` y continúe.
+
+Responder `y` significaría sobrescribir el sistema de archivos ext4 existente en la Partition 1 y aceptar destruir los datos que contiene.
 
 ### Hacer que la partición sea de arranque
 
@@ -278,4 +290,4 @@ Escriba el tamaño deseado y haga clic en `Aceptar`{.action}. El volumen se ampl
 
 ## Más información
 
-Interactúe con nuestra comunidad de usuarios en <https://community.ovh.com/en/>.
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.es-us.md
index 21fe97a89bf..188bfff9d2e 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.es-us.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: Reparticionar un VPS tras un upgrade de almacenamiento
 excerpt: "Cómo aumentar el espacio en disco útil después de una actualización"
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objetivo
@@ -163,7 +163,19 @@ First sector (2048-41943039, default 2048): 2048
 Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 41943039
 ```
 
-En la línea «First sector», asegúrese de que el valor por defecto coincide con el que ha anotado anteriormente. Si es diferente, utilice el valor anotado.
+En la línea `First sector`, asegúrese de que el valor por defecto coincide con el que ha anotado anteriormente. Si es diferente, utilice el valor anotado.
+
+Si aparece el siguiente mensaje:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Introduzca `n` y continúe.
+
+Responder `y` significaría sobrescribir el sistema de archivos ext4 existente en la Partition 1 y aceptar destruir los datos que contiene.
 
 ### Hacer que la partición sea de arranque
 
@@ -278,4 +290,4 @@ Escriba el tamaño deseado y haga clic en `Aceptar`{.action}. El volumen se ampl
 
 ## Más información
 
-Interactúe con nuestra comunidad de usuarios en <https://community.ovh.com/en/>.
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.fr-ca.md
index b7dc2d7e376..94a94194ff0 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Repartitionner un VPS après un upgrade de stockage
 excerpt: "Découvrez comment augmenter l'espace disque utilisable suite à une mise à niveau"
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objectif
@@ -163,6 +163,18 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 Dans la ligne `First sector`, assurez-vous que la valeur par défaut est la même que celle que vous avez notée précédemment. Si elle diffère, utilisez la valeur que vous avez notée.
 
+Si le message suivant s'affiche :
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Entrez « n » et continuez.
+
+Répondre « y » signifierait écraser le système de fichiers ext4 existant sur la Partition 1 et accepter de détruire les données qu'elle contient.
+
 ### Rendre la partition amorçable (<i>bootable</i>)
 
 Vous devez maintenant vous assurer que la partition est amorçable (<i>bootable</i>). Pour ce faire, utilisez la commande `a`{.action} :
@@ -275,4 +287,4 @@ Entrez la taille souhaitée et cliquez sur `OK`{.action}. Votre volume sera alor
 
 ## Aller plus loin
 
-Échangez avec notre [communauté d'utilisateurs](/links/community).
+Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.fr-fr.md
index dbc41a07d1e..9802b5c16f0 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Repartitionner un VPS après un upgrade de stockage
 excerpt: "Découvrez comment augmenter l'espace disque utilisable suite à une mise à niveau"
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objectif
@@ -163,7 +163,19 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 Dans la ligne `First sector`, assurez-vous que la valeur par défaut est la même que celle que vous avez notée précédemment. Si elle diffère, utilisez la valeur que vous avez notée.
 
-#### Rendre la partition amorçable (<i>bootable</i>)
+Si le message suivant s'affiche :
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Entrez `n` et continuez.
+
+Répondre `y` signifierait écraser le système de fichiers ext4 existant sur la Partition 1 et accepter de détruire les données qu'elle contient.
+
+### Rendre la partition amorçable (<i>bootable</i>)
 
 Vous devez maintenant vous assurer que la partition est amorçable (<i>bootable</i>). Pour ce faire, utilisez la commande `a`{.action} :
 
@@ -275,4 +287,4 @@ Entrez la taille souhaitée et cliquez sur `OK`{.action}. Votre volume sera alor
 
 ## Aller plus loin
 
-Échangez avec notre [communauté d'utilisateurs](/links/community).
+Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.it-it.md
index 13a12d64298..10959a29686 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Partizionare un VPS dopo un upgrade di storage
 excerpt: "Come aumentare lo spazio su disco utilizzabile in seguito a un aggiornamento"
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Obiettivo
@@ -166,6 +166,18 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 Assicurati che il valore predefinito indicato nella riga `First sector` corrisponda a quello annotato precedentemente (se differente, utilizza quest’ultimo).
 
+Se viene visualizzato il seguente messaggio:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Digita `n` e continua.
+
+Rispondere `y` significherebbe sovrascrivere il file system ext4 esistente sulla partizione 1 e accettare di distruggere i dati in essa contenuti.
+
 ### Rendi la partizione avviabile (bootable)
 
 Per assicurarti che la partizione sia avviabile, esegui il comando `a`{.action}: 
@@ -279,4 +291,4 @@ Inserisci la dimensione desiderata e clicca su `OK`{.action}. Il volume verrà p
 
 ## Per saperne di più
 
-Contatta la nostra Community di utenti all’indirizzo <https://community.ovh.com/en/>.
+Contatta la nostra [Community di utenti](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.pl-pl.md
index 74733c6454e..be8a5a03c88 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: Zmiana rozmiaru partycji serwera VPS po zmianie oferty przestrzeni dyskowej
 excerpt: "Dowiedz się, jak zwiększyć przestrzeń dyskową po aktualizacji"
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Wprowadzenie
@@ -165,9 +165,21 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 Musisz upewnić się, że wartość domyślna w wierszu `First sector` jest taka sama, jak wartość zanotowana wcześniej. Jeśli jest inna, należy użyć zanotowanej wartości.
 
-### Ustawianie partycji bootowalnej
+Jeśli pojawi się następujący komunikat:
 
-Teraz należy upewnić się, że partycja jest bootowalna. Możesz to zrobić za pomocą polecenia `a`{.action}.
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Wpisz `n` i kontynuuj.
+
+Odpowiedź `y` oznaczałaby nadpisanie istniejącego systemu plików ext4 na Partition 1 i zgodę na zniszczenie zawartych na niej danych.
+
+### Ustawianie partycji bootowalnej (bootable)
+
+Teraz należy upewnić się, że partycja jest bootowalna (bootable). Możesz to zrobić za pomocą polecenia `a`{.action}.
 
 ```console
 Command (m for help): a
@@ -278,4 +290,4 @@ Wprowadź żądany rozmiar i kliknij `OK`{.action}. Wolumen zostanie wówczas ro
 
 ## Sprawdź również
 
-Przyłącz się do społeczności naszych użytkowników na stronie <https://community.ovh.com/en/>.
+Dołącz do [grona naszych użytkowników](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.pt-pt.md
index 72eddcdb565..536f87e8c81 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/upsize_vps_partition/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: Reparticionar um VPS após um upgrade de armazenamento
 excerpt: "Saiba como aumentar a quantidade de espaço útil no disco após uma atualização"
-updated: 2023-09-05
+updated: 2025-11-05
 ---
 
 ## Objetivo
@@ -165,6 +165,18 @@ Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4194303
 
 Na linha `First sector`, certifique-se que o valor predefinido é igual ao que foi anotado anteriormente. Se for diferente, use o valor que anotou antes.
 
+Se a seguinte mensagem for exibida:
+
+```console
+Partition #1 contains a ext4 signature.
+
+Do you want to remove the signature? [Y]es/[N]o:
+```
+
+Digite `n` e continue.
+
+Responder `y` significaria sobrescrever o sistema de ficheiros ext4 existente na partição 1 e aceitar destruir os dados nela contidos.
+
 ### Configurar uma partição de arranque (bootable)
 
 A seguir, certifique-se de que a partição seja de arranque (bootable). Para tal, utilize o comando `a`{.action}.
@@ -278,4 +290,4 @@ Introduza o tamanho pretendido e clique em `OK`{.action}. O seu volume será ent
 
 ## Quer saber mais?
 
-Fale com a nossa comunidade de utilizadores em [https://community.ovh.com/en/](https://community.ovh.com/en/).
+Fale com nossa [comunidade de utilizadores](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pt-pt.md
index 6f4bce55a8c..20072dcca04 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pt-pt.md
@@ -68,7 +68,7 @@ Para uma maior flexibilidade dos seus backups, pode ativar a opção Backup auto
 A opção de Backup automatizado Premium cria um backup do seu VPS a cada 24 horas no horário especificado.  
 Você terá acesso a todos os backups diários dos últimos 7 dias. Uma vez criados 7 backups, cada novo backup substituirá o mais antigo.
 
-Faça login no seu [Área de Cliente OVHcloudl](/links/manager), abra a seção `Bare Metal Cloud`{.action}, selecione `Servidor privado virtual`{.action} e, em seguida, clique no nome do seu VPS.
+Faça login no seu [Área de Cliente OVHcloud](/links/manager), abra a seção `Bare Metal Cloud`{.action}, selecione `Servidor privado virtual`{.action} e, em seguida, clique no nome do seu VPS.
 
 Clique na aba `Backup automatizado`{.action} no menu horizontal.
 
diff --git a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.de-de.md
index 1eb62680d15..619ea2743bc 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.de-de.md
@@ -366,11 +366,8 @@ Beachten Sie auch unserere Anleitung zur [Absicherung eines VPS](/pages/bare_met
 Es gibt mehrere Optionen, z. B.:
 
 - Download über SFTP: Verbinden Sie sich mit Ihrem VPS mit einem Software-Client, der SFTP unterstützt (z. B. [FileZilla](/pages/bare_metal_cloud/dedicated_servers/comment-deposer-ou-recuperer-des-donnees-sur-un-serveur-dedie-via-sftp)), und übertragen Sie alle Dateien im Root-Verzeichnis des Systems.
-
 - Download über `rsync` (Kommandozeilentool): Verwenden Sie den Befehl `rsync -avz -e ssh username@vps_ip_address:/ /local_directory/`, um alle Dateien und Ordner Ihres VPS herunterzuladen.
-
 - Download über die Option **Automatisches Backup**: Folgen Sie unserer Anleitung zur [Verwendung von automatischen Backups auf einem VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps), um Dateien aus einem Backup herunterzuladen.
-
 - Download über die Option **Snapshot**: Folgen Sie unserer Anleitung zur [Verwendung von Snapshots auf einem VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps), um einen VPS-Snapshot herunterzuladen.
 
 ///
@@ -430,9 +427,7 @@ Um zu überprüfen, ob Ihre IP-Adresse autorisiert ist, verwenden Sie den folgen
 Obwohl OVHcloud Sicherheitsmaßnahmen anwendet, um die gesamte Infrastruktur zu schützen, ist der Administrator eines VPS für die Sicherheit der darauf gehosteten Anwendungen und Daten verantwortlich.
 
 - Folgen Sie unserer Anleitung zur [Konfiguration der OVHcloud Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network), die in unserer Anti-DDoS-Infrastruktur integriert ist und die Exposition Ihrer Dienste gegenüber DDoS-Angriffen begrenzt.
-
 - Darüber hinaus können Sie unsere Anleitungen zur [Firewall-Konfiguration](/pages/bare_metal_cloud/virtual_private_servers/firewall-Linux-iptable) mit `iptables` auf Linux-basierten Distributionen und zur [Windows-Firewall](/pages/bare_metal_cloud/virtual_private_servers/activate-port-firewall-soft-win) verwenden.
-
 - Für Linux-basierte Distributionen auf einem VPS können Sie die Anweisungen in unserer Anleitung zur [Absicherung eines VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps) befolgen, um zusätzliche Sicherheitsmaßnahmen anzuwenden.
 
 ///
diff --git a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.en-gb.md
index 1720d05da2f..05be145b4ac 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.en-gb.md
@@ -367,11 +367,8 @@ To do this, please refer to our guide on [how to secure a VPS](/pages/bare_metal
 There are several options available, for example:
 
 - Download via SFTP: Connect to your VPS with a software client capable of SFTP (for example [FileZilla](/pages/bare_metal_cloud/dedicated_servers/comment-deposer-ou-recuperer-des-donnees-sur-un-serveur-dedie-via-sftp)), then transfer all files in the system's root directory.
-
 - Download via `rsync` (command line tool): Use the command `rsync -avz -e ssh username@vps_ip_address:/ /local_directory/` to download all files and folders from your VPS.
-
 - Download via the option **Automated Backup**: Follow our guide on [how to use automated backups on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps) to download files from a backup.
-
 - Download via the option **Snapshot**: Follow our guide on [how to use snapshots on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps) to download a VPS snapshot.
 
 ///
@@ -431,9 +428,7 @@ To verify that your IP address is authorized, use the following call:
 Although OVHcloud applies security measures to protect the entire infrastructure, the administrator of a VPS is responsible for the security of the applications and data hosted on it.
 
 - Follow our guide on [how to configure the OVHcloud Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) which is integrated in our Anti-DDoS infrastructure, limiting the exposure of your services to DDoS attacks.
-
 - In addition, you can use our guides on [how to configure your own firewall](/pages/bare_metal_cloud/virtual_private_servers/firewall-Linux-iptable) with `iptables` on Linux-based distributions and [how to enable the firewall on Windows](/pages/bare_metal_cloud/virtual_private_servers/activate-port-firewall-soft-win).
-
 - For Linux-based distributions on a VPS, you can follow the instructions in our guide on [how to secure a VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps) to apply additional security measures.
 
 ///
diff --git a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.es-es.md
index 71b5831ef22..d07c44e48e9 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.es-es.md
@@ -368,11 +368,8 @@ Para ello, consulte nuestra guía sobre [cómo asegurar un VPS](/pages/bare_meta
 Hay varias opciones disponibles, por ejemplo:
 
 - Descarga mediante SFTP: Conéctate a tu VPS con un cliente de software capaz de SFTP (por ejemplo [FileZilla](/pages/bare_metal_cloud/dedicated_servers/comment-deposer-ou-recuperer-des-donnees-sur-un-serveur-dedie-via-sftp)), y luego transfiere todos los archivos en el directorio raíz del sistema.
-
 - Descarga mediante `rsync` (herramienta de línea de comandos): Utiliza el comando `rsync -avz -e ssh username@vps_ip_address:/ /local_directory/` para descargar todos los archivos y carpetas de tu VPS.
-
 - Descarga mediante la opción **Copia de seguridad automática**: Sigue nuestra guía sobre [cómo usar copias de seguridad automáticas en un VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps) para descargar archivos desde una copia de seguridad.
-
 - Descarga mediante la opción **Snapshot**: Sigue nuestra guía sobre [cómo usar instantáneas en un VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps) para descargar una instantánea del VPS.
 
 ///
@@ -432,9 +429,7 @@ Para verificar que tu dirección IP está autorizada, utiliza la siguiente llama
 Aunque OVHcloud aplica medidas de seguridad para proteger toda la infraestructura, el administrador de un VPS es responsable de la seguridad de las aplicaciones y datos alojados en él.
 
 - Sigue nuestra guía sobre [cómo configurar el Firewall de la Red Edge de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/firewall_network) que está integrado en nuestra infraestructura Anti-DDoS, limitando la exposición de tus servicios a ataques DDoS.
-
 - Además, puedes utilizar nuestras guías sobre [cómo configurar tu propio firewall](/pages/bare_metal_cloud/virtual_private_servers/firewall-Linux-iptable) con `iptables` en distribuciones basadas en Linux y [cómo activar el firewall en Windows](/pages/bare_metal_cloud/virtual_private_servers/activate-port-firewall-soft-win).
-
 - Para distribuciones basadas en Linux en un VPS, puedes seguir las instrucciones de nuestra guía sobre [cómo proteger un VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps) para aplicar medidas de seguridad adicionales.
 
 ///
diff --git a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.fr-fr.md
index 0a2494f0ce8..64173bd61f2 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.fr-fr.md
@@ -371,11 +371,8 @@ Pour cela, aidez-vous de notre guide « [Sécuriser un VPS](/pages/bare_metal_cl
 Plusieurs possibilités s'offrent à vous, par exemple :
 
 - Téléchargement via SFTP : Connectez-vous à votre VPS avec un logiciel client SFTP (par exemple [FileZilla](/pages/bare_metal_cloud/dedicated_servers/comment-deposer-ou-recuperer-des-donnees-sur-un-serveur-dedie-via-sftp)), puis transférez tous les fichiers du répertoire racine du système.
-
 - Téléchargement via `rsync` (outil en ligne de commande) : Utilisez la commande `rsync -avz -e ssh username@vps_ip_address:/ /local_directory/` pour télécharger tous les fichiers et dossiers de votre VPS.
-
 - Téléchargement via l'option **Backup automatisé** : Suivez notre guide sur [l'utilisation des sauvegardes automatisées sur un VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps) pour télécharger des fichiers à partir d'une sauvegarde.
-
 - Téléchargement via l'option **Snapshot** : Suivez notre guide sur [l'utilisation des snapshots sur un VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps) pour télécharger un snapshot du VPS.
 
 ///
@@ -434,12 +431,10 @@ Pour vérifier que votre adresse IP est autorisée, utilisez l'appel suivant :
 
 Bien qu’OVHcloud applique des mesures de sécurité pour protéger l’ensemble de l’infrastructure, l’administrateur d’un VPS est responsable de la sécurité des applications et des données qui y sont hébergées.
 
-- Suivez notre guide « [Comment configurer le Edge Network Firewall OVHcloud](/pages/bare_metal_cloud/dedicated_servers/firewall_network) », service intégré à notre infrastructure Anti-DDoS afin de limiter l'exposition de vos services aux attaques DDoS.
-
+- Suivez notre guide « [Comment configurer le Edge Network Firewall OVHcloud](/pages/bare_metal_cloud/dedicated_servers/firewall_network) », service intégré à notre infrastructure Anti-DDoS afin de limiter l'exposition de vos services aux attaques DDoS. 
 - De plus, vous pouvez utiliser nos guides :
     - [Configurer le pare-feu sous Linux avec Iptables](/pages/bare_metal_cloud/virtual_private_servers/firewall-Linux-iptable)
     - [Configurer le pare-feu sous Windows](/pages/bare_metal_cloud/virtual_private_servers/activate-port-firewall-soft-win).
-
 - Pour les distributions Linux sur un VPS, vous pouvez suivre les instructions de notre guide « [Sécuriser un VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps) » pour appliquer des mesures de sécurité supplémentaires.
 
 ///
diff --git a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.it-it.md
index f55d78fcbb0..955d8bd1c70 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.it-it.md
@@ -366,11 +366,8 @@ Per farlo, si prega di fare riferimento alla nostra guida su [come proteggere un
 Sono disponibili diverse opzioni, ad esempio:
 
 - Scarica via SFTP: Connetti il tuo VPS con un client software in grado di utilizzare SFTP (ad esempio [FileZilla](/pages/bare_metal_cloud/dedicated_servers/comment-deposer-ou-recuperer-des-donnees-sur-un-serveur-dedie-via-sftp)), quindi trasferisci tutti i file nella directory radice del sistema.
-
 - Scarica via `rsync` (strumento da riga di comando): Utilizza il comando `rsync -avz -e ssh username@vps_ip_address:/ /local_directory/` per scaricare tutti i file e le cartelle dal tuo VPS.
-
 - Scarica tramite l'opzione **Backup automatico**: Segui la nostra guida su [come utilizzare i backup automatici su un VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps) per scaricare file da un backup.
-
 - Scarica tramite l'opzione **Snapshot**: Segui la nostra guida su [come utilizzare gli snapshot su un VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps) per scaricare uno snapshot del VPS.
 
 ///
@@ -430,9 +427,7 @@ Per verificare che il tuo indirizzo IP sia autorizzato, utilizza la seguente chi
 Sebbene OVHcloud applichi misure di sicurezza per proteggere l'intera infrastruttura, l'amministratore di un VPS è responsabile della sicurezza delle applicazioni e dei dati ospitati su di esso.
 
 - Segui la nostra guida su [come configurare il firewall della rete Edge di OVHcloud](/pages/bare_metal_cloud/dedicated_servers/firewall_network) integrato nella nostra infrastruttura Anti-DDoS, limitando l'esposizione dei tuoi servizi agli attacchi DDoS.
-
 - Inoltre, puoi utilizzare le nostre guide su [come configurare il tuo firewall](/pages/bare_metal_cloud/virtual_private_servers/firewall-Linux-iptable) con `iptables` su distribuzioni basate su Linux e [come abilitare il firewall su Windows](/pages/bare_metal_cloud/virtual_private_servers/activate-port-firewall-soft-win).
-
 - Per distribuzioni basate su Linux su un VPS, puoi seguire le istruzioni nella nostra guida su [come proteggere un VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps) per applicare misure di sicurezza aggiuntive.
 
 ///
diff --git a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.pl-pl.md
index 1e08de44025..3690810aaf4 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.pl-pl.md
@@ -367,11 +367,8 @@ W tym celu zapoznaj się z przewodnikiem [Zabezpieczenie serwera VPS](/pages/bar
 Istnieje kilka możliwości, na przykład:
 
 - Pobranie przez SFTP: Połącz się z prywatnym serwerem wirtualnym za pomocą klienta programowego dysponującego dostępem SFTP (na przykład [FileZilla](/pages/bare_metal_cloud/dedicated_servers/comment-deposer-ou-recuperer-des-donnees-sur-un-serveur-dedie-via-sftp)), następnie prześlij wszystkie pliki z katalogu głównego systemu.
-
 - Pobierz za pomocą `rsync` (narzędzie wiersza poleceń): Wpisz polecenie `rsync -avz -e ssh nazwa użytkownika@vps_ip_address:/ /local_directory/`, aby pobrać z Twojego serwera VPS wszystkie pliki i foldery.
-
 - Pobierz za pomocą opcji **Automatyczne kopie zapasowe**: Zapoznaj się z przewodnikiem [Jak korzystać ze zautomatyzowanych kopii zapasowych na serwerze VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps), aby pobrać pliki z kopii zapasowej.
-
 - Pobierz za pomocą opcji **Snapshot**: Zapoznaj się z przewodnikiem [Jak korzystać z Snapshotów na serwerze VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps), aby pobrać snapshot z serwera VPS.
 
 ///
@@ -431,9 +428,7 @@ Aby sprawdzić, czy adres IP jest dozwolony, użyj następującego wywołania:
 Chociaż OVHcloud stosuje środki bezpieczeństwa w celu ochrony całej infrastruktury, administrator serwera VPS jest odpowiedzialny za bezpieczeństwo aplikacji i danych na nim hostowanych.
 
 - Zapoznaj się z przewodnikiem [Aktywacja i konfiguracja Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network), który jest zintegrowany z naszą infrastrukturą Anty-DDoS, ograniczając ekspozycję Twoich usług na ataki DDoS.
-
 - Ponadto, zapoznaj się z naszymi przewodnikami dotyczącymi [jak skonfigurować własny firewall](/pages/bare_metal_cloud/virtual_private_servers/firewall-Linux-iptable) z `iptable` dla dystrybucji opartych na systemie Linux oraz [jak włączyć firewall w systemie Windows](/pages/bare_metal_cloud/virtual_private_servers/activate-port-firewall-soft-win).
-
 - W przypadku dystrybucji opartych na systemie Linux na serwerze VPS należy postępować zgodnie z instrukcjami zawartymi w przewodniku [How to secure a VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps), aby zastosować dodatkowe środki bezpieczeństwa.
 
 ///
diff --git a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.pt-pt.md
index b661a4db7ad..c00535286f4 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/vps-faq/guide.pt-pt.md
@@ -368,11 +368,8 @@ Para isso, consulte nosso guia sobre [como proteger um VPS](/pages/bare_metal_cl
 Existem várias opções disponíveis, por exemplo:
 
 - Baixar via SFTP: Conecte-se ao seu VPS com um cliente de software capaz de SFTP (por exemplo, [FileZilla](/pages/bare_metal_cloud/dedicated_servers/comment-deposer-ou-recuperer-des-donnees-sur-un-serveur-dedie-via-sftp)), depois transfira todos os arquivos no diretório raiz do sistema.
-
 - Baixar via `rsync` (ferramenta de linha de comando): Use o comando `rsync -avz -e ssh username@vps_ip_address:/ /local_directory/` para baixar todos os arquivos e pastas do seu VPS.
-
 - Baixar via a opção **Backup Automático**: Siga nosso guia sobre [como usar backups automáticos em um VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps) para baixar arquivos de um backup.
-
 - Baixar via a opção **Snapshot**: Siga nosso guia sobre [como usar snapshots em um VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps) para baixar um snapshot do VPS.
 
 ///
@@ -432,9 +429,7 @@ Para verificar se seu endereço IP está autorizado, use a seguinte chamada:
 Embora a OVHcloud aplique medidas de segurança para proteger toda a infraestrutura, o administrador de um VPS é responsável pela segurança das aplicações e dados hospedados nele.
 
 - Siga nosso guia sobre [como configurar a firewall da OVHcloud Edge Network](/pages/bare_metal_cloud/dedicated_servers/firewall_network), integrada em nossa infraestrutura Anti-DDoS, limitando a exposição dos seus serviços a ataques DDoS.
-
 - Além disso, você pode usar nossos guias sobre [como configurar sua própria firewall](/pages/bare_metal_cloud/virtual_private_servers/firewall-Linux-iptable) com `iptables` em distribuições baseadas em Linux e [como ativar a firewall no Windows](/pages/bare_metal_cloud/virtual_private_servers/activate-port-firewall-soft-win).
-
 - Para distribuições baseadas em Linux em um VPS, você pode seguir as instruções em nosso guia sobre [como proteger um VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps) para aplicar medidas de segurança adicionais.
 
 ///
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.de-de.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.de-de.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.de-de.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-asia.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-asia.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-asia.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-au.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-au.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-au.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-ca.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-ca.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-ca.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-gb.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-gb.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-gb.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-ie.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-ie.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-ie.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-sg.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-sg.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-sg.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-us.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-us.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-us.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.es-es.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.es-es.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.es-es.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.es-us.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.es-us.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.es-us.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.fr-ca.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.fr-ca.md
index 5393efd36a3..109363e348a 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.fr-ca.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Les concepts fondamentaux de Public VCF as-a-Service"
 excerpt: "Decouvrez les concepts fondamentaux de Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objectif
@@ -58,7 +58,6 @@ De plus, les administrateurs d'organisation ont la capacité de copier des élé
 
 <a name="key-features"></a>
 
-
 ### Fonctionnalités de Public VCF as-a-Service chez OVHcloud
 
 Retrouvez ci-dessous une comparaison des fonctionnalités fournies par OVHcloud sur ses 3 offres de Public VCF as-a-Service.
@@ -67,7 +66,6 @@ Retrouvez ci-dessous une comparaison des fonctionnalités fournies par OVHcloud
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅             |       -     |
-|Public VCF as-a-Service Premium  |              ✅             |       ✅      |
 
 #### Cluster Management
 
@@ -84,65 +82,64 @@ Retrouvez ci-dessous une comparaison des fonctionnalités fournies par OVHcloud
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                             	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                 Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               |
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|        	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳     	|    ⏳      	| In Roadmap (via OVHcloud uIAM service)                                    |
+| vCPU over-allocation                	|     ⏳    	|    ⏳    	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	 | Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	        |
-|-----------------------------------|----------	|----------	|---------	|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Routing & Switching IPv4        	 |         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	        |
-| Public IPv4 Range               	 | ✅        	| ✅        	| ✅       	| 	                                                                                                                                                                                                           |
-| Private Network - vRack support   | ✅        	| ✅        	| ✅       	| In Roadmap                                                                                                                                                                                                	 |
-| Routing & Switching IPv6        	 |          	|          	|         	| in Roadmap                                                                                                                                                                                         	        |
-| VPN                             	 |          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	        |
-| Load Balancing                  	 |          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	        |
-| Advanced Load Balancing         	 |          	|          	|         	| In Roadmap                                                                                                                                                                                         	        |                                                                                          	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+| Routing & Switching IPv4        	 |  -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	        |
+| Public IPv4 Range               	 | ✅        	| ✅        	|  	                                                                                                                                                                                                           |
+| Private Network - vRack support   | ✅        	| ✅        	| In Roadmap                                                                                                                                                                                                	 |
+| Routing & Switching IPv6        	 | -         	| ⏳         	|  in Roadmap                                                                                                                                                                                         	        |
+| VPN                             	 | -         	| ✅        	|  L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	        |
+| Load Balancing                  	 | -        	| -       	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	        |
+| Advanced Load Balancing         	 | -        	| ⏳         	| In Roadmap                                                                                                                                                                                         	        |                                                                                          	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	|  -      	|     ✅    	|           |
+| Distributed Firewall 	|  -      	|     ✅    	|           |
+|    Security groups   	|  -       	|     ✅    	|           |
+|       IDS / IPS      	|  -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	|  -        	|     ⏳     	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	|Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|          1 per VM          	|
+| Protection / Replication VMs 	|     ⏳     	|     ⏳    	| in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|    ⏳     	|     ⏳  	| In Roadmap - Resource management Metrics, Dashboard, Reporting|
 
 ## Aller plus loin
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.fr-fr.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.fr-fr.md
index 5393efd36a3..109363e348a 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.fr-fr.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Les concepts fondamentaux de Public VCF as-a-Service"
 excerpt: "Decouvrez les concepts fondamentaux de Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objectif
@@ -58,7 +58,6 @@ De plus, les administrateurs d'organisation ont la capacité de copier des élé
 
 <a name="key-features"></a>
 
-
 ### Fonctionnalités de Public VCF as-a-Service chez OVHcloud
 
 Retrouvez ci-dessous une comparaison des fonctionnalités fournies par OVHcloud sur ses 3 offres de Public VCF as-a-Service.
@@ -67,7 +66,6 @@ Retrouvez ci-dessous une comparaison des fonctionnalités fournies par OVHcloud
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅             |       -     |
-|Public VCF as-a-Service Premium  |              ✅             |       ✅      |
 
 #### Cluster Management
 
@@ -84,65 +82,64 @@ Retrouvez ci-dessous une comparaison des fonctionnalités fournies par OVHcloud
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                             	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                 Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               |
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|        	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳     	|    ⏳      	| In Roadmap (via OVHcloud uIAM service)                                    |
+| vCPU over-allocation                	|     ⏳    	|    ⏳    	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	 | Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	        |
-|-----------------------------------|----------	|----------	|---------	|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Routing & Switching IPv4        	 |         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	        |
-| Public IPv4 Range               	 | ✅        	| ✅        	| ✅       	| 	                                                                                                                                                                                                           |
-| Private Network - vRack support   | ✅        	| ✅        	| ✅       	| In Roadmap                                                                                                                                                                                                	 |
-| Routing & Switching IPv6        	 |          	|          	|         	| in Roadmap                                                                                                                                                                                         	        |
-| VPN                             	 |          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	        |
-| Load Balancing                  	 |          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	        |
-| Advanced Load Balancing         	 |          	|          	|         	| In Roadmap                                                                                                                                                                                         	        |                                                                                          	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+| Routing & Switching IPv4        	 |  -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	        |
+| Public IPv4 Range               	 | ✅        	| ✅        	|  	                                                                                                                                                                                                           |
+| Private Network - vRack support   | ✅        	| ✅        	| In Roadmap                                                                                                                                                                                                	 |
+| Routing & Switching IPv6        	 | -         	| ⏳         	|  in Roadmap                                                                                                                                                                                         	        |
+| VPN                             	 | -         	| ✅        	|  L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	        |
+| Load Balancing                  	 | -        	| -       	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	        |
+| Advanced Load Balancing         	 | -        	| ⏳         	| In Roadmap                                                                                                                                                                                         	        |                                                                                          	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	|  -      	|     ✅    	|           |
+| Distributed Firewall 	|  -      	|     ✅    	|           |
+|    Security groups   	|  -       	|     ✅    	|           |
+|       IDS / IPS      	|  -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	|  -        	|     ⏳     	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	|Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|          1 per VM          	|
+| Protection / Replication VMs 	|     ⏳     	|     ⏳    	| in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|    ⏳     	|     ⏳  	| In Roadmap - Resource management Metrics, Dashboard, Reporting|
 
 ## Aller plus loin
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.it-it.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.it-it.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.it-it.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.pl-pl.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.pl-pl.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.pl-pl.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.pt-pt.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.pt-pt.md
index 27cf4f539e2..da993c2a931 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.pt-pt.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-get-concepts/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - The fundamentals of Public VCF as-a-Service"
 excerpt: "Discover the basic concepts of Public VCF as-a-Service"
-updated: 2024-12-19
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -66,7 +66,6 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 |:------------:|:---------------------------:|:------------:|
 |Public VCF as-a-Service Standard |              -              |       -      |
 |Public VCF as-a-Service Advanced |              ✅              |       -      |
-|Public VCF as-a-Service Premium  |              ✅              |       ✅      |
 
 #### Cluster Management
 
@@ -83,65 +82,64 @@ Below is a comparison of the features provided by OVHcloud on its 3 Public VCF a
 
 ##### Virtual Machine Management
 
-|         Features        	| Standard 	| Advanced 	| Premium 	|                                    Comments                                   	|
-|:-----------------------:	|:--------:	|:--------:	|:-------:	|:-----------------------------------------------------------------------------:	|
-|        Create VM        	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-| Manage Virtual Machines 	|     ✅    	|     ✅    	|    ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
-|      Affinity Rules     	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|    ✅    	|                                                                               	|
-|    VMware Marketplace   	|     ✅    	|     ✅     |    ✅     	| Allowed to deploy VMs with pre-packaged software solutions  	                    |
-|    Create VM catalogs   	|     ✅    	|     ✅     |    ✅     	|                     Build your own catalog of VM templates                    	|
+|         Features        	| Standard 	| Advanced 	|                                    Comments                                   	|
+|:-----------------------:	|:--------:	|:--------:	|:-----------------------------------------------------------------------------:	|
+|        Create VM        	|     ✅    	|     ✅    	|                                                                               	|
+| Manage Virtual Machines 	|     ✅    	|     ✅    	|                  Start, Stop, Suspend, Delete, Copy/clone...                  	|
+|      Affinity Rules     	|     ✅    	|     ✅    	|                                                                               	|
+|   Anti-Affinity Rules   	|     ✅    	|     ✅    	|                                                                              	|
+|    VMware Marketplace   	|     ✅    	|     ✅     | Allowed to deploy VMs with pre-packaged software solutions  	                    |
+|    Create VM catalogs   	|     ✅    	|     ✅     |                     Build your own catalog of VM templates                    	|
 
 #### Organisation / Virtual Datacenter Management
 
-|               Features              	| Standard 	| Advanced 	| Premium 	|                                                 Comments                                                	|
-|:-----------------------------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------------------------------------------------------------:	|
-|           User Management           	|     ✅    	|     ✅    	|    ✅    	|            Manage users in a Public VCF as-a-Service           	|
-| Identity Provider Integration - SSO 	|          	|          	|         	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
-| vCPU over-allocation                	|         	|        	|       	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
+|               Features              	| Standard 	| Advanced 	|                                                 Comments                                                	|
+|:-----------------------------------:	|:--------:	|:--------:	|:-------------------------------------------------------------------------------------------------------:	|
+|           User Management           	|     ✅    	|     ✅    	|            Manage users in a Public VCF as-a-Service           	|
+| Identity Provider Integration - SSO 	|     ⏳    	|     ⏳    	| In Roadmap (via OVHcloud uIAM service)                                                                  	|
+| vCPU over-allocation                	|     ⏳   	|     ⏳  	| In Roadmap - Allow users to adjust the quantity of vCPU/GHz for a virtual DC Possible through **OVH manager or API** 	|
 
 #### Networking
 
-| Features                        	| Standard 	| Advanced 	| Premium 	| Comments                                                                                                                                                                                           	|
+| Features                        	| Standard 	| Advanced 	|Comments                                                                                                                                                                                           	|
 |---------------------------------	|----------	|----------	|---------	|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------	|
-| Routing & Switching IPv4        	|         	| ✅        	| ✅       	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
-| Public IPv4 Range               	| ✅        	| ✅        	| ✅       	|                                                                                                                                                                                                    	|
-| Private Network - vRack support 	| ✅        	| ✅        	| ✅       	| in Roadmap                                                                                                                                                                                                   	|
-| Routing & Switching IPv6        	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
-| VPN                             	|          	| ✅        	| ✅       	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
-| Load Balancing                  	|          	|          	|         	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
-| Advanced Load Balancing         	|          	|          	|         	| in Roadmap                                                                                                                                                                                         	|
+| Routing & Switching IPv4        	| -       	| ✅        	| Network segments, distributed & non distributed routing, Routed Network with/without NAT BGP/ DHCP/ DNS/ Static routes Cross virtual DC Networking on the same site. Not supported: OSPF, VRF Lite 	|
+| Public IPv4 Range               	| ✅        	| ✅        	|                                                                                                                                                                                                     	|
+| Private Network - vRack support 	| ✅        	| ✅        	|  in Roadmap                                                                                                                                                                                                   	|
+| Routing & Switching IPv6        	| -        	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
+| VPN                             	| -        	| ✅        	| L2VPN, VPN IPsec Policy Based Not Supported : SSL VPN, Routed based IPsec VPN                                                                                                                      	|
+| Load Balancing                  	| -        	| -        	| Not supported with native Public VCF as-a-Service network capabilities                                                                                                                                                 	|
+| Advanced Load Balancing         	| -         	| ⏳        	| in Roadmap                                                                                                                                                                                         	|
 
 #### Security
 
-|       Features       	| Standard 	| Advanced 	| Premium 	|  Comments  	|
-|:--------------------:	|:--------:	|:--------:	|:-------:	|:----------:	|
-|   Stateful Firewall  	|        	|     ✅    	|    ✅    	|            	|
-| Distributed Firewall 	|        	|     ✅    	|    ✅    	|            	|
-|    Security groups   	|         	|     ✅    	|    ✅    	|            	|
-|       IDS / IPS      	|          	|          	|         	| in Roadmap 	|
-|          WAF         	|          	|          	|         	| in Roadmap 	|
+|       Features       	| Standard 	| Advanced 	| |  Comments  	|
+|:--------------------:	|:--------:	|:--------:	|:----------:	|
+|   Stateful Firewall  	| -      	|     ✅    	|            	|
+| Distributed Firewall 	| -      	|     ✅    	|            	|
+|    Security groups   	| -       	|     ✅    	|            	|
+|       IDS / IPS      	| -        	|     ⏳    	| in Roadmap 	|
+|          WAF         	| -        	|     ⏳    	| in Roadmap 	|
 
 #### Data protection
 
-|           Features           	| Standard 	| Advanced 	| Premium 	|           Comments          	|
-|:----------------------------:	|:--------:	|:--------:	|:-------:	|:---------------------------:	|
-|      Backup as a Service     	|     ✅    	|     ✅    	|    ✅    	| Veeam Managed Backup Option 	|
-|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|    ✅    	|           1 per VM          	|
-| Protection / Replication VMs 	|          	|          	|         	|          in Roadmap         	|
+|           Features           	| Standard 	| Advanced 	|           Comments          	|
+|:----------------------------:	|:--------:	|:--------:	|:---------------------------:	|
+|      Backup as a Service     	|     ✅    	|     ✅    	| Veeam Managed Backup Option 	|
+|   Virtual Machine Snapshots  	|     ✅    	|     ✅    	|           1 per VM          	|
+| Protection / Replication VMs 	|     ⏳    	|     ⏳    	|          in Roadmap         	|
 
 #### Storage
 
-|              Features             	| Standard 	| Advanced 	| Premium 	| Comments 	|
-|:---------------------------------:	|:--------:	|:--------:	|:-------:	|:--------:	|
-|           NFS datastore           	|     ✅    	|     ✅    	|    ✅    	|          	|
-| High performance datastore (vSAN) 	|          	|          	|    ✅    	|          	|
+|              Features             	| Standard 	| Advanced 	| Comments 	|
+|:---------------------------------:	|:--------:	|:--------:	|:--------:	|
+|           NFS datastore           	|     ✅    	|     ✅    	|          	|
 
 #### Monitoring
 
-|     Features    	| Standard 	| Advanced 	| Premium 	|                      Comments                     	|
-|:---------------:	|:--------:	|:--------:	|:-------:	|:-------------------------------------------------:	|
-| Aria operations 	|         	|         	|        	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
+|     Features    	| Standard 	| Advanced 	|                      Comments                     	|
+|:---------------:	|:--------:	|:--------:	|:-------------------------------------------------:	|
+| Aria operations 	|   ⏳    	|    ⏳    	| In Roadmap - Resource management Metrics, Dashboard, Reporting 	|
 
 ## Go further
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.de-de.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.de-de.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.de-de.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-asia.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-asia.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-asia.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-au.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-au.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-au.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-ca.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-ca.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-ca.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-gb.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-gb.md
index 552f9834004..ed33839d191 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-gb.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-03
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-ie.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-ie.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-ie.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-sg.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-sg.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-sg.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-us.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-us.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-us.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.es-es.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.es-es.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.es-es.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.es-us.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.es-us.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.es-us.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.fr-ca.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.fr-ca.md
index 512d84c6775..47304d480d4 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.fr-ca.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Concepts réseaux et bonnes pratiques"
 excerpt: "Découvrez les puissantes capacités de mise en réseau de Public VCF as-a-Service avec ce guide complet sur les concepts et fonctionnalités clés"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,7 +97,6 @@ Voici un comparatif des 3 offres proposées par Public VCF as-a-Service.
 |:-----------------:|:---------------------------:|:------------:|
 | **Public VCF as-a-ServiceStandard.** |              -              |      -       |
 | **Public VCF as-a-ServiceAdvanced.** |              ✅              |       -      |
-| **Public VCF as-a-ServicePremium.**  |              ✅              |      ✅       |
 
 Les fonctionnalités de réseau avancé et de sécurité au sein de Public VCF as-a-Service ne sont disponibles que dans les offres **Advanced et Premium**.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.fr-fr.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.fr-fr.md
index 1df2583c16c..49d15b21be9 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.fr-fr.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Concepts réseaux et bonnes pratiques"
 excerpt: "Découvrez les puissantes capacités de mise en réseau de Public VCF as-a-Service avec ce guide complet sur les concepts et fonctionnalités clés"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,7 +97,6 @@ Voici un comparatif des 3 offres proposées par Public VCF as-a-Service.
 |:-----------------:|:---------------------------:|:------------:|
 | **Public VCF as-a-ServiceStandard.** |              -              |      -       |
 | **Public VCF as-a-ServiceAdvanced.** |              ✅              |       -      |
-| **Public VCF as-a-ServicePremium.**  |              ✅              |      ✅       |
 
 Les fonctionnalités de réseau avancé et de sécurité au sein de Public VCF as-a-Service ne sont disponibles que dans les offres **Advanced et Premium**.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.it-it.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.it-it.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.it-it.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.pl-pl.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.pl-pl.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.pl-pl.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.pt-pt.md b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.pt-pt.md
index 552f9834004..2303cbfdc3c 100644
--- a/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.pt-pt.md
+++ b/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_network_concepts/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "Public VCF as-a-Service - Network concepts and best practices"
 excerpt: "Discover the powerful networking capabilities of Public VCF as-a-Service with this comprehensive guide (key concepts and features)"
-updated: 2025-03-03
+updated: 2025-11-04
 ---
 
 <style>
@@ -97,8 +97,7 @@ Here is a comparison of the 3 solutions offered by Public VCF as-a-Service.
 |              | Advanced Network & Security | vSAN Storage |
 |:------------:|:---------------------------:|:------------:|
 | Standard Public VCF as-a-Service |              -              |      -       |
-|Public VCF as-a-Service Advanced |              ✅              |      -       |
-|Public VCF as-a-Service Premium  |              ✅               |       ✅       |
+| Public VCF as-a-Service Advanced |              ✅              |      -       |
 
 Here we see that only the advanced networking and security features within Public VCF as-a-Service are available in the **Advanced and Premium** offers.
 
diff --git a/pages/hosted_private_cloud/opcp/how-to-setup-lacp-on-a-node/guide.fr-fr.md b/pages/hosted_private_cloud/opcp/how-to-setup-lacp-on-a-node/guide.fr-fr.md
new file mode 100644
index 00000000000..83b07c005cc
--- /dev/null
+++ b/pages/hosted_private_cloud/opcp/how-to-setup-lacp-on-a-node/guide.fr-fr.md
@@ -0,0 +1,367 @@
+---
+title: "OPCP - Comment configurer LACP sur un noeud"
+excerpt: "Apprenez à configurer un noeud dans OpenStack pour utiliser LACP (Link Aggregation Control Protocol)"
+updated: 2025-11-07
+---
+
+
+## Objectif
+
+Ce guide explique comment configurer un **noeud** (serveur physique) dans **OPCP** pour activer **LACP (Link Aggregation Control Protocol)**.  
+La configuration de LACP doit être appliquée sur le noeud avant de déployer une instance, afin que les interfaces réseau soient correctement agrégées.
+Nous verrons également comment configurer le **bonding** (association logique de plusieurs interfaces réseau pour former une seule interface virtuelle) au niveau de votre instance, afin de tirer pleinement parti du **LACP**.
+
+> [!warning]
+> Un utilisateur standard ne peut pas configurer LACP lui-même.  
+> Vous devez être **admin**, ou disposer de **noeud disponible** dans votre projet OpenStack.
+>
+> Il est recommandé de configurer LACP **avant** le déploiement d’une instance.  
+> Ce guide **ne couvre pas** la configuration d'un noeud déjà en production.
+
+## Pourquoi utiliser LACP ?
+
+LACP peut être utilisé dans deux cas d'usage précis :  
+
+- **Augmenter la capacité réseau.** En agrégeant plusieurs cartes réseau, vous pourrez ajouter la bande passante de chaque carte réseau ajoutée à cet agrégat, pour les mêmes réseaux.
+- **Augmenter la résilience.** Chaque serveur de OPCP bénéficie de 4 interfaces 25G. Chaque serveur est relié à deux switchs réseau (A&B) pour assurer la résilience en cas de panne matérielle de l'un d'entre eux. LACP permet de créer des interfaces virtuelles résilientes en cas de panne matérielle en aggrégant deux cartes réseau reliées sur des switchs distincts.
+
+## Prérequis
+
+Avant de commencer, assurez-vous de disposer des éléments suivants :
+
+- Disposer d'un service [OPCP](/links/hosted-private-cloud/onprem-cloud-platform) actif.
+- Un accès **[OpenStack CLI configuré](/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials)** avec les droits nécessaires (`clouds.yaml` ou variables d’environnement).
+- Le rôle **admin** et/ou ou des noeuds transférés dans votre projet.
+- LACP est une configuration réseau spécifique, nécessitant des connaissances réseau et système avancées. Nous vous conseillons d'appliquer ce guide si vous connaissez déjà l'un ou plusieurs des concepts suivants : configuration de noeuds au sein de OpenStack Ironic, gestion des ports au sein de OpenStack Neutron, et la connaissance de la CLI OpenStack
+
+## En pratique
+
+### Configuration du noeud
+
+#### 1. Lister les noeuds
+
+La liste des noeuds disponibles dans votre projet peut être affichée avec la commande suivante :
+
+```bash
+openstack baremetal node list
+```
+
+**Exemple de sortie :**
+
+```bash
++--------------------------------------+----------------+--------------------------------------+-------------+--------------------+-------------+
+| UUID                                 | Name           | Instance UUID                        | Power State | Provisioning State | Maintenance |
++--------------------------------------+----------------+--------------------------------------+-------------+--------------------+-------------+
+| 88830859-5b16-4935-8f41-d381b754cbe5 | SERVER-1       | None                                 | power off   | available          | False       |
+| 726bb7e9-3b20-4a44-99d7-2af747983781 | SERVER-2       | None                                 | power off   | available          | False       |
+| af711edf-a579-491e-b474-3c03639ed99b | SERVER-3       | 83b7083b-bbdd-4327-941c-ee91197818c5 | None        | active             | True        |
++--------------------------------------+----------------+--------------------------------------+-------------+--------------------+-------------+
+```
+
+---
+
+#### 2. Transférer la propriété d’un noeud (admin uniquement)
+
+Un admin peut transférer la propriété d’un noeud à un projet donné :
+
+```bash
+openstack baremetal node set <node-id> --owner <project-id>
+```
+
+---
+
+#### 3. Lister les ports réseau
+
+Chaque carte réseau physique, appelée Network Interface Card (NIC), d’un nœud est représentée dans OpenStack par un port.
+
+Pour afficher la liste des ports associés à un noeud :
+
+```bash
+openstack baremetal port list --node <node-id>
+```
+
+**Exemple de sortie :**
+
+```bash
++--------------------------------------+-------------------+
+| UUID                                 | Address           |
++--------------------------------------+-------------------+
+| 068a06b2-ebf9-48c9-a3c3-94016ca5e3da | 85:32:f2:87:29:da |
+| 4937d704-7517-4525-86d1-abecb94a7ce9 | 85:32:f2:87:29:db |
+| 422eece6-dcfa-40cd-975d-ba8bb11c774e | 85:32:f2:89:66:f8 |
+| 34073903-92ad-47d1-a751-15aa96991415 | 85:32:f2:89:66:f9 |
++--------------------------------------+-------------------+
+```
+
+Pour visualiser les détails d'un port, y compris les informations sur la connexion physique.
+Cela est particulièrement utile si vous souhaitez configurer un **bonding LACP 2x2**, en répartissant les NIC sur deux switches différents pour assurer une **meilleure redondance et tolérance aux pannes**.  
+
+```bash
+openstack baremetal port show <port-id>
+```
+
+**Exemple de sortie :**
+
+```bash
+openstack baremetal port show 71899d54-546d-4fdd-8d8b-52ad986bf425
++-----------------------+------------------------------------------------------------------------------------------------+
+| Field                 | Value                                                                                          |
++-----------------------+------------------------------------------------------------------------------------------------+
+| address               | 85:32:f2:89:66:f9                                                                             |
+| created_at            | 2025-01-06T10:43:38.020574+00:00                                                               |
+| extra                 | {}                                                                                             |
+| internal_info         | {}                                                                                             |
+| is_smartnic           | False                                                                                          |
+| local_link_connection | {'switch_id': 'c0:00:15:8c:33:78', 'port_id': 'Ethernet25/2', 'switch_info': 'demo-tor1b-a70'} |
+| node_uuid             | ddc7c763-74fc-4900-b9e6-5463233836b0                                                           |
+| physical_network      | None                                                                                           |
+| portgroup_uuid        | c3d3fcb3-7a92-4257-b944-736d222e8c4a                                                           |
+| pxe_enabled           | False                                                                                          |
+| updated_at            | 2025-11-06T09:52:46.355883+00:00                                                               |
+| uuid                  | 71899d54-546d-4fdd-8d8b-52ad986bf425                                                           |
++-----------------------+------------------------------------------------------------------------------------------------+
+```
+
+---
+
+#### 4. Activer le mode maintenance
+
+Avant toute modification de configuration réseau, le noeud doit être placé en **mode maintenance**. Cela assure que ce noeud ne puisse pas être déployé durant toute l'opération  :
+
+```bash
+openstack baremetal node maintenance set <node-id>
+```
+
+---
+
+#### 5. Créer un groupe de ports (LACP Bond)
+
+Le **groupe de ports** permet d’activer l’agrégation LACP entre plusieurs interfaces réseau.
+
+Utilisez le paramètre `--mode 802.3ad` pour activer LACP.  
+Si vous n’indiquez pas d’adresse MAC avec `--address`, l’adresse d’un des ports sera utilisée automatiquement.
+
+> [!note]
+> Vous pouvez créer :
+> - un **groupe de ports unique** pour un bond 1×4, ou  
+> - deux **groupes de ports** pour des bonds 2×2.
+
+**Exemple :**
+
+```bash
+openstack baremetal port group create \
+  --node 88830859-5b16-4935-8f41-d381b754cbe5 \
+  --name portgroup-lacp \
+  --mode 802.3ad \
+  --address 00:00:00:20:00:01
+```
+
+**Exemple de sortie :**
+
+```bash
++----------------------------+-------------------------------------------+
+| Champ                      | Valeur                                    |
++----------------------------+-------------------------------------------+
+| uuid                       | d082c2ab-5960-44e3-920d-3d6dfb6811e9      |
+| address                    | 00:00:00:20:00:01                         |
+| node_uuid                  | 88830859-5b16-4935-8f41-d381b754cbe5      |
+| name                       | portgroup-lacp                            |
+| mode                       | 802.3ad                                   |
+| standalone_ports_supported | True                                      |
++----------------------------+-------------------------------------------+
+```
+
+---
+
+#### 6. Associer les ports au groupe
+
+Chaque port du noeud doit être associé au groupe de ports créé :
+
+```bash
+openstack baremetal port set --port-group <port-group-id> <port-id>
+```
+
+**Exemple :**
+
+```bash
+openstack baremetal port set --port-group d082c2ab-5960-44e3-920d-3d6dfb6811e9 068a06b2-ebf9-48c9-a3c3-94016ca5e3da
+openstack baremetal port set --port-group d082c2ab-5960-44e3-920d-3d6dfb6811e9 4937d704-7517-4525-86d1-abecb94a7ce9
+openstack baremetal port set --port-group d082c2ab-5960-44e3-920d-3d6dfb6811e9 422eece6-dcfa-40cd-975d-ba8bb11c774e
+openstack baremetal port set --port-group d082c2ab-5960-44e3-920d-3d6dfb6811e9 34073903-92ad-47d1-a751-15aa96991415
+```
+
+---
+
+#### 7. Désactiver le mode maintenance
+
+Une fois la configuration terminée, désactivez le mode maintenance :
+
+```bash
+openstack baremetal node maintenance unset  <node-id>
+```
+
+---
+
+#### 8. Créer une instance sur le noeud configuré
+
+Une fois votre noeud configuré avec LACP, vous pouvez déployer une instance.
+
+Par défaut, OpenStack sélectionne un hôte en fonction du **flavor** choisi et des **règles du scheduler**, ce qui ne garantit pas que le noeud que vous venez de configurer sera utilisé.
+
+Pour vous assurer que votre instance sera déployée sur ce nœud précis, vous pouvez cibler ce dernier utilisant sa **zone de disponibilité** :
+
+```bash
+openstack server create --availability-zone "nova::<node-id>"
+```
+
+**Exemple :**
+
+```bash
+openstack server create --image <image-name> \
+   --nic net-id=NETWORK1,v4-fixed-ip=198.18.56.200 \
+   --flavor <flavor-id> \
+   --key-name <keypair-name>  \
+   --availability-zone "nova::<node-id>" \
+   <instance-name>
+```
+
+---
+
+#### Résumé des étapes
+
+| Étape | Action | Commande |
+|-------|---------|-----------|
+| 1 | Lister les noeuds | `openstack baremetal node list` |
+| 2 | Transférer la propriété | `openstack baremetal node set <node-id> --owner <tenant-id>` |
+| 3 | Lister les ports | `openstack baremetal port list --node <node-id>` |
+| 4 | Activer le mode maintenance | `openstack baremetal node maintenance set <node-id>` |
+| 5 | Créer un groupe LACP | `openstack baremetal port group create --node <node-id> --name <port-group-name> --mode 802.3ad` |
+| 6 | Associer les ports | `openstack baremetal port set --port-group <port-group-id> <port-id>` |
+| 7 | Désactiver le mode maintenance | `openstack baremetal node maintenance unset <node-id>` |
+| 8 | Créer une instance | `openstack server create --image <image-name> --nic net-id=<network-1> --flavor <flavor-id> --key-name <keypair-name> --availability-zone "nova::<node-id>" <instance-name>` |
+
+### Configuration du système d’exploitation de l’instance
+
+Après avoir configuré votre noeud dans OpenStack et déployé un système d’exploitation, il reste à configurer le réseau afin de bénéficier du network **bonding**, qui permet d’agréger plusieurs interfaces réseau pour plus de performance et de redondance.
+
+#### Vérifier la configuration du bonding
+
+Sur certaines images (comme **Debian 12** ou **Ubuntu 22.04**), la configuration du **bonding** est automatiquement détectée et configurée.  
+Cependant, d’autres distributions peuvent nécessiter un ajustement manuel.
+
+##### 1. Vérifier les bonds actifs
+
+```bash
+ls /proc/net/bonding/
+bond0
+```
+
+##### 2. Vérifier les interfaces membres
+
+```bash
+cat /proc/net/bonding/bond0 | grep Interface
+Slave Interface: ens22f1np1
+Slave Interface: ens22f0np0
+Slave Interface: ens21f1np1
+Slave Interface: ens21f0np0
+```
+
+---
+
+##### 3. Vérifier la politique de hachage (`Transmit Hash Policy`)
+
+```bash
+cat /proc/net/bonding/* | grep Trans
+Transmit Hash Policy: layer2 (0)
+```
+
+> [!warning]  
+> Pour exploiter toute la bande passante, configurez la politique `layer3+4` (par défaut, certains OS utilisent `layer2`, moins performante).  
+> Plus de détails : [Ubuntu Bonding Documentation](https://help.ubuntu.com/community/UbuntuBonding?utm_source=chatgpt.com)
+
+---
+
+#### Modifier la configuration
+
+##### 1. Changement à chaud (non persistant)
+
+Si vous souhaitez tester votre configuration manuellement, vous pouvez utiliser la commande suivante :
+
+```bash
+sudo ip link set bond0 type bond xmit_hash_policy layer3+4
+```
+
+Attention, cette configuration sera réinitialisée si votre machine redémarre.
+
+#### 2. Changement persistant (exemple via Netplan et cloud-init)
+
+Créez votre fichier de configuration (ex. `/etc/cloud/cloud.cfg.d/99-custom-network.cfg`) pour y inclure :
+
+```yaml
+network:
+  version: 2
+  ethernets:
+    ens21f0np0: {}
+    ens21f1np1: {}
+    ens22f0np0: {}
+    ens22f1np1: {}
+  bonds:
+    bond0:
+      dhcp4: true
+      interfaces:
+        - ens21f0np0
+        - ens21f1np1
+        - ens22f0np0
+        - ens22f1np1
+      macaddress: 00:00:00:20:00:23
+      parameters:
+        mode: 802.3ad
+        transmit-hash-policy: layer3+4
+        lacp-rate: fast
+        mii-monitor-interval: 100
+```
+
+Puis appliquez la configuration en rédémarrant l'instance.
+
+---
+
+#### 3. Tester la bande passante avec `iperf3`
+
+Pour tester correctement LACP, vous devez disposer de **2 noeuds** dans le **même réseau**, tous deux configurés avec LACP.
+
+##### noeud Iperf3 (noeud 1)
+
+```bash
+iperf3 -s
+```
+
+##### Client Iperf3 (noeud 2)
+
+Utilisez `-P` pour générer plusieurs flux parallèles, afin d’atteindre la bande passante maximale.
+
+```bash
+iperf3 -c <ip-du-noeud> -P 64
+```
+
+##### Exemple de résultat
+
+```bash
+[SUM] 0.0000-10.0121 sec   110 GBytes  94.0 Gbits/sec
+```
+
+Avec un lien 4×25 Gbps, vous devriez atteindre environ **100 Gbps**.  
+Il peux être nécessaire d'ajuster certains paramètres système pour exploiter pleinement cette capacité.
+
+---
+
+## Conclusion
+
+Vous avez configuré :
+
+- Le **LACP (802.3ad)** au niveau du noeud Baremetal OpenStack,  
+- Le **paramétrage du bonding** dans l’OS invité,  
+- Et validé la **performance réseau** via `iperf3`.
+
+Votre instance est désormais prête à exploiter toute la bande passante disponible du lien agrégé.
+
+---
diff --git a/pages/hosted_private_cloud/opcp/how-to-setup-lacp-on-a-node/meta.yaml b/pages/hosted_private_cloud/opcp/how-to-setup-lacp-on-a-node/meta.yaml
new file mode 100644
index 00000000000..b25a5e6c67f
--- /dev/null
+++ b/pages/hosted_private_cloud/opcp/how-to-setup-lacp-on-a-node/meta.yaml
@@ -0,0 +1,2 @@
+id: 0339bbc9-0794-431e-bbad-88f58c70bdbb
+full_slug: how-to-setup-lacp-on-a-node
\ No newline at end of file
diff --git a/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials/guide.fr-fr.md b/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials/guide.fr-fr.md
index fbe14beb037..b3989a61471 100644
--- a/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials/guide.fr-fr.md
+++ b/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials/guide.fr-fr.md
@@ -1,174 +1,179 @@
 ---
-title: "OPCP -  Comment utiliser les API et obtenir les informations d'identification"
-excerpt: "Ce document décrit les étapes nécessaires pour configurer Keycloak et le CLI OpenStack afin de permettre l’authentification via Keycloak"
-updated: 2025-10-30
+title: "OPCP - Comment utiliser les API et obtenir les informations d'identification"
+excerpt: "Découvrez les étapes nécessaires pour configurer Keycloak et le CLI OpenStack afin de permettre l’authentification via Keycloak"
+updated: 2025-11-07
 ---
 
 ## Objectif
-**OPCP** intégre une authentification centralisée avec **Keycloak**.  
-Il est donc nécessaire de configurer le **CLI OpenStack** afin qu’il utilise Keycloak comme fournisseur d’identité (Identity Provider).
 
-Ce document décrit les étapes nécessaires pour configurer **Keycloak** et le **CLI OpenStack** afin de permettre l’authentification via Keycloak.
-  
+**OPCP** intègre une authentification centralisée avec **Keycloak**. Il est donc nécessaire de configurer la **CLI OpenStack** afin qu’il utilise Keycloak comme fournisseur d’identité (Identity Provider).
+
+**Ce guide décrit les étapes nécessaires pour configurer Keycloak et la CLI OpenStack afin de permettre l’authentification via Keycloak.**
 
 ## Prérequis
+
 - Être administrateur de l'infrastructure [OPCP](/links/hosted-private-cloud/onprem-cloud-platform) et avoir accès à l'interface d'administration (admin.dashboard).
 - Avoir accès à l'interface d'administration Keyloack admin.
-- Avoir un utilisateur avec les droits suffisants pour se connecter à Horizon sur l'offre OPCP.
-
+- Avoir un utilisateur avec les droits suffisants pour se connecter à [Horizon](https://horizon.cloud.ovh.net/auth/login/) sur l'offre OPCP.
 
 ## En pratique
-### 1. Création d’un client Keycloak pour le CLI OpenStack
 
-Un **client Keycloak dédié** est requis afin de permettre au CLI OpenStack de communiquer de manière sécurisée avec le serveur Keycloak.
+### Création d’un client Keycloak pour la CLI OpenStack
+
+Un client **Keycloak dédié** est nécessaire pour permettre à la CLI OpenStack de communiquer de manière sécurisée avec le serveur Keycloak.
 
 #### Étapes
 
-1. **Connexion à l’interface d’administration Keycloak**  
-   Connectez-vous à votre instance Keycloak et sélectionnez le *realm* dans lequel les utilisateurs OpenStack sont définis.
+1\. **Connexion à l’interface d’administration Keycloak**
 
-2. **Création d’un nouveau client**
-   - Allez dans la section **Clients**.  
-   - Cliquez sur **Créer un client**.  
-   - Renseignez un **Client ID**, par exemple :
+- Connectez-vous à votre instance Keycloak et sélectionnez le *realm* dans lequel les utilisateurs OpenStack sont définis.
 
-     ```text
-     openstack-cli
-     ```
+2\. **Création d’un nouveau client**
 
-   - Cliquez sur **Suivant**.
+- Allez dans la section `Clients` et cliquez sur `Créer un client`{.action}.  
+- Renseignez un **Client ID**, par exemple :
 
-3. **Activation de l’authentification du client**
-   - Activez **Client Authentication** (mettre sur **ON**).  
-   - Cliquez sur **Suivant**, puis sur **Enregistrer**.
+   ```console
+   openstack-cli
+   ```
+
+- Cliquez sur `Suivant`{.action}.
 
-4. **Configuration des portées (Client Scopes)**
-   - Ouvrez l’onglet **Client Scopes**.  
-   - Sélectionnez la portée nommée :
+3\. **Activation de l’authentification du client**
 
-     ```text
-     [votre-client-id]-dedicated
-     ```
+- Activez le **Client Authentication** (mettre sur **ON**).  
+- Cliquez sur `Suivant`{.action}, puis sur `Enregistrer`{.action}.
 
-   - Cliquez sur **Configurer un nouveau mapper**.
+4\. **Configuration des portées (Client Scopes)**
 
-5. **Ajout d’un mapper d’attributs de groupe utilisateur**
-   - Choisissez le type de mapper **aggregated-user-group-attribute-mapper**.  
-   - Configurez les champs suivants :
+- Ouvrez l’onglet `Client Scopes`.  
+- Sélectionnez la portée nommée :
 
-     | Champ | Valeur |
-     |--------|--------|
-     | **Name** | `projects` |
-     | **User Attribute** | `project` |
-     | **Token Claim Name** | `projects` |
+```console
+[votre-client-id]-dedicated
+```
 
-   - Cliquez sur **Enregistrer**.
+- Cliquez sur `Configurer un nouveau mapper`{.action}.
 
-6. **Récupération des identifiants du client**
-   - Allez dans l’onglet **Credentials** du client que vous venez de créer.  
-   - Copiez et conservez de manière sécurisée la **Client Secret** — il sera nécessaire lors de la configuration du CLI OpenStack.
+5\. **Ajout d’un mapper d’attributs de groupe utilisateur**
 
----
+- Choisissez le type de mapper **aggregated-user-group-attribute-mapper**.  
+- Configurez les champs suivants :
 
-### 2. Configuration du CLI OpenStack
+   | Champ | Valeur |
+   |--------|--------|
+   | **Name** | `projects` |
+   | **User Attribute** | `project` |
+   | **Token Claim Name** | `projects` |
 
-Une fois le client Keycloak créé, le CLI OpenStack doit être configuré pour utiliser ce client comme fournisseur d’identité OIDC (OpenID Connect).
+- Cliquez sur `Enregistrer`{.action}.
+
+6\. **Récupération des identifiants du client**
+
+- Allez dans l’onglet `Credentials` du client que vous venez de créer.
+- Copiez et conservez de manière sécurisée la **Client Secret** — il sera nécessaire lors de la configuration du CLI OpenStack.
+  
+
+### Configuration de la CLI OpenStack
+
+Une fois le client Keycloak créé, la CLI OpenStack doit être configurée pour utiliser ce client comme fournisseur d'identité OIDC (OpenID Connect).
 
 #### Étapes
 
-1. **Installer les outils CLI OpenStack**  
-   Si ce n’est pas déjà fait :
+1\. **Installer les outils CLI OpenStack**
 
-   ```bash
-   pip install python-openstackclient
-   ```
+Si ce n’est pas déjà fait :
 
-2. **Définir les variables d’environnement pour l’authentification Keycloak**  
-   Exemple :
-
-   ```bash
-    export OS_INTERFACE=public
-    export OS_IDENTITY_API_VERSION=3
-    export OS_AUTH_URL="https://keystone.domain.ovh"
-    export OS_AUTH_TYPE="v3oidcpassword"
-    export OS_PROTOCOL="openid"
-    export OS_IDENTITY_PROVIDER="keycloak-admin"
-    export OS_CLIENT_ID="keycloak-client-id"
-    export OS_CLIENT_SECRET="keycloak-client-credentials"
-    export OS_DISCOVERY_ENDPOINT="https://admin.keycloak.domain.ovh/realms/master/.well-known/openid-configuration"
-    export OS_USERNAME="keycloak-user-username"
-    export OS_PASSWORD="keycloak-user-password"
-    export OS_PROJECT_ID="project-id"
-   ```
+```bash
+sudo pip install python-openstackclient
+```
 
-    > **Tips 1**
-    > : Vous pouvez utiliser le script suivant afin de générer le fichier de configuration openrc.sh facilement :  
-
-    ```bash
-    #!/usr/bin/env bash
-
-    read -p "Your environment's base FQDN (e.g. example.bmp.ovhgoldorack.ovh): " FQDN_ENV
-
-    read -p 'master or pod realm ? (master/pod): ' REALM
-    if [ "$REALM" != "master" ] && [ "$REALM" != "pod" ]; then
-        echo "Invalid input. Please enter either 'master' or 'pod'."
-        exit 1
-    fi
-
-    read -p 'Keycloak client ID: ' KC_CLIENT_ID
-    read -srp 'Keycloak client secret: ' KC_CLIENT_SECRET && echo
-
-    read -p 'Keycloak username: ' KC_USERNAME_INPUT
-    read -srp 'Keycloak password: ' KC_PASSWORD_INPUT && echo
-
-    read -p 'Openstack Project ID (not the name): ' PROJECT_ID
-
-    printf "\n\nHere is your configuration, paste it to your shell or use the generate openrc.sh file\n\n"
-    cat << EOM
-    export OS_INTERFACE=public
-    export OS_IDENTITY_API_VERSION=3
-    export OS_AUTH_URL="https://keystone.${FQDN_ENV}"
-    export OS_AUTH_TYPE="v3oidcpassword"
-    export OS_PROTOCOL="openid"
-    export OS_IDENTITY_PROVIDER=$([ "$REALM" = "master" ] && echo "keycloak-admin" || echo "keycloak")
-    export OS_CLIENT_ID="$KC_CLIENT_ID"
-    export OS_CLIENT_SECRET="$KC_CLIENT_SECRET"
-    export OS_DISCOVERY_ENDPOINT="https://$([ "$REALM" = "master" ] && echo "admin.keycloak" || echo "keycloak").${FQDN_ENV}/realms/$REALM/.well-known/openid-configuration"
-    export OS_USERNAME="$KC_USERNAME_INPUT"
-    export OS_PASSWORD="$KC_PASSWORD_INPUT"
-    export OS_PROJECT_ID="$PROJECT_ID"
-    EOM
-
-    echo "#!/usr/bin/env bash
-
-    export OS_INTERFACE=public
-    export OS_IDENTITY_API_VERSION=3
-    export OS_AUTH_URL="https://keystone.${FQDN_ENV}"
-    export OS_AUTH_TYPE="v3oidcpassword"
-    export OS_PROTOCOL="openid"
-    export OS_IDENTITY_PROVIDER=$([ "$REALM" = "master" ] && echo "keycloak-admin" || echo "keycloak")
-    export OS_CLIENT_ID="$KC_CLIENT_ID"
-    export OS_CLIENT_SECRET="$KC_CLIENT_SECRET"
-    export OS_DISCOVERY_ENDPOINT="https://$([ "$REALM" = "master" ] && echo "admin.keycloak" || echo "keycloak").${FQDN_ENV}/realms/$REALM/.well-known/openid-configuration"
-    export OS_USERNAME="$KC_USERNAME_INPUT"
-    export OS_PASSWORD="$KC_PASSWORD_INPUT"
-    export OS_PROJECT_ID="$PROJECT_ID > $PROJECT_ID."-openrc.sh"
-    ```
-
-    > **Tips: Configuration d'un proxy**  
-    > Si vous utilisez un proxy pour accéder a votre service, vous devez configurer vos variables d'environnement pour prendre en compte ce proxy.  
-    Pour ce faire, ajoutez les lignes de commande suivantes :
-
-    ```bash
-    export https_proxy=http://your-adress-ip:port/
-    export http_proxy=http://your-adress-ip:port/
-    ```
+2\. **Définir les variables d’environnement pour l’authentification Keycloak**
 
----
+Exemple :
+
+```bash
+export OS_INTERFACE=public
+export OS_IDENTITY_API_VERSION=3
+export OS_AUTH_URL="https://keystone.domain.ovh"
+export OS_AUTH_TYPE="v3oidcpassword"
+export OS_PROTOCOL="openid"
+export OS_IDENTITY_PROVIDER="keycloak-admin"
+export OS_CLIENT_ID="keycloak-client-id"
+export OS_CLIENT_SECRET="keycloak-client-credentials"
+export OS_DISCOVERY_ENDPOINT="https://admin.keycloak.domain.ovh/realms/master/.well-known/openid-configuration"
+export OS_USERNAME="keycloak-user-username"
+export OS_PASSWORD="keycloak-user-password"
+export OS_PROJECT_ID="project-id"
+```
+
+> **Tips 1**
+> Vous pouvez utiliser le script suivant afin de générer le fichier de configuration openrc.sh facilement :  
+
+```bash
+ #!/usr/bin/env bash
+
+read -p "Your environment's base FQDN (e.g. example.bmp.ovhgoldorack.ovh): " FQDN_ENV
+
+read -p 'master or pod realm ? (master/pod): ' REALM
+if [ "$REALM" != "master" ] && [ "$REALM" != "pod" ]; then
+    echo "Invalid input. Please enter either 'master' or 'pod'."
+    exit 1
+fi
+
+read -p 'Keycloak client ID: ' KC_CLIENT_ID
+read -srp 'Keycloak client secret: ' KC_CLIENT_SECRET && echo
+
+read -p 'Keycloak username: ' KC_USERNAME_INPUT
+read -srp 'Keycloak password: ' KC_PASSWORD_INPUT && echo
+
+read -p 'Openstack Project ID (not the name): ' PROJECT_ID
+
+printf "\n\nHere is your configuration, paste it to your shell or use the generate openrc.sh file\n\n"
+cat << EOM
+export OS_INTERFACE=public
+export OS_IDENTITY_API_VERSION=3
+export OS_AUTH_URL="https://keystone.${FQDN_ENV}"
+export OS_AUTH_TYPE="v3oidcpassword"
+export OS_PROTOCOL="openid"
+export OS_IDENTITY_PROVIDER=$([ "$REALM" = "master" ] && echo "keycloak-admin" || echo "keycloak")
+export OS_CLIENT_ID="$KC_CLIENT_ID"
+export OS_CLIENT_SECRET="$KC_CLIENT_SECRET"
+export OS_DISCOVERY_ENDPOINT="https://$([ "$REALM" = "master" ] && echo "admin.keycloak" || echo "keycloak").${FQDN_ENV}/realms/$REALM/.well-known/openid-configuration"
+export OS_USERNAME="$KC_USERNAME_INPUT"
+export OS_PASSWORD="$KC_PASSWORD_INPUT"
+export OS_PROJECT_ID="$PROJECT_ID"
+EOM
+
+echo "#!/usr/bin/env bash
+
+export OS_INTERFACE=public
+export OS_IDENTITY_API_VERSION=3
+export OS_AUTH_URL="https://keystone.${FQDN_ENV}"
+export OS_AUTH_TYPE="v3oidcpassword"
+export OS_PROTOCOL="openid"
+export OS_IDENTITY_PROVIDER=$([ "$REALM" = "master" ] && echo "keycloak-admin" || echo "keycloak")
+export OS_CLIENT_ID="$KC_CLIENT_ID"
+export OS_CLIENT_SECRET="$KC_CLIENT_SECRET"
+export OS_DISCOVERY_ENDPOINT="https://$([ "$REALM" = "master" ] && echo "admin.keycloak" || echo "keycloak").${FQDN_ENV}/realms/$REALM/.well-known/openid-configuration"
+export OS_USERNAME="$KC_USERNAME_INPUT"
+export OS_PASSWORD="$KC_PASSWORD_INPUT"
+export OS_PROJECT_ID="$PROJECT_ID > $PROJECT_ID."-openrc.sh"
+```
 
-### 3. Vérification de la configuration
+> **Tips: Configuration d'un proxy**  
+> Si vous utilisez un proxy pour accéder a votre service, vous devez configurer vos variables d'environnement pour prendre en compte ce proxy.
 
-Vos pouvez tester votre configuration à l’aide de quelques commandes simples :
+Pour ce faire, ajoutez les lignes de commande suivantes :
+
+```bash
+export https_proxy=http://your-adress-ip:port/
+export http_proxy=http://your-adress-ip:port/
+```
+
+### Vérification de la configuration
+
+Vous pouvez tester votre configuration à l’aide de quelques commandes simples :
 
 ```bash
 openstack token issue
@@ -178,9 +183,8 @@ openstack server list
 
 Si ces commandes retournent des résultats, l’intégration **Keycloak ↔ OpenStack** est correctement configurée.
 
----
 
-### 4. Dépannage (Troubleshooting)
+### Dépannage (Troubleshooting)
 
 | Problème | Cause possible | Solution |
 |-----------|----------------|-----------|
@@ -188,12 +192,9 @@ Si ces commandes retournent des résultats, l’intégration **Keycloak ↔ Open
 | `Unauthorized` | L’utilisateur n’est pas associé au bon groupe ou projet | Vérifiez les attributs `project` de l’utilisateur dans Keycloak |
 | `OIDC discovery failed` | Mauvaise URL dans `DISCOVERY_ENDPOINT` | Assurez-vous qu’elle pointe bien vers le *realm* correct de Keycloak |
 
----
 
-### 5. Références
+### Références
 
 - [Documentation Keycloak – OpenID Connect](https://www.keycloak.org/docs/latest/server_admin/#_oidc)
 - [Documentation OpenStack Keystone](https://docs.openstack.org/keystone/latest/)
 - [Documentation OVHcloud OPCP](https://docs.opcp.ovh)
-
----
\ No newline at end of file
diff --git a/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials/meta.yaml b/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials/meta.yaml
index 80547741e38..66a34e5e07b 100644
--- a/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials/meta.yaml
+++ b/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials/meta.yaml
@@ -1,2 +1,2 @@
 id: 6eb6dd6a-46a3-4f8f-b263-3362729401db
-full_slug: how-to-use-api-and-get-credentials
\ No newline at end of file
+full_slug: opcp-use-api-get-credentials
\ No newline at end of file
diff --git a/pages/index-translations.de.yaml b/pages/index-translations.de.yaml
index 5dac99c7303..d217208153a 100644
--- a/pages/index-translations.de.yaml
+++ b/pages/index-translations.de.yaml
@@ -78,6 +78,8 @@ hosted-private-cloud-hosted-private-cloud-powered-by-vmware-tanzu: VMware Tanzu
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-secnumcloud: SecNumCloud
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-vrops: VMware vROps
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-migration: Migration
+hosted-private-cloud-hosted-private-cloud-opcp: On-Prem Cloud Plateform
+hosted-private-cloud-hosted-private-cloud-opcp-getting-started: Erste Schritte
 hosted-private-cloud-sap-ovhcloud: SAP on OVHcloud
 hosted-private-cloud-sap-ovhcloud-concepts: Konzepte
 hosted-private-cloud-sap-ovhcloud-getting-started: Erste Schritte
@@ -115,6 +117,8 @@ public-cloud-quantum-computing: Quantum computing
 public-cloud-quantum-computing-general-information: General information
 public-cloud-quantum-computing-emulator: Quantum emulators
 public-cloud-quantum-computing-emulators-guides: Guides
+public-cloud-quantum-computing-qpus: Quantum QPUs
+public-cloud-quantum-computing-qpus-guides: Guides
 public-cloud-containers-orchestration: Containers & Orchestration
 public-cloud-containers-orchestration-managed-kubernetes-k8s: Managed Kubernetes Service (MKS)
 public-cloud-containers-orchestration-managed-kubernetes-k8s-getting-started: Getting started
@@ -391,4 +395,4 @@ observability-logs-data-platform-visualizing-querying-exploiting: Visualizing, q
 observability-logs-data-platform-opensearch-index: OpenSearch Index as a service
 observability-logs-data-platform-security-conformity: Security and conformity
 observability-logs-data-platform-usecases: Usecases
-observability-logs-data-platform-services-logs: OVHcloud Service Logs
\ No newline at end of file
+observability-logs-data-platform-services-logs: OVHcloud Service Logs
diff --git a/pages/index-translations.es.yaml b/pages/index-translations.es.yaml
index 0af79bcc440..408d30f6cfc 100755
--- a/pages/index-translations.es.yaml
+++ b/pages/index-translations.es.yaml
@@ -78,6 +78,8 @@ hosted-private-cloud-hosted-private-cloud-powered-by-vmware-tanzu: VMware Tanzu
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-secnumcloud: SecNumCloud
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-vrops: VMware vROps
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-migration: Migración
+hosted-private-cloud-hosted-private-cloud-opcp: On-Prem Cloud Plateform
+hosted-private-cloud-hosted-private-cloud-opcp-getting-started: Primeros pasos
 hosted-private-cloud-sap-ovhcloud: SAP on OVHcloud
 hosted-private-cloud-sap-ovhcloud-concepts: Conceptos
 hosted-private-cloud-sap-ovhcloud-getting-started: Primeros pasos
@@ -115,6 +117,8 @@ public-cloud-quantum-computing: Quantum computing
 public-cloud-quantum-computing-general-information: General information
 public-cloud-quantum-computing-emulator: Quantum emulators
 public-cloud-quantum-computing-emulators-guides: Guides
+public-cloud-quantum-computing-qpus: Quantum QPUs
+public-cloud-quantum-computing-qpus-guides: Guides
 public-cloud-containers-orchestration: Containers & Orchestration
 public-cloud-containers-orchestration-managed-kubernetes-k8s: Managed Kubernetes Service (MKS)
 public-cloud-containers-orchestration-managed-kubernetes-k8s-getting-started: Getting started
diff --git a/pages/index-translations.fq.yaml b/pages/index-translations.fq.yaml
index 7e29b26ccb8..f325081a8ee 100755
--- a/pages/index-translations.fq.yaml
+++ b/pages/index-translations.fq.yaml
@@ -78,6 +78,8 @@ hosted-private-cloud-hosted-private-cloud-powered-by-vmware-tanzu: VMware Tanzu
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-secnumcloud: SecNumCloud
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-vrops: VMware vROps
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-migration: Migration
+hosted-private-cloud-hosted-private-cloud-opcp: On-Prem Cloud Plateform
+hosted-private-cloud-hosted-private-cloud-opcp-getting-started: Premiers pas
 hosted-private-cloud-sap-ovhcloud: SAP on OVHcloud
 hosted-private-cloud-sap-ovhcloud-concepts: Concepts
 hosted-private-cloud-sap-ovhcloud-getting-started: Premiers pas
@@ -111,11 +113,13 @@ public-cloud-ai-and-machine-learning-ai-ecosystem-guides: AI Partners - Guides
 public-cloud-ai-and-machine-learning-ai-endpoints: AI Endpoints
 public-cloud-ai-and-machine-learning-ai-endpoints-guides: AI Endpoints - Guides
 public-cloud-ai-and-machine-learning-ai-endpointstutorials: AI Endpoints - Tutoriels
-public-cloud-containers-orchestration: Containers & Orchestration
 public-cloud-quantum-computing: Quantum computing
 public-cloud-quantum-computing-general-information: General information
 public-cloud-quantum-computing-emulator: Quantum emulators
 public-cloud-quantum-computing-emulators-guides: Guides
+public-cloud-quantum-computing-qpus: Quantum QPUs
+public-cloud-quantum-computing-qpus-guides: Guides
+public-cloud-containers-orchestration: Containers & Orchestration
 public-cloud-containers-orchestration-managed-kubernetes-k8s: Managed Kubernetes Service (MKS)
 public-cloud-containers-orchestration-managed-kubernetes-k8s-getting-started: Getting started
 public-cloud-containers-orchestration-managed-kubernetes-k8s-troubleshooting: Troubleshooting
diff --git a/pages/index-translations.fr.yaml b/pages/index-translations.fr.yaml
index ab57fda0c55..be99e169898 100755
--- a/pages/index-translations.fr.yaml
+++ b/pages/index-translations.fr.yaml
@@ -79,6 +79,8 @@ hosted-private-cloud-hosted-private-cloud-powered-by-vmware-tanzu: VMware Tanzu
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-secnumcloud: SecNumCloud
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-vrops: VMware vROps
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-migration: Migration
+hosted-private-cloud-hosted-private-cloud-opcp: On-Prem Cloud Plateform
+hosted-private-cloud-hosted-private-cloud-opcp-getting-started: Premiers pas
 hosted-private-cloud-sap-ovhcloud: SAP on OVHcloud
 hosted-private-cloud-sap-ovhcloud-concepts: Concepts
 hosted-private-cloud-sap-ovhcloud-getting-started: Premiers pas
@@ -116,6 +118,8 @@ public-cloud-quantum-computing: Quantum computing
 public-cloud-quantum-computing-general-information: General information
 public-cloud-quantum-computing-emulator: Quantum emulators
 public-cloud-quantum-computing-emulators-guides: Guides
+public-cloud-quantum-computing-qpus: Quantum QPUs
+public-cloud-quantum-computing-qpus-guides: Guides
 public-cloud-containers-orchestration: Containers & Orchestration
 public-cloud-containers-orchestration-managed-kubernetes-k8s: Managed Kubernetes Service (MKS)
 public-cloud-containers-orchestration-managed-kubernetes-k8s-getting-started: Getting started
diff --git a/pages/index-translations.it.yaml b/pages/index-translations.it.yaml
index 67bbc63304a..1f59029c5da 100644
--- a/pages/index-translations.it.yaml
+++ b/pages/index-translations.it.yaml
@@ -78,6 +78,8 @@ hosted-private-cloud-hosted-private-cloud-powered-by-vmware-tanzu: VMware Tanzu
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-secnumcloud: SecNumCloud
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-vrops: VMware vROps
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-migration: Migrazione
+hosted-private-cloud-hosted-private-cloud-opcp: On-Prem Cloud Plateform
+hosted-private-cloud-hosted-private-cloud-opcp-getting-started: Per iniziare
 hosted-private-cloud-sap-ovhcloud: SAP on OVHcloud
 hosted-private-cloud-sap-ovhcloud-concepts: Concetti
 hosted-private-cloud-sap-ovhcloud-getting-started: Per iniziare
@@ -115,6 +117,8 @@ public-cloud-quantum-computing: Quantum computing
 public-cloud-quantum-computing-general-information: General information
 public-cloud-quantum-computing-emulator: Quantum emulators
 public-cloud-quantum-computing-emulators-guides: Guides
+public-cloud-quantum-computing-qpus: Quantum QPUs
+public-cloud-quantum-computing-qpus-guides: Guides
 public-cloud-containers-orchestration: Containers & Orchestration
 public-cloud-containers-orchestration-managed-kubernetes-k8s: Managed Kubernetes Service (MKS)
 public-cloud-containers-orchestration-managed-kubernetes-k8s-getting-started: Getting started
diff --git a/pages/index-translations.pl.yaml b/pages/index-translations.pl.yaml
index 4149b028605..02952946da2 100755
--- a/pages/index-translations.pl.yaml
+++ b/pages/index-translations.pl.yaml
@@ -78,6 +78,8 @@ hosted-private-cloud-hosted-private-cloud-powered-by-vmware-tanzu: VMware Tanzu
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-secnumcloud: SecNumCloud
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-vrops: VMware vROps
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-migration: Migracja
+hosted-private-cloud-hosted-private-cloud-opcp: On-Prem Cloud Plateform
+hosted-private-cloud-hosted-private-cloud-opcp-getting-started: Pierwsze kroki
 hosted-private-cloud-sap-ovhcloud: SAP on OVHcloud
 hosted-private-cloud-sap-ovhcloud-concepts: Koncepcje
 hosted-private-cloud-sap-ovhcloud-getting-started: Pierwsze kroki
@@ -115,6 +117,8 @@ public-cloud-quantum-computing: Quantum computing
 public-cloud-quantum-computing-general-information: General information
 public-cloud-quantum-computing-emulator: Quantum emulators
 public-cloud-quantum-computing-emulators-guides: Guides
+public-cloud-quantum-computing-qpus: Quantum QPUs
+public-cloud-quantum-computing-qpus-guides: Guides
 public-cloud-containers-orchestration: Containers & Orchestration
 public-cloud-containers-orchestration-managed-kubernetes-k8s: Managed Kubernetes Service (MKS)
 public-cloud-containers-orchestration-managed-kubernetes-k8s-getting-started: Getting started
diff --git a/pages/index-translations.pt.yaml b/pages/index-translations.pt.yaml
index 52714a3a54d..11016c534ee 100755
--- a/pages/index-translations.pt.yaml
+++ b/pages/index-translations.pt.yaml
@@ -78,6 +78,8 @@ hosted-private-cloud-hosted-private-cloud-powered-by-vmware-tanzu: VMware Tanzu
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-secnumcloud: SecNumCloud
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-vrops: VMware vROps
 hosted-private-cloud-hosted-private-cloud-powered-by-vmware-migration: Migração
+hosted-private-cloud-hosted-private-cloud-opcp: On-Prem Cloud Plateform
+hosted-private-cloud-hosted-private-cloud-opcp-getting-started: Primeiros passos
 hosted-private-cloud-sap-ovhcloud: SAP on OVHcloud
 hosted-private-cloud-sap-ovhcloud-concepts: Conceitos
 hosted-private-cloud-sap-ovhcloud-getting-started: Primeiros passos
@@ -115,6 +117,8 @@ public-cloud-quantum-computing: Quantum computing
 public-cloud-quantum-computing-general-information: General information
 public-cloud-quantum-computing-emulator: Quantum emulators
 public-cloud-quantum-computing-emulators-guides: Guides
+public-cloud-quantum-computing-qpus: Quantum QPUs
+public-cloud-quantum-computing-qpus-guides: Guides
 public-cloud-containers-orchestration: Containers & Orchestration
 public-cloud-containers-orchestration-managed-kubernetes-k8s: Managed Kubernetes Service (MKS)
 public-cloud-containers-orchestration-managed-kubernetes-k8s-getting-started: Getting started
diff --git a/pages/index.md b/pages/index.md
index 37a28e7225e..eddcf75a0c0 100644
--- a/pages/index.md
+++ b/pages/index.md
@@ -550,6 +550,9 @@
             + [Move2Cloud - Migrating VMware Workloads to OVHcloud Hosted Private Cloud with Veeam Replication](hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_migration_veeam)
             + [Move2Cloud - Migrating VMware Workloads to OVHcloud Hosted Private Cloud with Zerto](hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_migration_zerto)
             + [Migrating OmniOS datastores](hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_migration_omnios)
+    + [OPCP](hosted-private-cloud-opcp)
+        + [Getting started](hosted-private-cloud-opcp-getting-started)
+            + [How to use API and get credentials](hosted_private_cloud/opcp/how-to-use-api-and-get-credentials)
     + [Nutanix on OVHcloud](products/hosted-private-cloud-nutanix-on-ovhcloud)
         + [Getting started](hosted-private-cloud-nutanix-on-ovhcloud-getting-started)
             + [Nutanix global high-level documentation](hosted_private_cloud/nutanix_on_ovhcloud/01-global-high-level-doc)
@@ -1122,6 +1125,7 @@
                 + [Managing users and projects in Managed Rancher Service](public_cloud/containers_orchestration/managed_rancher_service/managing-users-and-projects)
                 + [Tutorial - How to use Rancher CLI](public_cloud/containers_orchestration/managed_rancher_service/using-rancher-cli)
                 + [Orchestration product reversibility policy](account_and_service_management/reversibility/12-reversibility-orchestration)
+                + [Configure access control using OVHcloud IAM on an OVHcloud Managed Rancher Service](public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication)
             + [Resources](public-cloud-containers-orchestration-managed-rancher-service-resources)
                 + [Managed Rancher Service supported versions and lifecycle policy](public_cloud/containers_orchestration/managed_rancher_service/lifecycle-policy)
             + [Creating or importing a Kubernetes cluster](public-cloud-containers-orchestration-managed-rancher-service-creating-importing-kubernetes)
@@ -1279,7 +1283,10 @@
             + [Troubleshooting](public_cloud/quantum_computing/troubleshooting)
         + [Emulators](products/public-cloud-quantum-computing-emulator)
             + [Guides](public-cloud-quantum-computing-emulators-guides)
-                + [Quantum emulators - Getting started](public_cloud/quantum_computing/getting-started-emulators)
+                + [Quantum emulators - Getting started](public_cloud/quantum_computing/emulators/getting-started)
+        + [QPUs](products/public-cloud-quantum-computing-qpu)
+            + [Guides](public-cloud-quantum-computing-qpu-guides)
+                + [QPUs - Getting started](public_cloud/quantum_computing/qpus/getting-started)
     + [Analytics](products/public-cloud-data-analytics)
         + [General information](products/public-cloud-data-analytics-general-information)
             + [Analytics - Security overview](public_cloud/public_cloud_databases/information_01_security_overview)
@@ -1600,8 +1607,6 @@
             + [Migrating an MX Plan email account to an Email Pro or Exchange account](web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel)
             + [Manually migrate your email account](web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration)
             + [Migrating email accounts using OVHcloud Mail Migrator](web_cloud/email_and_collaborative_solutions/migrating/migration_omm)
-            + [Migrating a Gmail account to an OVHcloud email account via the OVHcloud Mail Migrator](web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-            + [Authorising less secure connections on Gmail](web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
             + [Migrating your email account from one OVHcloud email platform to another](web_cloud/email_and_collaborative_solutions/migrating/migration_platform)
         + [Troubleshooting](web-cloud-email-collaborative-solutions-troubleshooting)
             + [Unable to send or receive emails](web_cloud/email_and_collaborative_solutions/troubleshooting/diagnostic_advanced)
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.de-de.md b/pages/manage_and_operate/kms/architecture-overview/guide.de-de.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.de-de.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.en-asia.md b/pages/manage_and_operate/kms/architecture-overview/guide.en-asia.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.en-asia.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.en-au.md b/pages/manage_and_operate/kms/architecture-overview/guide.en-au.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.en-au.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.en-ca.md b/pages/manage_and_operate/kms/architecture-overview/guide.en-ca.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.en-ca.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.en-gb.md b/pages/manage_and_operate/kms/architecture-overview/guide.en-gb.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.en-gb.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.en-ie.md b/pages/manage_and_operate/kms/architecture-overview/guide.en-ie.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.en-ie.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.en-sg.md b/pages/manage_and_operate/kms/architecture-overview/guide.en-sg.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.en-sg.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.en-us.md b/pages/manage_and_operate/kms/architecture-overview/guide.en-us.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.en-us.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.es-es.md b/pages/manage_and_operate/kms/architecture-overview/guide.es-es.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.es-es.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.es-us.md b/pages/manage_and_operate/kms/architecture-overview/guide.es-us.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.es-us.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.fr-ca.md b/pages/manage_and_operate/kms/architecture-overview/guide.fr-ca.md
index f865cf7fb6c..efd8d4fc1b3 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.fr-ca.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS - Aperçu de l'architecture"
 excerpt: "Découvrez comment nous gérons la sécurité de l'infrastructure OKMS"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objectif
@@ -85,6 +85,12 @@ L'emplacement de la sauvegarde dépend de l'emplacement du service OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -129,6 +135,8 @@ Les régions concernées par la certification PCI-DSS sont :
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Aller plus loin
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.fr-fr.md b/pages/manage_and_operate/kms/architecture-overview/guide.fr-fr.md
index f865cf7fb6c..efd8d4fc1b3 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.fr-fr.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS - Aperçu de l'architecture"
 excerpt: "Découvrez comment nous gérons la sécurité de l'infrastructure OKMS"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objectif
@@ -85,6 +85,12 @@ L'emplacement de la sauvegarde dépend de l'emplacement du service OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -129,6 +135,8 @@ Les régions concernées par la certification PCI-DSS sont :
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Aller plus loin
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.it-it.md b/pages/manage_and_operate/kms/architecture-overview/guide.it-it.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.it-it.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.pl-pl.md b/pages/manage_and_operate/kms/architecture-overview/guide.pl-pl.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.pl-pl.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/manage_and_operate/kms/architecture-overview/guide.pt-pt.md b/pages/manage_and_operate/kms/architecture-overview/guide.pt-pt.md
index 3e358c4491f..200008ec8d8 100644
--- a/pages/manage_and_operate/kms/architecture-overview/guide.pt-pt.md
+++ b/pages/manage_and_operate/kms/architecture-overview/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "OKMS Architecture overview"
 excerpt: "Discover how we handle the security of the OKMS infrastructure"
-updated: 2025-10-24
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -85,6 +85,12 @@ The backup location depends on the location of the OKMS.
 - **EU-WEST-LIM**
     - KMS Backup Region 1 : EU-WEST-LIM
     - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-WEST-ERI**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
+- **EU-CENTRAL-WAW**
+    - KMS Backup Region 1 : EU-WEST-GRA
+    - KMS Backup Region 2 : EU-WEST-SBG
 - **EU-SOUTH-MIL**
     - KMS Backup Region 1 : EU-WEST-GRA
     - KMS Backup Region 2 : EU-WEST-SBG
@@ -128,6 +134,8 @@ Regions available for PCI-DSS certification:
 - EU-WEST-SBG
 - EU-WEST-GRA
 - EU-WEST-LIM
+- EU-WEST-ERI
+- EU-CENTRAL-WAW
 - CA-EAST-BHS
 
 ## Go further
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.de-de.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.de-de.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.de-de.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-asia.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-asia.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-asia.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-au.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-au.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-au.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-ca.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-ca.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-ca.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-gb.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-gb.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-gb.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-ie.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-ie.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-ie.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-sg.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-sg.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-sg.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-us.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-us.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-us.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.es-es.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.es-es.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.es-es.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.es-us.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.es-us.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.es-us.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.fr-ca.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.fr-ca.md
index baf93ebbdb4..a78a647d2c1 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.fr-ca.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "CLI - Se servir des tokens d'accès (EN)"
 excerpt: "Découvrez comment créer des tokens d'accès avec la CLI ovhai"
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.fr-fr.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.fr-fr.md
index baf93ebbdb4..a78a647d2c1 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.fr-fr.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: "CLI - Se servir des tokens d'accès (EN)"
 excerpt: "Découvrez comment créer des tokens d'accès avec la CLI ovhai"
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.it-it.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.it-it.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.it-it.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.pl-pl.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.pl-pl.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.pl-pl.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.pt-pt.md b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.pt-pt.md
index c31d72e50e8..ef768fa7532 100644
--- a/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.pt-pt.md
+++ b/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: CLI - Manage access tokens
 excerpt: Learn how to create Application tokens with the ovhai CLI
-updated: 2023-05-11
+updated: 2025-11-06
 ---
 
 ## Objective
@@ -21,11 +21,13 @@ If you need any help while creating a new token, run `ovhai token create --help`
 ``` {.console}
 Usage: ovhai token create [OPTIONS] --role <ROLE> <NAME>
 
+Create an application token
+
 Arguments:
   <NAME>  Token's name
 
 Options:
-  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs [possible values: read, operator]
+  -r, --role <ROLE>                  Operator role gives all access, read role only allow to access job's APIs. DEPRECATED VALUES: "read", "operator" => replaced by "ai_training_read", "ai_training_operator" [possible values: read, operator, ai_training_read, ai_training_operator, quantum_operator, quantum_reader]
       --token <TOKEN>                Authentication using Token rather than OAuth
   -l, --label-selector <name=value>  Only jobs with this label's name and value will be accessible using this token
   -o, --output <OUTPUT>              Command output format [possible values: json, yaml, description]
diff --git a/pages/public_cloud/ai_machine_learning/deploy_tuto_19_flux/guide.en-gb.md b/pages/public_cloud/ai_machine_learning/deploy_tuto_19_flux/guide.en-gb.md
index aa5056a8263..07ea66792c2 100644
--- a/pages/public_cloud/ai_machine_learning/deploy_tuto_19_flux/guide.en-gb.md
+++ b/pages/public_cloud/ai_machine_learning/deploy_tuto_19_flux/guide.en-gb.md
@@ -323,6 +323,7 @@ Run the following command to deploy your application:
 >>   --env VAE_FILE=ae.safetensors \
 >>   --env CLIP_FILE_1=clip_l.safetensors \
 >>   --env CLIP_FILE_2=t5xxl_fp16.safetensors
+>> ```
 >>
 > **Kontext Dev**
 >>
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.de-de.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.de-de.md
index ee4498e142a..4a0026505eb 100755
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.de-de.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: 'Verwenden von Backups zum Erzeugen oder Wiederherstellen von Instanzen'
 excerpt: 'Erfahren Sie hier, wie Sie Instanzen aus Backups oder wiederherstellen'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Ziel
@@ -21,6 +21,17 @@ Sie können diese Instanzsicherungen für zwei grundlegende Zwecke verwenden:
 
 ## In der praktischen Anwendung
 
+> [!primary]
+>
+> Es stehen Ihnen zwei Arten von Backups zur Verfügung:
+>
+> - Lokal: In derselben Region wie Ihre Instanz gespeichert.
+> - Fern: Automatisch in eine andere von Ihnen gewählte Region repliziert.
+>
+> Die Operationen des **Erstellens** und **Wiederherstellens** einer Instanz aus einem entfernten Backup werden vollständig über die OVHcloud API unterstützt, was eine größere Flexibilität und mühelose Integration in Ihre Automatisierungsprozesse bietet.
+>
+> **Hinweis:** Diese Vorgänge stehen noch nicht über das OVHcloud Kundencenter zur Verfügung.
+
 ### Eine Instanz aus einem Backup erstellen
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-asia.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-asia.md
index 034f9cf33b6..772e6cd10b7 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-asia.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Using instance backups to create or restore an instance
 excerpt: Find out how to restore an instance or create a new one from a backup
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -21,6 +21,18 @@ You can make use of these instance backups for two basic purposes:
 
 ## Instructions
 
+> [!primary]
+>
+> Two types of backups are available:
+>
+> - Local: Stored in the same region as your instance.
+> - Distant: Automatically replicated in another region of your choice.
+>
+> The operations of **creating** and **restoring** an instance from a distant backup are fully supported via the OVHcloud API, offering greater flexibility and effortless integration into your automation processes.
+>
+> **Note :** These operations are not yet available through the OVHcloud Control Panel.
+>
+
 ### Creating an instance from a backup
 
 > [!tabs]
@@ -180,4 +192,4 @@ You can make use of these instance backups for two basic purposes:
 
 [Creating instance backups](/pages/public_cloud/compute/save_an_instance)
 
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-au.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-au.md
index 034f9cf33b6..772e6cd10b7 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-au.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Using instance backups to create or restore an instance
 excerpt: Find out how to restore an instance or create a new one from a backup
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -21,6 +21,18 @@ You can make use of these instance backups for two basic purposes:
 
 ## Instructions
 
+> [!primary]
+>
+> Two types of backups are available:
+>
+> - Local: Stored in the same region as your instance.
+> - Distant: Automatically replicated in another region of your choice.
+>
+> The operations of **creating** and **restoring** an instance from a distant backup are fully supported via the OVHcloud API, offering greater flexibility and effortless integration into your automation processes.
+>
+> **Note :** These operations are not yet available through the OVHcloud Control Panel.
+>
+
 ### Creating an instance from a backup
 
 > [!tabs]
@@ -180,4 +192,4 @@ You can make use of these instance backups for two basic purposes:
 
 [Creating instance backups](/pages/public_cloud/compute/save_an_instance)
 
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-ca.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-ca.md
index 0c56884d708..772e6cd10b7 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-ca.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Using instance backups to create or restore an instance
 excerpt: Find out how to restore an instance or create a new one from a backup
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -21,6 +21,18 @@ You can make use of these instance backups for two basic purposes:
 
 ## Instructions
 
+> [!primary]
+>
+> Two types of backups are available:
+>
+> - Local: Stored in the same region as your instance.
+> - Distant: Automatically replicated in another region of your choice.
+>
+> The operations of **creating** and **restoring** an instance from a distant backup are fully supported via the OVHcloud API, offering greater flexibility and effortless integration into your automation processes.
+>
+> **Note :** These operations are not yet available through the OVHcloud Control Panel.
+>
+
 ### Creating an instance from a backup
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-gb.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-gb.md
index 034f9cf33b6..b10514e997f 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-gb.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Using instance backups to create or restore an instance
 excerpt: Find out how to restore an instance or create a new one from a backup
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -21,6 +21,18 @@ You can make use of these instance backups for two basic purposes:
 
 ## Instructions
 
+> [!primary]
+>
+> Two types of backups are available:
+>
+> - Local: Stored in the same region as your instance.
+> - Distant: Automatically replicated in another region of your choice.
+>
+> The operations of **creating** and **restoring** an instance from a distant backup are fully supported via the OVHcloud API, offering greater flexibility and effortless integration into your automation processes.
+>
+> **Note :** These operations are not yet available through the OVHcloud Control Panel.
+>
+
 ### Creating an instance from a backup
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-ie.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-ie.md
index 0c56884d708..772e6cd10b7 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-ie.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Using instance backups to create or restore an instance
 excerpt: Find out how to restore an instance or create a new one from a backup
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -21,6 +21,18 @@ You can make use of these instance backups for two basic purposes:
 
 ## Instructions
 
+> [!primary]
+>
+> Two types of backups are available:
+>
+> - Local: Stored in the same region as your instance.
+> - Distant: Automatically replicated in another region of your choice.
+>
+> The operations of **creating** and **restoring** an instance from a distant backup are fully supported via the OVHcloud API, offering greater flexibility and effortless integration into your automation processes.
+>
+> **Note :** These operations are not yet available through the OVHcloud Control Panel.
+>
+
 ### Creating an instance from a backup
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-sg.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-sg.md
index 0c56884d708..772e6cd10b7 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-sg.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Using instance backups to create or restore an instance
 excerpt: Find out how to restore an instance or create a new one from a backup
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -21,6 +21,18 @@ You can make use of these instance backups for two basic purposes:
 
 ## Instructions
 
+> [!primary]
+>
+> Two types of backups are available:
+>
+> - Local: Stored in the same region as your instance.
+> - Distant: Automatically replicated in another region of your choice.
+>
+> The operations of **creating** and **restoring** an instance from a distant backup are fully supported via the OVHcloud API, offering greater flexibility and effortless integration into your automation processes.
+>
+> **Note :** These operations are not yet available through the OVHcloud Control Panel.
+>
+
 ### Creating an instance from a backup
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-us.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-us.md
index 0c56884d708..772e6cd10b7 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-us.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Using instance backups to create or restore an instance
 excerpt: Find out how to restore an instance or create a new one from a backup
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objective
@@ -21,6 +21,18 @@ You can make use of these instance backups for two basic purposes:
 
 ## Instructions
 
+> [!primary]
+>
+> Two types of backups are available:
+>
+> - Local: Stored in the same region as your instance.
+> - Distant: Automatically replicated in another region of your choice.
+>
+> The operations of **creating** and **restoring** an instance from a distant backup are fully supported via the OVHcloud API, offering greater flexibility and effortless integration into your automation processes.
+>
+> **Note :** These operations are not yet available through the OVHcloud Control Panel.
+>
+
 ### Creating an instance from a backup
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.es-es.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.es-es.md
index d70b5c39ff1..316cde0a13f 100755
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.es-es.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: 'Crear o restaurar un servidor virtual a partir de un snapshot'
 excerpt: 'Descubra cómo crear o restaurar la copia de seguridad de una instancia'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objetivo
@@ -21,6 +21,17 @@ Quizá necesite, en algún momento, restaurar su instancia utilizando un snapsho
 
 ## Procedimiento
 
+> [!primary]
+>
+> Están disponibles dos tipos de copias de seguridad:
+>
+> - Local: almacenada en la misma región que su instancia.
+> - Remota: automáticamente replicada en otra región de su elección.
+>
+> Las operaciones de **creación** y **restauración** de una instancia desde un backup remoto son totalmente compatibles a través de la API OVHcloud, ofreciendo una mayor flexibilidad y una integración más sencilla en sus procesos de automatización.
+>
+> **Nota:** Estas operaciones no están disponibles aún desde el área de cliente de OVHcloud.
+
 ### Crear una instancia a partir de un snapshot
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.es-us.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.es-us.md
index 7babd4ff490..cbe48240062 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.es-us.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: 'Crear o restaurar un servidor virtual a partir de un snapshot'
 excerpt: 'Descubra cómo crear o restaurar la copia de seguridad de una instancia'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objetivo
@@ -21,6 +21,17 @@ Quizá necesite, en algún momento, restaurar su instancia utilizando un snapsho
 
 ## Procedimiento
 
+> [!primary]
+>
+> Están disponibles dos tipos de copias de seguridad:
+>
+> - Local: almacenada en la misma región que su instancia.
+> - Remota: automáticamente replicada en otra región de su elección.
+>
+> Las operaciones de **creación** y **restauración** de una instancia desde un backup remoto son totalmente compatibles a través de la API OVHcloud, ofreciendo una mayor flexibilidad y una integración más sencilla en sus procesos de automatización.
+>
+> **Nota:** Estas operaciones no están disponibles aún desde el área de cliente de OVHcloud.
+
 ### Crear una instancia a partir de un snapshot
 
 > [!tabs]
@@ -120,7 +131,7 @@ Quizá necesite, en algún momento, restaurar su instancia utilizando un snapsho
 >> ```
 >>
 
-### Restaurar una instancia a partir de un snapshot
+### Restaurar una instancia desde una copia de seguridad
 
 > [!tabs]
 > A través del área de cliente de OVHcloud
@@ -179,4 +190,4 @@ Quizá necesite, en algún momento, restaurar su instancia utilizando un snapsho
 
 [Guardar una copia de seguridad de una instancia](/pages/public_cloud/compute/save_an_instance)
 
-Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
+Interactúe con nuestra [comunidad de usuarios](/links/community).
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.fr-ca.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.fr-ca.md
index 685fa6eb3fc..515a068a51a 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.fr-ca.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: 'Créer / restaurer un serveur virtuel a partir d’une sauvegarde'
 excerpt: 'Découvrez comment créer ou restaurer la sauvegarde d’une instance'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objectif
@@ -21,6 +21,18 @@ Vous pouvez être amenés à vouloir restaurer votre instance grâce à une sauv
 
 ## En pratique
 
+> [!primary]
+>
+> Deux types de sauvegardes sont disponibles :
+>
+> - Locale : stockée dans la même région que votre instance.
+> - Distante : automatiquement répliquée dans une autre région de votre choix.
+>
+> Les opérations de **création** et de **restauration** d'une instance depuis une sauvegarde distante sont entièrement prises en charge via l’API OVHcloud, offrant une plus grande flexibilité et une intégration facilitée dans vos processus d’automatisation.
+>
+> **Note :** Ces opérations ne sont pas encore disponibles depuis l’espace client OVHcloud.
+>
+
 ### Créer une instance a partir d'une sauvegarde
 
 > [!tabs]
@@ -70,7 +82,7 @@ Vous pouvez être amenés à vouloir restaurer votre instance grâce à une sauv
 >>
 >> ![public-cloud-instance-backup-horizon-2](images/restorebackuphorizon2.png){.thumbnail}
 >>
->>  Choisissez le modèle d'instance désiré, puis cliquez sur l'onglet `Networks`{.action}.
+>> Choisissez le modèle d'instance désiré, puis cliquez sur l'onglet `Networks`{.action}.
 >>
 >> > [!warning]
 >> >
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.fr-fr.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.fr-fr.md
index 1f57aeec683..8161fc96df7 100644
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.fr-fr.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: 'Créer / restaurer un serveur virtuel a partir d’une sauvegarde'
 excerpt: 'Découvrez comment créer ou restaurer la sauvegarde d’une instance'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objectif
@@ -21,6 +21,18 @@ Vous pouvez être amenés à vouloir restaurer votre instance grâce à une sauv
 
 ## En pratique
 
+> [!primary]
+>
+> Deux types de sauvegardes sont disponibles :
+>
+> - Locale : stockée dans la même région que votre instance.
+> - Distante : automatiquement répliquée dans une autre région de votre choix.
+>
+> Les opérations de **création** et de **restauration** d'une instance depuis une sauvegarde distante sont entièrement prises en charge via l’API OVHcloud, offrant une plus grande flexibilité et une intégration facilitée dans vos processus d’automatisation.
+>
+> **Note :** Ces opérations ne sont pas encore disponibles depuis l’espace client OVHcloud.
+>
+
 ### Créer une instance a partir d'une sauvegarde
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.it-it.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.it-it.md
index 510ba9dfe3f..2e59d1c29ac 100755
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.it-it.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: 'Crea/ripristina il tuo server virtuale da un backup'
 excerpt: 'Scopri come creare o ripristinare il backup di un’istanza'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Obiettivo
@@ -21,6 +21,17 @@ Ripristinare un’istanza utilizzando un backup è necessario, ad esempio, se ha
 
 ## Procedura
 
+> [!primary]
+>
+> Sono disponibili due tipi di backup:
+>
+> - Locale: memorizzato nella stessa regione della tua istanza.
+> - Remoto: automaticamente replicato in un'altra regione a tua scelta.
+>
+> Le operazioni di **creazione** e **ripristino** di un’istanza da un backup remoto sono totalmente supportate tramite l’API OVHcloud, offrendo una maggiore flessibilità e una integrazione semplificata nei Suoi processi di automazione.
+>
+> **Nota:** Queste operazioni non sono ancora disponibili dallo Spazio Cliente OVHcloud.
+
 ### Crea un’istanza a partire da un backup
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.pl-pl.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.pl-pl.md
index 7aa868e993e..1fe6d0ad9d7 100755
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.pl-pl.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: 'Tworzenie / przywracanie serwera wirtualnego na podstawie kopii zapasowej'
 excerpt: 'Dowiedz się, jak utworzyć lub przywrócić kopię zapasową instancji'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Wprowadzenie
@@ -21,6 +21,17 @@ Może zajść konieczność przywrócenia instancji z kopii zapasowej, np. w prz
 
 ## W praktyce
 
+> [!primary]
+>
+> Dostępne są dwa typy kopii zapasowych:
+>
+> - Lokalna: przechowywana w tej samej regionie co Twoja instancja.
+> - Dystansowa: automatycznie replikowana w innym regionie, który wybierzesz.
+>
+> Operacje **tworzenia** i **przywracania** instancji z odległej kopii zapasowej są w pełni obsługiwane przez API OVHcloud, co zapewnia większą elastyczność i łatwą integrację z procesami automatyzacji.
+>
+> **Uwaga :** Te operacje nie są jeszcze dostępne za pośrednictwem Panelu klienta OVHcloud.
+
 ### Tworzenie instancji na podstawie kopii zapasowej
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.pt-pt.md b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.pt-pt.md
index 34dfa86031c..d3e74affe8b 100755
--- a/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.pt-pt.md
+++ b/pages/public_cloud/compute/create_restore_a_virtual_server_with_a_backup/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: 'Criar / Restaurar um servidor virtual a partir de um backup'
 excerpt: 'Saiba como criar ou restaurar o backup de uma instância'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objetivo
@@ -21,6 +21,17 @@ Pode querer restaurar a sua instância através de um backup, por exemplo, em ca
 
 ## Instruções
 
+> [!primary]
+>
+> Dois tipos de cópias de segurança estão disponíveis:
+>
+> - Local: armazenada na mesma região que a sua instância.
+> - Remota: automaticamente replicada noutra região à sua escolha.
+>
+> As operações de **criação** e de **restauro** de uma instância a partir de um backup remoto são inteiramente suportadas através da API OVHcloud, oferecendo uma maior flexibilidade e uma integração facilitada nos seus processos de automatização.
+>
+> **Nota:** Estas operações ainda não estão disponíveis a partir da área de cliente OVHcloud.
+
 ### Criar uma instância a partir de um backup
 
 > [!tabs]
diff --git a/pages/public_cloud/compute/migration_between_regions/guide.de-de.md b/pages/public_cloud/compute/migration_between_regions/guide.de-de.md
index 6e605fe0484..dad26655abb 100644
--- a/pages/public_cloud/compute/migration_between_regions/guide.de-de.md
+++ b/pages/public_cloud/compute/migration_between_regions/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: "Migration von Instanzen zwischen verschiedenen Regionen"
 excerpt: "Erfahren Sie, wie Sie eine OVHcloud Public Cloud-Instanz zwischen 1AZ und 3AZ Regionen migrieren."
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Ziel
@@ -37,8 +37,6 @@ OVHcloud bietet zwei Arten von Backups an, mit unterschiedlichem Verhalten, abh
 >
 > Lokale Backups sind in allen Verfügbarkeitszonen innerhalb einer 3AZ-Region zugänglich. Sie können direkt zum Schritt der Instanzneuanlage übergehen.
 >
-> Derzeit ist die Erstellung eines Distanz-Backups nicht über das OVHcloud Kundencenter möglich. Diesen Vorgang können Sie nur über die OVHcloud API oder OpenStack durchführen.
->
 
 Eine Instanz kann gesichert werden:
 
diff --git a/pages/public_cloud/compute/migration_between_regions/guide.en-gb.md b/pages/public_cloud/compute/migration_between_regions/guide.en-gb.md
index 19ae1ab7da1..e7019f713ca 100644
--- a/pages/public_cloud/compute/migration_between_regions/guide.en-gb.md
+++ b/pages/public_cloud/compute/migration_between_regions/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: 'Migration of instances between different regions'
 excerpt: 'This guide describes how to migrate an OVHcloud Public Cloud instance between two regions, 1AZ and 3AZ. It covers the backup, transfer and re-creation steps, with instructions via the Manager, Horizon or the OpenStack CLI.'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objectives
@@ -37,8 +37,6 @@ OVHcloud offers two types of backup, with different behaviors depending on the t
 >
 > Local backups are accessible from all availability zones within a 3AZ region. You can proceed directly to the instance re-creation stage.
 >
-> Currently, creating a distant backup is not available through the OVHcloud Control Panel. You can only perform this action via the OVHcloud API or OpenStack.
->
 
 An instance can be backed up:
 
diff --git a/pages/public_cloud/compute/migration_between_regions/guide.es-es.md b/pages/public_cloud/compute/migration_between_regions/guide.es-es.md
index 689605187fa..fcf00844ccd 100644
--- a/pages/public_cloud/compute/migration_between_regions/guide.es-es.md
+++ b/pages/public_cloud/compute/migration_between_regions/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: 'Migración de instancias entre zonas de disponibilidad (AZ)'
 excerpt: 'Este guía describe cómo migrar una instancia de Public Cloud de OVHcloud entre dos zonas de disponibilidad (AZ), 1AZ y 3AZ. Cubre los pasos de backup, transferencia y recreación, con instrucciones a través del Manager, Horizon o la CLI OpenStack.'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objetivo
@@ -37,8 +37,6 @@ OVHcloud ofrece dos tipos de backups, con comportamientos diferentes según el t
 >
 > Los backups locales están disponibles desde todas las zonas de disponibilidad de una región 3AZ. Puede pasar directamente al paso de recreación de la instancia.
 >
-> Actualmente, la creación de un backup remoto no está disponible a través del área de cliente de OVHcloud. Solo puede realizar esta acción a través de la API de OVHcloud o OpenStack.
->
 
 El backup de una instancia puede realizarse:
 
diff --git a/pages/public_cloud/compute/migration_between_regions/guide.fr-fr.md b/pages/public_cloud/compute/migration_between_regions/guide.fr-fr.md
index bdd3340d87a..5965a3b5512 100644
--- a/pages/public_cloud/compute/migration_between_regions/guide.fr-fr.md
+++ b/pages/public_cloud/compute/migration_between_regions/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: 'Migration d’instances entre zones de disponibilité (AZ)'
 excerpt: 'Ce guide décrit comment migrer une instance Public Cloud OVHcloud entre deux zones de disponibilité (AZ), 1AZ et 3AZ. Il couvre les étapes de sauvegarde, transfert et recréation, avec instructions via le Manager, Horizon ou la CLI OpenStack.'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objectifs
@@ -37,8 +37,6 @@ OVHcloud propose deux types de sauvegardes, avec des comportements différents s
 >
 > Les sauvegardes locales sont accessibles depuis toutes les zones de disponibilité d’une région 3AZ. Vous pouvez directement passer à l’étape de recréation de l’instance.
 >
-> Actuellement, la création d'une sauvegarde distante n'est pas disponible via l'espace client OVHcloud. Vous ne pouvez effectuer cette action que via l'API OVHcloud ou OpenStack.
->
 
 La sauvegarde d'une instance peut être réalisée :
 
diff --git a/pages/public_cloud/compute/migration_between_regions/guide.it-it.md b/pages/public_cloud/compute/migration_between_regions/guide.it-it.md
index aa7baa1598b..f516f293c54 100644
--- a/pages/public_cloud/compute/migration_between_regions/guide.it-it.md
+++ b/pages/public_cloud/compute/migration_between_regions/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: 'Migrazione di istanze tra zone di disponibilità (AZ)'
 excerpt: "Questa guida descrive come migrare un'istanza Public Cloud OVHcloud tra due zone di disponibilità (AZ), 1AZ e 3AZ. Copre le fasi di backup, trasferimento e ricreazione, con istruzioni tramite il Manager, Horizon o la CLI OpenStack."
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Obiettivi
@@ -37,8 +37,6 @@ OVHcloud offre due tipi di backup, con comportamenti diversi in base al tipo di
 >
 > I backup locali sono accessibili da tutte le zone di disponibilità di una regione 3AZ. È possibile passare direttamente alla fase di ricreazione dell'istanza.
 >
-> Al momento, la creazione di un backup remoto non è disponibile tramite lo Spazio Cliente OVHcloud. È possibile effettuare questa azione solo tramite l'API OVHcloud o OpenStack.
->
 
 Il backup di un'istanza può essere effettuato:
 
diff --git a/pages/public_cloud/compute/migration_between_regions/guide.pl-pl.md b/pages/public_cloud/compute/migration_between_regions/guide.pl-pl.md
index b72c9718654..96fc67ab383 100644
--- a/pages/public_cloud/compute/migration_between_regions/guide.pl-pl.md
+++ b/pages/public_cloud/compute/migration_between_regions/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: 'Migracja instancji między różnymi regionami'
 excerpt: 'Przewodnik opisuje, jak migrować instancję OVHcloud Public Cloud między dwoma regionami, 1AZ i 3AZ. Obejmuje kroki tworzenia kopii zapasowej, transferu i ponownego tworzenia, z instrukcjami za pomocą Managera, Horizon lub OpenStack CLI.'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Wprowadzenie
@@ -37,8 +37,6 @@ OVHcloud oferuje dwa typy kopii zapasowych, z różnymi zachowaniami w zależno
 >
 > Lokalne kopie zapasowe są dostępne ze wszystkich stref dostępności w regionie 3AZ. Możesz przejść bezpośrednio do etapu ponownego tworzenia instancji.
 >
-> Obecnie tworzenie odległej kopii zapasowej nie jest dostępne za pomocą Panelu klienta OVHcloud. Można to zrobić tylko za pomocą API OVHcloud lub OpenStack.
->
 
 Instancję można zabezpieczyć:
 
diff --git a/pages/public_cloud/compute/migration_between_regions/guide.pt-pt.md b/pages/public_cloud/compute/migration_between_regions/guide.pt-pt.md
index 0368513dd17..5f54a79c498 100644
--- a/pages/public_cloud/compute/migration_between_regions/guide.pt-pt.md
+++ b/pages/public_cloud/compute/migration_between_regions/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: 'Migração de instâncias entre zonas de disponibilidade (AZ)'
 excerpt: 'Este guia descreve como migrar uma instância Public Cloud OVHcloud entre duas zonas de disponibilidade (AZ), 1AZ e 3AZ. Ele abrange as etapas de backup, transferência e recriação, com instruções via Manager, Horizon ou CLI OpenStack.'
-updated: 2025-10-15
+updated: 2025-11-04
 ---
 
 ## Objetivo
@@ -37,8 +37,6 @@ OVHcloud oferece dois tipos de backups, com comportamentos diferentes dependendo
 >
 > Os backups locais estão disponíveis a partir de todas as zonas de disponibilidade de uma região 3AZ. Você pode passar diretamente para a etapa de recriação da instância.
 >
-> Atualmente, a criação de um backup remoto não está disponível via Área de Cliente OVHcloud. Você só pode realizar esta ação via API OVHcloud ou OpenStack.
->
 
 O backup de uma instância pode ser realizado:
 
diff --git a/pages/public_cloud/compute/save_an_instance/guide.de-de.md b/pages/public_cloud/compute/save_an_instance/guide.de-de.md
index 86972e624c0..6e64142ac5a 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.de-de.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: Backup einer Instanz erstellen
 excerpt: Erfahren Sie hier, wie Sie eine Public Cloud Instanz in Ihrem OVHcloud Kundencenter sichern
-updated: 2025-10-14
+updated: 2025-11-04
 ---
 
 <style>
@@ -43,11 +43,11 @@ Sie können ein einzelnes Backup einer Instanz erstellen oder einen Zeitplan kon
 > Zwei Arten von Sicherungen sind verfügbar:
 >
 > - *Local*: Eine lokale Sicherung wird in derselben Region wie Ihre Instanz gespeichert.
-> - *Distant*: Eine entfernte Sicherung erstellt automatisch eine Kopie der lokalen Sicherung in einer anderen von Ihnen ausgewählten Region.
+> - *Distant*: Eine Distanz-Sicherung erstellt automatisch eine Kopie der lokalen Sicherung in einer anderen, von Ihnen ausgewählten Region.
 >
-> Jede Sicherung wird gesondert berechnet. Die ferne Sicherung wird gemäß der Speicherplatzkosten der ausgewählten fernen Region berechnet.
+> Jede Sicherung wird gesondert berechnet. Die Distanz-Sicherung wird gemäß der Speicherplatzkosten der ausgewählten Region berechnet.
 >
-> Momentan ist die Erstellung einer entfernten Sicherung nicht über das OVHcloud Kundencenter verfügbar. Sie können dies nur über die OVHcloud API und OpenStack durchführen.
+> **Hinweis:** Local Zones sind für entfernte Backups nicht geeignet.
 
 > [!tabs]
 > Über das OVHcloud Kundencenter
@@ -66,9 +66,15 @@ Sie können ein einzelnes Backup einer Instanz erstellen oder einen Zeitplan kon
 >>
 >> ///
 >>
->> Der Fortschritt der Sicherung kann nicht in Echtzeit verfolgt werden. Sie können jedoch den Status der Sicherung im Bereich `Instance Backup`{.action} unter dem Menüpunkt **Compute** im linken Menü einsehen, wo der Status `Sicherung läuft` angezeigt wird.
+>> /// details | Entferntes Backup
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> Geben Sie einen Namen für das Backup ein. Überprüfen Sie die Preisinformationen. Klicken Sie auf `Fern-Backup hinzufügen (Option)`{.action}, geben Sie einen Namen für das Backup ein, wählen Sie eine Region aus und klicken Sie auf `Bestätigen`{.action}
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
+>>
+>> ///
+>>
+>> Der Fortschritt der Sicherung kann nicht in Echtzeit verfolgt werden. Allerdings wird im Bereich `Instance Backup`{.action} unter **Compute** im linken Menü während des Vorgangs der Status `Backup in Bearbeitung` angezeigt.
 >>
 >> Nach Abschluss der Sicherung wird diese im Bereich `Instance Backup`{.action} unter dem Menüpunkt **Compute** im linken Menü angezeigt.
 >>
@@ -76,7 +82,16 @@ Sie können ein einzelnes Backup einer Instanz erstellen oder einen Zeitplan kon
 >>
 > Über die OVHcloud API <a name="createinstanceviaapi"></a>
 >>
->> Loggen Sie sich in die [OVHcloud API-Konsole](/links/console) ein und verwenden Sie den folgenden API-Aufruf:
+>> Loggen Sie sich in die [OVHcloud API-Konsole](/links/console).
+>>
+>> Sie können anschließend alle verfügbaren Regionen mit folgendem API-Aufruf anzeigen:
+>>
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>> Verwenden Sie anschließend folgenden API-Aufruf:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ Sie können ein einzelnes Backup einer Instanz erstellen oder einen Zeitplan kon
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> Sie können alle verfügbaren Regionen mit folgendem Befehl auflisten:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Lokale Sicherung
 >>
 >> Führen Sie anschließend den folgenden Befehl aus, um eine Sicherung Ihrer Instanz zu erstellen:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.en-asia.md b/pages/public_cloud/compute/save_an_instance/guide.en-asia.md
index d697ad0a9d7..516fc18b50f 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.en-asia.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.en-asia.md
@@ -47,7 +47,8 @@ You can create a single backup of an instance or configure a schedule in order t
 >
 > Each backup is billed separately — the distant backup will be charged based on the storage pricing of the selected remote region.
 >
-> Currently, creating a distant backup is not available through the OVHcloud Control Panel. You can only perform this action via the OVHcloud API or OpenStack.
+> **Note:** Local Zones are not eligible for distant backups.
+>
 
 > [!tabs]
 > Via the OVHcloud Control Panel
@@ -66,17 +67,31 @@ You can create a single backup of an instance or configure a schedule in order t
 >>
 >> ///
 >>
->> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
+>> /// details | Distant backup
+>>
+>> Enter a name for the backup. Review the pricing information. Click `Add a remote backup (Option)`{.action}, enter a name for distant backup, select a region and click `Confirm`{.action}
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ///
+>>
+>> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
 >>
 >> Once the backup is complete, it will be available in the `Instance Backup`{.action} section under **Compute** in the left-hand menu.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Via the OVHcloud API <a name="createinstanceviaapi"></a>
+>> Log in to the [OVHcloud API](/links/console).
+>>
+>> You can then list all available regions using the following API call:
 >>
->> Log in to the [OVHcloud API](/links/console) and use the following API call:
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>>  Then use the following API call:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ You can create a single backup of an instance or configure a schedule in order t
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> You can list all available regions using the following command:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Local backup
 >>
 >> Then run the following command to create a backup of your instance:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.en-au.md b/pages/public_cloud/compute/save_an_instance/guide.en-au.md
index d697ad0a9d7..516fc18b50f 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.en-au.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.en-au.md
@@ -47,7 +47,8 @@ You can create a single backup of an instance or configure a schedule in order t
 >
 > Each backup is billed separately — the distant backup will be charged based on the storage pricing of the selected remote region.
 >
-> Currently, creating a distant backup is not available through the OVHcloud Control Panel. You can only perform this action via the OVHcloud API or OpenStack.
+> **Note:** Local Zones are not eligible for distant backups.
+>
 
 > [!tabs]
 > Via the OVHcloud Control Panel
@@ -66,17 +67,31 @@ You can create a single backup of an instance or configure a schedule in order t
 >>
 >> ///
 >>
->> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
+>> /// details | Distant backup
+>>
+>> Enter a name for the backup. Review the pricing information. Click `Add a remote backup (Option)`{.action}, enter a name for distant backup, select a region and click `Confirm`{.action}
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ///
+>>
+>> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
 >>
 >> Once the backup is complete, it will be available in the `Instance Backup`{.action} section under **Compute** in the left-hand menu.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Via the OVHcloud API <a name="createinstanceviaapi"></a>
+>> Log in to the [OVHcloud API](/links/console).
+>>
+>> You can then list all available regions using the following API call:
 >>
->> Log in to the [OVHcloud API](/links/console) and use the following API call:
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>>  Then use the following API call:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ You can create a single backup of an instance or configure a schedule in order t
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> You can list all available regions using the following command:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Local backup
 >>
 >> Then run the following command to create a backup of your instance:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.en-ca.md b/pages/public_cloud/compute/save_an_instance/guide.en-ca.md
index d697ad0a9d7..516fc18b50f 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.en-ca.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.en-ca.md
@@ -47,7 +47,8 @@ You can create a single backup of an instance or configure a schedule in order t
 >
 > Each backup is billed separately — the distant backup will be charged based on the storage pricing of the selected remote region.
 >
-> Currently, creating a distant backup is not available through the OVHcloud Control Panel. You can only perform this action via the OVHcloud API or OpenStack.
+> **Note:** Local Zones are not eligible for distant backups.
+>
 
 > [!tabs]
 > Via the OVHcloud Control Panel
@@ -66,17 +67,31 @@ You can create a single backup of an instance or configure a schedule in order t
 >>
 >> ///
 >>
->> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
+>> /// details | Distant backup
+>>
+>> Enter a name for the backup. Review the pricing information. Click `Add a remote backup (Option)`{.action}, enter a name for distant backup, select a region and click `Confirm`{.action}
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ///
+>>
+>> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
 >>
 >> Once the backup is complete, it will be available in the `Instance Backup`{.action} section under **Compute** in the left-hand menu.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Via the OVHcloud API <a name="createinstanceviaapi"></a>
+>> Log in to the [OVHcloud API](/links/console).
+>>
+>> You can then list all available regions using the following API call:
 >>
->> Log in to the [OVHcloud API](/links/console) and use the following API call:
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>>  Then use the following API call:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ You can create a single backup of an instance or configure a schedule in order t
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> You can list all available regions using the following command:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Local backup
 >>
 >> Then run the following command to create a backup of your instance:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.en-gb.md b/pages/public_cloud/compute/save_an_instance/guide.en-gb.md
index 66d8983e141..cf1bcbbbc94 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.en-gb.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Backing up an instance
 excerpt: Find out how to back up a Public Cloud instance in the OVHcloud Control Panel or via OpenStack
-updated: 2025-10-14
+updated: 2025-11-04
 ---
 
 <style>
@@ -47,7 +47,8 @@ You can create a single backup of an instance or configure a schedule in order t
 >
 > Each backup is billed separately — the distant backup will be charged based on the storage pricing of the selected remote region.
 >
-> Currently, creating a distant backup is not available through the OVHcloud Control Panel. You can only perform this action via the OVHcloud API or OpenStack.
+> **Note:** Local Zones are not eligible for distant backups.
+>
 
 > [!tabs]
 > Via the OVHcloud Control Panel
@@ -66,17 +67,31 @@ You can create a single backup of an instance or configure a schedule in order t
 >>
 >> ///
 >>
->> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
+>> /// details | Distant backup
+>>
+>> Enter a name for the backup. Review the pricing information. Click `Add a remote backup (Option)`{.action}, enter a name for distant backup, select a region and click `Confirm`{.action}
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ///
+>>
+>> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
 >>
 >> Once the backup is complete, it will be available in the `Instance Backup`{.action} section under **Compute** in the left-hand menu.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Via the OVHcloud API <a name="createinstanceviaapi"></a>
+>> Log in to the [OVHcloud API](/links/console).
+>>
+>> You can then list all available regions using the following API call:
 >>
->> Log in to the [OVHcloud API](/links/console) and use the following API call:
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>>  Then use the following API call:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ You can create a single backup of an instance or configure a schedule in order t
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> You can list all available regions using the following command:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Local backup
 >>
 >> Then run the following command to create a backup of your instance:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.en-ie.md b/pages/public_cloud/compute/save_an_instance/guide.en-ie.md
index d697ad0a9d7..516fc18b50f 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.en-ie.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.en-ie.md
@@ -47,7 +47,8 @@ You can create a single backup of an instance or configure a schedule in order t
 >
 > Each backup is billed separately — the distant backup will be charged based on the storage pricing of the selected remote region.
 >
-> Currently, creating a distant backup is not available through the OVHcloud Control Panel. You can only perform this action via the OVHcloud API or OpenStack.
+> **Note:** Local Zones are not eligible for distant backups.
+>
 
 > [!tabs]
 > Via the OVHcloud Control Panel
@@ -66,17 +67,31 @@ You can create a single backup of an instance or configure a schedule in order t
 >>
 >> ///
 >>
->> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
+>> /// details | Distant backup
+>>
+>> Enter a name for the backup. Review the pricing information. Click `Add a remote backup (Option)`{.action}, enter a name for distant backup, select a region and click `Confirm`{.action}
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ///
+>>
+>> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
 >>
 >> Once the backup is complete, it will be available in the `Instance Backup`{.action} section under **Compute** in the left-hand menu.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Via the OVHcloud API <a name="createinstanceviaapi"></a>
+>> Log in to the [OVHcloud API](/links/console).
+>>
+>> You can then list all available regions using the following API call:
 >>
->> Log in to the [OVHcloud API](/links/console) and use the following API call:
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>>  Then use the following API call:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ You can create a single backup of an instance or configure a schedule in order t
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> You can list all available regions using the following command:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Local backup
 >>
 >> Then run the following command to create a backup of your instance:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.en-sg.md b/pages/public_cloud/compute/save_an_instance/guide.en-sg.md
index d697ad0a9d7..516fc18b50f 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.en-sg.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.en-sg.md
@@ -47,7 +47,8 @@ You can create a single backup of an instance or configure a schedule in order t
 >
 > Each backup is billed separately — the distant backup will be charged based on the storage pricing of the selected remote region.
 >
-> Currently, creating a distant backup is not available through the OVHcloud Control Panel. You can only perform this action via the OVHcloud API or OpenStack.
+> **Note:** Local Zones are not eligible for distant backups.
+>
 
 > [!tabs]
 > Via the OVHcloud Control Panel
@@ -66,17 +67,31 @@ You can create a single backup of an instance or configure a schedule in order t
 >>
 >> ///
 >>
->> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
+>> /// details | Distant backup
+>>
+>> Enter a name for the backup. Review the pricing information. Click `Add a remote backup (Option)`{.action}, enter a name for distant backup, select a region and click `Confirm`{.action}
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ///
+>>
+>> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
 >>
 >> Once the backup is complete, it will be available in the `Instance Backup`{.action} section under **Compute** in the left-hand menu.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Via the OVHcloud API <a name="createinstanceviaapi"></a>
+>> Log in to the [OVHcloud API](/links/console).
+>>
+>> You can then list all available regions using the following API call:
 >>
->> Log in to the [OVHcloud API](/links/console) and use the following API call:
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>>  Then use the following API call:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ You can create a single backup of an instance or configure a schedule in order t
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> You can list all available regions using the following command:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Local backup
 >>
 >> Then run the following command to create a backup of your instance:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.en-us.md b/pages/public_cloud/compute/save_an_instance/guide.en-us.md
index d697ad0a9d7..516fc18b50f 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.en-us.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.en-us.md
@@ -47,7 +47,8 @@ You can create a single backup of an instance or configure a schedule in order t
 >
 > Each backup is billed separately — the distant backup will be charged based on the storage pricing of the selected remote region.
 >
-> Currently, creating a distant backup is not available through the OVHcloud Control Panel. You can only perform this action via the OVHcloud API or OpenStack.
+> **Note:** Local Zones are not eligible for distant backups.
+>
 
 > [!tabs]
 > Via the OVHcloud Control Panel
@@ -66,17 +67,31 @@ You can create a single backup of an instance or configure a schedule in order t
 >>
 >> ///
 >>
->> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
+>> /// details | Distant backup
+>>
+>> Enter a name for the backup. Review the pricing information. Click `Add a remote backup (Option)`{.action}, enter a name for distant backup, select a region and click `Confirm`{.action}
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ///
+>>
+>> It is not possible to monitor backup progress in real time. However, in the `Instance Backup`{.action} section under **Compute** in the left-hand menu, the status `Backup in progress` will be displayed during the process.
 >>
 >> Once the backup is complete, it will be available in the `Instance Backup`{.action} section under **Compute** in the left-hand menu.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Via the OVHcloud API <a name="createinstanceviaapi"></a>
+>> Log in to the [OVHcloud API](/links/console).
+>>
+>> You can then list all available regions using the following API call:
 >>
->> Log in to the [OVHcloud API](/links/console) and use the following API call:
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>>  Then use the following API call:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ You can create a single backup of an instance or configure a schedule in order t
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> You can list all available regions using the following command:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Local backup
 >>
 >> Then run the following command to create a backup of your instance:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.es-es.md b/pages/public_cloud/compute/save_an_instance/guide.es-es.md
index 81217818d3d..d893b96b783 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.es-es.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.es-es.md
@@ -47,7 +47,8 @@ Puede crear una copia de seguridad única de una instancia o configurar una plan
 >
 > Cada copia de seguridad se factura por separado. La copia de seguridad remota se facturará según la tarifa de almacenamiento de la región remota seleccionada.
 >
-> Actualmente, la creación de una copia de seguridad remota no está disponible a través del área de cliente de OVHcloud. Solo puede hacerlo a través de la API OVHcloud y Openstack.
+> **Nota :** las Local Zones no son compatibles con copias de seguridad remotas.
+
 
 > [!tabs]
 > A través del área de cliente de OVHcloud
@@ -66,17 +67,31 @@ Puede crear una copia de seguridad única de una instancia o configurar una plan
 >>
 >> ///
 >>
->> No es posible seguir el progreso del backup en tiempo real. Sin embargo, puede consultar el estado del backup en la sección `Instance Backup`{.action} bajo la sección **Compute** del menú de la izquierda, donde se mostrará el estado `Backup en curso`.
+>> /// details | Copia de seguridad remota
+>>
+>> Introduzca un nombre para la copia de seguridad y revise la información de precios. Haga clic en `Añadir una copia de seguridad remota (Opción)`{.action}, introduzca un nombre para la copia de seguridad remota, seleccione una región y haga clic en `Confirmar`{.action}.
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
+>>
+>> ///
+>>
+>> No es posible seguir el progreso de la copia de seguridad en tiempo real. Sin embargo, puede consultar el estado de la copia de seguridad en la sección `Instance Backup`{.action} bajo la sección **Compute** del menú izquierdo, donde se mostrará el estado `Copia de seguridad en curso` durante el proceso.
 >>
 >> Una vez finalizado el backup, este estará disponible en la sección `Instance Backup`{.action} bajo la sección **Compute** en el menú de la izquierda.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > A través de la API de OVHcloud <a name="createinstanceviaapi"></a>
+>> Inicie sesión en [la API de OVHcloud](/links/console).
+>>
+>> Puede listar todas las regiones disponibles utilizando la siguiente llamada a la API:
+>>
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
 >>
->> Inicie sesión en la [API de OVHcloud](/links/console) y utilice la siguiente llamada a la API:
+>> Utilice a continuación la siguiente llamada a la API:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ Puede crear una copia de seguridad única de una instancia o configurar una plan
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> Puede listar todas las regiones disponibles utilizando el siguiente comando:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Backup local
 >>
 >> Ejecute el siguiente comando para crear un backup de su instancia:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.es-us.md b/pages/public_cloud/compute/save_an_instance/guide.es-us.md
index a582f7f923c..2569b5d0c6d 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.es-us.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.es-us.md
@@ -47,7 +47,8 @@ Puede crear una copia de seguridad única de una instancia o configurar una plan
 >
 > Cada copia de seguridad se factura por separado. La copia de seguridad remota se facturará según la tarifa de almacenamiento de la región remota seleccionada.
 >
-> Actualmente, la creación de una copia de seguridad remota no está disponible a través del área de cliente de OVHcloud. Solo puede hacerlo a través de la API OVHcloud y Openstack.
+> **Nota :** las Local Zones no son compatibles con copias de seguridad remotas.
+
 
 > [!tabs]
 > A través del área de cliente de OVHcloud
@@ -66,17 +67,31 @@ Puede crear una copia de seguridad única de una instancia o configurar una plan
 >>
 >> ///
 >>
->> No es posible seguir el progreso del backup en tiempo real. Sin embargo, puede consultar el estado del backup en la sección `Instance Backup`{.action} bajo la sección **Compute** del menú de la izquierda, donde se mostrará el estado `Backup en curso`.
+>> /// details | Copia de seguridad remota
+>>
+>> Introduzca un nombre para la copia de seguridad y revise la información de precios. Haga clic en `Añadir una copia de seguridad remota (Opción)`{.action}, introduzca un nombre para la copia de seguridad remota, seleccione una región y haga clic en `Confirmar`{.action}.
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
+>>
+>> ///
+>>
+>> No es posible seguir el progreso de la copia de seguridad en tiempo real. Sin embargo, puede consultar el estado de la copia de seguridad en la sección `Instance Backup`{.action} bajo la sección **Compute** del menú izquierdo, donde se mostrará el estado `Copia de seguridad en curso` durante el proceso.
 >>
 >> Una vez finalizado el backup, este estará disponible en la sección `Instance Backup`{.action} bajo la sección **Compute** en el menú de la izquierda.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > A través de la API de OVHcloud <a name="createinstanceviaapi"></a>
+>> Inicie sesión en [la API de OVHcloud](/links/console).
+>>
+>> Puede listar todas las regiones disponibles utilizando la siguiente llamada a la API:
+>>
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
 >>
->> Inicie sesión en la [API de OVHcloud](/links/console) y utilice la siguiente llamada a la API:
+>> Utilice a continuación la siguiente llamada a la API:
 >>
 >> > [!api]
 >> >
@@ -111,6 +126,12 @@ Puede crear una copia de seguridad única de una instancia o configurar una plan
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> Puede listar todas las regiones disponibles utilizando el siguiente comando:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Backup local
 >>
 >> Ejecute el siguiente comando para crear un backup de su instancia:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.fr-ca.md b/pages/public_cloud/compute/save_an_instance/guide.fr-ca.md
index 42e10edf333..6b6371e5904 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.fr-ca.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.fr-ca.md
@@ -47,7 +47,7 @@ Vous pouvez créer une sauvegarde unique d'une instance ou configurer un plannin
 >
 > Chaque sauvegarde est facturée séparément. La sauvegarde distante sera facturée selon la tarification du stockage dans la région distante sélectionnée.
 >
-> Actuellement, la création d’une sauvegarde distante n’est pas disponible via l'espace client OVHcloud. Vous pouvez l’effectuer uniquement via l’API OVHcloud et Openstack.
+> **Note :** les Local Zones ne sont pas éligibles pour les sauvegardes distantes
 >
 
 > [!tabs]
@@ -67,17 +67,31 @@ Vous pouvez créer une sauvegarde unique d'une instance ou configurer un plannin
 >>
 >> ///
 >>
->> Il n'est pas possible de suivre la progression de la sauvegarde en temps réel. Cependant, vous pouvez consulter le statut de la sauvegarde dans la section `Instance Backup`{.action} sous la rubrique **Compute** du menu de gauche, où l'état `Backup en cours` sera affiché pendant le processus.
+>> /// details | Sauvegarde distante
+>>
+>> Entrez un nom pour la sauvegarde et vérifiez les informations tarifaires. Cliquez sur `Ajouter un backup distant (Option)`{.action}, entrez un nom pour la sauvegarde distante, sélectionnez une région et cliquez sur `Confirmer`{.action}.
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ///
+>>
+>> Il n'est pas possible de suivre la progression de la sauvegarde en temps réel. Cependant, vous pouvez consulter le statut de la sauvegarde dans la section `Instance Backup`{.action} sous la rubrique **Compute** du menu de gauche, où l'état `Backup en cours` sera affiché pendant le processus.
 >>
 >> Une fois la sauvegarde terminée, celle-ci sera disponible dans la section `Instance Backup`{.action} sous la rubrique **Compute** dans le menu de gauche.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Via l'API OVHcloud <a name="createinstanceviaapi"></a>
+>> Authentifiez-vous sur [l'API OVHcloud](/links/console).
+>>
+>> Vous pouvez répertorier toutes les régions disponibles à l'aide de l'appel API suivant :
 >>
->> Authentifiez-vous sur [l'API OVHcloud](/links/console) et utilisez l'appel API suivant :
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>> Utilisez ensuite l'appel API suivant :
 >>
 >> > [!api]
 >> >
@@ -112,6 +126,12 @@ Vous pouvez créer une sauvegarde unique d'une instance ou configurer un plannin
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> Vous pouvez répertorier toutes les régions disponibles à l'aide de la commande suivante :
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Sauvegarde locale
 >>
 >> Exécutez ensuite la commande suivante pour créer une sauvegarde de votre instance :
diff --git a/pages/public_cloud/compute/save_an_instance/guide.fr-fr.md b/pages/public_cloud/compute/save_an_instance/guide.fr-fr.md
index ea1b243c69b..5706647aea6 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.fr-fr.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.fr-fr.md
@@ -47,7 +47,7 @@ Vous pouvez créer une sauvegarde unique d'une instance ou configurer un plannin
 >
 > Chaque sauvegarde est facturée séparément. La sauvegarde distante sera facturée selon la tarification du stockage dans la région distante sélectionnée.
 >
-> Actuellement, la création d’une sauvegarde distante n’est pas disponible via l'espace client OVHcloud. Vous pouvez l’effectuer uniquement via l’API OVHcloud et Openstack.
+> **Note :** les Local Zones ne sont pas éligibles pour les sauvegardes distantes
 >
 
 > [!tabs]
@@ -67,17 +67,31 @@ Vous pouvez créer une sauvegarde unique d'une instance ou configurer un plannin
 >>
 >> ///
 >>
->> Il n'est pas possible de suivre la progression de la sauvegarde en temps réel. Cependant, vous pouvez consulter le statut de la sauvegarde dans la section `Instance Backup`{.action} sous la rubrique **Compute** du menu de gauche, où l'état `Backup en cours` sera affiché pendant le processus.
+>> /// details | Sauvegarde distante
+>>
+>> Entrez un nom pour la sauvegarde et vérifiez les informations tarifaires. Cliquez sur `Ajouter un backup distant (Option)`{.action}, entrez un nom pour la sauvegarde distante, sélectionnez une région et cliquez sur `Confirmer`{.action}.
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ///
+>>
+>> Il n'est pas possible de suivre la progression de la sauvegarde en temps réel. Cependant, vous pouvez consulter le statut de la sauvegarde dans la section `Instance Backup`{.action} sous la rubrique **Compute** du menu de gauche, où l'état `Backup en cours` sera affiché pendant le processus.
 >>
 >> Une fois la sauvegarde terminée, celle-ci sera disponible dans la section `Instance Backup`{.action} sous la rubrique **Compute** dans le menu de gauche.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Via l'API OVHcloud <a name="createinstanceviaapi"></a>
+>> Authentifiez-vous sur [l'API OVHcloud](/links/console).
+>>
+>> Vous pouvez répertorier toutes les régions disponibles à l'aide de l'appel API suivant :
 >>
->> Authentifiez-vous sur [l'API OVHcloud](/links/console) et utilisez l'appel API suivant :
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>> Utilisez ensuite l'appel API suivant :
 >>
 >> > [!api]
 >> >
@@ -112,6 +126,12 @@ Vous pouvez créer une sauvegarde unique d'une instance ou configurer un plannin
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> Vous pouvez répertorier toutes les régions disponibles à l'aide de la commande suivante :
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Sauvegarde locale
 >>
 >> Exécutez ensuite la commande suivante pour créer une sauvegarde de votre instance :
diff --git a/pages/public_cloud/compute/save_an_instance/guide.it-it.md b/pages/public_cloud/compute/save_an_instance/guide.it-it.md
index e6248c10f1c..2fe00f726d6 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.it-it.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.it-it.md
@@ -47,7 +47,7 @@ Crea un backup unico di un'istanza o configura una pianificazione per automatizz
 >
 > Ogni backup è fatturato separatamente. Il backup remoto verrà fatturato in base alla tariffa di archiviazione della regione remota selezionata.
 >
-> Al momento, la creazione di un backup remoto non è disponibile tramite il Spazio Cliente OVHcloud. Puoi eseguirla solo tramite l'API OVHcloud e Openstack.
+> **Nota :** le Local Zones non sono idonee per i backup remoti.
 
 > [!tabs]
 > Attraverso il Spazio Cliente OVHcloud
@@ -66,17 +66,31 @@ Crea un backup unico di un'istanza o configura una pianificazione per automatizz
 >>
 >> ///
 >>
->> Non è possibile seguire in tempo reale l'avanzamento del backup. Tuttavia, puoi consultare lo stato del backup nella sezione `Instance Backup`{.action} sotto la voce **Compute** del menu a sinistra, dove verrà visualizzato lo stato `Backup in corso`.
+>> /// details | Backup remoto
+>>
+>> Inserisci un nome per il backup e verifica le informazioni sui costi. Clicca su `Aggiungi un backup remoto (Opzione)`{.action}, inserisci un nome per il backup remoto, seleziona una regione e clicca su `Conferma`{.action}.
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
+>>
+>> ///
+>>
+>> Non è possibile seguire in tempo reale l'avanzamento del backup. Tuttavia, puoi consultare lo stato del backup nella sezione `Instance Backup`{.action} sotto la voce **Compute** del menu a sinistra, dove verrà visualizzato lo stato `Backup in corso` durante il processo.
 >>
 >> Una volta completato il backup, sarà disponibile nella sezione `Instance Backup`{.action} sotto la voce **Compute** nel menu a sinistra.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Attraverso l'API OVHcloud <a name="createinstanceviaapi"></a>
+>> Accedi a [l'API OVHcloud](/links/console).
+>>
+>> Puoi elencare tutte le regioni disponibili utilizzando il seguente chiamata API :
+>>
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
 >>
->> Accedi all'[API OVHcloud](/links/console) e utilizza la seguente chiamata API:
+>> Utilizza quindi la seguente chiamata API :
 >>
 >> > [!api]
 >> >
@@ -111,6 +125,12 @@ Crea un backup unico di un'istanza o configura una pianificazione per automatizz
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> Puoi elencare tutte le regioni disponibili utilizzando il seguente comando :
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Backup locale
 >>
 >> Esegui il seguente comando per creare un backup della tua istanza:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.pl-pl.md b/pages/public_cloud/compute/save_an_instance/guide.pl-pl.md
index 8a0dabbb3ea..3cc1d3270ea 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.pl-pl.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: 'Tworzenie kopii zapasowej instancji'
 excerpt: 'Dowiedz się, jak utworzyć kopię zapasową instancji Public Cloud w Panelu klienta OVHcloud'
-updated: 2025-10-14
+updated: 2025-11-04
 ---
 
 <style>
@@ -47,7 +47,7 @@ Możesz utworzyć kopię zapasową instancji lub skonfigurować harmonogram, aby
 >
 > Każda kopia zapasowa jest rozliczana oddzielnie. Kopia zapasowa dystansowa zostanie rozliczona zgodnie z opłatami za przechowywanie danych w wybranej regionie dystansowej.
 >
-> Obecnie tworzenie kopii zapasowej dystansowej nie jest dostępne przez Panelu Klienta OVHcloud. Można to wykonać tylko za pomocą API OVHcloud i Openstack.
+> **Uwaga:** Local Zones nie są uprawnione do odległych kopii zapasowych.
 
 > [!tabs]
 > Przez Panelu Klienta OVHcloud
@@ -66,17 +66,31 @@ Możesz utworzyć kopię zapasową instancji lub skonfigurować harmonogram, aby
 >>
 >> ///
 >>
->> Nie można śledzić postępu kopii zapasowej w czasie rzeczywistym. Można jednak sprawdzić jej status w sekcji `Instance Backup`{.action} pod sekcją **Compute** w lewym menu, gdzie zostanie wyświetlony stan `Kopia zapasowa w trakcie`.
+>> /// details | Dystansowa kopia zapasowa
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> Wprowadź nazwę kopii zapasowej. Przejrzyj informacje o cenach. Kliknij `Dodaj odległą kopię zapasową (Opcja)`{.action}, wprowadź nazwę dla odległej kopii zapasowej, wybierz region i kliknij `Potwierdź`{.action}
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
+>>
+>> ///
+>>
+>> Nie jest możliwe monitorowanie postępu kopii zapasowej w czasie rzeczywistym. Jednak w sekcji `Instance Backup`{.action} pod **Compute** w lewym menu, podczas procesu będzie wyświetlany status `Kopia zapasowa w trakcie wykonywania`.
 >>
 >> Po zakończeniu kopii zapasowej będzie ona dostępna w sekcji `Instance Backup`{.action} pod sekcją **Compute** w lewym menu.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Przez API OVHcloud <a name="createinstanceviaapi"></a>
+>> Zaloguj się do [API OVHcloud](/links/console).
 >>
->> Zaloguj się do [API OVHcloud](/links/console) i użyj poniższego wywołania API:
+>> Możesz następnie wyświetlić listę wszystkich dostępnych regionów za pomocą poniższego wywołania API:
+>>
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>> Następnie użyj poniższego wywołania API:
 >>
 >> > [!api]
 >> >
@@ -111,6 +125,12 @@ Możesz utworzyć kopię zapasową instancji lub skonfigurować harmonogram, aby
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> Możesz wyświetlić listę wszystkich dostępnych regionów za pomocą poniższego polecenia:
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Lokalna kopia zapasowa
 >>
 >> Uruchom poniższe polecenie, aby utworzyć kopię zapasową swojej instancji:
diff --git a/pages/public_cloud/compute/save_an_instance/guide.pt-pt.md b/pages/public_cloud/compute/save_an_instance/guide.pt-pt.md
index a0089e428f8..321b8fcbd20 100644
--- a/pages/public_cloud/compute/save_an_instance/guide.pt-pt.md
+++ b/pages/public_cloud/compute/save_an_instance/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: 'Guardar uma instância'
 excerpt: 'Saiba como efetuar o backup de uma instância Public Cloud a partir da Área de Cliente OVHcloud'
-updated: 2025-10-14
+updated: 2025-11-04
 ---
 
 <style>
@@ -47,7 +47,7 @@ Pode criar um backup único de uma instância ou configurar um planeamento para
 >
 > Cada backup é cobrado separadamente. O backup remoto será cobrado de acordo com a tarifa de armazenamento da região remota selecionada.
 >
-> Atualmente, a criação de um backup remoto não está disponível por meio do área de cliente OVHcloud. Você pode fazê-lo apenas por meio da API OVHcloud e Openstack.
+> **Nota :** as Local Zones não são elegíveis para cópias de segurança remotas.
 
 
 > [!tabs]
@@ -67,17 +67,31 @@ Pode criar um backup único de uma instância ou configurar um planeamento para
 >>
 >> ///
 >>
->> Não é possível acompanhar o progresso do backup em tempo real. No entanto, você pode consultar o status do backup na seção `Instance Backup`{.action} sob a seção **Compute** no menu à esquerda, onde será exibido o status `Backup em andamento`.
+>> /// details | Cópia de segurança remota
 >>
->> ![public-cloud-instance-backup](images/backup_in_progress.png){.thumbnail}
+>> Introduza um nome para a cópia de segurança e verifique as informações tarifárias. Clique em `Adicionar backup remoto (Opção)`{.action}, introduza um nome para a cópia de segurança remota, selecione uma região e clique em `Confirmar`{.action}.
+>>
+>> ![public-cloud-instance-backup](images/createdistantbackup.png){.thumbnail}
+>>
+>> ///
+>>
+>> Não é possível seguir o progresso da cópia de segurança em tempo real. No entanto, pode consultar o estado da cópia de segurança na secção `Instance Backup`{.action} sob a rubrica **Compute** do menu à esquerda, onde será exibido o estado `Backup em curso` durante o processo.
 >>
 >> Após o término do backup, ele estará disponível na seção `Instance Backup`{.action} sob a seção **Compute** no menu à esquerda.
 >>
 >> ![public-cloud-instance-backup](images/createbackup3.png){.thumbnail}
 >>
 > Através da API OVHcloud <a name="createinstanceviaapi"></a>
+>> Autentique-se na [API OVHcloud](/links/console).
 >>
->> Faça login na [API OVHcloud](/links/console) e utilize a seguinte chamada de API:
+>> Pode listar todas as regiões disponíveis utilizando o seguinte pedido API :
+>>
+>> > [!api]
+>> >
+>> > @api {v1} /cloud GET  /cloud/project/{serviceName}/region
+>> >
+>>
+>> Utilize em seguida o seguinte pedido API :
 >>
 >> > [!api]
 >> >
@@ -112,6 +126,12 @@ Pode criar um backup único de uma instância ou configurar um planeamento para
 >> +--------------------------------------+-----------+--------+--------------------------------------------------+--------------+
 >> ```
 >>
+>> Pode listar todas as regiões disponíveis utilizando o seguinte comando :
+>>
+>> ```bash
+>> $ openstack region list
+>> ```
+>>
 >> /// details | Backup local
 >>
 >> Execute o seguinte comando para criar um backup da sua instância:
diff --git a/pages/public_cloud/compute/save_an_instance/images/backup_in_progress.png b/pages/public_cloud/compute/save_an_instance/images/backup_in_progress.png
deleted file mode 100644
index 2ac2fc2b2b0..00000000000
Binary files a/pages/public_cloud/compute/save_an_instance/images/backup_in_progress.png and /dev/null differ
diff --git a/pages/public_cloud/compute/save_an_instance/images/createbackup1.png b/pages/public_cloud/compute/save_an_instance/images/createbackup1.png
index 97b7b901fbb..1a9f74c6253 100644
Binary files a/pages/public_cloud/compute/save_an_instance/images/createbackup1.png and b/pages/public_cloud/compute/save_an_instance/images/createbackup1.png differ
diff --git a/pages/public_cloud/compute/save_an_instance/images/createbackup2bis.png b/pages/public_cloud/compute/save_an_instance/images/createbackup2bis.png
index 55a934b19b5..9940ffe9de9 100644
Binary files a/pages/public_cloud/compute/save_an_instance/images/createbackup2bis.png and b/pages/public_cloud/compute/save_an_instance/images/createbackup2bis.png differ
diff --git a/pages/public_cloud/compute/save_an_instance/images/createbackup3.png b/pages/public_cloud/compute/save_an_instance/images/createbackup3.png
index a3e2a3ac5a8..f517897a320 100644
Binary files a/pages/public_cloud/compute/save_an_instance/images/createbackup3.png and b/pages/public_cloud/compute/save_an_instance/images/createbackup3.png differ
diff --git a/pages/public_cloud/compute/save_an_instance/images/createdistantbackup.png b/pages/public_cloud/compute/save_an_instance/images/createdistantbackup.png
new file mode 100644
index 00000000000..d42a341da6a
Binary files /dev/null and b/pages/public_cloud/compute/save_an_instance/images/createdistantbackup.png differ
diff --git a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.fr-ca.md b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.fr-ca.md
index ab9417a8dee..07e0f58af4a 100644
--- a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.fr-ca.md
+++ b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.fr-ca.md
@@ -47,7 +47,7 @@ Le tableau ci-dessous vous permet de différencier les options disponibles sur v
     - [Depuis l’interface Horizon](#horizon-unshelve)
     - [Depuis les API Openstack/Nova](#openstack-nova-unshelve)
 - [Éteindre (suspend) une instance](#stop-suspend-instance)
-    - [Depuis l’espace client OVHcloudl](#stop-control-panel)
+    - [Depuis l’espace client OVHcloud](#stop-control-panel)
     - [Depuis l’interface Horizon](#stop-horizon)
     - [Depuis les API Openstack/Nova](#stop-openstack-nova)
 - [Mettre en pause une instance](#pause-instance)
diff --git a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.fr-fr.md b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.fr-fr.md
index ab9417a8dee..07e0f58af4a 100644
--- a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.fr-fr.md
+++ b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.fr-fr.md
@@ -47,7 +47,7 @@ Le tableau ci-dessous vous permet de différencier les options disponibles sur v
     - [Depuis l’interface Horizon](#horizon-unshelve)
     - [Depuis les API Openstack/Nova](#openstack-nova-unshelve)
 - [Éteindre (suspend) une instance](#stop-suspend-instance)
-    - [Depuis l’espace client OVHcloudl](#stop-control-panel)
+    - [Depuis l’espace client OVHcloud](#stop-control-panel)
     - [Depuis l’interface Horizon](#stop-horizon)
     - [Depuis les API Openstack/Nova](#stop-openstack-nova)
 - [Mettre en pause une instance](#pause-instance)
diff --git a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.it-it.md b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.it-it.md
index 3a1787ae692..9ea7ff3fd3f 100644
--- a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.it-it.md
+++ b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.it-it.md
@@ -48,7 +48,7 @@ La tabella qui sotto ti permette di differenziare le opzioni disponibili sulle t
     - [Dall'interfaccia Horizon](#horizon-unshelve)
     - [Dalle API OpenStack/Nova](#openstack-nova-unshelve)
 - [Spegnere (suspend) un'istanza](#stop-suspend-instance)
-    - [Nello Spazio Cliente OVHcloudl](#stop-control-panel)
+    - [Nello Spazio Cliente OVHcloud](#stop-control-panel)
     - [Dall'interfaccia Horizon](#stop-horizon)
     - [Dalle API OpenStack/Nova](#stop-openstack-nova)
 - [Mettere in pausa un'istanza](#pause-instance)
diff --git a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.pl-pl.md b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.pl-pl.md
index 2b942e2df32..8b320341e40 100644
--- a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.pl-pl.md
+++ b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.pl-pl.md
@@ -47,7 +47,7 @@ Poniższa tabela pozwoli Ci odróżnić opcje dostępne dla Twoich instancji. Ko
     - [Z poziomu interfejsu Horizon](#horizon-unshelve)
     - [Korzystanie z API OpenStack/Nova](#openstack-nova-unshelve)
 - [Wyłącz (suspend) instancję](#stop-suspend-instance)
-    - [W Panelu klienta OVHcloudl](#stop-control-panel)
+    - [W Panelu klienta OVHcloud](#stop-control-panel)
     - [Z poziomu interfejsu Horizon](#stop-horizon)
     - [Korzystanie z API OpenStack/Nova](#stop-openstack-nova)
 - [Wstrzymaj instancję](#pause-instance)
diff --git a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.pt-pt.md b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.pt-pt.md
index d48e0ec34f7..cf509f0d7f9 100644
--- a/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.pt-pt.md
+++ b/pages/public_cloud/compute/suspend_or_pause_an_instance/guide.pt-pt.md
@@ -47,7 +47,7 @@ A tabela abaixo permite-lhe diferenciar as opções disponíveis nas suas instâ
     - [Da interface Horizon](#horizon-unshelve)
     - [Utilização das API OpenStack/Nova](#openstack-nova-unshelve)
 - [Desativar (suspend) uma instância](#stop-suspend-instance)
-    - [Da Área de Cliente OVHcloudl](#stop-control-panel)
+    - [Da Área de Cliente OVHcloud](#stop-control-panel)
     - [Da interface Horizon](#stop-horizon)
     - [Utilização das API OpenStack/Nova](#stop-openstack-nova)
 - [Colocar em pausa uma instância (*pause*)](#pause-instance)
diff --git a/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/guide.en-gb.md b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/guide.en-gb.md
new file mode 100644
index 00000000000..f5dd5599ddd
--- /dev/null
+++ b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/guide.en-gb.md
@@ -0,0 +1,207 @@
+---
+title: 'Configure access control using OVHcloud IAM on an OVHcloud Managed Rancher Service'
+excerpt: 'Learn how to enable and manage OVHcloud IAM authentication to control access to your Managed Rancher Service (MRS) using centralized identities and roles'
+updated: 2025-11-04
+---
+
+<style>
+details>summary {
+    color:rgb(33, 153, 232) !important;
+    cursor: pointer;
+}
+details>summary::before {
+    content:'\25B6';
+    padding-right:1ch;
+}
+details[open]>summary::before {
+    content:'\25BC';
+}
+</style>
+
+## Objective
+
+OVHcloud Managed Rancher Service (MRS) supports authentication through OVHcloud IAM, allowing you to manage access using centralized user identities and roles.
+
+This guide explains how to enable IAM authentication and control user access to your Rancher service using OVHcloud IAM users and roles.
+
+## Requirements
+
+- An OVHcloud Managed Rancher Service (see the [Creating, updating and accessing a Managed Rancher Service](/pages/public_cloud/containers_orchestration/managed_rancher_service/create-update-rancher) guide for more information).
+
+## Instructions
+
+### Introduction to OVHcloud IAM
+
+OVHcloud IAM (Identity and Access Management) is a centralized system that lets you control who can access your OVHcloud services and what actions they can perform. It provides fine-grained access management through users, groups, and roles.
+
+When integrated with the Managed Rancher Service (MRS), OVHcloud IAM replaces Rancher’s local authentication system. This allows you to:
+
+- Use Single Sign-On (SSO) with your OVHcloud credentials to access Rancher.
+- Assign predefined IAM roles (such as base, ovhRestrictedAdmin, standard) to define access levels.
+- Manage permissions efficiently at scale using IAM groups and projects.
+
+Integrating IAM with your Rancher service ensures consistent access control across all your OVHcloud resources, reducing manual management and improving overall security.
+
+### Activate/disable authentication via OVHcloud IAM
+
+> [!warning]
+>
+> When you enable OVHcloud IAM authentication on your Managed Rancher Service:
+> 
+> - Local users will remain functional, so you can continue logging in with your usual Rancher accounts.
+> - If the "admin" password is regenerated while IAM authentication is enabled, or if no user has ever logged in locally, the ability to log in with the IAM root user will be impossible. To restore access with the IAM root user, log in first with a local admin account.
+> 
+> From this point on, IAM roles and policies control access for users authenticated via OVHcloud IAM.
+>
+
+> [!tabs]
+> Via the OVHcloud Control Panel (coming soon)
+>> > [!primary]
+>> >
+>> > Managing IAM from the OVHcloud Control Panel is not yet available and will be added in a future release.
+>> >
+>>
+> Via the OVHcloud API
+>>
+>> > [!api]
+>> >
+>> > @api {v2} /publicCloud PUT /publicCloud/project/{projectId}/rancher/{rancherId}
+>> >
+>>
+>> With the request body:
+>>
+>> ```json
+>> {
+>>   "targetSpec": {
+>>     "iamAuthEnabled": true, // true to enable IAM, false to disable
+>>     "name": "my_rancher", // Name of the Managed Rancher Service
+>>     "plan": "STANDARD", // Plan of the Managed Rancher Service
+>>     "version": "1.0.0" // Version of the Managed Rancher Service
+>>   }
+>> }
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > Make sure all the information in the JSON (service name, plan, version) is correct. Using incorrect values will result in an error when activating or disabling IAM.
+>> >
+>>
+>> Replace:
+>>
+>> - `projectId` with the ID of your Public Cloud project.
+>> - `rancherId` with the ID of the Managed Rancher Service.
+>>
+>> You can retrieve the `rancherId` in two ways:
+>>
+>> - **Via API:**
+>> 
+>> > [!api]
+>> >
+>> > @api {v2} /publicCloud GET /publicCloud/project/{projectId}/rancher
+>> >
+>>
+>> - **Via the OVHcloud Control Panel:**
+>>
+>> Log in to the [OVHcloud Control Panel](/links/manager), navigate to the `Public Cloud`{.action} section, and select the relevant project. Then, in the left-hand menu under **Containers & Orchestration**, click on `Managed Rancher Service`{.action}.
+>>
+
+### Authentication using SSO with OVHcloud IAM users
+
+Once IAM authentication is enabled on your Managed Rancher Service, access to the Rancher UI is managed via OVHcloud Single Sign-On (SSO). Users no longer log in with local Rancher credentials but authenticate directly using their OVHcloud IAM identity.
+
+> [!primary]
+>
+> Local Rancher users remain functional even after enabling OVHcloud IAM, but their use is not recommended. Access and permissions should be managed through OVHcloud IAM roles and policies for consistency and security.
+>
+
+To log in via SSO:
+
+- Open the `Rancher user interface`{.action} from the Control Panel.
+
+![rancher user interface](images/rancher_interface.png){.thumbnail}
+
+- You will be redirected to the Managed Rancher Service authentication page.
+
+/// details | No user has ever logged in locally
+
+Click on `Use a local user`{.action} to go to the local login page.
+
+To recover the admin password required for authentication, use the following API call:
+
+> [!api]
+>
+> @api {v2} /publicCloud POST /publicCloud/project/{projectId}/rancher/{rancherId}/adminCredentials
+>
+
+Replace:
+
+- `projectId` with the ID of your Public Cloud project.
+- `rancherId` with the ID of the Managed Rancher Service.
+
+Copy the returned password, then paste it on the authentication page.
+
+Make sure to check the box to accept the `End User License Agreement & Terms & Conditions`{.action}, then click `Continue`{.action}.
+
+You can now log out and proceed with your normal workflow.
+
+///
+
+Click on `Log in with OIDC`, which will take you to the OVHcloud authentication page. There, log in using your OVHcloud IAM credentials.
+
+![login with SSO](images/iam_authentication.png){.thumbnail}
+
+- Access to Rancher is granted based on the IAM role associated with your user account.
+
+> [!primary]
+>
+> Only users with the appropriate IAM role (base, standard and ovhRestrictedAdmin) can access the registry after IAM authentication is enabled.
+>
+
+### Managing access rights with OVHcloud IAM
+
+OVHcloud IAM provides three predefined roles for managing access to your Managed Rancher Service (MRS):
+
+- base
+- standard
+- ovhRestrictedAdmin
+
+> [!primary]
+>
+> **base** role: Base users can only log in and do not have any additional permissions.
+>
+> **standard** role: Standard users can create new clusters and manage clusters and projects they have been granted access to.
+>
+> **ovhRestrictedAdmin** role: OVHcloud Restricted Admins have full control over all resources in downstream clusters but do not have access to the local cluster.
+>
+
+These roles are assigned through IAM policies. To create and configure a policy, log in to the [OVHcloud Control Panel](/links/manager) and navigate to the `Identity, Security & Operations`{.action} section. Then, in the left-hand menu under **Identity and Access management**, click on `Policies`{.action} and click the `Create a policy`{.action} button.
+
+![Create policy](images/managing_iam.png){.thumbnail}
+
+Define users and groups, name your policy, add the users you want to include and optionally, add user groups if they have already been created.
+
+![Create policy users](images/create_policy.png){.thumbnail width="700"}
+
+Set permissions for MRS: 
+
+- In the `Product types`{.action} section, select `Public Cloud / Managed Rancher Service (MRS) project`{.action}.
+- In the `Resources`{.action} section, choose the specific MRS service to which the policy will apply.
+
+![Create policy product types](images/create_policy_product_types.png){.thumbnail}
+
+Expand `Public Cloud / Managed Rancher Service (MRS) project`{.action} and select the desired role for the users defined in the policy.
+
+![Create policy roles](images/create_policy_action.png){.thumbnail width="700"}
+
+### Go further
+
+To go further you can look at our guides on:
+
+- [Managing users and projects](/pages/public_cloud/containers_orchestration/managed_private_registry/managing-users-and-projects).
+- [Creating and using a private image](/pages/public_cloud/containers_orchestration/managed_private_registry/creating-and-using-a-private-image).
+
+If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
+
+Our team remains available on our dedicated Discord Channel, do not hesitate to join and reach us : <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our Container and Orchestration services.
+
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/create_policy.png b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/create_policy.png
new file mode 100644
index 00000000000..29570632710
Binary files /dev/null and b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/create_policy.png differ
diff --git a/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/create_policy_action.png b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/create_policy_action.png
new file mode 100644
index 00000000000..c9626c2976d
Binary files /dev/null and b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/create_policy_action.png differ
diff --git a/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/create_policy_product_types.png b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/create_policy_product_types.png
new file mode 100644
index 00000000000..943b819890a
Binary files /dev/null and b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/create_policy_product_types.png differ
diff --git a/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/iam_authentication.png b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/iam_authentication.png
new file mode 100644
index 00000000000..2248d772153
Binary files /dev/null and b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/iam_authentication.png differ
diff --git a/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/managing_iam.png b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/managing_iam.png
new file mode 100644
index 00000000000..7f27ed82e02
Binary files /dev/null and b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/managing_iam.png differ
diff --git a/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/rancher_interface.png b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/rancher_interface.png
new file mode 100644
index 00000000000..19df086c719
Binary files /dev/null and b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/images/rancher_interface.png differ
diff --git a/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/meta.yaml b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/meta.yaml
new file mode 100644
index 00000000000..ae5cbd0bf6f
--- /dev/null
+++ b/pages/public_cloud/containers_orchestration/managed_rancher_service/managing-iam-authentication/meta.yaml
@@ -0,0 +1,2 @@
+id: ff1f372d-0656-46b5-ac8e-31dcef6e4076
+full_slug: public-cloud-managed-rancher-service-iam-authentication
\ No newline at end of file
diff --git a/pages/public_cloud/quantum_computing/billing/guide.en-gb.md b/pages/public_cloud/quantum_computing/billing/guide.en-gb.md
index 0157dfcf4a8..8627a02375e 100644
--- a/pages/public_cloud/quantum_computing/billing/guide.en-gb.md
+++ b/pages/public_cloud/quantum_computing/billing/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Quantum computing - Billing and lifecycle
 excerpt: Learn how we bill Quantum Notebooks
-updated: 2025-06-17
+updated: 2025-11-06
 ---
 
 > [!warning]
@@ -10,7 +10,7 @@ updated: 2025-06-17
 
 ## Objective
 
-**OVHcloud Quantum Notebooks** are managed Jupyter and VSCode notebooks with assigned CPU or GPU resources, eliminating the need for installation and maintenance. This documentation will detail the notebook **lifecycle and billing**.
+**OVHcloud Quantum Notebooks** are managed Jupyter and VS Code notebooks with assigned CPU or GPU resources, eliminating the need for installation and maintenance. This documentation will detail the notebook **lifecycle and billing**.
 
 ## Introduction
 
@@ -37,10 +37,11 @@ Quantum Notebooks is a **pay-per-use solution**. You only pay for the **resource
 
 **Included** in Quantum Notebooks resources:
 
-- Dedicated CPU/GPU compute resources (based on the selected amount during notebook creation)
+- Dedicated CPU/GPU compute resources (based on the selected amount during notebook creation).
+- For **Quantum QPU**, an additional remote Quantum Processing Unit compute resource is available on your notebook.
 - Ephemeral local notebook storage (the size depends on the selected compute resources). The first 10GB are free.
-- Workspace remote storage (Optional)
-- Ingress/Egress network traffic (Optional)
+- Workspace remote storage (Optional).
+- Ingress/Egress network traffic (Optional).
 
 Here is a detailed graph that illustrates every step that is billed or not during the Quantum Notebooks workflow:
 
@@ -50,6 +51,8 @@ Here is a detailed graph that illustrates every step that is billed or not durin
 
 During the notebook creation, you can select **compute resources**, known as CPUs or GPUs. Their official pricing is available in the [OVHcloud Control Panel](/links/manager) or on the [OVHcloud Public Cloud website](/links/public-cloud/prices).
 
+When your program needs to access to the remote QPU, QPU time is charged by the second. You will only be charged for your QPU usage time.
+
 Rates for compute are mentioned per hour to facilitate reading of the prices, but the billing granularity remains **per minute**.
 
 As stated above and shown in the image above, you pay for these resources as long as you consume them. This happens when the image of your notebook is pulled, during the `STARTING` phase, but also during `RUNNING` and `STOPPING` phases, until you reach the `STOPPED` phase.
@@ -62,7 +65,7 @@ There are three types of storage within Quantum Notebooks:
 - Workspace storage
 - Ephemeral local storage
 
-The pricing of these different storages is different.
+The pricing of these storages is different.
 
 #### Remote Object storage
 
@@ -90,53 +93,73 @@ This storage is not billed as it is directly linked to the compute resource(s) y
 
 ### Pricing examples
 
-#### Example 1: one GPU notebook for 10 hours then deleted
-
-We start one Quantum Notebook, with two GPUs and we keep it running for 10 hours then we **delete it**.
-
-- compute resources: 2 x GPU NVIDIA V100s (1,93€ / hour)
-- remote storage: nothing
-- duration: 10 hours then deleted
-
-Price calculation for compute: 10 (hours) x 2 (GPU) x 1,93€ (price / GPU) = **38,6 euros**, billed at the end of the month.
-
-#### Example 2: one GPU notebook for 10 hours but stopped, not deleted
-
-We start one Quantum Notebook, with two GPUs and we keep it running for 10 hours then we stop it and finally we **delete it after 10 days**.
-
-- compute resources: 2 x GPU NVIDIA V100s (1,93 / hour)
-- remote storage: nothing
-- workspace storage: 100GB used. The first 10GB are free.
-- duration: 10 hours then stopped for 10 days
-
-Price calculation for compute : 10 (hours) x 2 (GPU) x 1,93 (price / GPU) = **38,6 euros**, billed at the end of the month.
-Price calculation for workspace : 90 (GB) x 0,01€ (price for object storage / GB) = **0,9 euros**, billed at the end of the month.
-
-#### Example 3: one GPU notebook for 10 hours with 1TB remote storage
-
-We start one Quantum Notebook, with two GPUs and 1TB remote storage. We keep it running for 10 hours then we delete it.
-
-- compute resources: 2 x GPU NVIDIA V100s (1,93 / hour)
-- remote storage: 1TB in OVHcloud Object Storage
-- workspace storage: 100GB used. The first 10GB are free.
-- duration: 10 hours then we delete it.
-
-Price calculation for compute: 10 (hours) x 2 (GPU) x 1,93 (price / GPU) = **38,6 euros**, billed at the end of the month.
-Price calculation for workspace: 90 (GB) x 0,01€ (price for object storage / GB) = **0,9 euros**, billed at the end of the month.
-
-Also, price calculation for remote Object Storage : 1000 (GB) x 0,01€ (price for object storage / GB) = **10 euros**, billed at the end of the month.
-
-#### Example 4: 15 CPU notebooks for 5 hours then deleted
-
-We start 15 Quantum Notebooks, each of them with one vCPU
-
-- compute resources: 1 x vCPU (0,03€ /hour /cpu)
-- remote storage: nothing
-- duration: 5 hours then we delete it.
-
-Price calculation for compute: 15 (notebooks) x 5 (hours) x 1 (CPU) x 0,03€ (price / CPU) = **2,25 euros**, billed at the end of the month.
-
-## Going further
+> [!tabs]
+> **For Quantum Emulators**
+>>
+>> **Example 1: One GPU notebook for 10 hours then deleted**
+>> 
+>> We start one Quantum Notebook with two GPUs and we keep it running for 10 hours then we **delete it**.
+>> 
+>> - Compute resources: 2 x GPU NVIDIA V100s (1,93€ / hour)
+>> - Remote storage: Nothing
+>> - Duration: 10 hours then deleted
+>> 
+>> Price calculation for compute: 10 (hours) x 2 (GPU) x 1,93€ (price / GPU) = **38,6 euros**, billed at the end of the month.
+>> 
+>> **Example 2: One GPU notebook for 10 hours but stopped, not deleted**
+>> 
+>> We start one Quantum Notebook, with two GPUs and we keep it running for 10 hours then we stop it and finally we **delete it after 10 days**.
+>> 
+>> - Compute resources: 2 x GPU NVIDIA V100s (1,93 / hour)
+>> - Remote storage: Nothing
+>> - Workspace storage: 100GB used. The first 10GB are free.
+>> - Duration: 10 hours then stopped for 10 days
+>> 
+>> Price calculation for compute : 10 (hours) x 2 (GPU) x 1,93 (price / GPU) = **38,6 euros**, billed at the end of the month.
+>> Price calculation for workspace : 90 (GB) x 0,01€ (price for object storage / GB) = **0,9 euros**, billed at the end of the month.
+>> 
+>> **Example 3: One GPU notebook for 10 hours with 1TB remote storage**
+>> 
+>> We start one Quantum Notebook, with two GPUs and 1TB remote storage. We keep it running for 10 hours then we delete it.
+>> 
+>> - Compute resources: 2 x GPU NVIDIA V100s (1,93 / hour)
+>> - Remote storage: 1TB in OVHcloud Object Storage
+>> - Workspace storage: 100GB used. The first 10GB are free.
+>> - Duration: 10 hours then we delete it.
+>> 
+>> Price calculation for compute: 10 (hours) x 2 (GPU) x 1,93 (price / GPU) = **38,6 euros**, billed at the end of the month.
+>> Price calculation for workspace: 90 (GB) x 0,01€ (price for object storage / GB) = **0,9 euros**, billed at the end of the month.
+>> 
+>> Also, price calculation for remote Object Storage : 1000 (GB) x 0,01€ (price for object storage / GB) = **10 euros**, billed at the end of the month.
+>> 
+>> **Example 4: 15 CPU notebooks for 5 hours then deleted**
+>> 
+>> We start 15 Quantum Notebooks, each of them with one vCPU
+>> 
+>> - Compute resources: 1 x vCPU (0,03€ /hour /cpu)
+>> - Remote storage: Nothing
+>> - Duration: 5 hours then we delete it.
+>> 
+>> Price calculation for compute: 15 (notebooks) x 5 (hours) x 1 (CPU) x 0,03€ (price / CPU) = **2,25 euros**, billed at the end of the month.
+>>
+> **For Quantum QPUs**
+>>
+>> Pricing of Quantum QPUs notebooks are the same than Quantum Emulators but you will pay only for the time you use a QPU.
+>>
+>> **Example 1: One CPU used during 10 hours + one Pasqal QPU Orion Beta used during 1 hour**
+>> 
+>> We start one Quantum QPU Notebook, with one CPU and we keep it running for 10 hours then we **delete it**.
+>> We use one hour of the Orion Pasqal QPU which costs 3000€ / hour.
+>> 
+>> - Compute resources: 1 x Intel CPU VCore (0,03€ / hour)
+>> - Remote storage: Nothing
+>> - Duration: 10 hours then deleted
+>> - QPU usage: 1 x Pasqal QPU Orion Beta (3000€ / hour)
+>> 
+>> Price calculation for compute: 10 (hours) x 1 (CPU) x 0,03€ (price / CPU) + 1 (hour) x 3000€ (price / QPU) = **3000,3 euros**, billed at the end of the month.
+>>
+
+## Go further
 
 For training or technical assistance, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis.
 
diff --git a/pages/public_cloud/quantum_computing/billing/images/billing.png b/pages/public_cloud/quantum_computing/billing/images/billing.png
index e7e6335521f..e426cc2c9c3 100644
Binary files a/pages/public_cloud/quantum_computing/billing/images/billing.png and b/pages/public_cloud/quantum_computing/billing/images/billing.png differ
diff --git a/pages/public_cloud/quantum_computing/billing/images/lifecycle.png b/pages/public_cloud/quantum_computing/billing/images/lifecycle.png
index 958a57810ac..4eb4a2b979c 100644
Binary files a/pages/public_cloud/quantum_computing/billing/images/lifecycle.png and b/pages/public_cloud/quantum_computing/billing/images/lifecycle.png differ
diff --git a/pages/public_cloud/quantum_computing/capabilities/guide.en-gb.md b/pages/public_cloud/quantum_computing/capabilities/guide.en-gb.md
index 393957065ca..e69bd9dde8b 100644
--- a/pages/public_cloud/quantum_computing/capabilities/guide.en-gb.md
+++ b/pages/public_cloud/quantum_computing/capabilities/guide.en-gb.md
@@ -148,12 +148,14 @@ OVHcloud Quantum Notebooks comes with pre-installed Quantum environments.
 List of available Quantum Environments:
 
 - Alice & Bob Felis
-- C12
 - Atos myQLM
-- Pasqal Pulser
-- Quandela Perceval
+- C12
 - IBM Qiskit
+- IQM SQK
+- Pasqal Pulser
+- Pasqal Pulser for QPU
 - QPerfect MIMIQ
+- Quandela Perceval
 - Quobly
 
 #### Environment customization
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/guide.en-gb.md b/pages/public_cloud/quantum_computing/emulators/getting-started/guide.en-gb.md
similarity index 84%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/guide.en-gb.md
rename to pages/public_cloud/quantum_computing/emulators/getting-started/guide.en-gb.md
index e7ea1dd7841..543ed43332c 100644
--- a/pages/public_cloud/quantum_computing/getting-started-emulators/guide.en-gb.md
+++ b/pages/public_cloud/quantum_computing/emulators/getting-started/guide.en-gb.md
@@ -1,32 +1,23 @@
 ---
-title: Quantum computing - Getting started with emulators
-excerpt: Learn how to bootstrap a Quantum Notebook emulator
-updated: 2025-06-17
+title: Quantum computing - Getting started with Emulators Notebooks
+excerpt: Learn how to set up a Quantum Emulators Notebook
+updated: 2025-11-06
 ---
 
 > [!warning]
 >
 > Some links on this documentation refer to the AI and Machine Learning solution. Quantum computing shares the same infrastructure as a service so you might be redirected to another section of this documentation.
+>
 
 ## Introduction
 
 A **Notebook** is a document that integrates code, rich text elements, and multimedia, making it a convenient tool for quantum analysis and visualization.
 
-**OVHcloud Quantum Emulators** is our managed solution for Jupyter and VSCode Notebooks. You can easily launch Notebooks with the required CPU and GPU resources while enjoying benefits like pre-installed dependencies and Quantum frameworks, secure user access, and simplified data management.
+**OVHcloud Quantum Emulators** is our managed solution for Jupyter and VS Code Notebooks. You can easily launch Notebooks with the required CPU and GPU resources while enjoying benefits like pre-installed dependencies and Quantum frameworks, secure user access, and simplified data management.
 
 ## Objective
 
-This guide demonstrates how to create, configure, access, stop, restart, and delete a Quantum Notebook emulator.
-
-## Requirements
-
-- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](/links/manager)
-- A Public Cloud user with the **Administrator** or **Quantum Operator & Objectstore Operator** roles
-
-## Instructions
-
-To create your first Quantum Notebook, we recommend using the **OVHcloud Control Panel (UI)**. This method is user-friendly and ideal for beginners.
+This guide demonstrates how to create, configure, access, stop, restart and delete a Quantum Emulators Notebook from the **OVHcloud Control Panel (UI)**. This method is user-friendly and ideal for beginners.
 
 Alternatively, you can use one of the following methods:
 
@@ -36,12 +27,20 @@ Alternatively, you can use one of the following methods:
 
 Each method offers its distinct advantages, depending on your expertise and preferred workflow.
 
-### OVHcloud Quantum Solutions Authorization Process
+## Requirements
+
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- Access to the [OVHcloud Control Panel](/links/manager).
+- A Public Cloud user with the **Administrator** or **Quantum Operator & Objectstore Operator** roles.
+
+## Instructions
 
-If you're using the CLI, API, or SDK, you will need to complete an authorization process before creating a Quantum Notebook. To do so, follow these steps:
+### OVHcloud Quantum Solutions authorization process
+
+If you're using the CLI, API, or SDK, you will need to complete an authorization process before creating a Quantum Emulators Notebook. To do so, follow these steps:
 
 1. Log in to the [OVHcloud Control Panel](/links/manager) and navigate to the `Public Cloud`{.action} section.
-2. Select the Public Cloud project you want to use and click on the `Quantum computing`{.action} category.
+2. Select the Public Cloud project you want to use and click the `Quantum Emulators`{.action} category.
 3. Click the `Create a Notebook`{.action} button. The authorization process will take place silently in the background.
 
 ![Create a Notebook Control Panel manager 01](images/creating-a-notebook-using-UI-01.png){.thumbnail}
@@ -52,69 +51,70 @@ To create a Quantum Notebook, follow these steps:
 
 > [!tabs]
 > **Using the Control Panel (UI)**
->>
->> Navigate to the `Public Cloud`{.action} section of the [OVHcloud Control Panel](/links/manager) and click on the `Quantum computing`{.action} category.
+>> 
+>> Navigate to the `Public Cloud`{.action} section of the [OVHcloud Control Panel](/links/manager), click the `Quantum Emulators`{.action} category.
 >> Click the `Create a Notebook`{.action} button and follow the prompts to specify the configuration of your Quantum Notebook.
 >>
->> **1\. Notebook Name**
->>
+>> ![Create a Notebook Control Panel manager 01](images/creating-a-notebook-using-UI-01.png){.thumbnail}
+>> 
+>> **1\. Notebook name**
+>> 
 >> Give a name to your notebook. This will make it easier to manage when you have multiple Quantum Notebooks created.
 >> 
 >> **2\. Notebook location**
->>
+>> 
 >> Next, select a location.
->>
+>> 
 >> ![Create a Notebook Control Panel manager 02](images/creating-a-notebook-using-UI-02.png){.thumbnail}
->>
->> **3\. Compute Resources**
->>
+>> 
+>> **3\. Compute resources**
+>> 
 >> Specify and adjust the type and amount of computing resources (CPU / GPU) for your Quantum Notebook. Use the `+`{.action} and `-`{.action} buttons to increase or decrease the number of CPUs and GPUs, depending on your needs.
 >> 
->> Click the `Next`{.action} button.
->>
+>> Click `Next`{.action}.
+>> 
 >> ![Create a Notebook Control Panel manager 03](images/creating-a-notebook-using-UI-03.png){.thumbnail}
->>
->> **4\. Pre-configured Frameworks**
->>
->> Choose the Quantum python framework you want to use, which will be pre-installed and ready to use when your notebook is launched. A wide range of Quantum frameworks are available in different versions. Select the version that suits your needs. Then, click the `Next`{.action} button to continue.
->>
+>> 
+>> **4\. Pre-configured frameworks**
+>> 
+>> Choose the Quantum Python framework you want to use, which will be pre-installed and ready to use when your notebook is launched. A wide range of Quantum frameworks are available in different versions. Select the version that suits your needs. Then, click `Next`{.action} to continue.
+>> 
 >> ![Create a Notebook Control Panel manager 04](images/creating-a-notebook-using-UI-04.png){.thumbnail}
->>
+>> 
 >> **5\. Live-code editor**
->>
+>> 
 >> Choose the code editor you want.
->>
+>> 
 >> ![Create a Notebook Control Panel manager 05](images/creating-a-notebook-using-UI-05.png){.thumbnail}
->>
->> **6\. Privacy Settings**
->>
->> Next, select your privacy settings and click the `Next`{.action} button.
->>
+>> 
+>> **6\. Privacy settings**
+>> 
+>> Then, select your privacy settings and click `Next`{.action}.
+>> 
 >> > [!warning]
 >> >
->> > *Public access* will expose your data and code to anyone getting the Quantum Notebook link. Be careful and don't use it with sensitive data. On the other hand, *Restricted access* will ask a user and password combination or a Quantum token to access the Notebook content, ensuring a secure environment.
->>
->>
+>> > *Public access* will expose your data and code to anyone getting the Quantum Notebook link. Be careful not to use it with sensitive data. On the other hand, *Restricted access* will require a user and password combination or a Quantum token to access the Notebook content to ensure a secure environment.
+>> 
 >> ![Create a Notebook Control Panel manager 06](images/creating-a-notebook-using-UI-06.png){.thumbnail}
->>
+>> 
 >> **7\. Advanced configuration**
->>
->> By default, your Quantum Notebook comes with **ephemeral storage** (local storage). But in this step, you can also link Object Storage containers and Git repositories to your notebook, to easily access your remote data.
->>
+>> 
+>> By default, your Quantum Notebook comes with **ephemeral storage** (local storage). But in this step, you can also link Object Storage containers and Git repositories to your notebook to easily access your remote data.
+>> 
 >> If you want to learn more about configuring containers and Git repositories in the Notebook, you can refer to this [AI & Machine learning documentation](/pages/public_cloud/ai_machine_learning/notebook_guide_data_ui). For now, we will launch a classic Notebook without any external volumes added to it.
->>
->> Click the `Next`{.action} button.
+>> 
+>> Click `Next`{.action}.
 >>
 >> ![Create a Notebook Control Panel manager 07](images/creating-a-notebook-using-UI-07.png){.thumbnail}
->>
->> **SSH public keys** allow you to access your Notebook remotely. This section is optional, click the `Next`{.action} button.
->>
+>> 
+>> **SSH public keys** allow you to access your Notebook remotely. This section is optional, click `Next`{.action}.
+>> 
 >> **9\. Launch the Quantum Notebook**
->>
->> At the end of the process, review your settings and click the `Order now`{.action} button to confirm and launch the creation of your Notebook. You will be redirected to you notebook dashboard:
+>> 
+>> At the end of the process, review your settings and click the `Order now`{.action} button to confirm and launch the creation of your Notebook. You will be redirected to your notebook dashboard:
 >> 
 >> ![Create a Notebook Control Panel manager 10](images/creating-a-notebook-using-UI-08b.png){.thumbnail}
->>
+>> 
 >> > [!primary]
 >> >
 >> > Note at the bottom of the screen the equivalent *ovhai* CLI command. This command allows you to run the exact same Notebook using the CLI.
@@ -152,7 +152,7 @@ To create a Quantum Notebook, follow these steps:
 >>
 >> > [!warning]
 >> > 
->> > **Alpha Warning**: This package is currently in the **alpha phase** of development. The APIs and functionalities of the package may not be fully tested.
+>> > **Alpha version warning**: This package is currently in the **alpha phase** of development. The APIs and functionalities of the package may not be fully tested.
 >>
 >> 1. Create a bearer token from the *ovhai* CLI. For more detailed instructions on creating a token, check the [manage access tokens](/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli) documentation.
 >> 2. Install the `ovhai` Python SDK and follow the instructions in the [ovhai PyPI](https://pypi.org/project/ovhai/) page to create a Quantum Notebook.
@@ -211,21 +211,21 @@ To create a Quantum Notebook, follow these steps:
 
 ### Accessing your Quantum Notebook
 
-Once your Quantum Notebook is created and running, you can access it using the `JupyterLab` link in the Quantum Emulators board or through the `ovhai` CLI, Quantum API, or Python SDK.
+Once your Quantum Notebook is created and running, you can access it using the `JupyterLab` link in the Quantum Notebooks board or through the `ovhai` CLI, Quantum API, or Python SDK.
 
 > [!tabs]
 > **Using the Control Panel (UI)**
->>
->> Click the `JupyterLab`{.action} link in the `Access` column:
->>
+>> 
+>> Click the `JupyterLab`{.action} link in the `Publisher` column:
+>> 
 >> ![Accessing a Notebook Control Panel manager 1](images/accessing-a-notebook-using-UI-1.png){.thumbnail}
->>
+>> 
 >> You can also access the Notebook from its dedicated page:
->>
+>> 
 >> ![Accessing a Notebook Control Panel manager 2](images/accessing-a-notebook-using-UI-2.png){.thumbnail}
->>
+>> 
 >> On the Notebook page, you will find information about the Notebook, including specifications, billing, and attached data, as well as a monitoring URL for real-time metrics.
->>
+>> 
 > **Using ovhai CLI**
 >>
 >> The `URL` of your Notebook should be displayed in your terminal and you can display it by running `ovhai notebook list` to retrieve the `URL`.
@@ -236,7 +236,7 @@ Once your Quantum Notebook is created and running, you can access it using the `
 >>
 > **Using the Quantum API**
 >>
->> The `URL` of your Notebook should be displayed in the 'Response' panel:
+>> The `URL` of your Notebook should appear in the `Response` panel:
 >>
 >> ![Access a Notebook API](images/accessing-a-notebook-using-API.png){.thumbnail}
 >>
@@ -295,24 +295,23 @@ Once your Quantum Notebook is created and running, you can access it using the `
 >>
 >> print(json.loads(response.content.decode()))
 >> ```
+>>
 
 ### Connecting to your Quantum Notebook
 
 To connect to your Quantum Notebook, you'll need to authenticate using a username and password combination or an access token.
 
-> [!tabs]
-> **Using a Username and Password**
->>
->> Enter your Public Cloud project user's username and password to log in to your Quantum Notebook.
->>
->> ![Notebook Authentication Credentials](images/notebook-authentication-creds.png){.thumbnail}
->>
-> **Using an Access Token**
->>
->> Click the `Login with token` button and enter your access token to log in to your Quantum Notebook.
->>
->> ![Notebook Authentication Token](images//notebook-authentication-token.png){.thumbnail}
->>
+**Using a Username and Password**
+
+Enter your Public Cloud project user's credentials to log in to your Quantum Notebook.
+
+![Notebook Authentication Credentials](images/notebook-authentication-creds.png){.thumbnail}
+
+**Using an Access Token**
+
+Click the `Login with token` button and enter your access token to log in to your Quantum Notebook.
+
+![Notebook Authentication Token](images/notebook-authentication-token.png){.thumbnail}
 
 ### Stopping a Quantum Notebook
 
@@ -320,12 +319,12 @@ You can stop your Quantum Notebook at any time to release its compute resources.
 
 > [!tabs]
 > **Using the Control Panel (UI)**
->>
+>> 
 >> Go to the Quantum Notebooks board and click on the `...`{.action} button next to the Notebook you want to stop.
 >> Click the `Stop`{.action} button to stop the Notebook. Or, on the notebook board, you can click on the `red button`{.action} at the top of the page.
->>
+>> 
 >> ![Stop a Notebook Control Panel manager](images/stopping-a-notebook-using-UI.png){.thumbnail}
->>
+>> 
 > **Using ovhai CLI**
 >>
 >> Run the command `ovhai notebook stop <NOTEBOOK_UUID>` to stop the Notebook.
@@ -354,6 +353,7 @@ You can stop your Quantum Notebook at any time to release its compute resources.
 >> with client as client:
 >>     response = notebook_stop.sync_detailed(client=client, id=id)
 >> ```
+>>
 
 ### Restarting a stopped Notebook
 
@@ -361,12 +361,12 @@ To restart a stopped Notebook, follow these steps:
 
 > [!tabs]
 > **Using the Control Panel (UI)**
->>
+>> 
 >> Go to the Quantum Notebooks board and click on the `...`{.action} button next to the Notebook you want to restart.
 >> Click the `Start` button to restart the Notebook. Or, on the notebook board, you can click on the `blue button`{.action} at the top of the page.
->>
+>> 
 >> ![Restart a Notebook Control Panel manager](images/restarting-a-notebook-using-UI.png){.thumbnail}
->>
+>> 
 > **Using ovhai CLI**
 >>
 >> Run the command `ovhai notebook start <NOTEBOOK_UUID>` to restart the Notebook.
@@ -403,12 +403,12 @@ The notebook must be stopped before deleting it. To delete a Notebook, follow th
 
 > [!tabs]
 > **Using the Control Panel (UI)**
->>
+>> 
 >> Go to the Quantum Notebooks board and click on the `...`{.action} button next to the Notebook you want to delete.
 >> Click the `Delete`{.action} button to stop the Notebook. Or, on the notebook board, you can click on the `Delete notebook`{.action} button at the bottom of the page.
->>
+>> 
 >> ![Delete a Notebook Control Panel manager](images/deleting-a-notebook-using-UI.png){.thumbnail}
->>
+>> 
 > **Using ovhai CLI**
 >>
 >> Run the command `ovhai notebook delete <NOTEBOOK_UUID>` to delete the Notebook.
@@ -441,10 +441,10 @@ The notebook must be stopped before deleting it. To delete a Notebook, follow th
 >> ```
 >>
 
-## Going further
+## Go further
 
 - Discover how to access your Object Storage data and Git repositories from your Notebooks using the UI [here](/pages/public_cloud/ai_machine_learning/notebook_guide_data_ui).
-- Learn about the technical features, capabilities, and limitations of the Public Cloud Quantum Notebooks offer [here](/pages/public_cloud/quantum_computing/capabilities).
+- Learn about the technical features, capabilities, and limitations of the Public Cloud Quantum Notebooks offering [here](/pages/public_cloud/quantum_computing/capabilities).
 - Get some hints on how to debug your Notebooks if things go wrong [here](/pages/public_cloud/quantum_computing/troubleshooting).
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
@@ -455,4 +455,4 @@ We would love to help answer questions and appreciate any feedback you may have.
 
 Please send us your questions, feedback, and suggestions regarding Quantum Notebooks:
 
-- In the #quantum-computing channel of the OVHcloud [Discord server](https://discord.gg/ovhcloud).
+- In the #quantum-computing channel of the OVHcloud [Discord server](https://discord.gg/ovhcloud).
\ No newline at end of file
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/accessing-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-API copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/accessing-a-notebook-using-API.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-API copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-API.png
new file mode 100644
index 00000000000..ac292b727c5
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-API.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/accessing-a-notebook-using-UI-1.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-UI-1.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/accessing-a-notebook-using-UI-1.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-UI-1.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/accessing-a-notebook-using-UI-2.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-UI-2.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/accessing-a-notebook-using-UI-2.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-UI-2.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/accessing-a-notebook-using-ovhai-CLI.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-ovhai-CLI copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/accessing-a-notebook-using-ovhai-CLI.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-ovhai-CLI copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-ovhai-CLI.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-ovhai-CLI.png
new file mode 100644
index 00000000000..804d0fa026d
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/accessing-a-notebook-using-ovhai-CLI.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-API-01.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-API-01 copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-API-01.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-API-01 copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-API-01.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-API-01.png
new file mode 100644
index 00000000000..ec2008dc7cc
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-API-01.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-01.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-01 copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-01.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-01 copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-01.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-01.png
new file mode 100644
index 00000000000..4ee3447349c
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-01.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-02.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-02.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-02.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-02.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-03.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-03.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-03.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-03.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-04.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-04.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-04.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-04.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-05.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-05.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-05.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-05.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-06.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-06.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-06.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-06.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-07.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-07.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-07.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-07.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-08b.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-08b.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-08b.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-08b.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-09.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-09.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-UI-09.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-UI-09.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-ovhai-CLI.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-ovhai-CLI copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/creating-a-notebook-using-ovhai-CLI.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-ovhai-CLI copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-ovhai-CLI.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-ovhai-CLI.png
new file mode 100644
index 00000000000..fa4abe5bebd
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/creating-a-notebook-using-ovhai-CLI.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/deleting-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/deleting-a-notebook-using-API copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/deleting-a-notebook-using-API.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/deleting-a-notebook-using-API copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/deleting-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/deleting-a-notebook-using-API.png
new file mode 100644
index 00000000000..f89b37e8678
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/deleting-a-notebook-using-API.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/deleting-a-notebook-using-UI.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/deleting-a-notebook-using-UI.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/deleting-a-notebook-using-UI.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/deleting-a-notebook-using-UI.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/notebook-authentication-creds.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-creds copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/notebook-authentication-creds.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-creds copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-creds.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-creds.png
new file mode 100644
index 00000000000..444a85c581f
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-creds.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/notebook-authentication-token.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-token copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/notebook-authentication-token.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-token copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-token.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-token.png
new file mode 100644
index 00000000000..a18445fdc9c
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/notebook-authentication-token.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/restarting-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/restarting-a-notebook-using-API copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/restarting-a-notebook-using-API.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/restarting-a-notebook-using-API copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/restarting-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/restarting-a-notebook-using-API.png
new file mode 100644
index 00000000000..2b142d9244d
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/restarting-a-notebook-using-API.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/restarting-a-notebook-using-UI.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/restarting-a-notebook-using-UI.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/restarting-a-notebook-using-UI.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/restarting-a-notebook-using-UI.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/stopping-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/stopping-a-notebook-using-API copy.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/stopping-a-notebook-using-API.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/stopping-a-notebook-using-API copy.png
diff --git a/pages/public_cloud/quantum_computing/emulators/getting-started/images/stopping-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/stopping-a-notebook-using-API.png
new file mode 100644
index 00000000000..5974071da32
Binary files /dev/null and b/pages/public_cloud/quantum_computing/emulators/getting-started/images/stopping-a-notebook-using-API.png differ
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/images/stopping-a-notebook-using-UI.png b/pages/public_cloud/quantum_computing/emulators/getting-started/images/stopping-a-notebook-using-UI.png
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/images/stopping-a-notebook-using-UI.png
rename to pages/public_cloud/quantum_computing/emulators/getting-started/images/stopping-a-notebook-using-UI.png
diff --git a/pages/public_cloud/quantum_computing/getting-started-emulators/meta.yaml b/pages/public_cloud/quantum_computing/emulators/getting-started/meta.yaml
similarity index 100%
rename from pages/public_cloud/quantum_computing/getting-started-emulators/meta.yaml
rename to pages/public_cloud/quantum_computing/emulators/getting-started/meta.yaml
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/guide.en-gb.md b/pages/public_cloud/quantum_computing/qpus/getting-started/guide.en-gb.md
new file mode 100644
index 00000000000..2d5b453fe91
--- /dev/null
+++ b/pages/public_cloud/quantum_computing/qpus/getting-started/guide.en-gb.md
@@ -0,0 +1,461 @@
+---
+title: Quantum computing - Getting started with QPUs Notebooks
+excerpt: Learn how to set up a Quantum QPUs Notebook
+updated: 2025-11-06
+---
+
+> [!warning]
+>
+> Some links on this documentation refer to the AI and Machine Learning solution. Quantum computing shares the same infrastructure as a service so you might be redirected to another section of this documentation.
+>
+
+## Introduction
+
+A **Notebook** is a document that integrates code, rich text elements, and multimedia, making it a convenient tool for quantum analysis and visualization.
+
+**OVHcloud Quantum QPUs** is our managed solution for Jupyter and VS Code Notebooks designed to run jobs on a real Quantum Processing Unit. The notebook still works similarly to an OVHcloud Quantum Emulators notebook, but with a managed token to access a remote QPU. Additional fees will be calculated for the use of this QPU.
+
+## Objective
+
+This guide demonstrates how to create, configure, access, stop, restart, and delete a Quantum QPUs Notebook from the **OVHcloud Control Panel (UI)**. This method is user-friendly and ideal for beginners.
+
+Alternatively, you can use one of the following methods:
+
+- The **ovhai** command-line interface (CLI)
+- The **Quantum API**
+- The **ovhai** Python SDK
+
+Each method offers its distinct advantages, depending on your expertise and preferred workflow.
+
+## Requirements
+
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- Access to the [OVHcloud Control Panel](/links/manager).
+- A Public Cloud user with the **Administrator** or **Quantum Operator & Objectstore Operator** roles.
+
+## Instructions
+
+### OVHcloud Quantum Solutions authorization process
+
+If you're using the CLI, API, or SDK, you will need to complete an authorization process before creating a Quantum QPUs Notebook. To do so, follow these steps:
+
+1. Log in to the [OVHcloud Control Panel](/links/manager) and navigate to the `Public Cloud`{.action} section.
+2. Select the Public Cloud project you want to use and click the `Quantum QPUs`{.action} category.
+3. Click the `Create a Notebook`{.action} button. The authorization process will take place silently in the background.
+
+![Create a Notebook Control Panel manager 01](images/creating-a-notebook-using-UI-01.png){.thumbnail}
+
+### Launch your first Quantum Notebook
+
+To create a Quantum Notebook, follow these steps:
+
+> [!tabs]
+> **Using the Control Panel (UI)**
+>> 
+>> Navigate to the `Public Cloud`{.action} section of the [OVHcloud Control Panel](/links/manager) and click the `Quantum QPUs`{.action} category.
+>> Click the `Create a Notebook`{.action} button and follow the prompts to specify the configuration of your Quantum Notebook.
+>>
+>> ![Create a Notebook Control Panel manager 01](images/creating-a-notebook-using-UI-01.png){.thumbnail}
+>> 
+>> **1\. Notebook name**
+>> 
+>> Give a name to your notebook. This will make it easier to manage when you have multiple Quantum Notebooks created.
+>> 
+>> **2\. Notebook location**
+>> 
+>> Next, select a location.
+>> 
+>> ![Create a Notebook Control Panel manager 02](images/creating-a-notebook-using-UI-02.png){.thumbnail}
+>> 
+>> **3\. Compute resources**
+>> 
+>> Specify and adjust the type and amount of computing resources (CPU / GPU) for your Quantum Notebook. Use the `+`{.action} and `-`{.action} buttons to increase or decrease the number of CPUs and GPUs, depending on your needs.
+>> 
+>> Click `Next`{.action}.
+>> 
+>> ![Create a Notebook Control Panel manager 03](images/creating-a-notebook-using-UI-03.png){.thumbnail}
+>> 
+>> **4\. Pre-configured frameworks**
+>> 
+>> Choose the Quantum Python framework you want to use, which will be pre-installed and ready to use when your notebook is launched. Select the version that suits your needs. Then, click `Next`{.action} to continue.
+>> 
+>> ![Create a Notebook Control Panel manager 04](images/creating-a-notebook-using-UI-04.png){.thumbnail}
+>> 
+>> **5\. Live-code editor**
+>> 
+>> Choose the code editor you want.
+>> 
+>> ![Create a Notebook Control Panel manager 05](images/creating-a-notebook-using-UI-05.png){.thumbnail}
+>> 
+>> **6\. Privacy settings**
+>> 
+>> Then, select your privacy settings and click `Next`{.action}.
+>> 
+>> > [!warning]
+>> >
+>> > *Public access* will expose your data and code to anyone getting the Quantum Notebook link. Be careful not to use it with sensitive data. On the other hand, *Restricted access* will require a user and password combination or a Quantum token to access the Notebook content to ensure a secure environment.
+>> 
+>> ![Create a Notebook Control Panel manager 06](images/creating-a-notebook-using-UI-06.png){.thumbnail}
+>> 
+>> **7\. Advanced configuration**
+>> 
+>> By default, your Quantum Notebook comes with **ephemeral storage** (local storage). But in this step, you can also link Object Storage containers and Git repositories to your notebook to easily access your remote data.
+>> 
+>> If you want to learn more about configuring containers and Git repositories in the Notebook, you can refer to this [AI & Machine learning documentation](/pages/public_cloud/ai_machine_learning/notebook_guide_data_ui). For now, we will launch a classic Notebook without any external volumes added to it.
+>> 
+>> Click `Next`{.action}.
+>> 
+>> ![Create a Notebook Control Panel manager 07](images/creating-a-notebook-using-UI-07.png){.thumbnail}
+>> 
+>> **SSH public keys** allow you to access your Notebook remotely. This section is optional, click `Next`{.action}.
+>> 
+>> **9\. Launch the Quantum Notebook**
+>> 
+>> At the end of the process, review your settings and click the `Order now`{.action} button to confirm and launch the creation of your Notebook. You will be redirected to your notebook dashboard:
+>> 
+>> ![Create a Notebook Control Panel manager 10](images/creating-a-notebook-using-UI-08b.png){.thumbnail}
+>> 
+>> > [!primary]
+>> >
+>> > Note at the bottom of the screen the equivalent *ovhai* CLI command. This command allows you to run the exact same Notebook using the CLI.
+>> >
+>>
+>> When your Notebook is created, it will appear on your Quantum QPUs tab:
+>>
+>> ![Create a Notebook Control Panel manager 11](images/creating-a-notebook-using-UI-09.png){.thumbnail}
+>>
+> **Using ovhai CLI**
+>>
+>> If you prefer to use the command line interface to launch your Quantum Notebook, please follow these steps:
+>>
+>> 1. Follow this [AI & Machine learning](/pages/public_cloud/ai_machine_learning/cli_10_howto_install_cli) documentation to install the `ovhai` CLI and log in. 
+>> 2. Visit this second documentation to learn [how to create your Quantum Notebook using commands](/pages/public_cloud/ai_machine_learning/cli_11_howto_run_notebook_cli).
+>>
+>> ![Create a Notebook ovhai CLI](images/creating-a-notebook-using-ovhai-CLI.png){.thumbnail}
+>>
+> **Using the AI Solution API**
+>>
+>> 1. Create a bearer token from the *ovhai* CLI. For more detailed instructions on creating a token, check the [manage access tokens](/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli) documentation.
+>> 2. Navigate to the desired region and follow the instructions to create a Quantum Notebook.
+>>     - [GRA AI Solution API](https://gra.ai.cloud.ovh.net/#/), for Gravelines, France.
+>>     - [BHS AI Solution API](https://bhs.ai.cloud.ovh.net/#/), for Beauharnois, Canada.
+>> 3. `Submit a new notebook`{.action} POST method
+>>
+>> > [!warning]
+>> > 
+>> > Make sure to select `Bearer Auth` instead of `OAuth 2.0`, which is selected by default.
+>> >
+>>
+>> ![Create a Notebook API token authentication](images/creating-a-notebook-using-API-01.png){.thumbnail}
+>>
+> **Using the Python SDK**
+>>
+>> > [!warning]
+>> > 
+>> > **Alpha version warning**: This package is currently in the **alpha phase** of development. The APIs and functionalities of the package may not be fully tested.
+>>
+>> 1. Create a bearer token from the *ovhai* CLI. For more detailed instructions on creating a token, check the [manage access tokens](/pages/public_cloud/ai_machine_learning/cli_13_howto_app_token_cli) documentation.
+>> 2. Install the `ovhai` Python SDK and follow the instructions in the [ovhai PyPI](https://pypi.org/project/ovhai/) page to create a Quantum Notebook.
+>> 3. Finally, open your terminal and run `pip install ovhai`.
+>>
+>> Here is a basic example of how to do it, making it easy for you to get started:
+>>
+>> ```python
+>> from ovhai import AuthenticatedClient
+>> from ovhai.api.notebook import notebook_new
+>> from ovhai.models import NotebookSpec, Notebook
+>> from ovhai.ovhai_types import Response
+>>
+>> client = AuthenticatedClient(
+>>     base_url="https://bhs.ai.cloud.ovh.net",
+>>     token="YOUR_QUANTUM_TOKEN",
+>> )
+>> 
+>> # Define notebook parameters
+>> editor_id = "jupyterlab"
+>> framework_id = "pasqal-qpu"
+>> framework_version = "1.6.2-py312-cpu"
+>> framework_qpu_flavor_id = "orion-beta"
+>> nb_cpu = 1
+>> 
+>> # Create the notebook creation request
+>> notebook_specs = {
+>>     "env": {"editorId": editor_id, "frameworkId": framework_id, "frameworkVersion": framework_version},
+>>     "quantumResources": {"qpuFlavorId": framework_qpu_flavor_id},
+>>     "resources": {"cpu": nb_cpu},
+>> }
+>> 
+>> with client as client:
+>>     response: Response[Notebook] = notebook_new.sync_detailed(
+>>         client=client, body=NotebookSpec.from_dict(notebook_specs)
+>>     )
+>>     
+>>     import json
+>>     response_content = response.content.decode('utf-8')  # Decode bytes to a string
+>>     response_dict = json.loads(response_content)
+>>
+>>     status_code = response.status_code
+>>     id_ = response_dict['id']
+>>     spec = response_dict['spec']
+>>     status = response_dict['status']
+>>     state = status['state']
+>>     info = status['info']
+>>     url = response_dict['status']['url']
+>>
+>>     print(f"Status code: {status_code}")
+>>     print(f"ID: {id_}")
+>>     print(f"Spec: {spec}")
+>>     print(f"State: {state}")
+>>     print(f"Info: {info}")
+>>     print(f"URL: {url}")
+>> ```
+>>
+
+### Accessing your Quantum Notebook
+
+Once your Quantum Notebook is created and running, you can access it using the `JupyterLab` link in the Quantum Notebooks board or through the `ovhai` CLI, Quantum API, or Python SDK.
+
+> [!tabs]
+> **Using the Control Panel (UI)**
+>> 
+>> Click the `JupyterLab`{.action} link in the `Access` column:
+>> 
+>> ![Accessing a Notebook Control Panel manager 1](images/accessing-a-notebook-using-UI-1.png){.thumbnail}
+>> 
+>> You can also access the Notebook from its dedicated page:
+>> 
+>> ![Accessing a Notebook Control Panel manager 2](images/accessing-a-notebook-using-UI-2.png){.thumbnail}
+>> 
+>> On the Notebook page, you will find information about the Notebook, including specifications, billing, and attached data, as well as a monitoring URL for real-time metrics.
+>> 
+> **Using ovhai CLI**
+>>
+>> The `URL` of your Notebook should be displayed in your terminal and you can display it by running `ovhai notebook list` to retrieve the `URL`.
+>>
+>> ![Access a Notebook ovhai CLI](images/accessing-a-notebook-using-ovhai-CLI.png){.thumbnail}
+>>
+>> You can also get Notebook information using `ovhai notebook get <NOTEBOOK_UUID>`.
+>>
+> **Using the Quantum API**
+>>
+>> The `URL` of your Notebook should appear in the `Response` panel:
+>>
+>> ![Access a Notebook API](images/accessing-a-notebook-using-API.png){.thumbnail}
+>>
+>> If not, use the `Paginated list of notebooks`{.action} GET endpoint method:
+>>
+>> You can also get Notebook information using the `Get notebook information`{.action} GET endpoint method.
+>>
+> **Using the Python SDK**
+>>
+>> Run the following code to list all Quantum Notebooks:
+>>
+>> ```python
+>> from ovhai import AuthenticatedClient
+>> from ovhai.api.notebook import notebook_get_all
+>> from ovhai.models import NotebookList
+>> from ovhai.ovhai_types import Response
+>>
+>> from ovhai import AuthenticatedClient
+>>
+>> client = AuthenticatedClient(
+>>     base_url="https://bhs.ai.cloud.ovh.net",
+>>     token="YOUR_QUANTUM_TOKEN",
+>> )
+>>
+>> with client as client:
+>>     response: Response[NotebookList] = notebook_get_all.sync_detailed(client=client)
+>>     import json
+>>     response = json.loads(response.content.decode())
+>>     for notebook_info in response["items"]:
+>>         print(f"ID: {notebook_info['id']}")
+>>         print(f"Name: {notebook_info['spec']['name']}")
+>>         print(f"Status: {notebook_info['status']['state']}")
+>>         print(f"Framework: {notebook_info['spec']['env']['frameworkId']}")
+>>         print(f"Framework version: {notebook_info['spec']['env']['frameworkVersion']}")
+>>         print(f"Editor: {notebook_info['spec']['env']['editorId']}")
+>>         print(f"Access link: {notebook_info['status']['url']}")
+>>         print("---------------")
+>> ```
+>>
+>> You can also get Notebook information with this code sample:
+>>
+>> ```python
+>> from ovhai.api.notebook import notebook_get
+>> from ovhai import AuthenticatedClient
+>> import json
+>> 
+>> client = AuthenticatedClient(
+>>     base_url="https://bhs.ai.cloud.ovh.net",
+>>     token="YOUR_QUANTUM_TOKEN",
+>> )
+>> id = "YOUR_NOTEBOOK_UUID"
+>> 
+>> with client as client:
+>>     response = notebook_get.sync_detailed(
+>>         id=id, client=client
+>>     )
+>>
+>> print(json.loads(response.content.decode()))
+>> ```
+>>
+
+### Connecting to your Quantum Notebook
+
+To connect to your Quantum Notebook, you'll need to authenticate using a username and password combination or an access token.
+
+**Using a Username and Password**
+
+Enter your Public Cloud project user's credentials to log in to your Quantum Notebook.
+
+![Notebook Authentication Credentials](images/notebook-authentication-creds.png){.thumbnail}
+
+**Using an Access Token**
+
+Click the `Login with token` button and enter your access token to log in to your Quantum Notebook.
+
+![Notebook Authentication Token](images/notebook-authentication-token.png){.thumbnail}
+
+### Stopping a Quantum Notebook
+
+You can stop your Quantum Notebook at any time to release its compute resources. This will release its compute resources but will keep your Notebook data and installed libraries. Therefore, you will not incur any further charges for compute unless you restart the Notebook. However, attached storage will be billed at the price of OVHcloud Object Storage (consult the [Quantum Notebooks Billing documentation](/pages/public_cloud/quantum_computing/billing) for more information). To do so, follow these steps:
+
+> [!tabs]
+> **Using the Control Panel (UI)**
+>> 
+>> Go to the Quantum Notebooks board and click on the `...`{.action} button next to the Notebook you want to stop.
+>> Click the `Stop`{.action} button to stop the Notebook. Or, on the notebook board, you can click on the `red button`{.action} at the top of the page.
+>> 
+>> ![Stop a Notebook Control Panel manager](images/stopping-a-notebook-using-UI.png){.thumbnail}
+>> 
+> **Using ovhai CLI**
+>>
+>> Run the command `ovhai notebook stop <NOTEBOOK_UUID>` to stop the Notebook.
+>>
+>> If you do not know its UUID, remember that you can easily list all your existing Quantum Notebooks by running `ovhai notebook list`.
+>>
+> **Using the Quantum API**
+>>
+>> Select the `Stop a running notebook` endpoint and provide the UUID of the Notebook you want to stop.
+>>
+>> ![Stop a Notebook API](images/stopping-a-notebook-using-API.png){.thumbnail}
+>>
+> **Using the Python SDK**
+>>
+>> Use the `notebook_stop` method to stop the Notebook.
+>>
+>> ```python
+>> from ovhai.api.notebook import notebook_stop
+>> from ovhai import AuthenticatedClient
+>> client = AuthenticatedClient(
+>>     base_url="https://bhs.ai.cloud.ovh.net",
+>>     token="YOUR_QUANTUM_TOKEN",
+>> )
+>> id = "YOUR_NOTEBOOK_UUID"
+>> 
+>> with client as client:
+>>     response = notebook_stop.sync_detailed(client=client, id=id)
+>> ```
+>>
+
+### Restarting a stopped Notebook
+
+To restart a stopped Notebook, follow these steps:
+
+> [!tabs]
+> **Using the Control Panel (UI)**
+>> 
+>> Go to the Quantum Notebooks board and click on the `...`{.action} button next to the Notebook you want to restart.
+>> Click the `Start` button to restart the Notebook. Or, on the notebook board, you can click on the `blue button`{.action} at the top of the page.
+>> 
+>> ![Restart a Notebook Control Panel manager](images/restarting-a-notebook-using-UI.png){.thumbnail}
+>> 
+> **Using ovhai CLI**
+>>
+>> Run the command `ovhai notebook start <NOTEBOOK_UUID>` to restart the Notebook.
+>>
+> **Using the Quantum API**
+>>
+>> Select the `Start a stopped notebook` endpoint and provide the UUID of the Notebook you want to restart.
+>>
+>> ![Restart a Notebook API](images/restarting-a-notebook-using-API.png){.thumbnail}
+>>
+> **Using the Python SDK**
+>>
+>> Use the `notebook_start` method to restart the Notebook.
+>>
+>> ```python
+>> from ovhai.api.notebook import notebook_start
+>> from ovhai import AuthenticatedClient
+>> client = AuthenticatedClient(
+>>     base_url="https://gra.ai.cloud.ovh.net",
+>>     token="YOUR_QUANTUM_TOKEN",
+>> )
+>> id = "YOUR_NOTEBOOK_UUID"
+>>
+>> with client as client:
+>>     response = notebook_start.sync_detailed(
+>>         id=id, client=client
+>>     )
+>> ```
+>>
+
+### Deleting a Notebook
+
+The notebook must be stopped before deleting it. To delete a Notebook, follow these steps:
+
+> [!tabs]
+> **Using the Control Panel (UI)**
+>> 
+>> Go to the Quantum Notebooks board and click on the `...`{.action} button next to the Notebook you want to delete.
+>> Click the `Delete`{.action} button to stop the Notebook. Or, on the notebook board, you can click on the `Delete notebook`{.action} button at the bottom of the page.
+>> 
+>> ![Delete a Notebook Control Panel manager](images/deleting-a-notebook-using-UI.png){.thumbnail}
+>> 
+> **Using ovhai CLI**
+>>
+>> Run the command `ovhai notebook delete <NOTEBOOK_UUID>` to delete the Notebook.
+>>
+> **Using the Quantum API**
+>>
+>> Select the `Delete permanently a notebook` endpoint and provide the UUID of the Notebook you want to delete.
+>>
+>> ![Delete a Notebook API](images/deleting-a-notebook-using-API.png){.thumbnail}
+>>
+> **Using the Python SDK**
+>>
+>> Use the `notebook_delete` method to delete the Notebook.
+>> ```python
+>> from ovhai.api.notebook import notebook_delete
+>> from ovhai import AuthenticatedClient
+>>
+>> client = AuthenticatedClient(
+>>     base_url="https://gra.ai.cloud.ovh.net",
+>>     token="YOUR_QUANTUM_TOKEN",
+>> )
+>> id = "YOUR_NOTEBOOK_UUID"
+>>
+>> with client as client:
+>>     response = notebook_delete.sync_detailed(
+>>         id=id, client=client, force=False
+>>     )
+>>
+>>     print(response.content.decode())
+>> ```
+>>
+
+## Go further
+
+- Discover how to access your Object Storage data and Git repositories from your Notebooks using the UI [here](/pages/public_cloud/ai_machine_learning/notebook_guide_data_ui).
+- Learn about the technical features, capabilities, and limitations of the Public Cloud Quantum Notebooks offering [here](/pages/public_cloud/quantum_computing/capabilities).
+- Get some hints on how to debug your Notebooks if things go wrong [here](/pages/public_cloud/quantum_computing/troubleshooting).
+
+If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
+
+## Feedback
+
+We would love to help answer questions and appreciate any feedback you may have.
+
+Please send us your questions, feedback, and suggestions regarding Quantum Notebooks:
+
+- In the #quantum-computing channel of the OVHcloud [Discord server](https://discord.gg/ovhcloud).
\ No newline at end of file
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-API.png
new file mode 100644
index 00000000000..7fb4d6a5f60
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-API.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-UI-1.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-UI-1.png
new file mode 100644
index 00000000000..022f75d14df
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-UI-1.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-UI-2.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-UI-2.png
new file mode 100644
index 00000000000..d5a2400826b
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-UI-2.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-ovhai-CLI.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-ovhai-CLI.png
new file mode 100644
index 00000000000..8a964468d20
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/accessing-a-notebook-using-ovhai-CLI.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-API-01.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-API-01.png
new file mode 100644
index 00000000000..a3def52a665
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-API-01.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-01 copy.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-01 copy.png
new file mode 100644
index 00000000000..c06eba61a67
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-01 copy.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-01.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-01.png
new file mode 100644
index 00000000000..c06eba61a67
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-01.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-02.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-02.png
new file mode 100644
index 00000000000..0db2843358b
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-02.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-03.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-03.png
new file mode 100644
index 00000000000..f516f2a0a84
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-03.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-04.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-04.png
new file mode 100644
index 00000000000..f7c0878b6d5
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-04.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-05.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-05.png
new file mode 100644
index 00000000000..69f1c544721
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-05.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-06.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-06.png
new file mode 100644
index 00000000000..97578660661
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-06.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-07.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-07.png
new file mode 100644
index 00000000000..7be561f49b1
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-07.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-08b.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-08b.png
new file mode 100644
index 00000000000..34a27f04519
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-08b.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-09.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-09.png
new file mode 100644
index 00000000000..03f1607a88d
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-UI-09.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-ovhai-CLI.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-ovhai-CLI.png
new file mode 100644
index 00000000000..49d878e33c9
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/creating-a-notebook-using-ovhai-CLI.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/deleting-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/deleting-a-notebook-using-API.png
new file mode 100644
index 00000000000..ad8fb1e3fd8
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/deleting-a-notebook-using-API.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/deleting-a-notebook-using-UI.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/deleting-a-notebook-using-UI.png
new file mode 100644
index 00000000000..fb3ed9494fe
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/deleting-a-notebook-using-UI.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-creds copy.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-creds copy.png
new file mode 100644
index 00000000000..444a85c581f
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-creds copy.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-creds.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-creds.png
new file mode 100644
index 00000000000..444a85c581f
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-creds.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-token copy.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-token copy.png
new file mode 100644
index 00000000000..a18445fdc9c
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-token copy.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-token.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-token.png
new file mode 100644
index 00000000000..a18445fdc9c
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/notebook-authentication-token.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/restarting-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/restarting-a-notebook-using-API.png
new file mode 100644
index 00000000000..4bf8f2ed2df
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/restarting-a-notebook-using-API.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/restarting-a-notebook-using-UI.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/restarting-a-notebook-using-UI.png
new file mode 100644
index 00000000000..68b72895ab2
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/restarting-a-notebook-using-UI.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/stopping-a-notebook-using-API.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/stopping-a-notebook-using-API.png
new file mode 100644
index 00000000000..89d70d8a7af
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/stopping-a-notebook-using-API.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/images/stopping-a-notebook-using-UI.png b/pages/public_cloud/quantum_computing/qpus/getting-started/images/stopping-a-notebook-using-UI.png
new file mode 100644
index 00000000000..0d4a61abb07
Binary files /dev/null and b/pages/public_cloud/quantum_computing/qpus/getting-started/images/stopping-a-notebook-using-UI.png differ
diff --git a/pages/public_cloud/quantum_computing/qpus/getting-started/meta.yaml b/pages/public_cloud/quantum_computing/qpus/getting-started/meta.yaml
new file mode 100755
index 00000000000..f862ec176db
--- /dev/null
+++ b/pages/public_cloud/quantum_computing/qpus/getting-started/meta.yaml
@@ -0,0 +1,2 @@
+id: 652470cf-23b5-46b0-a22d-23036ab087cd
+full_slug: public-cloud-quantum-computing-emulator-getting-started
\ No newline at end of file
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_android/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_android/guide.fr-fr.md
index ee0e410e963..9d6fa82d4f0 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_android/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_android/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les adresses e-mail de l'offre E-mail Pro peuvent être configurées sur différ
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_ios/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_ios/guide.fr-fr.md
index cf1f96b278d..147e6179a55 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_ios/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_ios/guide.fr-fr.md
@@ -14,7 +14,7 @@ Les comptes E-mail Pro peuvent être configurés sur différents logiciels de me
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons ce guide à votre disposition afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons ce guide à votre disposition afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 >
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_mail_macos/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_mail_macos/guide.fr-fr.md
index f7b68773a56..59e596bc3fb 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_mail_macos/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_mail_macos/guide.fr-fr.md
@@ -14,7 +14,7 @@ Les comptes E-mail Pro peuvent être configurés sur différents logiciels de me
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 >
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_2016/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_2016/guide.fr-fr.md
index 4c070f6ce1a..c2d0a332b7f 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_2016/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_2016/guide.fr-fr.md
@@ -14,7 +14,7 @@ Les comptes E-mail Pro peuvent être configurés sur différents logiciels de me
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 > 
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 > 
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_2016_mac/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_2016_mac/guide.fr-fr.md
index f1d66195529..be247b6550d 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_2016_mac/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_2016_mac/guide.fr-fr.md
@@ -14,7 +14,7 @@ Les comptes E-mail Pro peuvent être configurés sur différents logiciels de me
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 > 
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 > 
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_android/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_android/guide.fr-fr.md
index 3eec7fda702..526d1f5a77e 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_android/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_outlook_android/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes E-mail Pro peuvent être configurés sur différents logiciels de me
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.es-es.md
index 31df3dcd2e6..c84c9c0e997 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.es-es.md
@@ -43,7 +43,7 @@ El **nuevo Outlook** reemplaza desde el 1 de enero de 2025 la aplicación **Corr
 
 OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen en usted. Por lo tanto, es su responsabilidad asegurar su correcto funcionamiento.
 
-Le proporcionamos esta guía para acompañarlo en las tareas más comunes. Sin embargo, le recomendamos contactar a un [socio especializado](https://marketplace.ovhcloud.com/c/support-collaboration) y/o al proveedor del servicio si encuentra dificultades. Tenga en cuenta que no podremos proporcionar asistencia. Para obtener más información, consulte la sección "[Más información](#go-further)" de esta guía.
+Le proporcionamos esta guía para acompañarlo en las tareas más comunes. Sin embargo, le recomendamos contactar a un [socio especializado](/links/partner) y/o al proveedor del servicio si encuentra dificultades. Tenga en cuenta que no podremos proporcionar asistencia. Para obtener más información, consulte la sección "[Más información](#go-further)" de esta guía.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.fr-fr.md
index d1396e90fc9..31dd0021a84 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.fr-fr.md
@@ -43,7 +43,7 @@ Le **nouvel Outlook** remplace depuis le 1 janvier 2025 l'application **Courrier
 
 OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 
-Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « [Aller plus loin](go-further) » de ce guide.
+Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « [Aller plus loin](go-further) » de ce guide.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.it-it.md
index 168ad4b7206..a8f6a7e4df0 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.it-it.md
@@ -43,7 +43,7 @@ Il **nuovo Outlook** sostituisce, dal 1° gennaio 2025, l'applicazione **Posta**
 
 OVHcloud mette a tua disposizione servizi di cui sei responsabile per la configurazione, gestione e funzionamento. Pertanto, spetta a te assicurarsi che funzionino correttamente.
 
-Ti forniamo questa guida per aiutarti nelle operazioni più comuni. Tuttavia, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) e/o l'editore del servizio se incontri difficoltà. Non saremo in grado di fornirti assistenza. Ulteriori informazioni nella sezione "[Per saperne di più](#go-further)" di questa guida.
+Ti forniamo questa guida per aiutarti nelle operazioni più comuni. Tuttavia, ti consigliamo di contattare un [partner specializzato](/links/partner) e/o l'editore del servizio se incontri difficoltà. Non saremo in grado di fornirti assistenza. Ulteriori informazioni nella sezione "[Per saperne di più](#go-further)" di questa guida.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.pl-pl.md
index 88f76b89525..77fd0542927 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.pl-pl.md
@@ -43,7 +43,7 @@ Adresy e-mail w ramach oferty [E-Mail Pro](/links/web/email-pro) mogą być konf
 
 OVHcloud udostępnia usługi, za których konfigurację, zarządzanie i działanie jesteś odpowiedzialny. Należy do Ciebie zapewnić ich poprawne funkcjonowanie.
 
-Zapewniamy tę dokumentację, aby ułatwić Ci wykonywanie typowych zadań. W przypadku problemów zalecam skontaktowanie się z [specjalistycznym partnerem](https://marketplace.ovhcloud.com/c/support-collaboration) lub producentem usługi. Nie będziemy mogli udzielić dalszej pomocy. Więcej informacji w sekcji "[Sprawdź również](#go-further)" niniejszej dokumentacji.
+Zapewniamy tę dokumentację, aby ułatwić Ci wykonywanie typowych zadań. W przypadku problemów zalecam skontaktowanie się z [specjalistycznym partnerem](/links/partner) lub producentem usługi. Nie będziemy mogli udzielić dalszej pomocy. Więcej informacji w sekcji "[Sprawdź również](#go-further)" niniejszej dokumentacji.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.pt-pt.md
index 24011aa2d6a..44f39941e30 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/email_pro/how_to_configure_windows_10/guide.pt-pt.md
@@ -43,7 +43,7 @@ O **novo Outlook** substitui, a partir de 1 de janeiro de 2025, o aplicativo **E
 
 A OVHcloud fornece serviços que você é responsável por configurar, gerenciar e operar. Portanto, cabe a você garantir seu funcionamento adequado.
 
-Fornecemos este guia para ajudá-lo nas tarefas mais comuns. No entanto, recomendamos contatar um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou o fornecedor do serviço se encontrar dificuldades. Não estaremos aptos a fornecer assistência adicional. Mais informações na seção "[Quer saber mais?](#go-further)" deste guia.
+Fornecemos este guia para ajudá-lo nas tarefas mais comuns. No entanto, recomendamos contatar um [parceiro especializado](/links/partner) e/ou o fornecedor do serviço se encontrar dificuldades. Não estaremos aptos a fornecer assistência adicional. Mais informações na seção "[Quer saber mais?](#go-further)" deste guia.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_android/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_android/guide.fr-fr.md
index 14204d76b0c..4b82fe4f6c0 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_android/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_android/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les adresses e-mail de l'offre Exchange peuvent être configurées sur différen
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_ios/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_ios/guide.fr-fr.md
index 333fb57996e..30e64c67aad 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_ios/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_ios/guide.fr-fr.md
@@ -14,7 +14,7 @@ Les comptes Exchange peuvent être configurés sur différents logiciels de mess
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons ce guide à votre disposition afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons ce guide à votre disposition afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 >
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_mail_macos/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_mail_macos/guide.fr-fr.md
index 506695dd080..4b0950fe913 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_mail_macos/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_mail_macos/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes Exchange peuvent être configurés sur différents logiciels de mess
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 >
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_outlook_2016/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_outlook_2016/guide.fr-fr.md
index 22cf961a855..ab9f814542c 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_outlook_2016/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_outlook_2016/guide.fr-fr.md
@@ -14,7 +14,7 @@ Les comptes Exchange peuvent être configurés sur différents logiciels de mess
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 <iframe class="video" width="560" height="315" src="https://www.youtube-nocookie.com/embed/zx7LAzmDrFw?si=DAWV56-E1or1Vgnr" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_outlook_2016_mac/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_outlook_2016_mac/guide.fr-fr.md
index 756d3d5ad50..0e531c0031e 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_outlook_2016_mac/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_outlook_2016_mac/guide.fr-fr.md
@@ -12,7 +12,7 @@ Les comptes Exchange peuvent être configurés sur différents logiciels de mess
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 > 
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 > 
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_windows_10/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_windows_10/guide.fr-fr.md
index 36cb17ce697..657cc2366b0 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_windows_10/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/how_to_configure_windows_10/guide.fr-fr.md
@@ -14,7 +14,7 @@ Les comptes Exchange peuvent être configurés sur différents logiciels de mess
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 > 
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 > 
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/microsoft_office/office_proplus/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/microsoft_office/office_proplus/guide.fr-fr.md
index c8d9462540f..82ffcae5138 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/microsoft_office/office_proplus/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/microsoft_office/office_proplus/guide.fr-fr.md
@@ -28,7 +28,7 @@ Ce guide est basé sur les informations délivrées dans le guide Microsoft [Dé
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 > 
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 > 
 
 ### Méthode 1: Configuration manuelle
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration/guide.fr-fr.md
index 7b39dce4a25..9c1826e2181 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration/guide.fr-fr.md
@@ -14,7 +14,7 @@ updated: 2025-04-28
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Retrouvez plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Retrouvez plus d'informations dans la section « Aller plus loin » de ce guide.
 >
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.de-de.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.de-de.md
deleted file mode 100644
index 9703224f95c..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.de-de.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: 'Einen Gmail-Account mit dem OVH Mail Migrator auf einen OVHcloud E-Mail-Account migrieren'
-excerpt: 'In dieser Anleitung erfahren Sie, wie Sie Ihre Gmail-Accounts mit dem OVH Mail Migrator zu OVHcloud migrieren'
-updated: 2020-03-09
----
-
-## Ziel
-
-Der [OVH Mail Migrator](https://omm.ovh.net) (OMM) wurde von OVHcloud entwickelt. Mit diesem Online-Interface können Sie Ihre E-Mail-Konten von einem Host auf einen anderen migrieren. Dabei können verschiedene Inhalte wie beispielsweise E-Mails, Kontakte, Kalender und Aufgaben übertragen werden, sofern diese mit Ihren OVHcloud E-Mail-Konten kompatibel sind.
-
-In dieser Anleitung wird beschrieben, wie Sie mit OMM die verschiedenen Elemente aus Ihrem Google Mail-Account in Ihr OVHcloud E-Mail-Konto importieren.
-
-**Erfahren Sie, wie Sie Ihren Google Mail-Account mithilfe unseres OMM-Tools auf ein E-Mail-Konto bei OVHcloud migrieren.**
-
-## Voraussetzungen
-
-- Sie haben einen E-Mail-Dienst bei OVHcloud ([Exchange](/links/web/emails-hosted-exchange), [E-Mail Pro](/links/web/email-pro) oder MX Plan, aus dem MX Plan Angebot oder als Teil eines [OVHcloud Webhostings](/links/web/hosting)).
-- Sie verfügen über die Login-Daten für die E-Mail-Accounts, die Sie migrieren möchten (Quell-Accounts).
-- Sie verfügen über die Login-Daten der OVHcloud E-Mail-Accounts, auf die Sie die Inhalte übertragen möchten (Ziel-Accounts).
-
-## In der praktischen Anwendung
-
-### Schritt 1: E-Mail- und Ordnermigration
-
-> [!primary]
-> Damit eine Migration möglich ist, müssen Sie das IMAP-Protokoll in Ihrem Google Mail-Account aktivieren. Folgen Sie dazu der Google-Anleitung
-> [Gmail-Nachrichten über andere E-Mail-Clients empfangen](https://support.google.com/mail/answer/7126229?hl=de).
-
-Sobald das IMAP-Protokoll in Ihrem Google Mail-Account aktiviert ist, gehen Sie auf [OMM](https://omm.ovh.net).
-
-Klicken Sie auf `Migration`{.action} und dann auf `Neue Migration`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-Das folgende Fenster wird angezeigt:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Füllen Sie die erforderlichen Felder aus, wie in den beiden folgenden Tabellen angegeben:
-
-**Quellkonto**
-
-| Information            	| Beschreibung                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Server-Typ         	| Wählen Sie **„IMAP“**  im Dropdown-Menü.         									|
-| Server-URL          	| Geben Sie **„imap.gmail.com“** ein.                       					 			  	|
-| Login						| Geben Sie Ihre Gmail-Adresse an.															|
-| Passwort				| Geben Sie das Passwort Ihrer Gmail-Adresse ein.										|
-
-**Ziel-Konto**
-
-| Information            	| Beschreibung                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Server-Typ         	| Wählen Sie im Dropdown-Menü die Option **„Hosted by OVH (Autodetect)“**.   											|
-| Server-URL          	| Das Feld wird automatisch ausgefüllt.                     					  		 							|
-| Login						| Geben Sie Ihre OVHcloud E-Mail-Adresse ein.																			|
-| Passwort				| Klicken Sie auf `Einstellungen erkennen`{.action} und geben Sie das Passwort für Ihre OVHcloud E-Mail-Adresse ein.	|
-
-Aktivieren Sie im Abschnitt **„Optionen“** nur **„E-Mails“**. Die anderen Optionen sind in IMAP nicht verfügbar. Die Migration von Kontakten und Kalendern erfolgt in den Schritten 2 und 3.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-Im Feld **„Informationen“** können Sie eine E-Mail-Adresse eingeben, unter der Sie über den Fortschritt der Migration informiert werden. Dieses Feld ist optional. Klicken Sie dann auf `Migration starten`{.action}
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-Das Migrationsverfolgungsfenster wird angezeigt. Sie können es offen lassen, um die Live-Migration zu verfolgen, oder es schließen. Das hat keine Auswirkungen auf die Migration.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> Beim Starten der Migration wird möglicherweise die folgende Meldung angezeigt:
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-In diesem Fall rufen Sie den Posteingang Ihres Google Mail-Accounts auf und überprüfen Sie, ob Sie eine E-Mail mit Betreff in einer Variante von **„Kritische Sicherheitswarnung“** erhalten haben. Hier greift eine von Google Mail durchgeführte Sicherheitsmaßnahme. Um diesen Zustand zu beheben, folgen Sie unserer Anleitung [Weniger sichere Verbindungen in Google Mail zulassen](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm).
-
-Nachdem Sie in Google Mail **„weniger sichere Apps“ zugelassen** haben, können Sie die Migration neu starten.
-
-### Schritt 2: Kalendermigration
-
-#### 2.1 Ein Kalender-Backup in Google Mail wieder herstellen
-
-Um Ihren Kalender in Ihren OVHcloud-Account zu importieren, erstellen Sie ein Backup von Ihrer Google Mail-Oberfläche aus. Folgen Sie dazu der offiziellen Google-Dokumentation:
-
-[Google-Kalender exportieren](https://support.google.com/calendar/answer/37111?hl=de)
-
-Wenn Ihr Google Mail-Account mehrere Kalender enthält, laden Sie dabei eine Archivdatei zum Entpacken herunter. Sie finden jeden Kalender im Format **.ics**.
-
-#### 2.2 Ihren Kalender über OMM importieren
-
-> [!primary]
-> Die Kalendermigration von OMM ist nur mit Exchange Accounts kompatibel.
-
-Nachdem Sie das Backup Ihres Kalenders im Format **.ics** wiederhergestellt haben, gehen Sie auf [OMM](https://omm.ovh.net).
-
-Gehen Sie oben auf die Registerkarte `PST/ICS/VCF-MIGRATION`{.action} und klicken Sie dann auf `Neue PST/ICS/VCF-Migration`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Füllen Sie die angeforderten Felder gemäß der folgenden Tabelle aus und klicken Sie auf `Migration starten`{.action}:
-
-| Information            	| Beschreibung                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Geben Sie die OVHcloud E-Mail-Adresse ein, zu der Sie Ihren Kalender migrieren.           	|
-| Passwort           	| Geben Sie das Passwort für die Ziel-E-Mail-Adresse ein.                          	|
-| Kontakt-E-Mail 	| Geben Sie eine E-Mail-Adresse ein, über die Sie über den Fortschritt der Migration informiert werden und den Download einer Datei fortsetzen können.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Klicken Sie auf `Datei auswählen`{.action}, um die Kalender-Datei im Format **.ics** auf Ihrem Gerät zu selektieren, und klicken Sie dann auf `Hochladen`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Geben Sie dann das Passwort für Ihr Ziel-E-Mail-Konto ein und klicken Sie auf `Migration starten`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-Das Migrationsverfolgungsfenster (unten) wird angezeigt. Sie können es offen lassen, um die Live-Migration zu verfolgen, oder es schließen. Das hat keine Auswirkungen auf die Migration.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Schritt 3: Kontaktmigration
-
-> [!primary]
-> Die Kontaktmigration von OMM ist nur mit Exchange Accounts kompatibel.
-
-Um Ihre Kontakte in Ihren OVHcloud E-Mail-Account zu importieren, sichern Sie sie über Ihre Google Mail-Oberfläche. Folgen Sie dazu der offiziellen Google-Dokumentation:
-
-[Kontakte exportieren oder sichern](https://support.google.com/contacts/answer/7199294?hl=de)
-
-> [!warning]
-> Der Export muss im vCard-Format (**.vcf**) über die Google Mail-Oberfläche erfolgen. Diese Option wird Ihnen am Ende des Exports angeboten.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Füllen Sie die angeforderten Felder gemäß der folgenden Tabelle aus und klicken Sie auf `Migration starten`{.action}:
-
-| Information            	| Beschreibung                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Geben Sie die OVHcloud E-Mail-Adresse ein, zu der Sie Ihre Kontakte migrieren.            	|
-| Passwort           	| Geben Sie das Passwort für die Ziel-E-Mail-Adresse ein.                          	|
-| Kontakt-E-Mail 	| Geben Sie eine E-Mail-Adresse ein, über die Sie über den Fortschritt der Migration informiert werden und den Download einer Datei fortsetzen können.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Klicken Sie auf `Datei auswählen`{.action}, um die Kontakte-Datei mit Endung **.vcf** auf Ihrem Gerät zu selektieren, und klicken Sie dann auf `Hochladen`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Geben Sie das Passwort für Ihr Ziel-E-Mail-Konto ein und klicken Sie auf `Migration starten`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-Das Migrationsüberwachungsfenster wird angezeigt. Sie können es geöffnet lassen, um die Live-Migration zu verfolgen oder es schließen. Das hat keine Auswirkungen auf die Migration.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Weiterführende Informationen
-
-[Weniger sichere Verbindungen in Google Mail zulassen](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm).
-
-Treten Sie unserer [User Community](/links/community) bei.
\ No newline at end of file
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.en-ca.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.en-ca.md
deleted file mode 100644
index 4dd83318d27..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.en-ca.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: 'Migrating a Gmail account to an OVHcloud email account via the OVH Mail Migrator'
-excerpt: 'Find out how to migrate your Gmail accounts to OVHcloud using our OVH Mail Migrator tool'
-updated: 2020-03-09
----
-
-## Objective
-
-The [OVH Mail Migrator](https://omm.ovh.net/) is a tool created by OVHcloud. You can use it to migrate email accounts from one hosting provider to another. The process covers different types of content, such as emails, contacts, calendars and tasks, provided that they are compatible with your OVHcloud email accounts. 
-
-This guide describes how to use OMM to import various elements of your Gmail account to your OVHcloud account.
-
-**Find out how to migrate your Gmail account to OVHcloud using our OMM tool<b>.</b>**
-
-## Requirements
-
-- an email service with OVHcloud, e.g. [Exchange](/links/web/emails-hosted-exchange) or MX Plan (via the MX Plan standalone tool or included in an [OVHcloud web hosting](/links/web/hosting) plan)
-- access to the email accounts you want to migrate (the source accounts)
-- access to the OVHcloud email accounts that will be receiving the migrated data (the target accounts)
-
-## Instructions
-
-### Step 1: Migrate emails and folders.
-
-> [!primary]
-> For the migration to work, you will need to turn on IMAP protocol for your Gmail account. To this, follow the Google guide on
-> [how to turn on IMAP for your Gmail account](https://support.google.com/mail/answer/7126229?hl=en).
-
-Once you have turned on IMAP for your Gmail account, go to the [OMM](https://omm.ovh.net/) tool.
-
-Click `Migration`{.action}, then `New migration`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-The following window will pop up:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Fill in the mandatory fields depending on the indications of the two tables below:
-
-**Source Account**
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Server type         	| Select **IMAP** in the dropdown menu.         									|
-| Server URL          	| Enter **imap.gmail.com**.                       					 			  	|
-| Login						| Enter your Gmail address.															|
-| Password				| Enter the password for your Gmail address.										|
-
-**Target account**
-
-| Information            	| Description                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Server type         	| Select **Hosted by OVH (Autodetect)** in the dropdown menu.   											|
-| Server URL          	| The field will be auto-filled.                     					  		 							|
-| Login						| Enter your OVHcloud email address.																			|
-| Password				| Click `detect settings`{.action}, then enter the password of your OVHcloud email address.	|
-
-In the **Options** section, only tick **Mails**, as the other options will not be available in IMAP. Contacts and calendars will be migrated in steps 2 and 3.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-In the **Information** box, you can enter an email address that will be used to notify you regarding the migration’s progress. This field is optional. Next, click `Launch the migration`{.action}.
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-The migration tracking window (below) will then appear. You can leave it open to track the migration in real time, or you can close it — closing the window will not affect the migration process.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> When the migration is launched, you may see the message below:
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-If it appears, go to your Gmail account mailbox and check if you have received an email with the subject **“Critical security alert”**. This is a security measure put in place by Gmail. To resolve this situation, follow our guide on [authorising less secure connections on Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
-
-After you have **authorised less secure connections** on Gmail, you will need to relaunch the migration.
-
-### Step 2: Migrate calendars.
-
-#### 2.1: Retrieve a calendar backup on Gmail.
-
-To import your calendar to your OVHcloud account, you will need to retrieve a backup of the calendar via the Gmail interface. To do this, follow the Google guide:
-
-[How to export your calendars for your Gmail account](https://support.google.com/calendar/answer/37111?hl=en)
-
-If you have several calendars on your Gmail account, you will download an archive folder, which you then need to decompress. Each calendar will be exported in **.ics** format.
-
-#### 2.2: Import your calendar via OMM.
-
-> [!primary]
-> Calendar migration via OMM is only compatible with Exchange target accounts.
-
-Once you have retrieved the backup of your calendar in **.ics** format, go to [OMM](https://omm.ovh.net/).
-
-Click on the `PST/ICS/VCF`{.action} tab at the top, then click `New PST/ICS/VCF migration`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Fill in the fields in the following table, then click `Launch migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Enter the OVHcloud email address you would like to migrate your calendar to.           	|
-| Password           	| Enter the password for your target email address.                          	|
-| Communication email 	| Enter the email address you want to use for receiving updates on the migration progress, and for resuming file downloads.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Click `Choose a file`{.action} to retrieve the **.ics** calendar file on your PC, then click `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Then enter the password for your target account, and click `Launch migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-The migration tracking window (below) will then appear. You can leave it open to track the migration in real time, or you can close it — closing the window will not affect the migration process.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Step 3: Migrate your contacts.
-
-> [!primary]
-> Contact migration via OMM is only compatible with Exchange target accounts.
-
-To import your contacts to your OVHcloud account, you will need to retrieve a backup of the contacts via the Gmail interface. To do this, follow the Google guide:
-
-[How to export or back up contacts for your Gmail account](https://support.google.com/contacts/answer/7199294?hl=en)
-
-> [!warning]
-> The export must be taken in vCard (**.vcf**) format via the Gmail interface. This option is offered at the end of the export process.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Fill in the fields in the following table, then click `Launch migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Enter the OVHcloud email address you would like to migrate your contacts to.            	|
-| Password           	| Enter the password for your target email address.                          	|
-| Communication email 	| Enter the email address you want to use for receiving updates on the migration progress, and for resuming file downloads.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Click `Choose a file`{.action} to retrieve the **.vcf** contact file on your PC, then click `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Then enter the password for your target account, and click `Launch migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-The migration tracking window will then open. You can leave it open to track the migration in real time, or you can close it — closing the window will not affect the migration process.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Go further
-
-[Authorising less secure connections on Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
-
-Join our [community of users](/links/community).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.en-gb.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.en-gb.md
deleted file mode 100644
index 67284058226..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.en-gb.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: 'Migrating a Gmail account to an OVHcloud email account via the OVH Mail Migrator'
-excerpt: 'Find out how to migrate your Gmail accounts to OVHcloud using our OVH Mail Migrator tool'
-updated: 2020-03-09
----
-
-## Objective
-
-The [OVH Mail Migrator](https://omm.ovh.net/) is a tool created by OVHcloud. You can use it to migrate email accounts from one hosting provider to another. The process covers different types of content, such as emails, contacts, calendars and tasks, provided that they are compatible with your OVHcloud email accounts. 
-
-This guide describes how to use OMM to import various elements of your Gmail account to your OVHcloud account.
-
-**Find out how to migrate your Gmail account to OVHcloud using our OMM tool<b>.</b>**
-
-## Requirements
-
-- an email service with OVHcloud, e.g. [Exchange](/links/web/emails), [Email Pro](/links/web/email-pro) or MX Plan (via the MX Plan standalone tool or included in an [OVHcloud web hosting](/links/web/hosting) plan)
-- access to the email accounts you want to migrate (the source accounts)
-- access to the OVHcloud email accounts that will be receiving the migrated data (the target accounts)
-
-## Instructions
-
-### Step 1: Migrate emails and folders.
-
-> [!primary]
-> For the migration to work, you will need to turn on IMAP protocol for your Gmail account. To this, follow the Google guide on
-> [how to turn on IMAP for your Gmail account](https://support.google.com/mail/answer/7126229?hl=en).
-
-Once you have turned on IMAP for your Gmail account, go to the [OMM](https://omm.ovh.net/) tool.
-
-Click `Migration`{.action}, then `New migration`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-The following window will pop up:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Fill in the mandatory fields depending on the indications of the two tables below:
-
-**Source Account**
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Server type         	| Select **IMAP** in the dropdown menu.         									|
-| Server URL          	| Enter **imap.gmail.com**.                       					 			  	|
-| Login						| Enter your Gmail address.															|
-| Password				| Enter the password for your Gmail address.										|
-
-**Target account**
-
-| Information            	| Description                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Server type         	| Select **Hosted by OVH (Autodetect)** in the dropdown menu.   											|
-| Server URL          	| The field will be auto-filled.                     					  		 							|
-| Login						| Enter your OVHcloud email address.																			|
-| Password				| Click `detect settings`{.action}, then enter the password of your OVHcloud email address.	|
-
-In the **Options** section, only tick **Mails**, as the other options will not be available in IMAP. Contacts and calendars will be migrated in steps 2 and 3.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-In the **Information** box, you can enter an email address that will be used to notify you regarding the migration’s progress. This field is optional. Next, click `Launch the migration`{.action}.
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-The migration tracking window (below) will then appear. You can leave it open to track the migration in real time, or you can close it — closing the window will not affect the migration process.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> When the migration is launched, you may see the message below:
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-If it appears, go to your Gmail account mailbox and check if you have received an email with the subject **“Critical security alert”**. This is a security measure put in place by Gmail. To resolve this situation, follow our guide on [authorising less secure connections on Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
-
-After you have **authorised less secure connections** on Gmail, you will need to relaunch the migration.
-
-### Step 2: Migrate calendars.
-
-#### 2.1: Retrieve a calendar backup on Gmail.
-
-To import your calendar to your OVHcloud account, you will need to retrieve a backup of the calendar via the Gmail interface. To do this, follow the Google guide:
-
-[How to export your calendars for your Gmail account](https://support.google.com/calendar/answer/37111?hl=en)
-
-If you have several calendars on your Gmail account, you will download an archive folder, which you then need to decompress. Each calendar will be exported in **.ics** format.
-
-#### 2.2: Import your calendar via OMM.
-
-> [!primary]
-> Calendar migration via OMM is only compatible with Exchange target accounts.
-
-Once you have retrieved the backup of your calendar in **.ics** format, go to [OMM](https://omm.ovh.net/).
-
-Click on the `PST/ICS/VCF`{.action} tab at the top, then click `New PST/ICS/VCF migration`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Fill in the fields in the following table, then click `Launch migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Enter the OVHcloud email address you would like to migrate your calendar to.           	|
-| Password           	| Enter the password for your target email address.                          	|
-| Communication email 	| Enter the email address you want to use for receiving updates on the migration progress, and for resuming file downloads.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Click `Choose a file`{.action} to retrieve the **.ics** calendar file on your PC, then click `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Then enter the password for your target account, and click `Launch migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-The migration tracking window (below) will then appear. You can leave it open to track the migration in real time, or you can close it — closing the window will not affect the migration process.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Step 3: Migrate your contacts.
-
-> [!primary]
-> Contact migration via OMM is only compatible with Exchange target accounts.
-
-To import your contacts to your OVHcloud account, you will need to retrieve a backup of the contacts via the Gmail interface. To do this, follow the Google guide:
-
-[How to export or back up contacts for your Gmail account](https://support.google.com/contacts/answer/7199294?hl=en)
-
-> [!warning]
-> The export must be taken in vCard (**.vcf**) format via the Gmail interface. This option is offered at the end of the export process.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Fill in the fields in the following table, then click `Launch migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Enter the OVHcloud email address you would like to migrate your contacts to.            	|
-| Password           	| Enter the password for your target email address.                          	|
-| Communication email 	| Enter the email address you want to use for receiving updates on the migration progress, and for resuming file downloads.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Click `Choose a file`{.action} to retrieve the **.vcf** contact file on your PC, then click `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Then enter the password for your target account, and click `Launch migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-The migration tracking window will then open. You can leave it open to track the migration in real time, or you can close it — closing the window will not affect the migration process.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Go further
-
-[Authorising less secure connections on Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
-
-Join our [community of users](/links/community).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.en-ie.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.en-ie.md
deleted file mode 100644
index 67284058226..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.en-ie.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: 'Migrating a Gmail account to an OVHcloud email account via the OVH Mail Migrator'
-excerpt: 'Find out how to migrate your Gmail accounts to OVHcloud using our OVH Mail Migrator tool'
-updated: 2020-03-09
----
-
-## Objective
-
-The [OVH Mail Migrator](https://omm.ovh.net/) is a tool created by OVHcloud. You can use it to migrate email accounts from one hosting provider to another. The process covers different types of content, such as emails, contacts, calendars and tasks, provided that they are compatible with your OVHcloud email accounts. 
-
-This guide describes how to use OMM to import various elements of your Gmail account to your OVHcloud account.
-
-**Find out how to migrate your Gmail account to OVHcloud using our OMM tool<b>.</b>**
-
-## Requirements
-
-- an email service with OVHcloud, e.g. [Exchange](/links/web/emails), [Email Pro](/links/web/email-pro) or MX Plan (via the MX Plan standalone tool or included in an [OVHcloud web hosting](/links/web/hosting) plan)
-- access to the email accounts you want to migrate (the source accounts)
-- access to the OVHcloud email accounts that will be receiving the migrated data (the target accounts)
-
-## Instructions
-
-### Step 1: Migrate emails and folders.
-
-> [!primary]
-> For the migration to work, you will need to turn on IMAP protocol for your Gmail account. To this, follow the Google guide on
-> [how to turn on IMAP for your Gmail account](https://support.google.com/mail/answer/7126229?hl=en).
-
-Once you have turned on IMAP for your Gmail account, go to the [OMM](https://omm.ovh.net/) tool.
-
-Click `Migration`{.action}, then `New migration`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-The following window will pop up:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Fill in the mandatory fields depending on the indications of the two tables below:
-
-**Source Account**
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Server type         	| Select **IMAP** in the dropdown menu.         									|
-| Server URL          	| Enter **imap.gmail.com**.                       					 			  	|
-| Login						| Enter your Gmail address.															|
-| Password				| Enter the password for your Gmail address.										|
-
-**Target account**
-
-| Information            	| Description                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Server type         	| Select **Hosted by OVH (Autodetect)** in the dropdown menu.   											|
-| Server URL          	| The field will be auto-filled.                     					  		 							|
-| Login						| Enter your OVHcloud email address.																			|
-| Password				| Click `detect settings`{.action}, then enter the password of your OVHcloud email address.	|
-
-In the **Options** section, only tick **Mails**, as the other options will not be available in IMAP. Contacts and calendars will be migrated in steps 2 and 3.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-In the **Information** box, you can enter an email address that will be used to notify you regarding the migration’s progress. This field is optional. Next, click `Launch the migration`{.action}.
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-The migration tracking window (below) will then appear. You can leave it open to track the migration in real time, or you can close it — closing the window will not affect the migration process.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> When the migration is launched, you may see the message below:
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-If it appears, go to your Gmail account mailbox and check if you have received an email with the subject **“Critical security alert”**. This is a security measure put in place by Gmail. To resolve this situation, follow our guide on [authorising less secure connections on Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
-
-After you have **authorised less secure connections** on Gmail, you will need to relaunch the migration.
-
-### Step 2: Migrate calendars.
-
-#### 2.1: Retrieve a calendar backup on Gmail.
-
-To import your calendar to your OVHcloud account, you will need to retrieve a backup of the calendar via the Gmail interface. To do this, follow the Google guide:
-
-[How to export your calendars for your Gmail account](https://support.google.com/calendar/answer/37111?hl=en)
-
-If you have several calendars on your Gmail account, you will download an archive folder, which you then need to decompress. Each calendar will be exported in **.ics** format.
-
-#### 2.2: Import your calendar via OMM.
-
-> [!primary]
-> Calendar migration via OMM is only compatible with Exchange target accounts.
-
-Once you have retrieved the backup of your calendar in **.ics** format, go to [OMM](https://omm.ovh.net/).
-
-Click on the `PST/ICS/VCF`{.action} tab at the top, then click `New PST/ICS/VCF migration`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Fill in the fields in the following table, then click `Launch migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Enter the OVHcloud email address you would like to migrate your calendar to.           	|
-| Password           	| Enter the password for your target email address.                          	|
-| Communication email 	| Enter the email address you want to use for receiving updates on the migration progress, and for resuming file downloads.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Click `Choose a file`{.action} to retrieve the **.ics** calendar file on your PC, then click `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Then enter the password for your target account, and click `Launch migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-The migration tracking window (below) will then appear. You can leave it open to track the migration in real time, or you can close it — closing the window will not affect the migration process.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Step 3: Migrate your contacts.
-
-> [!primary]
-> Contact migration via OMM is only compatible with Exchange target accounts.
-
-To import your contacts to your OVHcloud account, you will need to retrieve a backup of the contacts via the Gmail interface. To do this, follow the Google guide:
-
-[How to export or back up contacts for your Gmail account](https://support.google.com/contacts/answer/7199294?hl=en)
-
-> [!warning]
-> The export must be taken in vCard (**.vcf**) format via the Gmail interface. This option is offered at the end of the export process.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Fill in the fields in the following table, then click `Launch migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Enter the OVHcloud email address you would like to migrate your contacts to.            	|
-| Password           	| Enter the password for your target email address.                          	|
-| Communication email 	| Enter the email address you want to use for receiving updates on the migration progress, and for resuming file downloads.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Click `Choose a file`{.action} to retrieve the **.vcf** contact file on your PC, then click `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Then enter the password for your target account, and click `Launch migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-The migration tracking window will then open. You can leave it open to track the migration in real time, or you can close it — closing the window will not affect the migration process.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Go further
-
-[Authorising less secure connections on Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
-
-Join our [community of users](/links/community).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.es-es.md
deleted file mode 100644
index 8aea16951d3..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.es-es.md
+++ /dev/null
@@ -1,164 +0,0 @@
----
-title: 'Migrar una cuenta de Gmail a una cuenta de correo electrónico de OVHcloud a través de OVH Mail Migrator'
-excerpt: 'Cómo migrar sus cuentas de Gmail a OVHcloud con nuestra herramienta OVH Mail Migrator'
-updated: 2020-03-09
----
-
-## Objetivo
-
-[OVH Mail Migrator](https://omm.ovh.net/) (OMM) es una herramienta creada por OVHcloud. Le permite migrar sus cuentas de correo electrónico de un proveedor de hosting a otro. El proceso tiene en cuenta los diferentes tipos de contenidos, por ejemplo, los correos electrónicos, los contactos, los calendarios y las tareas, siempre que estas últimas sean compatibles con sus cuentas de correo electrónico de OVHcloud. 
-
-<b>Esta guía explica cómo utilizar la herramienta OMM para importar los distintos elementos de su cuenta de Gmail a su cuenta de correo electrónico de OVHcloud.</b>
-
-**Aprenda a migrar su cuenta de Gmail a una cuenta de correo electrónico de OVHcloud mediante nuestra herramienta OMM.**
-
-## Requisitos
-
-- Disponer de un servicio de correo electrónico en OVHcloud, como [Exchange](/links/web/emails), [Email Pro](/links/web/email-pro) o MX Plan (teniendo contratado un plan MX Plan o, incluso, mediante un plan de [Web hosting de OVHcloud](/links/web/hosting)).
-- Disponer del nombre de usuario y la contraseña de las cuentas de correo electrónico que quiera migrar (las cuentas de origen).
-- Disponer del nombre de usuario y la contraseña de las cuentas de correo electrónico de OVHcloud que recibirán los datos que se migran (las cuentas de destino).
-
-## Procedimiento
-
-### Etapa 1: Migrar los correos electrónicos y las carpetas
-
-> [!primary]
-> Para posibilitar la migración, es necesario activar el protocolo IMAP de su cuenta Gmail. Para ello, consulte la guía de Google
-> [«Consulta tu correo de Gmail a través de otras plataformas de correo electrónico»](https://support.google.com/mail/answer/7126229?hl=es).
-
-Una vez activado el protocolo IMAP en su cuenta de Gmail, acceda a [la página de la herramienta OMM](https://omm.ovh.net/).
-
-Haga clic en `Migración`{.action} y, seguidamente, en `Nueva migración`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-Aparece la siguiente ventana:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Rellene los campos necesarios según las indicaciones de las siguientes dos tablas:
-
-**Cuenta de origen**
-
-| Dato            	| Descripción                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Tipo de servidor         	| Seleccione **«IMAP»** en el menú desplegable.         									|
-| URL del servidor          	| Introduzca **«imap.gmail.com»**.                       					 			  	|
-| Nombre de usuario						| Introduzca su dirección de Gmail.															|
-| Contraseña				| Introduzca la contraseña de su dirección de Gmail.										|
-
-**Cuenta de destino**
-
-| Dato            	| Descripción                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Tipo de servidor         	| Seleccione **«Alojado en OVHcloud (autodetección)»** en el menú desplegable.   											|
-| URL del servidor          	| El campo se rellena automáticamente.                     					  		 							|
-| Nombre de usuario						| Introduzca su dirección de correo electrónico de OVHcloud.																			|
-| Contraseña				| Haga clic en `Encontrar los parámetros`{.action} y, seguidamente, introduzca la contraseña de su dirección de correo electrónico de OVHcloud.	|
-
-En la sección **«Opciones»**, active únicamente **«Mensajes de correo electrónico»**, ya que las otras opciones no están disponibles en IMAP. La migración de los contactos y los calendarios se realizará en las etapas 2 y 3.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-En el marco de texto **«Información»**, puede introducir una dirección de correo electrónico en la que se le notificará sobre el progreso de la migración. Este campo es opcional. A continuación, haga clic en `Iniciar la migración`{.action}
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-Aparece la ventana de seguimiento de la migración (véase a continuación). Puede dejarla abierta para monitorizar la migración en directo o cerrarla, lo que no tendrá ningún efecto en la migración.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> Al ejecutar la migración, es posible que visualice el siguiente mensaje
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-En tal caso, acceda a la bandeja de entrada de su cuenta de Gmail y revise si ha recibido un correo electrónico con el asunto **«Alerta de seguridad importante sobre tu cuenta de Google vinculada»**. Se trata de una medida de seguridad instrumentada por Gmail. Para solucionar esta situación, consulte la guía [Cómo autorizar las conexiones poco seguras de Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
-
-Una vez **autorizadas las «Conexiones poco seguras»** en Gmail, puede reanudar la migración.
-
-### Etapa 2: Migrar calendarios
-
-#### 2.1\. Recuperar una copia de seguridad del calendario de Gmail
-
-Para importar su calendario a su cuenta de OVHcloud, recupere una copia de seguridad de dicho calendario en la interfaz de Gmail. Para ello, consulte la guía oficial de Google:
-
-[Cómo exportar tu calendario de Google](https://support.google.com/calendar/answer/37111?hl=es)
-
-Si tiene varios calendarios en su cuenta de Gmail, descargue un archivo comprimido. Cada calendario está disponible en formato **.ics**.
-
-#### 2.2\. Importar un calendario mediante la herramienta OMM
-
-> [!primary]
-> La migración de los calendarios mediante la herramienta OMM solo es compatible con las cuentas de Exchange.
-
-Una vez recuperada la copia de seguridad de su calendario en formato **.ics**, acceda a [la página de la herramienta OMM](https://omm.ovh.net/).
-
-Acceda a la pestaña `PST/ICS/VCF`{.action} en la parte superior y, seguidamente, haga clic en `Nueva migración PST/ICS/VCF`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Rellene los campos necesarios según la siguiente tabla y luego, haga clic en `Iniciar la migración`{.action}.
-
-| Dato            	| Descripción                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Nombre de usuario                  	| Indique la dirección de correo electrónico de OVHcloud a la que migrará su calendario.           	|
-| Contraseña           	| Introduzca la contraseña de la dirección de correo electrónico de destino.                          	|
-| Correo electrónico de comunicación 	| Introduzca una dirección de correo electrónico a efectos de recibir información sobre el progreso de la migración, lo que le permitirá reanudar la descarga de un fichero.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Haga clic en `Seleccionar un archivo`{.action} para recuperar, en su ordenador, el archivo **.ics** correspondiente a su calendario y, seguidamente, haga clic en `Cargar`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-A continuación, introduzca la contraseña de su cuenta de correo electrónico de destino y, luego, haga clic en `Iniciar la migración`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-Aparece la ventana de seguimiento de la migración (véase a continuación). Puede dejarla abierta para monitorizar la migración en directo o cerrarla, lo que no tendrá ningún efecto en la migración.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Etapa 3: Migrar contactos
-
-> [!primary]
-> La migración de los contactos mediante la herramienta OMM solo es compatible hacia las cuentas de Exchange.
-
-Para importar los contactos a su cuenta de OVHcloud, recupere una copia de seguridad de estos en su interfaz de Gmail. Para ello, consulte la guía oficial de Google:
-
-[Crear copias de seguridad de contactos o exportarlos](https://support.google.com/contacts/answer/7199294?hl=es
-)
-
-> [!warning]
-> La exportación se debe hacer en formato vCard (**.vcf**) a través de la interfaz de Gmail. Esta opción se propone al final de la exportación.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Rellene los campos necesarios según la siguiente tabla y luego, haga clic en `Iniciar la migración`{.action}.
-
-| Dato            	| Descripción                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Nombre de usuario                  	| Indique la dirección de correo electrónico de OVHcloud a la que migrarán sus contactos.            	|
-| Contraseña           	| Introduzca la contraseña de la dirección de correo electrónico de destino.                          	|
-| Correo electrónico de comunicación 	| Introduzca una dirección de correo electrónico a efectos de recibir información sobre el progreso de la migración, lo que le permitirá reanudar la descarga de un fichero.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Haga clic en `Seleccionar un archivo`{.action} para recuperar, en su ordenador, el archivo **.vcf** correspondiente a sus contactos y, seguidamente, haga clic en `Cargar`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-A continuación, introduzca la contraseña de su cuenta de correo electrónico de destino y, luego, haga clic en `Iniciar la migración`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-Aparece la ventana de seguimiento de la migración, la que puede dejar abierta para monitorizar la migración en directo o cerrarla, lo que no tendrá ningún efecto en la migración.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Más información
-
-[Cómo autorizar las conexiones poco seguras en Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
-
-Interactúe con nuestra [comunidad de usuarios](/links/community).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.fr-ca.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.fr-ca.md
deleted file mode 100644
index 775ec1bed41..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.fr-ca.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: 'Migrer un compte Gmail vers un compte e-mail OVHcloud via OVH Mail Migrator'
-excerpt: 'Apprenez à migrer vos comptes Gmail vers OVHcloud grâce à notre outil OVH Mail Migrator'
-updated: 2020-03-09
----
-
-## Objectif
-
-[OVH Mail Migrator](https://omm.ovh.net/) (OMM) est un outil créé par OVHcloud. Il permet de migrer vos comptes e-mail d'un hébergeur à un autre. Le processus prend en charge différents types de contenus, tels que les e-mails, les contacts, les calendriers et les tâches, tant que ces derniers sont compatibles avec vos comptes e-mail OVHcloud. 
-
-Ce guide décrit comment utiliser OMM pour importer les différents éléments de votre compte Gmail vers votre compte email OVHcloud.
-
-**Apprenez à migrer votre compte Gmail vers un compte e-mail OVHcloud grâce à notre outil OMM.**
-
-## Prérequis
-
-- Disposer d'un service e-mail chez OVHcloud, tel qu'une [offre Exchange](/links/web/emails-hosted-exchange) or MX Plan (via l'offre MX Plan seule ou incluse dans une [offre d'hébergement web OVHcloud](/links/web/hosting)).
-- Disposer des identifiants relatifs aux comptes e-mail que vous souhaitez migrer (les comptes source).
-- Disposer des identifiants relatifs aux comptes e-mail OVHcloud qui reçoivent les données migrées (les comptes de destination).
-
-## En pratique
-
-### Étape 1: migration des e-mails et dossiers
-
-> [!primary]
-> Pour que la migration soit possible, il faut activer le protocole IMAP sur votre compte Gmail. Pour cela, suivez le guide de Google
-> [comment activer l'IMAP pour votre compte Gmail](https://support.google.com/mail/answer/7126229?hl=fr).
-
-Une fois le protocole IMAP activé sur votre compte Gmail, rendez-vous sur [OMM](https://omm.ovh.net/).
-
-Cliquez sur `Migration`{.action} puis `Nouvelle migration`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-La fenêtre suivante apparait:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Complétez les champs requis selon les indications des deux tableaux ci-dessous:
-
-**Compte Source**
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Type de serveur         	| Selectionnez **«IMAP»**  dans le menu déroulant.         									|
-| URL du serveur          	| Saisissez **«imap.gmail.com»**.                       					 			  	|
-| Login						| Renseignez votre adresse Gmail.															|
-| Mot de passe				| Renseignez le mot de passe de votre adresse Gmail.										|
-
-**Compte de destination**
-
-| Information            	| Description                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Type de serveur         	| Selectionnez **«Hosted by OVH (Autodetect)»**  dans le menu déroulant.   											|
-| URL du serveur          	| Le champ se complète automatiquement.                     					  		 							|
-| Login						| Renseignez votre adresse e-mail OVHcloud.																			|
-| Mot de passe				| Cliquez sur `détecter les paramètres`{.action} puis renseignez le mot de passe de votre adresse e-mail OVHcloud.	|
-
-Dans la partie **«Options»**, cochez uniquement **«Mails»**, les autres options n'étant pas disponibles en IMAP. La migration des contacts et calendriers se fera aux étapes 2 et 3.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-Dans le cadre **«Information»**, vous pouvez renseignez une adresse e-mail sur laquelle vous serez notifié de l'avancement de la migration. Ce champ est facultatif. Cliquez ensuite sur `Démarer la migration`{.action}
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-La fenêtre de suivi de migration (ci-dessous) s'affiche alors. Vous pouvez la laisser ouverte pour suivre la migration en direct ou fermer celle-ci, cela n'aura pas d'incidence sur la migration.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> Au lancement de la migration, vous pouvez rencontrez le message ci-dessous
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-Dans ce cas de figure, rendez-vous dans la boite de réception de votre compte Gmail et vérifiez si vous avez reçu l'e-mail avec l'objet **«Alerte de sécurité critique»**. Il s'agit d'une mesure de sécurité mise en place par Gmail. Afin de résoudre cette situation, suivez le guide : [Comment autoriser les connexions moins sécurisées sur Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
-
-Après avoir **autorisé les «connexions moins sécurisées»** sur Gmail, vous pourrez relancer la migration.
-
-### Étape 2: migration des calendriers
-
-#### 2.1 récupérer une sauvegarde du calendrier sur Gmail
-
-Pour importer votre calendrier vers votre compte OVHcloud, récupérez une sauvegarde de celui-ci depuis votre interface Gmail. Pour cela, suivez le guide officiel de Google :
-
-[Comment exporter ses calendriers pour votre compte Gmail](https://support.google.com/calendar/answer/37111?hl=fr)
-
-Si vous avez plusieurs calendriers sur votre compte Gmail, vous téléchargerez un fichier d'archive à décompresser. Vous retrouverez chaque calendrier au format **.ics**.
-
-#### 2.2 importer son calendrier via OMM
-
-> [!primary]
-> La migration des calendriers par OMM n'est compatible que vers les comptes Exchange.
-
-Après avoir récupéré la sauvegarde de votre calendrier au format **.ics**, allez sur [OMM](https://omm.ovh.net/).
-
-Dirigez-vous sur l'onglet `PST/ICS/VCF`{.action} en haut, puis cliquez sur `Nouvelle migration PST/ICS/VCF`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Complétez les champs demandés selon le tableau suivant puis cliquez sur `Démarrer la migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Indiquez l'adresse e-mail OVHcloud vers laquelle vous migrez votre calendrier.           	|
-| Mot de passe           	| Renseignez le mot de passe de l'adresse e-mail de destination.                          	|
-| Email de communication 	| Renseignez une adresse e-mail qui servira à communiquer sur l'avancement de la migration et vous permettra de reprendre le téléchargement d'un fichier.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Cliquez sur `Choisir un fichier`{.action} pour récupérer, sur votre ordinateur, le fichier **.ics** de votre calendrier puis cliquez sur `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Renseignez alors le mot de passe de votre compte e-mail de destination puis cliquez sur `Démarrer la migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-La fenêtre de suivi de migration (ci-dessous) s'affiche alors. Vous pouvez la laisser ouverte pour suivre la migration en direct ou fermer celle-ci, cela n'aura pas d'incidence sur la migration.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Étape 3: migration des contacts
-
-> [!primary]
-> La migration des contacts par OMM n'est compatible que vers les comptes Exchange.
-
-Pour importer vos contacts vers votre compte OVHcloud, récupérez une sauvegarde de ces derniers depuis votre interface Gmail. Pour cela, suivez le guide officiel de Google :
-
-[Comment exporter ses contacts pour votre compte Gmail](https://support.google.com/contacts/answer/7199294?hl=fr)
-
-> [!warning]
-> L'export doit se faire au format vCard (**.vcf**) via l'interface Gmail. cette option vous est proposée à la fin de l'export.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Complétez les champs demandés selon le tableau suivant puis cliquez sur `Démarrer la migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Indiquez l'adresse e-mail OVHcloud vers laquelle vous migrez vos contacts.            	|
-| Mot de passe           	| Renseignez le mot de passe de l'adresse e-mail de destination.                          	|
-| Email de communication 	| Renseignez une adresse e-mail qui servira à communiquer sur l'avancement de la migration et vous permettra de reprendre le téléchargement d'un fichier.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Cliquez sur `Choisir un fichier`{.action} pour récupérer, sur votre ordinateur, le fichier **.vcf** de vos contacts puis cliquez sur `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Renseignez alors le mot de passe de votre compte e-mail de destination puis cliquez sur `Démarrer la migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-La fenêtre de suivi de migration s'affiche, vous pouvez laisser celle-ci ouverte pour suivre la migration en direct ou fermer celle-ci, cela n'aura pas d'incidence sur la migration.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Aller plus loin
-
-[Comment autoriser les connexions moins sécurisées sur Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
-
-Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.fr-fr.md
deleted file mode 100644
index a8c885908ed..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.fr-fr.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: 'Migrer un compte Gmail vers un compte e-mail OVHcloud via OVH Mail Migrator'
-excerpt: 'Apprenez à migrer vos comptes Gmail vers OVHcloud grâce à notre outil OVH Mail Migrator'
-updated: 2020-03-09
----
-
-## Objectif
-
-[OVH Mail Migrator](https://omm.ovh.net/) (OMM) est un outil créé par OVHcloud. Il permet de migrer vos comptes e-mail d'un hébergeur à un autre. Le processus prend en charge différents types de contenus, tels que les e-mails, les contacts, les calendriers et les tâches, tant que ces derniers sont compatibles avec vos comptes e-mail OVHcloud. 
-
-Ce guide décrit comment utiliser OMM pour importer les différents éléments de votre compte Gmail vers votre compte email OVHcloud.
-
-**Apprenez à migrer votre compte Gmail vers un compte e-mail OVHcloud grâce à notre outil OMM.**
-
-## Prérequis
-
-- Disposer d'un service e-mail chez OVHcloud, tel qu'une [offre Exchange](/links/web/emails), [E-mail Pro](/links/web/email-pro) ou MX Plan (via l'offre MX Plan seule ou incluse dans une [offre d'hébergement web OVHcloud](/links/web/hosting)).
-- Disposer des identifiants relatifs aux comptes e-mail que vous souhaitez migrer (les comptes source).
-- Disposer des identifiants relatifs aux comptes e-mail OVHcloud qui reçoivent les données migrées (les comptes de destination).
-
-## En pratique
-
-### Étape 1: migration des e-mails et dossiers
-
-> [!primary]
-> Pour que la migration soit possible, il faut activer le protocole IMAP sur votre compte Gmail. Pour cela, suivez le guide de Google
-> [comment activer l'IMAP pour votre compte Gmail](https://support.google.com/mail/answer/7126229?hl=fr).
-
-Une fois le protocole IMAP activé sur votre compte Gmail, rendez-vous sur [OMM](https://omm.ovh.net/).
-
-Cliquez sur `Migration`{.action} puis `Nouvelle migration`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-La fenêtre suivante apparait:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Complétez les champs requis selon les indications des deux tableaux ci-dessous:
-
-**Compte Source**
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Type de serveur         	| Selectionnez **«IMAP»**  dans le menu déroulant.         									|
-| URL du serveur          	| Saisissez **«imap.gmail.com»**.                       					 			  	|
-| Login						| Renseignez votre adresse Gmail.															|
-| Mot de passe				| Renseignez le mot de passe de votre adresse Gmail.										|
-
-**Compte de destination**
-
-| Information            	| Description                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Type de serveur         	| Selectionnez **«Hosted by OVH (Autodetect)»**  dans le menu déroulant.   											|
-| URL du serveur          	| Le champ se complète automatiquement.                     					  		 							|
-| Login						| Renseignez votre adresse e-mail OVHcloud.																			|
-| Mot de passe				| Cliquez sur `détecter les paramètres`{.action} puis renseignez le mot de passe de votre adresse e-mail OVHcloud.	|
-
-Dans la partie **«Options»**, cochez uniquement **«Mails»**, les autres options n'étant pas disponibles en IMAP. La migration des contacts et calendriers se fera aux étapes 2 et 3.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-Dans le cadre **«Information»**, vous pouvez renseignez une adresse e-mail sur laquelle vous serez notifié de l'avancement de la migration. Ce champ est facultatif. Cliquez ensuite sur `Démarer la migration`{.action}
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-La fenêtre de suivi de migration (ci-dessous) s'affiche alors. Vous pouvez la laisser ouverte pour suivre la migration en direct ou fermer celle-ci, cela n'aura pas d'incidence sur la migration.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> Au lancement de la migration, vous pouvez rencontrez le message ci-dessous
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-Dans ce cas de figure, rendez-vous dans la boite de réception de votre compte Gmail et vérifiez si vous avez reçu l'e-mail avec l'objet **«Alerte de sécurité critique»**. Il s'agit d'une mesure de sécurité mise en place par Gmail. Afin de résoudre cette situation, suivez le guide : [Comment autoriser les connexions moins sécurisées sur Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
-
-Après avoir **autorisé les «connexions moins sécurisées»** sur Gmail, vous pourrez relancer la migration.
-
-### Étape 2: migration des calendriers
-
-#### 2.1 récupérer une sauvegarde du calendrier sur Gmail
-
-Pour importer votre calendrier vers votre compte OVHcloud, récupérez une sauvegarde de celui-ci depuis votre interface Gmail. Pour cela, suivez le guide officiel de Google :
-
-[Comment exporter ses calendriers pour votre compte Gmail](https://support.google.com/calendar/answer/37111?hl=fr)
-
-Si vous avez plusieurs calendriers sur votre compte Gmail, vous téléchargerez un fichier d'archive à décompresser. Vous retrouverez chaque calendrier au format **.ics**.
-
-#### 2.2 importer son calendrier via OMM
-
-> [!primary]
-> La migration des calendriers par OMM n'est compatible que vers les comptes Exchange.
-
-Après avoir récupéré la sauvegarde de votre calendrier au format **.ics**, allez sur [OMM](https://omm.ovh.net/).
-
-Dirigez-vous sur l'onglet `PST/ICS/VCF`{.action} en haut, puis cliquez sur `Nouvelle migration PST/ICS/VCF`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Complétez les champs demandés selon le tableau suivant puis cliquez sur `Démarrer la migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Indiquez l'adresse e-mail OVHcloud vers laquelle vous migrez votre calendrier.           	|
-| Mot de passe           	| Renseignez le mot de passe de l'adresse e-mail de destination.                          	|
-| Email de communication 	| Renseignez une adresse e-mail qui servira à communiquer sur l'avancement de la migration et vous permettra de reprendre le téléchargement d'un fichier.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Cliquez sur `Choisir un fichier`{.action} pour récupérer, sur votre ordinateur, le fichier **.ics** de votre calendrier puis cliquez sur `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Renseignez alors le mot de passe de votre compte e-mail de destination puis cliquez sur `Démarrer la migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-La fenêtre de suivi de migration (ci-dessous) s'affiche alors. Vous pouvez la laisser ouverte pour suivre la migration en direct ou fermer celle-ci, cela n'aura pas d'incidence sur la migration.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Étape 3: migration des contacts
-
-> [!primary]
-> La migration des contacts par OMM n'est compatible que vers les comptes Exchange.
-
-Pour importer vos contacts vers votre compte OVHcloud, récupérez une sauvegarde de ces derniers depuis votre interface Gmail. Pour cela, suivez le guide officiel de Google :
-
-[Comment exporter ses contacts pour votre compte Gmail](https://support.google.com/contacts/answer/7199294?hl=fr)
-
-> [!warning]
-> L'export doit se faire au format vCard (**.vcf**) via l'interface Gmail. cette option vous est proposée à la fin de l'export.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Complétez les champs demandés selon le tableau suivant puis cliquez sur `Démarrer la migration`{.action}:
-
-| Information            	| Description                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Indiquez l'adresse e-mail OVHcloud vers laquelle vous migrez vos contacts.            	|
-| Mot de passe           	| Renseignez le mot de passe de l'adresse e-mail de destination.                          	|
-| Email de communication 	| Renseignez une adresse e-mail qui servira à communiquer sur l'avancement de la migration et vous permettra de reprendre le téléchargement d'un fichier.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Cliquez sur `Choisir un fichier`{.action} pour récupérer, sur votre ordinateur, le fichier **.vcf** de vos contacts puis cliquez sur `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Renseignez alors le mot de passe de votre compte e-mail de destination puis cliquez sur `Démarrer la migration`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-La fenêtre de suivi de migration s'affiche, vous pouvez laisser celle-ci ouverte pour suivre la migration en direct ou fermer celle-ci, cela n'aura pas d'incidence sur la migration.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Aller plus loin
-
-[Comment autoriser les connexions moins sécurisées sur Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
-
-Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.it-it.md
deleted file mode 100644
index 921a51ebf67..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.it-it.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: 'Migrare un account Gmail verso OVHcloud con OVH Mail Migrator'
-excerpt: 'Questa guida ti mostra come migrare i tuoi account Gmail verso OVHcloud grazie al nostro tool OVH Mail Migrator.'
-updated: 2020-03-09
----
-
-## Obiettivo
-
-[OVH Mail Migrator](https://omm.ovh.net/) è uno strumento creato per consentirti di migrare i tuoi account di posta elettronica da un hosting a un altro. Il processo include diversi tipi di contenuti, come email, contatti, calendari e task, a seconda della compatibilità con i tuoi account di posta elettronica OVHcloud. 
-
-Questa guida ti spiega come utilizzare OMM per importare i vari elementi del tuo account Gmail verso un altro account di posta elettronica OVHcloud.
-
-**Questa guida ti mostra come migrare i tuoi account Gmail verso un account di posta elettronica OVHcloud grazie al nostro tool OMM**.
-
-## Prerequisiti
-
-- Disporre di una soluzione email OVHcloud, come [Exchange](/links/web/emails), [Email Pro](/links/web/email-pro) o MX Plan (inclusa nel servizio MX Plan o in una [soluzione di hosting Web OVHcloud](/links/web/hosting)).
-- Disporre delle credenziali relative agli account email da migrare
-- Disporre delle credenziali relative agli account e-mail OVHcloud che ricevono i dati migrati (gli account di destinazione).
-
-## Procedura
-
-### Step 1: esegui la migrazione di email e cartelle
-
-> [!primary]
-> Per rendere possibile la migrazione, è necessario attivare il protocollo IMAP sul tuo account Gmail. Per farlo, segui la guida di Google
-> [come configurare IMAP per il tuo account Gmail](https://support.google.com/mail/answer/7126229?hl=it).
-
-Una volta attivato IMAP, accedi a [OMM](https://omm.ovh.net/).
-
-Clicca su `Migrazione`{.action} e poi su `Nuova migrazione`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-Visualizzi la seguente finestra:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Completa la tabella con le informazioni richieste per ogni sezione:
-
-**Account di origine**
-
-| Informazione            	| Descrizione                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Tipo di server         	| Seleziona **IMAP** nel menu a tendina.         									|
-| URL del server          	| Inserisci **«imap.gmail.com»**.                       					 			  	|
-| Login						| Inserisci il tuo indirizzo Gmail.															|
-| Password				| Inserisci la password associata all’account Gmail.										|
-
-**Account di destinazione**
-
-| Informazione            	| Descrizione                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Tipo di server         	| Seleziona **“Hosted by OVH (Autodetect)”** nel menu a tendina.   											|
-| URL del server          	| Questo campo è compilato automaticamente.                     					  		 							|
-| Login						| Inserisci il tuo indirizzo email OVHcloud																			|
-| Password				| Clicca su `rileva le impostazioni`{.action}e poi inserisci la password del tuo indirizzo email OVHcloud.	|
-
-Nella sezione **Opzioni**, spunta la casella **”Mails”**, dato che le altre opzioni non sono disponibili in IMAP. La migrazione di contatti e calendari verrà realizzata negli Step 2 e 3.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-Nel riquadro **“Informazioni”**, inserisci un indirizzo email su cui riceverai una notifica dello stato di avanzamento della migrazione. Questo campo è facoltativo. Clicca su `Avvia la migrazione`{.action}
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-A questo punto, compare una finestra con lo stato di avanzamento della migrazione (come mostrato qui di seguito). Puoi lasciarla aperta per seguire il processo di migrazione in tempo reale o chiuderla, e questo non inciderà in alcun modo sulla migrazione.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> All’avvio della migrazione, potresti visualizzare questi messaggi:
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-In questo caso, accedi alla casella di posta in arrivo del tuo account Gmail e controlla se hai ricevuto l’email con oggetto: **“Avviso di sicurezza”** Si tratta di una misura di sicurezza adottata da Gmail. Per risolvere questa situazione, consulta la guida:  [Consentire alle applicazioni meno sicure di accedere al tuo account Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
-
-Dopo aver **consentito l’accesso alle “applicazioni meno sicure”** su Gmail, puoi riavviare il processo di migrazione.
-
-### Step 2: esegui la migrazione dei calendari
-
-#### 2.1 Ripristina un backup del calendario su Gmail
-
-Per importare il tuo calendario nel tuo account OVHcloud, recupera un backup del calendario dalla tua interfaccia Gmail. Per effettuare l’operazione, segui la guida ufficiale di Google :
-
-[Come esportare i calendari per il tuo account Gmail](https://support.google.com/calendar/answer/37111?hl=it)
-
-Se disponi di più calendari sul tuo account Gmail, scarica un file di archivio da decomprimere. Ciascun calendario è disponibile in formato **.ics**.
-
-#### 2.2 Importa il tuo calendario con OMM
-
-> [!primary]
-> La migrazione dei calendari tramite OMM è compatibile solo con gli account Exchange.
-
-Dopo aver recuperato il backup del tuo calendario nel formato **.ics**, accedi a [OMM](https://omm.ovh.net/).
-
-Clicca sulla scheda `PST/ICS/VCF`{.action} situata in alto e poi su `Nuova migrazione PST/ICS/VCF`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Completa la tabella con le informazioni richieste per ogni sezione e poi clicca su `Avvia la migrazione`{.action}:
-
-| Informazione            	| Descrizione                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Inserisci l’indirizzo email OVHcloud verso cui migrare il tuo calendario.           	|
-| Password           	| Inserisci la password associata all’account di destinazione.                          	|
-| Email di comunicazione 	| Inserisci un indirizzo email per ricevere notifiche sullo stato di avanzamento della migrazione e per riprendere il download di un file.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Clicca su `Scegli un file`{.action} per recuperare il file **.ics** del tuo calendario, dal tuo computer, e poi clicca su `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-A questo punto inserisci la password del tuo account di destinazione, quindi clicca su `Avvia la migrazione`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-A questo punto, compare una finestra con lo stato di avanzamento della migrazione (come mostrato qui di seguito). Puoi lasciarla aperta per seguire il processo di migrazione in tempo reale o chiuderla, e questo non inciderà in alcun modo sulla migrazione.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Step 3: esegui la migrazione dei contatti
-
-> [!primary]
-> La migrazione dei contatti tramite OMM è compatibile solo con gli account Exchange.
-
-Per importare i tuoi contatti nel tuo account OVHcloud, recupera un backup dei contatti dalla tua interfaccia Gmail. Per effettuare l’operazione, segui la guida ufficiale di Google :
-
-[Come esportare i contatti dal tuo account Gmail](https://support.google.com/contacts/answer/7199294?hl=it)
-
-> [!warning]
-> L’esportazione deve essere effettuata nel formato vCard (**.vcf**) tramite l’interfaccia Gmail. Questa opzione ti viene proposta alla fine dell’esportazione.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Completa la tabella con le informazioni richieste per ogni sezione e poi clicca su `Avvia la migrazione`{.action}:
-
-| Informazione            	| Descrizione                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Indica l’indirizzo email OVHcloud verso cui vuoi migrare i tuoi contatti.            	|
-| Password           	| Inserisci la password associata all’account di destinazione.                          	|
-| Email di comunicazione 	| Inserisci un indirizzo email per ricevere notifiche sullo stato di avanzamento della migrazione e per riprendere il download di un file.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Clicca su `Scegli un file`{.action} per recuperare il file **.ics** dei tuoi contatti, dal tuo computer, e poi clicca su `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-A questo punto, inserisci la password del tuo account di destinazione, quindi clicca su `Avvia la migrazione`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-Compare una finestra con lo stato di avanzamento della migrazione. Puoi lasciarla aperta per seguire il processo di migrazione in tempo reale o chiuderla. Quest’ultima operazione non inciderà in alcun modo sulla migrazione.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Per saperne di più
-
-[Consentire alle applicazioni meno sicure di accedere al tuo account Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
-
-Contatta la nostra [Community di utenti](/links/community).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.pl-pl.md
deleted file mode 100644
index c396bc32982..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.pl-pl.md
+++ /dev/null
@@ -1,164 +0,0 @@
----
-title: 'Migracja konta Gmail do konta e-mail OVHcloud przy użyciu narzędzia OVH Mail Migrator'
-excerpt: 'Dowiedz się, jak przenieść swoje konta Gmail do OVHcloud przy użyciu narzędzia OVH Mail Migrator'
-updated: 2020-03-09
----
-
-## Wprowadzenie
-
-[OVH Mail Migrator](https://omm.ovh.net/) (OMM) jest narzędziem przygotowanym przez OVHcloud. Umożliwia ono przeprowadzanie migracji kont e-mail od jednego dostawcy usług hostingowych do drugiego. Operacja obejmuje przeniesienie różnych typów treści, takich jak e-maile, kontakty, kalendarze i zadania, o ile są one kompatybilne z Twoimi kontami e-mail w OVHcloud. 
-
-Z tego przewodnika dowiesz się, jak używać narzędzia OMM do importowania różnych elementów konta Gmail do konta e-mail OVHcloud.
-
-**Dowiedz się, jak przenieść Twoje konto Gmail do konta e-mail OVHcloud przy użyciu narzędzia OMM.**
-
-## Wymagania początkowe
-
-- Korzystanie z usługi poczty elektronicznej w OVHcloud, takiej jak [oferta Exchange](/links/web/emails), [E-mail Pro](/links/web/email-pro) lub MX Plan (w postaci oferty MX Plan lub kont e-mail dostępnych w ramach [hostingu OVHcloud](/links/web/hosting))
-- Posiadanie danych dostępowych do kont e-mail, które chcesz przenieść (konta źródłowe)
-- Posiadanie danych dostępowych do kont e-mail OVHcloud, na które przeniesione zostaną dane (konta docelowe)
-
-## W praktyce
-
-### Etap 1: Migracja e-maili i folderów
-
-> [!primary]
-> Aby migracja była możliwa, na koncie Gmail trzeba aktywować protokół IMAP. W tym celu postępuj zgodnie z przewodnikiem Google dotyczącym
-> [aktywowania protokołu IMAP na koncie Gmail](https://support.google.com/mail/answer/7126229?hl=pl).
-
-Po aktywowaniu protokołu IMAP na koncie Google, przejdź do strony narzędzia [OMM](https://omm.ovh.net/).
-
-Kliknij przycisk `Migracja`{.action}, a następnie `Nowa migracja`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-Pojawi się następujące okno:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Uzupełnij wymagane pola zgodnie z informacjami z dwóch poniższych tabel:
-
-**Konto źródłowe**
-
-| Informacja            	| Opis                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Typ serwera         	| Z menu rozwijanego wybierz pozycję **„IMAP”**.         									|
-| Adres URL serwera          	| Wpisz **„imap.gmail.com”**.                       					 			  	|
-| Login						| Wpisz Twój adres Gmail.															|
-| Hasło				| Wpisz hasło do Twojego konta Gmail.										|
-
-**Konto docelowe**
-
-| Informacja            	| Opis                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Typ serwera         	| Z menu rozwijanego wybierz opcję **„Hosting w OVH (wykrywanie automatyczne)”**.   											|
-| Adres URL serwera          	| Pole zostaje uzupełnione automatycznie.                     					  		 							|
-| Login						| Wpisz Twój adres e-mail OVHcloud.																			|
-| Hasło				| Kliknij polecenie `wykryj parametry`{.action}, a następnie wpisz hasło do Twojego konta e-mail OVHcloud.	|
-
-W sekcji **„Opcje”** zaznacz wyłącznie pozycję **„E-maile”**, ponieważ inne opcje nie są dostępne w przypadku protokołu IMAP. Migracja kontaktów i kalendarzy zostanie przeprowadzona w 2\. i 3\. etapie.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-W sekcji **„Informacje”** możesz wpisać adres e-mail, na który chcesz otrzymywać powiadomienia dotyczące postępów migracji. To pole jest opcjonalne. Następnie kliknij polecenie `Rozpocznij migrację`{.action}.
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-Pojawi się okno monitorowania migracji (poniżej). Możesz zostawić je otwarte, aby na bieżąco monitorować migrację, lub też je zamknąć bez wpływu na migrację.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> Podczas uruchamiania migracji może pojawić się poniższy komunikat:
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-W takim przypadku przejdź do skrzynki odbiorczej Twojego konta Gmail i sprawdź, czy przyszła wiadomość zatytułowana **„Krytyczny alert bezpieczeństwa”**. Jest to środek bezpieczeństwa stosowany przez Gmail. Należy wówczas postępować zgodnie z instrukcjami z przewodnika: [Jak zezwolić na mniej bezpieczne połączenia w Gmailu](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
-
-Gdy **zezwolisz na „mniej bezpieczne połączenia”** na koncie Gmail, możesz ponownie uruchomić migrację.
-
-### Etap 2: Migracja kalendarzy
-
-#### 2.1 Pobieranie kopii zapasowej kalendarza na koncie Gmail
-
-Aby zaimportować kalendarz do konta OVHcloud, musisz pobrać jego kopię zapasową z panelu Gmail. W tym celu postępuj zgodnie z instrukcjami w przewodniku Google:
-
-[Eksportowanie kalendarza z konta Gmail](https://support.google.com/calendar/answer/37111?hl=pl)
-
-Jeśli na koncie Google masz kilka kalendarzy, pobierzesz plik archiwum do rozpakowania. Każdy kalendarz będzie w formacie **.ics**.
-
-#### 2.2 Importowanie kalendarza przy użyciu narzędzia OMM
-
-> [!primary]
-> Migracja kalendarzy przy użyciu narzędzia OMM jest możliwa tylko do kont Exchange.
-
-Po pobraniu kopii zapasowej kalendarza w formacie **.ics** przejdź do strony narzędzia [OMM](https://omm.ovh.net/).
-
-U góry wybierz kartę `PST/ICS/VCF`{.action}, a następnie kliknij pozycję `Nowa migracja PST/ICS/VCF`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Uzupełnij wymagane pola zgodnie z informacjami podanymi w poniższej tabeli, a następnie kliknij polecenie `Rozpocznij migrację`{.action}:
-
-| Informacja            	| Opis                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Podaj adres e-mail OVHcloud, na który ma zostać przeprowadzona migracja kalendarza.           	|
-| Hasło           	| Wpisz hasło przypisane do docelowego konta e-mail.                          	|
-| E-mail do komunikacji 	| Podaj adres e-mail, na który będziesz otrzymywać informacje o postępach migracji i który pozwoli na wznowienie pobierania pliku.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Kliknij pozycję `Wybierz plik`{.action}, aby pobrać na Twój komputer plik kalendarza w formacie **.ics**, a następnie kliknij polecenie `Prześlij`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Podaj hasło przypisane do docelowego konta e-mail, a następnie kliknij polecenie `Rozpocznij migrację`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-Pojawi się okno monitorowania migracji (poniżej). Możesz zostawić je otwarte, aby na bieżąco monitorować migrację, lub też je zamknąć bez wpływu na migrację.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Etap 3: Migracja kontaktów
-
-> [!primary]
-> Migracja kontaktów przy użyciu narzędzia OMM jest możliwa tylko do kont Exchange.
-
-Aby zaimportować kontakty do konta OVHcloud, musisz pobrać ich kopię zapasową z panelu Gmail. W tym celu postępuj zgodnie z instrukcjami w przewodniku Google:
-
-[Eksportowanie kontaktów z konta Gmail](https://support.google.com/contacts/answer/7199294?hl=pl)
-
-> [!warning]
-> Eksport należy wykonać do formatu vCard (**.vcf**) przez panel Gmail. Ta opcja jest proponowana na koniec procesu eksportu.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Uzupełnij wymagane pola zgodnie z informacjami podanymi w poniższej tabeli, a następnie kliknij polecenie `Rozpocznij migrację`{.action}:
-
-| Informacja            	| Opis                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Login                  	| Podaj adres e-mail OVHcloud, na który ma zostać przeprowadzona migracja kontaktów.            	|
-| Hasło           	| Wpisz hasło przypisane do docelowego konta e-mail.                          	|
-| E-mail do komunikacji 	| Podaj adres e-mail, na który będziesz otrzymywać informacje o postępach migracji i który pozwoli na wznowienie pobierania pliku.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Kliknij pozycję `Wybierz plik`{.action}, aby pobrać na Twój komputer plik kontaktów w formacie **.vcf**, a następnie kliknij polecenie `Prześlij`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Podaj hasło przypisane do docelowego konta e-mail, a następnie kliknij polecenie `Rozpocznij migrację`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-Pojawi się okno monitorowania migracji. Możesz zostawić je otwarte, aby na bieżąco monitorować migrację, lub też je zamknąć bez wpływu na migrację.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Sprawdź również
-
-[Jak zezwolić na mniej bezpieczne połączenia w Gmailu](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
-
-Dołącz do [grona naszych użytkowników](/links/community).
-
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.pt-pt.md
deleted file mode 100644
index fea7b05d95d..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/guide.pt-pt.md
+++ /dev/null
@@ -1,164 +0,0 @@
----
-title: 'Migrar uma conta Gmail para uma conta de e-mail OVHcloud através do OVH Mail Migrator'
-excerpt: 'Aprenda a migrar as suas contas Gmail para o OVHcloud graças à nossa ferramenta OVH Mail Migrator'
-updated: 2020-03-09
----
-
-## Objetivo
-
-[OVH Mail Migrator](https://omm.ovh.net/) (OMM) é uma ferramenta criada pela OVHcloud. Permite migrar as suas contas de e-mail de um serviço de alojamento para outro. O processo considera vários tipos de conteúdo, como os e-mails, os contactos, os calendários e as tarefas, desde que eles sejam compatíveis com as suas contas de e-mail OVHcloud. 
-
-Este guia descreve como usar a OMM para importar os vários elementos da sua conta Gmail para a sua conta de e-mail OVHcloud.
-
-**Aprenda a migrar a sua conta Gmail para uma conta de e-mail OVHcloud graças à nossa ferramenta OMM.**
-
-## Requisitos
-
-- Ter um serviço de e-mail no OVHcloud, como uma [oferta Exchange](/links/web/emails), [E-mail Pro](/links/web/email-pro) ou MX Plan (através da oferta MX Plan sozinha ou incluída numa [oferta de serviço de alojamento web OVHcloud](/links/web/hosting)).
-- Ter dados de acesso relativos às contas de e-mail que pretende migrar (as contas de origem).
-- Ter dados de acesso relativos às contas de e-mail OVHcloud que recebem os dados migrados (as contas de destino).
-
-## Instruções
-
-### Etapa 1: migração dos e-mails e das pastas
-
-> [!primary]
-> Para que a migração seja possível, é preciso ativar o protocolo IMAP na sua conta Gmail. Para isso, observe o guia da Google
-> [como ativar o IMAP para a sua conta Gmail](https://support.google.com/mail/answer/7126229?hl=pt).
-
-Depois de o protocolo IMAP estar ativado na sua conta Gmail, vá a [OMM](https://omm.ovh.net/).
-
-Clique em `Migração`{.action} e, depois, em `Nova migração`{.action}.
-
-![omm](images/OMM-gmail-step01-01.png){.thumbnail}
-
-Surge a seguinte janela:
-
-![omm](images/OMM-gmail-step01-02.png){.thumbnail}
-
-Preencha os campos obrigatórios em função das indicações dos dois quadros seguintes:
-
-**Conta de Origem**
-
-| Informação            	| Descrição                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Tipo de servidor         	| Selecione **"IMAP"**  no menu pendente.         									|
-| URL do servidor          	| Introduza **"imap.gmail.com"**.                       					 			  	|
-| Nome de utilizador						| Insira o seu endereço Gmail.															|
-| Palavra-passe				| Insira a palavra-passe do seu endereço Gmail.										|
-
-**Conta de destino**
-
-| Informação            	| Descrição                                                                              							|
-|------------------------	|-------------------------------------------------------------------------------------------------------------------|
-| Tipo de servidor         	| Selecione **"Hosted by OVH (Autodetect)"**  no menu pendente.   											|
-| URL do servidor          	| O campo preenche-se automaticamente.                     					  		 							|
-| Nome de utilizador						| Insira o seu endereço de e-mail OVHcloud.																			|
-| Palavra-passe				| Clique em `detetar os parâmetros`{.action} e insira a palavra-passe do seu endereço de e-mail OVHcloud.	|
-
-Na parte **"Opções"**, preencha apenas **"E-mails"** dado que as outras opções não estão disponíveis em IMAP. A migração dos contactos e calendários será feita nas etapas 2 e 3.
-
-![omm](images/OMM-gmail-step01-03.png){.thumbnail}
-
-No quadro **"Informação"**, pode inserir um endereço de e-mail onde receberá notificações sobre o progresso da migração. Este campo é facultativo. Clique então em `Iniciar a migração`{.action}
-
-![omm](images/OMM-gmail-step01-04.png){.thumbnail}
-
-A janela de progresso da migração (indicada a seguir) será então apresentada. Pode deixá-la aberta para acompanhar a migração em direto ou fechá-la, isso não terá qualquer efeito na migração.
-
-![omm](images/OMM-gmail-step01-06.png){.thumbnail}
-
-> [!warning]
-> No início da migração, poderá surgir a seguinte mensagem
-
-![omm](images/OMM-gmail-step01-05.png){.thumbnail}
-
-Se isso acontecer, vá à caixa de entrada da sua conta Gmail e verifique se recebeu o e-mail com o assunto **"Alerta de segurança crítico"**. Trata-se de uma medida de segurança implementada pela Gmail. Para resolver esta situação, observe o guia: [Como autorizar as conexões menos seguras no Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
-
-Depois de ter **autorizado as "conexões menos seguras"** no Gmail, pode reiniciar a migração.
-
-### Etapa 2: migração dos calendários
-
-#### 2.1 Recuperar uma salvaguarda do calendário no Gmail
-
-Para importar o seu calendário para a sua conta OVHcloud, recupere uma salvaguarda do mesmo a partir da sua interface Gmail. Para isso, observe o guia oficial da Google:
-
-[Como exportar os calendários para a sua conta Gmail](https://support.google.com/calendar/answer/37111?hl=pt)
-
-Se tiver vários calendários na sua conta Gmail, irá transferir um ficheiro de arquivo que terá de descomprimir. Cada calendário estará no formato **.ics**.
-
-#### 2.2 Importar o calendário através de OMM
-
-> [!primary]
-> A migração dos calendários por OMM só é compatível para as contas Exchange.
-
-Depois de ter recuperado a salvaguarda do seu calendário no formato **.ics**, vá a [OMM](https://omm.ovh.net/).
-
-Vá ao separador `PST/ICS/VCF`{.action} em cima, e clique em `Nova migração PST/ICS/VCF`{.action}.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Preencha os campos solicitados de acordo com o seguinte quadro, e clique em `Iniciar a migração`{.action}:
-
-| Informação            	| Descrição                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Nome de utilizador                  	| Indique o endereço de e-mail OVHcloud para o qual deseja migrar o seu calendário.           	|
-| Palavra-passe           	| Insira a palavra-passe do endereço de e-mail de destino.                          	|
-| E-mail de comunicação 	| Insira um endereço de e-mail que servirá para comunicar sobre o progresso da migração e permitirá retomar a transferência de um ficheiro.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
- Clique em `Escolher um ficheiro`{.action} para recuperar, no seu computador, o ficheiro **.ics** do seu calendário, e clique em `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Insira então a palavra-passe da sua conta de e-mail de destino, e clique em `Iniciar a migração`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-A janela de progresso da migração (indicada a seguir) será então apresentada. Pode deixá-la aberta para acompanhar a migração em direto ou fechá-la, isso não terá qualquer efeito na migração.
-
-![omm](images/OMM-gmail-step02.png){.thumbnail}
-
-### Etapa 3: migração dos contactos
-
-> [!primary]
-> A migração dos contactos por OMM só é compatível para as contas Exchange.
-
-Para importar os seus contactos para a sua conta OVHcloud, recupere uma salvaguarda destes últimos a partir da sua interface Gmail. Para isso, observe o guia oficial da Google:
-
-[Como exportar os contactos para a sua conta Gmail](https://support.google.com/contacts/answer/7199294?hl=pt)
-
-> [!warning]
-> A exportação deve realizar-se no formato vCard (**.vcf**) através da interface Gmail. Esta opção é-lhe proposta no fim da exportação.
-
-![omm](images/OMM-gmail-step23-01.png){.thumbnail}
-
-Preencha os campos solicitados de acordo com o seguinte quadro, e clique em `Iniciar a migração`{.action}:
-
-| Informação            	| Descrição                                                                              	|
-|------------------------	|------------------------------------------------------------------------------------------	|
-| Nome de utilizador                  	| Indique o endereço de e-mail OVHcloud para o qual migra os seus contactos.            	|
-| Palavra-passe           	| Insira a palavra-passe do endereço de e-mail de destino.                          	|
-| E-mail de comunicação 	| Insira um endereço de e-mail que servirá para comunicar sobre o progresso da migração e permitirá retomar a transferência de um ficheiro.	|
-
-![omm](images/OMM-gmail-step23-02.png){.thumbnail}
-
-Clique em `Escolher um ficheiro`{.action} para recuperar, no seu computador, o ficheiro **.vcf** dos seus contactos, e clique em `Upload`{.action}.
-
-![omm](images/OMM-gmail-step23-03.png){.thumbnail}
-
-Insira então a palavra-passe da sua conta de e-mail de destino, e clique em `Iniciar a migração`{.action}.
-
-![omm](images/OMM-gmail-step23-04.png){.thumbnail}
-
-A janela de progresso da migração aparece. Pode deixá-la aberta para acompanhar a migração em direto ou fechá-la, isso não terá qualquer efeito na migração.
-
-![omm](images/OMM-gmail-step03.png){.thumbnail}
-
-## Quer saber mais?
-
-[Como autorizar as conexões menos seguras no Gmail](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
-
-Fale com nossa [comunidade de utilizadores](/links/community).
-
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-01.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-01.png
deleted file mode 100644
index 65a9dcf1db9..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-01.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-02.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-02.png
deleted file mode 100644
index e2663279105..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-02.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-03.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-03.png
deleted file mode 100644
index 0f57600e0cd..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-03.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-04.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-04.png
deleted file mode 100644
index d9b725de4de..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-04.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-05.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-05.png
deleted file mode 100644
index 0cfd3f1b9eb..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-05.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-06.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-06.png
deleted file mode 100644
index 5290852bedf..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step01-06.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step02.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step02.png
deleted file mode 100644
index cd8930f9515..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step02.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step03.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step03.png
deleted file mode 100644
index 5a3e3df760e..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step03.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-01.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-01.png
deleted file mode 100644
index 057c575ea3d..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-01.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-02.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-02.png
deleted file mode 100644
index 22e21e47b01..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-02.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-03.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-03.png
deleted file mode 100644
index 14d1609a44c..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-03.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-04.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-04.png
deleted file mode 100644
index 3d28df3a783..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/images/OMM-gmail-step23-04.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/meta.yaml b/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/meta.yaml
deleted file mode 100755
index 6bf62d8767e..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm/meta.yaml
+++ /dev/null
@@ -1,3 +0,0 @@
-id: 84cc9e1d-4755-412a-8553-0571ee99a397
-full_slug: email-omm-migrate-gmail-account-to-ovhcloud
-translation_banner: true
\ No newline at end of file
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.de-de.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.de-de.md
deleted file mode 100644
index 871d0c77b9f..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.de-de.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: 'Weniger sichere Verbindungen in Google Mail zulassen'
-flag: hidden
-updated: 2022-04-06
----
-
-## Ziel
-
-In dieser Anleitung wird erklärt, wie Sie die Option „Weniger sichere Apps zulassen" in Ihrem Google Mail-Account aktivieren.
-
-> [!primary] 
-> 
-Nachfolgend werden Schritte zur Konfiguration von Gmail im Zusammenhang mit dieser Anleitung beschrieben: 
-[Einen Gmail-Account mit dem OVH Mail Migrator auf einen OVHcloud E-Mail-Account migrieren](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-> 
-
-## In der praktischen Anwendung
-
-Wenn Sie eine Warnungsmail zum Account-Zugriff erhalten haben, klicken Sie auf `Aktivität einsehen`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-Nun wird angezeigt, dass ein Versuch, über ein Nicht-Google Protokoll zuzugreifen, stattgefunden hat. Klicken Sie auf `Ja, das war ich`{.action}
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-Das nächste Fenster informiert Sie darüber, dass trotz dieser Validierung eine Sperre aktiv ist. Klicken Sie direkt auf den folgenden Link: [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Klicken Sie auf die Schaltfläche rechts neben der Option „Weniger sichere Apps zulassen: AUS“ (siehe unten).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-Sie erhalten eine weitere Warn-E-Mail. Klicken Sie auf `Aktivität einsehen`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-Mit dieser Nachricht soll überprüft werden, ob Sie der Initiator dieser Aktivierung sind. Klicken Sie auf `Ja, das war ich`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Nach der Validierung zeigt die folgende Meldung an, dass Ihre Auswahl berücksichtigt wurde. Sie können sich jetzt auch mit Anwendungen außerhalb von Google Diensten in Ihrem Google Mail-Account anmelden.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> Sie benötigen ein Passwort mit mindestens 16 Zeichen auf Ihrem Gmail-Account, auch als "Application Passwort" bezeichnet. Wenn Sie „Weniger sichere Apps zulassen" aktivieren, muss Ihr Gmail-Account ein starkes Passwort verwenden.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Weiterführende Informationen
-
-[Einen Gmail-Account mit dem OVH Mail Migrator auf einen OVHcloud E-Mail-Account migrieren](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.en-ca.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.en-ca.md
deleted file mode 100644
index dee5e89b71f..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.en-ca.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: 'Authorising less secure connections on Gmail'
-flag: hidden
-updated: 2022-04-06
----
-
-## Objective
-
-This guide details how to enable the “authorise less secure apps” option on your Gmail account.
-
-> [!primary] This documentation is a step linked to our guide on
-> [Migrating a Gmail account to an OVHcloud email address via the OVH Mail Migrator.](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-
-## Instructions
-
-If you have received the email below with the subject **“Critical security alert**, click `View activity`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-The message below will appear, listing details on the attempt to use a protocol outside of the Google application. Click `Yes, this was me`{.action}.
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-The next window will inform you that in spite of this confirmation, the block will still be active. Click on the following link: [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Click on the toggle button to the right of “Allow less secure apps: OFF” (see below).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-You will receive a new email with the same subject — “Critical security alert”. click `View activity`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-The purpose of this email is to check if it was you that turned on less secure app access. Click `Yes, this was me`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Once you have confirmed, the message below will show that your choice has been processed. You can now log in to your Gmail account outside of Google applications.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> You need to have a password of at least 16 characters on your Gmail account, also called “application password”. When you “authorise less secure apps”, a strong password must be applied to your Gmail account.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Go further
-
-[Migrating a Gmail account to an OVHcloud email address via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.en-gb.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.en-gb.md
deleted file mode 100644
index dee5e89b71f..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.en-gb.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: 'Authorising less secure connections on Gmail'
-flag: hidden
-updated: 2022-04-06
----
-
-## Objective
-
-This guide details how to enable the “authorise less secure apps” option on your Gmail account.
-
-> [!primary] This documentation is a step linked to our guide on
-> [Migrating a Gmail account to an OVHcloud email address via the OVH Mail Migrator.](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-
-## Instructions
-
-If you have received the email below with the subject **“Critical security alert**, click `View activity`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-The message below will appear, listing details on the attempt to use a protocol outside of the Google application. Click `Yes, this was me`{.action}.
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-The next window will inform you that in spite of this confirmation, the block will still be active. Click on the following link: [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Click on the toggle button to the right of “Allow less secure apps: OFF” (see below).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-You will receive a new email with the same subject — “Critical security alert”. click `View activity`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-The purpose of this email is to check if it was you that turned on less secure app access. Click `Yes, this was me`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Once you have confirmed, the message below will show that your choice has been processed. You can now log in to your Gmail account outside of Google applications.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> You need to have a password of at least 16 characters on your Gmail account, also called “application password”. When you “authorise less secure apps”, a strong password must be applied to your Gmail account.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Go further
-
-[Migrating a Gmail account to an OVHcloud email address via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.en-ie.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.en-ie.md
deleted file mode 100644
index dee5e89b71f..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.en-ie.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: 'Authorising less secure connections on Gmail'
-flag: hidden
-updated: 2022-04-06
----
-
-## Objective
-
-This guide details how to enable the “authorise less secure apps” option on your Gmail account.
-
-> [!primary] This documentation is a step linked to our guide on
-> [Migrating a Gmail account to an OVHcloud email address via the OVH Mail Migrator.](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-
-## Instructions
-
-If you have received the email below with the subject **“Critical security alert**, click `View activity`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-The message below will appear, listing details on the attempt to use a protocol outside of the Google application. Click `Yes, this was me`{.action}.
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-The next window will inform you that in spite of this confirmation, the block will still be active. Click on the following link: [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Click on the toggle button to the right of “Allow less secure apps: OFF” (see below).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-You will receive a new email with the same subject — “Critical security alert”. click `View activity`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-The purpose of this email is to check if it was you that turned on less secure app access. Click `Yes, this was me`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Once you have confirmed, the message below will show that your choice has been processed. You can now log in to your Gmail account outside of Google applications.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> You need to have a password of at least 16 characters on your Gmail account, also called “application password”. When you “authorise less secure apps”, a strong password must be applied to your Gmail account.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Go further
-
-[Migrating a Gmail account to an OVHcloud email address via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.es-es.md
deleted file mode 100644
index 67d3b5e3e6d..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.es-es.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: 'Cómo autorizar las conexiones poco seguras en Gmail'
-flag: hidden
-updated: 2022-04-06
----
-
-## Objetivo
-
-<b>Esta guía explica cómo activar la opción «Autorizar las aplicaciones poco seguras» en su cuenta de Gmail.</b>
-
-> [!primary] Esta documentación constituye una etapa vinculada a la guía
-> [«Migrar una cuenta de Gmail a una dirección de correo electrónico de OVHcloud a través de OVH Mail Migrator»](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-
-## Procedimiento
-
-Si ha recibido un mensaje de correo electrónico con el asunto **«Alerta de seguridad importante sobre tu cuenta de Google vinculada»** como el que se muestra a continuación, haga clic en `Comprobar actividad`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-Aparece el siguiente mensaje, en el que se indican los detalles del intento de utilización de un protocolo fuera de la aplicación de Google. Haga clic en `Sí, he sido yo`{.action}.
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-En la siguiente ventana, se le informa que, a pesar de esta validación, hay un bloqueo activo. Haga clic directamente en el siguiente enlace: [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Haga clic en el botón a la derecha de la indicación «Autorizar las aplicaciones poco seguras» (véase a continuación).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-Se le enviará un nuevo mensaje de correo electrónico con el mismo asunto «Alerta de seguridad importante sobre tu cuenta de Google vinculada». Haga clic en `Comprobar actividad`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-Este mensaje tiene como objetivo comprobar que la activación corresponde a su propia iniciativa. Haga clic en `Sí, he sido yo`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Tras la validación, el siguiente mensaje le indica que su elección ha sido confirmada. A partir de ese momento, podrá conectarse a su cuenta de Gmail fuera de las aplicaciones de Google.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> Es necesario tener una contraseña de al menos 16 dígitos en su cuenta de Gmail, también llamada «contraseña de aplicación». ya que, al «Autorizar las aplicaciones poco seguras», es necesario que se aplique una contraseña segura en su cuenta de Gmail.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Más información
-
-[«Migrar una cuenta de Gmail a una dirección de correo electrónico de OVHcloud a través de OVH Mail Migrator»](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.fr-ca.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.fr-ca.md
deleted file mode 100644
index 178d6ad27c1..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.fr-ca.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: 'Comment autoriser les connexions moins sécurisées sur Gmail'
-flag: hidden
-updated: 2022-04-06
----
-
-## Objectif
-
-Ce guide vous détaille comment activer l'option "autoriser les applications moins sécurisées" sur votre compte Gmail.
-
-> [!primary]
-> 
-> Cette documentation est une étape liée au guide [«Migrer un compte Gmail vers une adresse e-mail OVHcloud via OVH Mail Migrator»](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-> 
-
-## En pratique
-
-Si vous avez reçu l'e-mail ci-dessous avec l'objet **«Alerte de sécurité critique»**. Cliquez sur `Consulter l'activité`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-Le message ci-dessous apparaît et mentionne les détails sur la tentative d'utilisation d'un protocole hors application Google. Cliquez sur `Oui, c'était moi`{.action}
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-La fenêtre suivante vous informe que, malgré cette validation, un blocage est actif. Cliquez directement sur le lien suivant : [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Cliquez sur le bouton à droite de la mention «Paramètre "Autoriser les applications moins sécurisées" désactivé» (voir ci-dessous).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-Un nouvel e-mail vous sera envoyé avec le même objet «Alerte de sécurité critique». Cliquez sur `Consulter l'activité`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-Ce message a pour but de vérifier que vous êtes bien à l'initiative de cette activation. Cliquez sur `Oui, c'était moi`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Après validation, le message ci-dessous indique que votre choix a bien été pris en compte. Vous pouvez à présent vous connecter à votre compte Gmail en dehors des applications Google.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> Le mot de passe de votre compte Gmail doit comporter un minimum de 16 caractères, et ainsi être considéré comme un « mot de passe d'application ». En effet, lorsque vous « autorisez les applications moins sécurisées », il est nécessaire qu'un mot de passe fort soit appliqué sur votre compte Gmail.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Aller plus loin
-
-[«Migrer une adresse Gmail vers une adresse e-mail OVHcloud via OVH Mail Migrator »](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.fr-fr.md
deleted file mode 100644
index 80bb5e9a0f5..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.fr-fr.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: 'Comment autoriser les connexions moins sécurisées sur Gmail'
-flag: hidden
-updated: 2022-04-06
----
-
-## Objectif
-
-Ce guide vous détaille comment activer l'option « autoriser les applications moins sécurisées » sur votre compte Gmail.
-
-> [!primary]
-> 
-> Cette documentation est une étape liée au guide [«Migrer un compte Gmail vers une adresse e-mail OVHcloud via OVH Mail Migrator»](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm).
-> 
-
-## En pratique
-
-Si vous avez reçu l'e-mail ci-dessous avec l'objet **«Alerte de sécurité critique»**. Cliquez sur `Consulter l'activité`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-Le message ci-dessous apparaît et mentionne les détails sur la tentative d'utilisation d'un protocole hors application Google. Cliquez sur `Oui, c'était moi`{.action}
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-La fenêtre suivante vous informe que, malgré cette validation, un blocage est actif. Cliquez directement sur le lien suivant : [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Cliquez sur le bouton à droite de la mention «Paramètre "Autoriser les applications moins sécurisées" désactivé» (voir ci-dessous).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-Un nouvel e-mail vous sera envoyé avec le même objet «Alerte de sécurité critique». Cliquez sur `Consulter l'activité`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-Ce message a pour but de vérifier que vous êtes bien à l'initiative de cette activation. Cliquez sur `Oui, c'était moi`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Après validation, le message ci-dessous indique que votre choix a bien été pris en compte. Vous pouvez à présent vous connecter à votre compte Gmail en dehors des applications Google.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> Le mot de passe de votre compte Gmail doit comporter un minimum de 16 caractères, et ainsi être considéré comme un « mot de passe d'application ». En effet, lorsque vous « autorisez les applications moins sécurisées », il est nécessaire qu'un mot de passe fort soit appliqué sur votre compte Gmail.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Aller plus loin
-
-[«Migrer une adresse Gmail vers une adresse e-mail OVHcloud via OVH Mail Migrator »](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.it-it.md
deleted file mode 100644
index 8d4810e32e1..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.it-it.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: 'Consentire alle applicazioni meno sicure di accedere al tuo account Gmail'
-flag: hidden
-updated: 2022-04-06
----
-
-## Obiettivo
-
-Questa guida ti mostra come attivare l’opzione “Consenti app meno sicure” nel tuo account Gmail.
-
-> [!primary]
-> Questa documentazione costituisce uno step della guida
-> [“Migrare un account Gmail verso OVHcloud con OVH Mail Migrator”](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-
-## Procedura
-
-Se hai ricevuto un’email con oggetto **“Avviso di sicurezza”**, clicca su `Controlla l’attività`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-Visualizzi il seguente messaggio, che fornisce i dettagli del tentativo di utilizzo di un protocollo al di fuori dell’applicazione Google. Clicca su `Sì, ero io`{.action}
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-La nuova pagina ti informa che, nonostante la conferma da parte tua, è stato attivato un blocco. Quindi clicca direttamente su questo link: [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Clicca sul pulsante a destra della voce “Consenti app meno sicure”: ‘Disattiva’ (come mostrato qui sotto).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-A questo punto, riceverai una nuova email con lo stesso oggetto “Avviso di scurezza.” clicca su `Controlla l’attività`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-Questo messaggio ha lo scopo di verificare che sei stato effettivamente tu a eseguire l’operazione di attivazione. Clicca su `Sì, ero io`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Dopo la convalida, questo messaggio ti conferma che la tua scelta è stata presa in carico. Ora puoi accedere al tuo account Gmail al di fuori delle applicazioni Google.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> È necessario avere una password di almeno 16 cifra sul tuo account Gmail, chiamata anche "password dell'applicazione". Quando autorizzi “Consenti app meno sicure”, è necessario applicare una password forte sul tuo account Gmail.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Per saperne di più
-
-[“Migrare un account Gmail verso OVHcloud con OVH Mail Migrator”](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.pl-pl.md
deleted file mode 100644
index 61e739a03b1..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.pl-pl.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: 'Jak zezwolić na mniej bezpieczne połączenia w Gmailu'
-flag: hidden
-updated: 2022-04-06
----
-
-## Wprowadzenie
-
-Z tego przewodnika dowiesz się, jak aktywować opcję „Zezwalaj na mniej bezpieczne aplikacje” na Twoim koncie Gmail.
-
-> [!primary] Ta dokumentacja jest etapem związanym z przewodnikiem
-> [„Migracja konta Gmail do adresu e-mail OVHcloud przy użyciu narzędzia OVH Mail Migrator”](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-
-## W praktyce
-
-Jeśli otrzymałeś poniższą wiadomość e-mail zatytułowaną **„Krytyczny alert bezpieczeństwa”**. Kliknij pozycję `Sprawdź aktywność`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-Pojawia się poniższy komunikat zawierający szczegółowe informacje na temat próby użycia protokołu poza aplikacją Google. Kliknij `Tak, to ja`{.action}
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-Pojawi się poniższe okno informujące, że mimo zatwierdzenia blokada jest aktywna. Kliknij bezpośrednio następujący link: [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Kliknij przycisk po prawej stronie od informacji „Zezwalaj na mniej bezpieczne aplikacje: WYŁĄCZONE” (patrz poniżej).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-Otrzymasz nową wiadomość e-mail, również zatytułowaną „Krytyczny alert bezpieczeństwa”. Kliknij pozycję `Sprawdź aktywność`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-Ta wiadomość ma na celu sprawdzenie, czy opcja ta została rzeczywiście aktywowana przez Ciebie. Kliknij `Tak, to ja`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Po potwierdzeniu pojawia się poniższy komunikat informujący, że Twój wybór został uwzględniony. Teraz możesz logować się do Twojego konta Gmail poza aplikacjami Google.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> Na koncie Gmail musisz posiadać hasło minimum 16 linii, zwane również "hasłem aplikacji". Podczas "autoryzacji aplikacji o niskim poziomie bezpieczeństwa" należy stosować silne hasło do konta Gmail.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Sprawdź również
-
-[„Migracja konta Gmail do adresu e-mail OVHcloud przy użyciu narzędzia OVH Mail Migrator”](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.pt-pt.md
deleted file mode 100644
index ecfcbec5604..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/guide.pt-pt.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: 'Cómo autorizar las conexiones poco seguras en Gmail'
-flag: hidden
-updated: 2022-04-06
----
-
-## Objetivo
-
-Este guia explica pormenorizadamente como ativar a opção "autorizar as aplicações menos seguras" na sua conta Gmail.
-
-> [!primary] Esta documentação é uma etapa associada ao guia
-> ["Migrar uma conta Gmail para um endereço de e-mail OVHcloud através do OVH Mail Migrator"](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
-
-## Instruções
-
-Se tiver recebido o e-mail seguinte com o assunto **"Alerta de segurança crítica"**. Clique em `Consultar a atividade`{.action}.
-
-![omm](images/OMM-gmail-security-01.png){.thumbnail}
-
-A mensagem seguinte aparece e indica os pormenores da tentativa de utilização de um protocolo exterior à aplicação Google. Clique em `Sim, era eu`{.action}
-
-![omm](images/OMM-gmail-security-02.png){.thumbnail}
-
-A janela seguinte indica que, apesar desta validação, um bloqueio se encontra ativo. Clique diretamente na seguinte ligação: [myaccount.google.com/lesssecureapps](https://myaccount.google.com/lesssecureapps)
-
-![omm](images/OMM-gmail-security-03.png){.thumbnail}
-
-Clique no botão do lado direito da indicação "Parâmetro 'Autorizar as aplicações menos seguras' desativado" (ver mais abaixo).
-
-![omm](images/OMM-gmail-security-04.png){.thumbnail}
-
-Um novo e-mail ser-lhe-á enviado com o mesmo assunto "Alerta de segurança crítico". Clique em `Consultar a atividade`{.action}.
-
-![omm](images/OMM-gmail-security-05.png){.thumbnail}
-
-Esta mensagem tem como objetivo verificar se esteve na origem desta ativação. Clique em `Sim, era eu`{.action}.
-
-![omm](images/OMM-gmail-security-06.png){.thumbnail}
-
-Depois da validação, a mensagem seguinte indica que a sua escolha foi considerada. Pode agora ligar-se à sua conta Gmail fora das aplicações Google.
-
-![omm](images/OMM-gmail-security-07.png){.thumbnail}
-
-> [!warning]
->
-> É necessário ter uma palavra-passe de 16 dígitos na sua conta Gmail, também conhecida como "password de aplicação". Quando "autorizar as aplicações menos seguras", é necessário que uma palavra-passe forte seja aplicada na sua conta Gmail.
->
-> ![omm](images/OMM-gmail-security-08.png){.thumbnail}
->
-
-## Quer saber mais?
-
-["Migrar um endereço Gmail para um endereço de e-mail OVHcloud através do OVH Mail Migrator"](/pages/web_cloud/email_and_collaborative_solutions/migrating/migrate_gmail_to_ovhcloud_by_omm)
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-01.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-01.png
deleted file mode 100644
index 69a998c9a46..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-01.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-02.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-02.png
deleted file mode 100644
index 5f5b4ffa8ad..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-02.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-03.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-03.png
deleted file mode 100644
index 0f54eaabd5f..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-03.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-04.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-04.png
deleted file mode 100644
index e5f52058492..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-04.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-05.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-05.png
deleted file mode 100644
index b29eb473da1..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-05.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-06.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-06.png
deleted file mode 100644
index aca3b3fcb1c..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-06.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-07.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-07.png
deleted file mode 100644
index 787b062e436..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-07.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-08.png b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-08.png
deleted file mode 100644
index dd26a61ef3f..00000000000
Binary files a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/images/OMM-gmail-security-08.png and /dev/null differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/meta.yaml b/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/meta.yaml
deleted file mode 100755
index df9f2dc5e70..00000000000
--- a/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail/meta.yaml
+++ /dev/null
@@ -1,3 +0,0 @@
-id: c96d19b2-4ff7-4d6f-bcce-8216b378d354
-full_slug: email-omm-migrate-gmail-account-to-ovhcloud-gmail-security
-translation_banner: true
\ No newline at end of file
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.de-de.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.de-de.md
index 435d05b92b5..6b4d9b095f0 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.de-de.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.de-de.md
@@ -22,7 +22,7 @@ MX Plan Accounts können auf verschiedenen, kompatiblen E-Mail-Clients eingerich
 > [!warning]
 > OVHcloud stellt Ihnen Dienstleistungen zur Verfügung, für deren Konfiguration und Verwaltung Sie die alleinige Verantwortung tragen. Es liegt somit bei Ihnen, sicherzustellen, dass diese ordnungsgemäß funktionieren.
 > 
-> Wir stellen Ihnen diese Anleitung zur Verfügung, um Ihnen bei der Bewältigung genereller Verwaltungsaufgaben zu helfen. Dennoch empfehlen wir Ihnen, einen [spezialisierten Partner](https://marketplace.ovhcloud.com/c/support-collaboration) oder den Herausgeber des Dienstes zu kontaktieren, wenn Sie bei der Administration Ihrer Dienste Hilfe benötigen. Weitere Informationen finden Sie am [Ende dieser Anleitung](#go-further).
+> Wir stellen Ihnen diese Anleitung zur Verfügung, um Ihnen bei der Bewältigung genereller Verwaltungsaufgaben zu helfen. Dennoch empfehlen wir Ihnen, einen [spezialisierten Partner](/links/partner) oder den Herausgeber des Dienstes zu kontaktieren, wenn Sie bei der Administration Ihrer Dienste Hilfe benötigen. Weitere Informationen finden Sie am [Ende dieser Anleitung](#go-further).
 >
 
 ## Voraussetzungen
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-asia.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-asia.md
index ec25658acb4..7f5bc2073ec 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-asia.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-asia.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services that you are responsible for configuring, managing and managing. It is therefore up to you to ensure that it works properly.
 >
-> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
+> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
 
 ## Requirements
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-au.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-au.md
index 32f31c20f9e..2aca5a7c5bc 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-au.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-au.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services that you are responsible for configuring, managing and managing. It is therefore up to you to ensure that it works properly.
 >
-> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
+> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
 
 ## Requirements
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-ca.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-ca.md
index 32f31c20f9e..2aca5a7c5bc 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-ca.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-ca.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services that you are responsible for configuring, managing and managing. It is therefore up to you to ensure that it works properly.
 >
-> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
+> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
 
 ## Requirements
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-gb.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-gb.md
index 32f31c20f9e..2aca5a7c5bc 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-gb.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-gb.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services that you are responsible for configuring, managing and managing. It is therefore up to you to ensure that it works properly.
 >
-> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
+> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
 
 ## Requirements
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-ie.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-ie.md
index 32f31c20f9e..2aca5a7c5bc 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-ie.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-ie.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services that you are responsible for configuring, managing and managing. It is therefore up to you to ensure that it works properly.
 >
-> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
+> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
 
 ## Requirements
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-sg.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-sg.md
index 32f31c20f9e..2aca5a7c5bc 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-sg.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-sg.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services that you are responsible for configuring, managing and managing. It is therefore up to you to ensure that it works properly.
 >
-> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
+> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
 
 ## Requirements
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-us.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-us.md
index 32f31c20f9e..2aca5a7c5bc 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-us.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.en-us.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services that you are responsible for configuring, managing and managing. It is therefore up to you to ensure that it works properly.
 >
-> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
+> We have provided you with this guide in order to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) and/or the service publisher if you experience any difficulties. We will not be able to assist you. You can find more information in the “Go further” section of this guide.
 
 ## Requirements
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.es-es.md
index 9064d36fe67..45ed069d1f6 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.es-es.md
@@ -23,7 +23,7 @@ Es posible configurar las cuentas MX Plan en el cliente de correo que usted util
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Por lo tanto, usted deberá asegurarse de que estos funcionen correctamente.
 >
-> Esta guía le ayudará a realizar las tareas más habituales. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte el apartado "Más información" de esta guía.
+> Esta guía le ayudará a realizar las tareas más habituales. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte el apartado "Más información" de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.es-us.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.es-us.md
index 9064d36fe67..45ed069d1f6 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.es-us.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.es-us.md
@@ -23,7 +23,7 @@ Es posible configurar las cuentas MX Plan en el cliente de correo que usted util
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Por lo tanto, usted deberá asegurarse de que estos funcionen correctamente.
 >
-> Esta guía le ayudará a realizar las tareas más habituales. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte el apartado "Más información" de esta guía.
+> Esta guía le ayudará a realizar las tareas más habituales. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte el apartado "Más información" de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.fr-ca.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.fr-ca.md
index 0a692d7c499..88590e9bc51 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.fr-ca.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.fr-ca.md
@@ -23,7 +23,7 @@ Les comptes MX Plan peuvent être configurés sur différents logiciels de messa
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/partner) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.fr-fr.md
index 0a692d7c499..9dbfb1d0b2d 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes MX Plan peuvent être configurés sur différents logiciels de messa
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.it-it.md
index 78fc6f2ee57..47d6268ba22 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.it-it.md
@@ -23,7 +23,7 @@ Gli account MX Plan possono essere configurati su client di posta compatibili. p
 >
 > OVHcloud mette a disposizione i servizi ma non si occupa della loro configurazione e gestione. garantirne il corretto funzionamento è quindi responsabilità dell’utente.
 >
-> Questa guida ti aiuta a eseguire le operazioni necessarie alla configurazione del tuo account. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) o il fornitore del servizio. OVH non sarà infatti in grado di fornirti assistenza. Per maggiori informazioni consulta la sezione "Per saperne di più".
+> Questa guida ti aiuta a eseguire le operazioni necessarie alla configurazione del tuo account. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](/links/partner) o il fornitore del servizio. OVH non sarà infatti in grado di fornirti assistenza. Per maggiori informazioni consulta la sezione "Per saperne di più".
 
 ## Prerequisiti
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.pl-pl.md
index d2eaa231455..c6c254418e1 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.pl-pl.md
@@ -23,7 +23,7 @@ Konta MX Plan mogą być skonfigurowane w jednym z kompatybilnych programów poc
 >
 > OVHcloud udostępnia różnorodne usługi, jednak to Ty odpowiadasz za ich konfigurację i zarządzanie nimi. Ponosisz więc odpowiedzialność za ich prawidłowe funkcjonowanie.
 >
-> Oddajemy w Twoje ręce niniejszy przewodnik, którego celem jest pomoc w jak najbardziej optymalnym wykonywaniu bieżących zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](https://marketplace.ovhcloud.com/c/support-collaboration) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji znajduje się w sekcji "Sprawdź również".
+> Oddajemy w Twoje ręce niniejszy przewodnik, którego celem jest pomoc w jak najbardziej optymalnym wykonywaniu bieżących zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](/links/partner) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji znajduje się w sekcji "Sprawdź również".
 
 ## Wymagania początkowe
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.pt-pt.md
index ab5a0e6b8ac..6d59ca1479a 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_android/guide.pt-pt.md
@@ -23,7 +23,7 @@ As contas MX Plan podem ser configuradas em diferentes softwares de e-mail compa
 >
 > A OVHcloud oferece-lhe serviços cuja configuração, gestão e responsabilidade é da sua responsabilidade. Assim, deverá assegurar o seu bom funcionamento.
 >
-> Este guia fornece as instruções necessárias para realizar as operações mais habituais. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte a secção "Quer saber mais?" deste guia.
+> Este guia fornece as instruções necessárias para realizar as operações mais habituais. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](/links/partner) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte a secção "Quer saber mais?" deste guia.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-asia.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-asia.md
index fdd04e0eb9c..7bd48bbfbdb 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-asia.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-asia.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
 > 
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
+> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
 > 
 
 ## Requirements
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-au.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-au.md
index 7979d9e6923..f92df17590d 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-au.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-au.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
 > 
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
+> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
 > 
 
 ## Requirements
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-ca.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-ca.md
index 7979d9e6923..f92df17590d 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-ca.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-ca.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
 > 
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
+> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
 > 
 
 ## Requirements
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-gb.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-gb.md
index 7979d9e6923..f92df17590d 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-gb.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-gb.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
 > 
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
+> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
 > 
 
 ## Requirements
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-ie.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-ie.md
index 7979d9e6923..f92df17590d 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-ie.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-ie.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
 > 
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
+> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
 > 
 
 ## Requirements
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-sg.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-sg.md
index 7979d9e6923..f92df17590d 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-sg.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-sg.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
 > 
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
+> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
 > 
 
 ## Requirements
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-us.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-us.md
index 7979d9e6923..f92df17590d 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-us.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.en-us.md
@@ -23,7 +23,7 @@ MX Plan accounts can be configured on various compatible email clients. This all
 >
 > OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
 > 
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](https://marketplace.ovhcloud.com/c/support-collaboration) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
+> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialized partner](/links/partner) or the software publisher if you encounter any difficulties. OVHcloud cannot provide you with technical support in this regard. You can find more information in the [Go further](#go-further) section of this guide.
 > 
 
 ## Requirements
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.es-es.md
index 95fd80c875a..ffa05391965 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.es-es.md
@@ -23,7 +23,7 @@ Es posible configurar las cuentas MX Plan en el cliente de correo que usted util
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Por lo tanto, usted deberá asegurarse de que estos funcionen correctamente.
 >
-> Esta guía le ayudará a realizar las tareas más habituales. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte el apartado «Más información» de esta guía.
+> Esta guía le ayudará a realizar las tareas más habituales. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte el apartado «Más información» de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.es-us.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.es-us.md
index 95fd80c875a..ffa05391965 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.es-us.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.es-us.md
@@ -23,7 +23,7 @@ Es posible configurar las cuentas MX Plan en el cliente de correo que usted util
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Por lo tanto, usted deberá asegurarse de que estos funcionen correctamente.
 >
-> Esta guía le ayudará a realizar las tareas más habituales. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte el apartado «Más información» de esta guía.
+> Esta guía le ayudará a realizar las tareas más habituales. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte el apartado «Más información» de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.fr-ca.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.fr-ca.md
index a89dbd88c6b..4dcbfc1bebf 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.fr-ca.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.fr-ca.md
@@ -23,7 +23,7 @@ Les comptes MX Plan peuvent être configurés sur différents logiciels de messa
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/partner) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.fr-fr.md
index a89dbd88c6b..4dc4f8d11e6 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes MX Plan peuvent être configurés sur différents logiciels de messa
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.it-it.md
index bd870505eae..70e258e1e16 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.it-it.md
@@ -23,7 +23,7 @@ Gli account MX Plan possono essere configurati su client di posta compatibili. p
 >
 > OVHcloud mette a disposizione i servizi ma non si occupa della loro configurazione e gestione. garantirne il corretto funzionamento è quindi responsabilità dell’utente.
 >
-> Questa guida ti aiuta a eseguire le operazioni necessarie alla configurazione del tuo account. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) o il fornitore del servizio. OVH non sarà infatti in grado di fornirti assistenza. Per maggiori informazioni consulta la sezione "Per saperne di più".
+> Questa guida ti aiuta a eseguire le operazioni necessarie alla configurazione del tuo account. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](/links/partner) o il fornitore del servizio. OVH non sarà infatti in grado di fornirti assistenza. Per maggiori informazioni consulta la sezione "Per saperne di più".
 
 ## Prerequisiti
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.pl-pl.md
index ebf5554ce70..751bd8aa815 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.pl-pl.md
@@ -23,7 +23,7 @@ Konta MX Plan mogą być skonfigurowane w jednym z kompatybilnych programów poc
 >
 > OVHcloud udostępnia różnorodne usługi, jednak to Ty odpowiadasz za ich konfigurację i zarządzanie nimi. Ponosisz więc odpowiedzialność za ich prawidłowe funkcjonowanie.
 >
-> Oddajemy w Twoje ręce niniejszy przewodnik, którego celem jest pomoc w jak najbardziej optymalnym wykonywaniu bieżących zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](https://marketplace.ovhcloud.com/c/support-collaboration) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji znajduje się w sekcji "[Sprawdź również](#go-further)".
+> Oddajemy w Twoje ręce niniejszy przewodnik, którego celem jest pomoc w jak najbardziej optymalnym wykonywaniu bieżących zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](/links/partner) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji znajduje się w sekcji "[Sprawdź również](#go-further)".
 
 ## Wymagania początkowe
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.pt-pt.md
index 9e452d0410f..5b6334868b6 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_outlook_app_ios/guide.pt-pt.md
@@ -23,7 +23,7 @@ As contas MX Plan podem ser configuradas em diferentes softwares de e-mail compa
 >
 > A OVHcloud oferece-lhe serviços cuja configuração, gestão e responsabilidade é da sua responsabilidade. Assim, deverá assegurar o seu bom funcionamento.
 >
-> Este guia fornece as instruções necessárias para realizar as operações mais habituais. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte a secção "[Quer saber mais?](#go-further)" deste guia.
+> Este guia fornece as instruções necessárias para realizar as operações mais habituais. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](/links/partner) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte a secção "[Quer saber mais?](#go-further)" deste guia.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.de-de.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.de-de.md
index ebf800f7b95..c6d7f4e60c2 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.de-de.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.de-de.md
@@ -294,7 +294,6 @@ Sie möchten zu einem anderen [E-Mail-Angebot](/links/web/emails) wechseln, um m
 - [E-Mail-Accounts von einer OVHcloud-E-Mail-Plattform auf eine andere migrieren](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel)
 - [E-Mail-Accounts manuell migrieren](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration)
 - [E-Mail-Accounts über OVH Mail Migrator migrieren](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm)
-- [Einen Google Mail-Account über den OVH Mail Migrator auf einen OVHcloud-E-Mail-Account migrieren](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-asia.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-asia.md
index d3028f3632d..065b1ee8c81 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-asia.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-asia.md
@@ -229,7 +229,6 @@ Want to change your [email solution](/links/web/emails) to get more space and fe
 - [Migrate your email addresses from one OVHcloud email platform to another](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrate your email address manually](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrate email accounts via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrate a Gmail account to an OVHcloud email account via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-au.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-au.md
index d3028f3632d..065b1ee8c81 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-au.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-au.md
@@ -229,7 +229,6 @@ Want to change your [email solution](/links/web/emails) to get more space and fe
 - [Migrate your email addresses from one OVHcloud email platform to another](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrate your email address manually](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrate email accounts via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrate a Gmail account to an OVHcloud email account via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-ca.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-ca.md
index d3028f3632d..065b1ee8c81 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-ca.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-ca.md
@@ -229,7 +229,6 @@ Want to change your [email solution](/links/web/emails) to get more space and fe
 - [Migrate your email addresses from one OVHcloud email platform to another](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrate your email address manually](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrate email accounts via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrate a Gmail account to an OVHcloud email account via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-gb.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-gb.md
index 6173f2800ac..e7f4975bdcd 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-gb.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-gb.md
@@ -295,7 +295,6 @@ Want to change your [email solution](/links/web/emails) to get more space and fe
 - [Migrate your email addresses from one OVHcloud email platform to another](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel)
 - [Migrate your email address manually](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration)
 - [Migrate email accounts via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm)
-- [Migrate a Gmail account to an OVHcloud email account via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail)
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-ie.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-ie.md
index badc2231bbe..c8447593b5c 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-ie.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-ie.md
@@ -295,7 +295,6 @@ Want to change your [email solution](/links/web/emails) to get more space and fe
 - [Migrate your email addresses from one OVHcloud email platform to another](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrate your email address manually](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrate email accounts via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrate a Gmail account to an OVHcloud email account via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-sg.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-sg.md
index d3028f3632d..065b1ee8c81 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-sg.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-sg.md
@@ -229,7 +229,6 @@ Want to change your [email solution](/links/web/emails) to get more space and fe
 - [Migrate your email addresses from one OVHcloud email platform to another](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrate your email address manually](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrate email accounts via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrate a Gmail account to an OVHcloud email account via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-us.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-us.md
index d3028f3632d..065b1ee8c81 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-us.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.en-us.md
@@ -229,7 +229,6 @@ Want to change your [email solution](/links/web/emails) to get more space and fe
 - [Migrate your email addresses from one OVHcloud email platform to another](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrate your email address manually](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrate email accounts via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrate a Gmail account to an OVHcloud email account via the OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.es-es.md
index ee07d161091..2fb6f6fe094 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.es-es.md
@@ -297,7 +297,6 @@ Si ha contratado [una de nuestras soluciones de correo de OVHcloud](/links/web/e
 - [Migrar las direcciones de correo electrónico de una plataforma de correo de OVHcloud a otra](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrar manualmente una dirección de correo electrónico](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrar cuentas de correo electrónico mediante OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrar una cuenta de Gmail a una cuenta de correo electrónico de OVHcloud mediante OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.es-us.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.es-us.md
index 4a93a424618..27fca2cc864 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.es-us.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.es-us.md
@@ -245,7 +245,6 @@ Si ha contratado [una de nuestras soluciones de correo de OVHcloud](/links/web/e
 - [Migrar las direcciones de correo electrónico de una plataforma de correo de OVHcloud a otra](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrar manualmente una dirección de correo electrónico](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrar cuentas de correo electrónico mediante OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrar una cuenta de Gmail a una cuenta de correo electrónico de OVHcloud mediante OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.fr-ca.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.fr-ca.md
index 4b243a67055..78f79865225 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.fr-ca.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.fr-ca.md
@@ -230,8 +230,7 @@ Vous souhaitez changer d'[offre e-mail](/links/web/emails) pour bénéficier de
 - [Migrer une adresse e-mail MX Plan vers un compte E-mail Pro ou Exchange](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrer vos adresses e-mail d'une plateforme e-mail OVHcloud vers une autre](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrer manuellement votre adresse e-mail](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
-- [Migrer des comptes e-mail via OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrer un compte Gmail vers un compte e-mail OVHcloud via OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
+- [Migrer des comptes e-mail via OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm)..
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.fr-fr.md
index 0038cd252a0..82cfd7d487b 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.fr-fr.md
@@ -297,7 +297,6 @@ Vous souhaitez changer d'[offre e-mail](/links/web/emails) pour bénéficier de
 - [Migrer vos adresses e-mail d'une plateforme e-mail OVHcloud vers une autre](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrer manuellement votre adresse e-mail](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrer des comptes e-mail via OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrer un compte Gmail vers un compte e-mail OVHcloud via OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.it-it.md
index 79206629db0..a6fa0c5e534 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.it-it.md
@@ -296,7 +296,6 @@ Per modificare il tuo [servizio di posta](/links/web/emails) e usufruire di più
 - [Migrare gli indirizzi email da una piattaforma di posta elettronica OVHcloud a un’altra](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrare manualmente l’indirizzo email](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrare account email tramite OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrare un account Gmail verso un account email OVHcloud tramite OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.pl-pl.md
index 9fe52896993..92af2c4433c 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.pl-pl.md
@@ -299,7 +299,6 @@ Chcesz zmienić [ofertę e-mail](/links/web/emails) na większą przestrzeń i w
 - [Przenoszenie adresów e-mail z jednej platformy e-mail OVHcloud na inną](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Ręczna migracja Twojego konta e-mail](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Przeniesienie kont e-mail za pomocą OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Przeniesienie konta Gmail do konta e-mail OVHcloud za pośrednictwem OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.pt-pt.md
index e2ee56ef1eb..0724c1875fb 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-emails/guide.pt-pt.md
@@ -295,7 +295,6 @@ Deseja mudar [de oferta de e-mail](/links/web/emails) para beneficiar de mais es
 - [Migrar os seus endereços de e-mail de uma plataforma de e-mail OVHcloud para outra](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_control_panel).
 - [Migrar manualmente o seu endereço de e-mail](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration).
 - [Migrar contas de e-mail através do OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/migration_omm).
-- [Migrar uma conta Gmail para uma conta de e-mail OVHcloud através do OVH Mail Migrator](/pages/web_cloud/email_and_collaborative_solutions/migrating/security_gmail).
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.de-de.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.de-de.md
index fcfcd9b9011..1e66a50321e 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.de-de.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: OVHcloud Zimbra FAQ
 excerpt: Hier finden Sie die häufigsten Fragen zur Migration der OVHcloud MX Plan Dienste nach Zimbra
-updated: 2024-11-15
+updated: 2025-11-04
 ---
 
 <style>
@@ -61,14 +61,40 @@ Besuchen Sie unsere Seite „[Zimbra-E-Mail-Adresse auf einem E-Mail-Client konf
 
 ///
 
+/// details | Wie kann ich mein Zimbra Angebot wechseln?
+
+Ihre Anforderungen ändern sich und Sie möchten mehr Funktionen für Ihr Zimbra nutzen oder benötigen sie nicht mehr. Die Zimbra Angebote sind flexibel. Folgen Sie den unten stehenden Anweisungen entsprechend Ihrer Situation:
+
+**Möchten Sie auf ein höheres Angebot wechseln?**
+
+1. Melden Sie sich bei Ihrem [OVHcloud Kundencenter](/links/manager) an.
+1. Gehen Sie in den Bereich `Web Cloud`{.action}.
+1. Klicken Sie auf `Zimbra Mail`{.action}.
+1. Klicken Sie auf `E-Mail-Konto`{.action}.
+1. Rechts neben dem E-Mail-Account, den Sie auf ein höheres Angebot wechseln möchten, klicken Sie auf `⁝`{.action}.
+1. Klicken Sie auf `Angebot wechseln`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+**Möchten Sie auf ein niedrigeres Angebot wechseln?**
+
+Die Schritte sind dieselben wie für den Wechsel zu einem höheren Angebot (siehe oben).
+
+> [!warning]
+>
+> Bevor Sie auf ein niedrigeres Angebot wechseln, stellen Sie sicher, dass folgende Punkte erfüllt sind:
+>
+> - Keine Dateien sind auf Ihrem Speichervolumen "Briefcase" gespeichert, wenn Sie auf das Angebot Starter wechseln.
+> - Der Inhalt Ihres E-Mail-Accounts muss weniger als 15 GB sein, wenn Sie auf das Angebot Starter wechseln.
+
+///
+
 ### Fragen zur Migration von MX Plan auf Zimbra
 
 Im Rahmen der Weiterentwicklung des MX Plan Angebots wird eine Migration von der derzeitigen Lösung mit Outlook Web App (OWA) auf die Zimbra Lösung und deren Webmail geplant.
 
 Wenn Sie von dieser Migration betroffen sind, finden Sie hier die häufigsten Fragen zu diesem Thema.
 
-///
-
 /// details | Was sind die Unterschiede zwischen Outlook Web App (OWA) und Zimbra Webmail?
 
 Zimbra bietet vergleichbare Funktionen und ein ähnliches Nutzererlebnis wie OWA. Eine Anleitung zur Verwendung von Zimbra finden Sie bereits unter [dieser Adresse](/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_zimbra).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.en-gb.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.en-gb.md
index 17706b4b00e..80ba20f2f4a 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.en-gb.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: OVHcloud Zimbra FAQ
 excerpt: Here you will find the most frequently asked questions about the migration of OVHcloud MX Plan solution to Zimbra
-updated: 2024-11-15
+updated: 2025-11-04
 ---
 
 <style>
@@ -61,14 +61,40 @@ Visit our page “[Configuring your Zimbra email address in an email client](/pa
 
 ///
 
+/// details | How to change my Zimbra plan ?
+
+Your needs are changing: you want to benefit from more features on your Zimbra account, or, conversely, you no longer need it. Zimbra plans are flexible, so follow the instructions below according to your situation:
+
+**Want to upgrade to a higher plan?**
+
+1. Log in to your [OVHcloud Control Panel](/links/manager).
+1. Go to the `Web Cloud`{.action} section.
+1. Click on `Zimbra Mail`{.action}.
+1. Click on the `Email account`{.action} tab.
+1. To the right of the email account for which you want to switch to a higher offer, click on `⁝`{.action}.
+1. Click on `Change plan`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+**Would you like to downgrade?**
+
+The steps are the same as for upgrading (detailed above).
+
+> [!warning]
+>
+> Before switching to a lower plan, please ensure the following:
+>
+> - No files are stored on your "Briefcase" storage volume if you are switching to the Starter plan.
+> - The content of your email account must be less than 15 GB if you are switching to the Starter plan.
+
+///
+
 ### Questions on MX Plan migration to Zimbra solution
 
 As part of the MX Plan solution upgrade, a migration is planned from the current webmail using Outlook Web App (OWA) to the Zimbra solution's webmail.
 
 If you are affected by this migration, you will find the most frequently asked questions here.
 
-///
-
 /// details | What are the differences between Outlook Web App (OWA) and Zimbra webmail?
 
 Zimbra offers similar features and a user experience close to OWA. A user guide for Zimbra is now available at [this address](/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_zimbra).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.en-ie.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.en-ie.md
index 17706b4b00e..80ba20f2f4a 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.en-ie.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: OVHcloud Zimbra FAQ
 excerpt: Here you will find the most frequently asked questions about the migration of OVHcloud MX Plan solution to Zimbra
-updated: 2024-11-15
+updated: 2025-11-04
 ---
 
 <style>
@@ -61,14 +61,40 @@ Visit our page “[Configuring your Zimbra email address in an email client](/pa
 
 ///
 
+/// details | How to change my Zimbra plan ?
+
+Your needs are changing: you want to benefit from more features on your Zimbra account, or, conversely, you no longer need it. Zimbra plans are flexible, so follow the instructions below according to your situation:
+
+**Want to upgrade to a higher plan?**
+
+1. Log in to your [OVHcloud Control Panel](/links/manager).
+1. Go to the `Web Cloud`{.action} section.
+1. Click on `Zimbra Mail`{.action}.
+1. Click on the `Email account`{.action} tab.
+1. To the right of the email account for which you want to switch to a higher offer, click on `⁝`{.action}.
+1. Click on `Change plan`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+**Would you like to downgrade?**
+
+The steps are the same as for upgrading (detailed above).
+
+> [!warning]
+>
+> Before switching to a lower plan, please ensure the following:
+>
+> - No files are stored on your "Briefcase" storage volume if you are switching to the Starter plan.
+> - The content of your email account must be less than 15 GB if you are switching to the Starter plan.
+
+///
+
 ### Questions on MX Plan migration to Zimbra solution
 
 As part of the MX Plan solution upgrade, a migration is planned from the current webmail using Outlook Web App (OWA) to the Zimbra solution's webmail.
 
 If you are affected by this migration, you will find the most frequently asked questions here.
 
-///
-
 /// details | What are the differences between Outlook Web App (OWA) and Zimbra webmail?
 
 Zimbra offers similar features and a user experience close to OWA. A user guide for Zimbra is now available at [this address](/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_zimbra).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.es-es.md
index b70b56d1927..e02dd5b8060 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: FAQ sobre la solución Zimbra OVHcloud
 excerpt: "Encuentre las preguntas sobre la migración a Zimbra para la solución MX Plan de OVHcloud"
-updated: 2024-11-15
+updated: 2025-11-04
 ---
 
 <style>
@@ -61,14 +61,40 @@ Consulte nuestra página "[Configurar una dirección de correo electrónico de Z
 
 ///
 
+/// details | ¿Cómo cambiar mi plan Zimbra?
+
+Sus necesidades cambian: desea disfrutar de más funciones en su cuenta Zimbra o, por el contrario, ya no la necesita. Las ofertas Zimbra son flexibles, siga las instrucciones que se indican a continuación en función de su situación:
+
+**¿Desea cambiar a un plan superior?**
+
+1. Inicie sesión en su [área de cliente de OVHcloud](/links/manager).
+1. Vaya a la sección `Web Cloud`{.action}.
+1. Haga clic en `Zimbra Mail`{.action}.
+1. Haga clic en la pestaña `Cuenta de correo`{.action}.
+1. A la derecha de la cuenta de correo para la que desea cambiar a un plan superior, haga clic en `⁝`{.action}.
+1. Haga clic en `Cambiar de plan`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+**¿Desea cambiar a un plan inferior?**
+
+Los pasos son los mismos que para el cambio a un plan superior (detallado anteriormente).
+
+> [!warning]
+>
+> Antes de cambiar a un plan inferior, asegúrese de los siguientes puntos:
+>
+> - No hay ningún archivo almacenado en su volumen de almacenamiento "Breifcase" si cambia a el plan Starter.
+> - El contenido de su cuenta de correo debe ser inferior a 15 Go si cambia a el plan Starter.
+
+///
+
 ### Preguntas sobre la migración MX Plan hacia la solución Zimbra
 
 Como parte de la evolución de la solución MX Plan, se ha planificado una migración desde la solución actual que utiliza el webmail Outlook Web Access (OWA) hacia la solución Zimbra y su webmail.
 
 Si esta migración le afecta, encontrará aquí las preguntas más frecuentes.
 
-///
-
 /// details | ¿En qué se diferencian los webmail Outlook Web App (OWA) y Zimbra?
 
 Zimbra ofrece las mismas funcionalidades y una usabilidad cercana a OWA. Ya está disponible una guía del usuario de Zimbra en [esta dirección](/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_zimbra).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.fr-fr.md
index cfdc07d4848..e8049935294 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: FAQ sur la solution Zimbra OVHcloud
 excerpt: "Retrouvez les questions concernant la migration vers Zimbra pour l'offre MX Plan OVHcloud"
-updated: 2024-11-15
+updated: 2025-11-05
 ---
 
 <style>
@@ -61,6 +61,34 @@ Consultez notre page « [Configurer son adresse e-mail Zimbra sur un logiciel de
 
 ///
 
+/// details | Comment changer mon offre Zimbra ?
+
+Vos besoins changent : vous souhaitez bénéficier de plus de fonctionnalités sur votre compte Zimbra, ou au contraire, vous n’en avez plus l’utilité. Les offres Zimbra sont flexibles, suivez les instructions ci-dessous en fonction de votre situation :
+
+**Vous souhaitez basculer vers une offre supérieure ?**
+
+1. Connectez-vous à votre [espace client OVHcloud](/links/manager).
+1. Rendez-vous dans la partie `Web Cloud`{.action}.
+1. Cliquez sur `Zimbra Mail`{.action}.
+1. Cliquez sur l'onglet `Compte email`{.action}.
+1. À droite du compte e-mail pour lequel vous souhaitez basculer vers l'offre supérieure, cliquez sur `⁝`{.action}.
+1. Cliquez sur `Changer d'offre`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+**Vous souhaitez basculer vers une offre inférieure ?**
+
+Les étapes sont les mêmes que pour le changement vers une offre supérieure (détaillé ci-dessus).
+
+> [!warning]
+>
+> Avant de basculer vers une offre inférieure, assurez-vous des points suivants :
+>
+> - Aucun fichier n'est stocké sur votre volume de stockage « Breifcase » si vous changez vers l'offre Starter.
+> - Le contenu de votre compte e-mail doit être inférieur à 15 Go si vous basculez vers l'offre Starter.
+
+///
+
 ### Questions sur la Migration MX Plan vers la solution Zimbra
 
 Dans le cadre de l'évolution de l'offre MX Plan, une migration est planifiée depuis la solution actuelle utilisant le webmail Outlook Web Acces (OWA) vers la solution Zimbra et son webmail.
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.it-it.md
index 61b5eef4131..5b09bcb0bd3 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Domande frequenti sulla soluzione Zimbra OVHcloud
 excerpt: "Ritrova le domande relative alla migrazione a Zimbra per il servizio MX Plan di OVHcloud"
-updated: 2024-11-15
+updated: 2025-11-04
 ---
 
 <style>
@@ -61,14 +61,40 @@ Consulta la nostra pagina "[Configurare un indirizzo email Zimbra su un client d
 
 ///
 
+/// details | Come modificare la mia offerta Zimbra ?
+
+I tuoi bisogni cambiano: desideri disporre di funzionalità aggiuntive sul tuo account Zimbra, oppure non ne hai più bisogno. Le offerte Zimbra sono flessibili, segui le istruzioni seguenti in base alla tua situazione:
+
+**Desideri passare a un piano superiore?**
+
+1. Accedi al tuo [Spazio Cliente OVHcloud](/links/manager).
+1. Vai alla sezione `Web Cloud`{.action}.
+1. Clicca su `Zimbra Mail`{.action}.
+1. Clicca sulla scheda `Account email`{.action}.
+1. A destra dell'account email per cui desideri passare a un piano superiore, clicca su `⁝`{.action}.
+1. Clicca su `Modificare soluzione`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+**Desideri passare a un piano inferiore?**
+
+Le fasi sono le stesse del cambio a un piano superiore (dettagliate sopra).
+
+> [!warning]
+>
+> Prima di passare a un piano inferiore, assicurati dei seguenti punti:
+>
+> - Nessun file è archiviato sul tuo volume di archiviazione "Briefcase" se passi all'offerta Starter.
+> - Il contenuto del tuo account email deve essere inferiore a 15 Go se passi all'offerta Starter.
+
+///
+
 ### Domande sulla migrazione MX Plan verso la soluzione Zimbra
 
 Nell'ambito dell'evoluzione dell'offerta MX Plan, dall'attuale soluzione che utilizza la webmail Outlook Web Access (OWA) è prevista una migrazione verso la soluzione Zimbra e la sua webmail.
 
 Se sei interessato da questa migrazione, qui trovi le domande più frequenti al riguardo.
 
-///
-
 /// details | Quali sono le differenze tra le Webmail Outlook Web App (OWA) e Zimbra?
 
 Zimbra offre le stesse funzionalità e un'ergonomia simile a OWA. Una guida all’utilizzo di Zimbra è già disponibile a [questo indirizzo](/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_zimbra).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.pl-pl.md
index 06d87ee435a..42bc3f3daea 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: FAQ dotyczący rozwiązania Zimbra OVHcloud
 excerpt: "Poszukaj odpowiedzi na pytania dotyczące migracji do Zimbry w ofercie MX Plan OVHcloud"
-updated: 2024-11-15
+updated: 2025-11-04
 ---
 
 <style>
@@ -61,14 +61,40 @@ Odwiedź naszą stronę "[Konfiguracja konta e-mail Zimbra w programie pocztowym
 
 ///
 
+/// details | Jak zmienić plan Zimbra?
+
+Twoje potrzeby się zmieniły: chcesz korzystać z większej liczby funkcji na swoim koncie Zimbra, albo przeciwnie, nie potrzebujesz już tylu funkcji. Oferty Zimbra są elastyczne, postępuj zgodnie z poniższymi instrukcjami w zależności od sytuacji:
+
+**Chcesz przejść na wyższy plan?**
+
+1. Zaloguj się do [panelu klienta OVHcloud](/links/manager).
+1. Przejdź do sekcji `Web Cloud`{.action}.
+1. Kliknij `Zimbra Mail`{.action}.
+1. Kliknij zakładkę `Konto e-mail`{.action}.
+1. Po prawej stronie konta e-mail, dla którego chcesz przejść na wyższą ofertę, kliknij `⁝`{.action}.
+1. Kliknij `Zmień ofertę`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+**Czy chcesz przejść na niższy plan?**
+
+Kroki są takie same jak w przypadku przejścia na wyższy plan (opisane powyżej).
+
+> [!warning]
+>
+> Przed przejściem na niższą ofertę upewnij się, że:
+>
+> - W pamięci masowej "Briefcase" nie są przechowywane żadne pliki, jeśli przechodzisz na plan Starter.
+> - Zawartość konta e-mail musi być mniejsza niż 15 GB, jeśli przechodzisz na plan Starter.
+
+///
+
 ### Pytania dotyczące migracji MX Plan na rozwiązanie Zimbra
 
 W ramach rozwoju oferty MX Plan zaplanowana jest migracja z aktualnego rozwiązania korzystającego z Webmail Outlook Web Access (OWA) na rozwiązanie Zimbra i jego interfejs webmail.
 
 Jeśli jesteś zainteresowany migracją, odnajdziesz tutaj najczęściej zadawane pytania na ten temat.
 
-///
-
 /// details | Czym się różni Webmail Outlook Web App (OWA) od Zimbry?
 
 Zimbra oferuje te same funkcje i ergonomię, co interfejs OWA. Przewodnik dotyczący korzystania z usługi Zimbra jest już dostępny pod adresem [ten adres](/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_zimbra).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.pt-pt.md
index ed4130876a8..e6c1ad5d6cb 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: FAQ sobre a solução Zimbra OVHcloud
 excerpt: "Encontre as questões relativas à migração para Zimbra para a oferta MX Plan da OVHcloud"
-updated: 2024-11-15
+updated: 2025-11-04
 ---
 
 <style>
@@ -61,14 +61,40 @@ Consulte a nossa página « [Configurar o seu endereço de e-mail Zimbra num pro
 
 ///
 
+/// details | Como alterar a minha oferta Zimbra?
+
+As suas necessidades mudam: pretende beneficiar de mais funcionalidades na sua conta Zimbra ou, pelo contrário, já não precisa delas. As ofertas Zimbra são flexíveis. Siga as instruções abaixo de acordo com a sua situação:
+
+**Pretende mudar para uma oferta superior?**
+
+1. Inicie sessão na sua [área de cliente OVHcloud](/links/manager).
+1. Dirija-se à secção `Web Cloud`{.action}.
+1. Clique em `Zimbra Mail`{.action}.
+1. Clique no separador `Conta de e-mail`{.action}.
+1. À direita da conta de correio electrónico para a qual pretende passar para uma oferta superior, clique em `⁝`{.action}.
+1. Clique em `Mudar de oferta`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+**Deseja mudar para uma oferta inferior?**
+
+Os passos são os mesmos que para mudar para uma oferta superior (detalhados acima).
+
+> [!warning]
+>
+> Antes de passar para uma oferta inferior, certifique-se dos seguintes pontos :
+>
+> - Nenhum ficheiro está armazenado no seu volume de armazenamento "Breifcase" se mudar para a oferta Starter.
+> - O conteúdo da sua conta de correio electrónico deve ser inferior a 15 Go se mudar para a oferta Starter.
+
+///
+
 ### Questões sobre a Migração MX Plan para a solução Zimbra
 
 No âmbito da evolução da oferta MX Plan, está planificada uma migração da solução atual que utiliza o webmail Outlook Web Access (OWA) para a solução Zimbra e o seu webmail.
 
 Se for afetado por esta migração, encontrará aqui as questões mais frequentes sobre esta questão.
 
-///
-
 /// details | Quais são as diferenças entre o webmail Outlook Web App (OWA) e o Zimbra?
 
 Zimbra oferece as mesmas funcionalidades e uma ergonomia semelhante ao OWA. Um guia de utilização do Zimbra está desde já disponível em [este endereço](/pages/web_cloud/email_and_collaborative_solutions/mx_plan/email_zimbra).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/images/zimbra-change-offer.png b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/images/zimbra-change-offer.png
new file mode 100644
index 00000000000..aa6b9f86400
Binary files /dev/null and b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/faq-zimbra/images/zimbra-change-offer.png differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_android/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_android/guide.fr-fr.md
index f4a8de8037b..632fa8e5d0c 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_android/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_android/guide.fr-fr.md
@@ -20,7 +20,7 @@ Les adresses e-mail de l'offre MX Plan peuvent être configurées sur différent
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_ios/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_ios/guide.fr-fr.md
index d645615e107..6f144196a64 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_ios/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_ios/guide.fr-fr.md
@@ -14,7 +14,7 @@ Les adresses e-mail de l'offre MX Plan peuvent être configurées sur un logicie
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons ce guide à votre disposition afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons ce guide à votre disposition afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 >
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_mail_macos/guide.fr-ca.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_mail_macos/guide.fr-ca.md
index 403264265be..d3d53287163 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_mail_macos/guide.fr-ca.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_mail_macos/guide.fr-ca.md
@@ -23,7 +23,7 @@ Les comptes MX Plan peuvent être configurés sur différents logiciels de messa
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/partner) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_mail_macos/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_mail_macos/guide.fr-fr.md
index 403264265be..4dc75a29e44 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_mail_macos/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_mail_macos/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes MX Plan peuvent être configurés sur différents logiciels de messa
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_outlook_2016/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_outlook_2016/guide.fr-fr.md
index a2a775718d6..5d50feacb98 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_outlook_2016/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_outlook_2016/guide.fr-fr.md
@@ -28,7 +28,7 @@ Les comptes MX Plan peuvent être configurés sur différents logiciels de messa
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 >
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 > 
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_outlook_2016_mac/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_outlook_2016_mac/guide.fr-fr.md
index fe5732a087d..07dfe9a72b0 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_outlook_2016_mac/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_outlook_2016_mac/guide.fr-fr.md
@@ -14,7 +14,7 @@ Les adresses e-mail de l'offre MX Plan peuvent être configurées sur un logicie
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 > 
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 > 
 
 ## Prérequis
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.es-es.md
index 37acf7ab79c..636cf01545c 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.es-es.md
@@ -45,7 +45,7 @@ El **nuevo Outlook** reemplaza desde el 1 de enero de 2025 a la aplicación **Co
 
 OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen en usted. Por lo tanto, es su responsabilidad asegurar su correcto funcionamiento.
 
-Le proporcionamos esta guía para acompañarlo en las tareas más comunes. Sin embargo, le recomendamos contactar a un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) y/o contactar al editor del servicio si encuentra dificultades. De hecho, no podremos proporcionarle asistencia. Más información en la sección "[Más información](#go-further)" de esta guía.
+Le proporcionamos esta guía para acompañarlo en las tareas más comunes. Sin embargo, le recomendamos contactar a un [partner especializado](/links/partner) y/o contactar al editor del servicio si encuentra dificultades. De hecho, no podremos proporcionarle asistencia. Más información en la sección "[Más información](#go-further)" de esta guía.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.es-us.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.es-us.md
index 37acf7ab79c..636cf01545c 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.es-us.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.es-us.md
@@ -45,7 +45,7 @@ El **nuevo Outlook** reemplaza desde el 1 de enero de 2025 a la aplicación **Co
 
 OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen en usted. Por lo tanto, es su responsabilidad asegurar su correcto funcionamiento.
 
-Le proporcionamos esta guía para acompañarlo en las tareas más comunes. Sin embargo, le recomendamos contactar a un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) y/o contactar al editor del servicio si encuentra dificultades. De hecho, no podremos proporcionarle asistencia. Más información en la sección "[Más información](#go-further)" de esta guía.
+Le proporcionamos esta guía para acompañarlo en las tareas más comunes. Sin embargo, le recomendamos contactar a un [partner especializado](/links/partner) y/o contactar al editor del servicio si encuentra dificultades. De hecho, no podremos proporcionarle asistencia. Más información en la sección "[Más información](#go-further)" de esta guía.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.fr-ca.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.fr-ca.md
index 89f37ee3a59..6743c4f5e64 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.fr-ca.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.fr-ca.md
@@ -45,7 +45,7 @@ Le **nouvel Outlook** remplace depuis le 1 janvier 2025 l'application **Courrier
 
 OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 
-Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/partner) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.fr-fr.md
index 89f37ee3a59..49e4441f2e5 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.fr-fr.md
@@ -45,7 +45,7 @@ Le **nouvel Outlook** remplace depuis le 1 janvier 2025 l'application **Courrier
 
 OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
 
-Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
+Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section « Aller plus loin » de ce guide.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.it-it.md
index 3ff8f46a55d..f6ee3dc5e56 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.it-it.md
@@ -45,7 +45,7 @@ Il **nuovo Outlook** sostituisce dall'1 gennaio 2025 l'applicazione **Posta** su
 
 OVHcloud mette a tua disposizione servizi di cui la configurazione, la gestione e la responsabilità ricadono su di te. Spetta quindi a te assicurarne il corretto funzionamento.
 
-Ti mettiamo a disposizione questa guida per accompagnarti nel miglior modo possibile nelle attività più comuni. Tuttavia, ti consigliamo di rivolgerti a un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) e/o di contattare l'editore del servizio se incontri difficoltà. Non saremo infatti in grado di fornirti assistenza. Ulteriori informazioni nella sezione "[Per saperne di più](#go-further)" di questa guida.
+Ti mettiamo a disposizione questa guida per accompagnarti nel miglior modo possibile nelle attività più comuni. Tuttavia, ti consigliamo di rivolgerti a un [partner specializzato](/links/partner) e/o di contattare l'editore del servizio se incontri difficoltà. Non saremo infatti in grado di fornirti assistenza. Ulteriori informazioni nella sezione "[Per saperne di più](#go-further)" di questa guida.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.pl-pl.md
index 61b2e165f09..2d6345d6f16 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.pl-pl.md
@@ -45,7 +45,7 @@ Od dnia 1 stycznia 2025 roku **nowy Outlook** zastąpił aplikację **Poczta** w
 
 OVHcloud udostępnia usługi, za których konfigurację, zarządzanie i odpowiedzialność odpowiadasz Ty. Należy więc do Ciebie zapewnić ich prawidłowe działanie.
 
-Udostępniamy tę instrukcję, aby pomóc w najczęstszych zadaniach. Jednakże, jeśli napotkasz trudności, zalecam skontaktowanie się z [partnerem specjalistą](https://marketplace.ovhcloud.com/c/support-collaboration) lub producentem usługi. Nie będziemy w stanie udzielić pomocy technicznej. Więcej informacji w sekcji "[Sprawdź również](#go-further)" tej instrukcji.
+Udostępniamy tę instrukcję, aby pomóc w najczęstszych zadaniach. Jednakże, jeśli napotkasz trudności, zalecam skontaktowanie się z [partnerem specjalistą](/links/partner) lub producentem usługi. Nie będziemy w stanie udzielić pomocy technicznej. Więcej informacji w sekcji "[Sprawdź również](#go-further)" tej instrukcji.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.pt-pt.md
index 454088d8c9e..538d1b8bc7a 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/mx_plan/how_to_configure_windows_10/guide.pt-pt.md
@@ -45,7 +45,7 @@ O **novo Outlook** substitui, desde 1º de janeiro de 2025, o aplicativo **Corre
 
 OVHcloud fornece serviços cuja configuração, gerenciamento e responsabilidade cabem a você. Portanto, é sua responsabilidade garantir o funcionamento correto.
 
-Fornecemos esta guia para ajudá-lo nas tarefas mais comuns. No entanto, recomendamos que você contate um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou o fornecedor do serviço se encontrar dificuldades. Não estaremos em condições de fornecer assistência. Mais informações na seção "[Quer saber mais?](#go-further)" desta guia.
+Fornecemos esta guia para ajudá-lo nas tarefas mais comuns. No entanto, recomendamos que você contate um [parceiro especializado](/links/partner) e/ou o fornecedor do serviço se encontrar dificuldades. Não estaremos em condições de fornecer assistência. Mais informações na seção "[Quer saber mais?](#go-further)" desta guia.
 
 ///
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.de-de.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.de-de.md
index 208c08bf0aa..d5cba9fc767 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.de-de.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: "Erste Schritte mit Zimbra"
 excerpt: "Erfahren Sie hier, wie Sie Ihr Zimbra Angebot über Ihr OVHcloud Kundencenter verwalten"
-updated: 2025-05-19
+updated: 2025-11-04
 ---
 
 <style>
@@ -38,6 +38,7 @@ Mit dem Zimbra Dienst bietet Ihnen OVHcloud eine kollaborative Open Source Messa
     - [Domainnamen bearbeiten](#domains-modify)
 - [E-Mail Accounts](#emails)
     - [E-Mail-Account erstellen](#emails-create)
+    - [Angebot ändern](#emails-offer)
 - [E-Mail-Account einsehen](#emails-consult)
 - [Weiterleitungen](#redirections)
 - [Alias](#alias)
@@ -133,6 +134,7 @@ Wählen Sie den betreffenden Tab aus:
 >>    - *MX-Eintrag automatisch konfigurieren*: Ermöglicht die automatische Eingabe der Empfangsserver von OVHcloud (gilt für alle E-Mail-Angebote von OVHcloud).
 >>    - *SPF-Eintrag automatisch konfigurieren*: Ermöglicht die automatische Eingabe des Eintrags, der den OVHcloud E-Mail-Servern den Versand Ihrer E-Mails erlaubt. Diese Registrierung gilt für alle OVHcloud E-Mail-Angebote.
 >>    - *DKIM-Eintrag automatisch konfigurieren*: Damit werden automatisch die erforderlichen Einträge für die Authentifizierung des Versands von E-Mails eingegeben.
+>>    - *SRV-Eintrag automatisch konfigurieren*: Ermöglicht die automatische Konfiguration der Parameter eines E-Mail-Accounts, wenn Sie ihn in einer E-Mail-Software (Outlook, Mail für Mac, Thunderbird usw.) hinzufügen.
 >>
 >> ![zimbra](images/zimbra_domain_add_internal02.png){.thumbnail .w-500}
 >>
@@ -167,6 +169,7 @@ Klicken Sie im Tab `Domain`{.action} Ihres Zimbra Dienstes auf das Symbol &#8285
     - **MX**: Notwendig zum Empfang Ihrer E-Mails.
     - **SPF**: Sicherheitseintrag, der von den meisten E-Mail-Empfänger-Servern verlangt wird, um die OVHcloud Server für den E-Mail-Versand mit Ihrem Domainnamen zu legitimieren.
     - **DKIM**: Ermöglicht die Einrichtung eines Signatursystems für jede E-Mail, die von Ihrem Zimbra-Dienst gesendet wird. Die Signatur wird vom Empfänger anhand des öffentlichen Schlüssels überprüft, der in Ihrer DNS-Zone hinterlegt ist.
+- **SRV**: Ermöglicht die Konfiguration Ihres Zimbra Accounts, wenn Sie ihn in einer E-Mail-Software (Outlook, Mail für Mac, Thunderbird usw.) einrichten.
 
 ![zimbra](images/zimbra_domain_modify02.png){.thumbnail .w-500}
 
@@ -218,6 +221,26 @@ Klicken Sie auf `Bestätigen`{.action}, um die Erstellung des Accounts zu starte
 
 ![zimbra](images/zimbra_emailaccounts_add.png){.thumbnail .w-500}
 
+### Angebot wechseln <a name="emails-offer"></a>
+
+Es ist möglich, jeden Zimbra Account auf ein höheres oder niedrigeres Angebot zu ändern.
+
+1. Melden Sie sich bei Ihrem [OVHcloud Kundencenter](/links/manager) an.
+1. Gehen Sie in den Bereich `Web Cloud`{.action}.
+1. Klicken Sie auf `Zimbra Mail`{.action}.
+1. Klicken Sie auf `E-Mail-Account`{.action}.
+1. Rechts neben dem E-Mail-Account, den Sie auf ein höheres Angebot wechseln möchten, klicken Sie auf `⁝`{.action}.
+1. Klicken Sie auf `Angebot wechseln`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+> [!warning]
+>
+> Bevor Sie auf ein niedrigeres Angebot wechseln, stellen Sie sicher, dass folgende Punkte erfüllt sind:
+>
+> - Keine Dateien sind auf Ihrem Speichervolumen "Aktentasche" gespeichert, wenn Sie auf das Angebot Starter wechseln.
+> - Der Inhalt Ihres E-Mail-Accounts muss weniger als 15 GB sein, wenn Sie auf das Angebot Starter wechseln.
+
 ### E-Mail-Account einsehen <a name="mail-consult"></a>
 
 Um Ihren E-Mail-Account einzusehen:
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.en-gb.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.en-gb.md
index 63b5892b7f5..c0fe9af1281 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.en-gb.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: "Getting started with the Zimbra solution"
 excerpt: "Find out how to get started with your Zimbra solution via the OVHcloud Control Panel"
-updated: 2025-05-19
+updated: 2025-11-04
 ---
 
 <style>
@@ -38,6 +38,7 @@ With the Zimbra solution, OVHcloud offers an open-source collaborative messaging
     - [Modify a domain name](#domains-modify)
 - [Email accounts](#emails)
     - [Create an email account](#emails-create)
+    - [Change plan](#emails-offer)
 - [Check your email account](#emails-consult)
 - [Redirections](#redirections)
 - [Alias](#alias)
@@ -133,6 +134,7 @@ Select the tab that corresponds to your choice:
 >>    - *Configure the MX record automatically*: This allows you to enter the OVHcloud incoming servers automatically (applies to all OVHcloud email solutions).
 >>    - *Configure the SPF record automatically*: This allows you to enter the record automatically, authorizing the OVHcloud sending email servers to send your emails. This registration is valid for all OVHcloud email solutions.
 >>    - *Configure the DKIM record automatically*: it allows you to automatically enter the records required to authenticate your email sending.
+>>    - *Automatically configure the SRV record*: it allows the automatic configuration of the parameters of an email account when you add it to an email software (Outlook, Mail for Mac, Thunderbird, etc.).
 >>
 >> ![zimbra](images/zimbra_domain_add_internal02.png){.thumbnail .w-500}
 >>
@@ -167,6 +169,7 @@ In the `Domain`{.action} tab of your Zimbra service, click on the "&#8285;" icon
     - **MX**: Essential for receiving your emails.
     - **SPF**: Security record that is required by the majority of recipient email servers to legitimize OVHcloud email sending servers with your domain name.
     - **DKIM**: Provides a signature system for each email sent by your Zimbra service. The signature is verified by the recipient using the public key visible in your DNS zone.
+    - **SRV**: Facilitates the configuration of your Zimbra account when you configure it on an email software (Outlook, Mail for Mac, Thunderbird, etc.).
 
 ![zimbra](images/zimbra_domain_modify02.png){.thumbnail .w-500}
 
@@ -218,6 +221,26 @@ Click `Confirm`{.action} to start creating the account.
 
 ![zimbra](images/zimbra_emailaccounts_add.png){.thumbnail .w-500}
 
+### Change plan <a name="emails-offer"></a>
+
+It is possible to upgrade or downgrade any Zimbra account.
+
+1. Log in to your [OVHcloud Control Panel](/links/manager).
+1. Go to the `Web Cloud`{.action} section.
+1. Click on `Zimbra Mail`{.action}.
+1. Click on the `Email account`{.action} tab.
+1. To the right of the email account for which you want to switch to a higher plan, click on `⁝`{.action}.
+1. Click on `Change plan`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+> [!warning]
+>
+> Before switching to a lower plan, make sure the following points:
+>
+> - No file is stored on your storage volume "Briefcase" if you are switching to the Starter plan.
+> - The content of your email account must be less than 15 GB if you are switching to the Starter plan.
+
 ### View your email account <a name="mail-consult"></a>
 
 To view your email account:
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.en-ie.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.en-ie.md
index 63b5892b7f5..9b23331ecd9 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.en-ie.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: "Getting started with the Zimbra solution"
 excerpt: "Find out how to get started with your Zimbra solution via the OVHcloud Control Panel"
-updated: 2025-05-19
+updated: 2025-11-04
 ---
 
 <style>
@@ -38,6 +38,7 @@ With the Zimbra solution, OVHcloud offers an open-source collaborative messaging
     - [Modify a domain name](#domains-modify)
 - [Email accounts](#emails)
     - [Create an email account](#emails-create)
+    - [Change plan](#emails-offer)
 - [Check your email account](#emails-consult)
 - [Redirections](#redirections)
 - [Alias](#alias)
@@ -132,7 +133,8 @@ Select the tab that corresponds to your choice:
 >> - **Custom configuration**: If you have already configured an email solution on your domain name, you can choose the elements that interest you.
 >>    - *Configure the MX record automatically*: This allows you to enter the OVHcloud incoming servers automatically (applies to all OVHcloud email solutions).
 >>    - *Configure the SPF record automatically*: This allows you to enter the record automatically, authorizing the OVHcloud sending email servers to send your emails. This registration is valid for all OVHcloud email solutions.
->>    - *Configure the DKIM record automatically*: it allows you to automatically enter the records required to authenticate your email sending.
+>>    - *Configure the DKIM record automatically*: it allows you to automatically enter the records required to authenticate your email sending
+>>    - *Automatically configure the SRV record*: it allows the automatic configuration of the parameters of an email account when you add it to an email software (Outlook, Mail for Mac, Thunderbird, etc.).
 >>
 >> ![zimbra](images/zimbra_domain_add_internal02.png){.thumbnail .w-500}
 >>
@@ -167,6 +169,7 @@ In the `Domain`{.action} tab of your Zimbra service, click on the "&#8285;" icon
     - **MX**: Essential for receiving your emails.
     - **SPF**: Security record that is required by the majority of recipient email servers to legitimize OVHcloud email sending servers with your domain name.
     - **DKIM**: Provides a signature system for each email sent by your Zimbra service. The signature is verified by the recipient using the public key visible in your DNS zone.
+    - **SRV**: Facilitates the configuration of your Zimbra account when you configure it on an email software (Outlook, Mail for Mac, Thunderbird, etc.).
 
 ![zimbra](images/zimbra_domain_modify02.png){.thumbnail .w-500}
 
@@ -218,6 +221,26 @@ Click `Confirm`{.action} to start creating the account.
 
 ![zimbra](images/zimbra_emailaccounts_add.png){.thumbnail .w-500}
 
+### Change plan <a name="emails-offer"></a>
+
+It is possible to upgrade or downgrade any Zimbra account.
+
+1. Log in to your [OVHcloud Control Panel](/links/manager).
+1. Go to the `Web Cloud`{.action} section.
+1. Click on `Zimbra Mail`{.action}.
+1. Click on the `Email account`{.action} tab.
+1. To the right of the email account for which you want to switch to a higher plan, click on `⁝`{.action}.
+1. Click on `Change plan`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+> [!warning]
+>
+> Before switching to a lower plan, make sure the following points:
+>
+> - No file is stored on your storage volume "Briefcase" if you are switching to the Starter plan.
+> - The content of your email account must be less than 15 GB if you are switching to the Starter plan.
+
 ### View your email account <a name="mail-consult"></a>
 
 To view your email account:
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.es-es.md
index 2c48d98ca04..45224987560 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "Primeros pasos con el producto Zimbra"
 excerpt: "Cómo empezar a utilizar la solución Zimbra desde el área de cliente de OVHcloud"
-updated: 2025-05-19
+updated: 2025-11-04
 ---
 
 <style>
@@ -38,6 +38,7 @@ Con el servicio Zimbra, OVHcloud le ofrece una plataforma de mensajería en cola
     - [Modificar un dominio](#domains-modify)
 - [Cuentas de correo electrónico](#emails)
     - [Crear una cuenta de correo electrónico](#emails-create)
+    - [Cambiar de plan](#emails-offer)
 - [Consultar la cuenta de correo](#emails-consult)
 - [Redirecciones](#redirections)
 - [Alias](#alias)
@@ -133,6 +134,7 @@ Seleccione la pestaña correspondiente a su elección:
 >>    - *Configurar el registro MX automáticamente*: Permite introducir automáticamente los servidores de recepción de OVHcloud (se aplica a todos los productos de correo de OVHcloud).
 >>    - *Configurar el registro SPF automáticamente*: Permite introducir automáticamente el registro que autoriza a los servidores de correo de envío de OVHcloud a transmitir sus mensajes de correo. Este registro es válido para todas las soluciones de correo de OVHcloud.
 >>    - *Configurar el registro DKIM automáticamente*: Permite introducir automáticamente los registros necesarios para autenticar los envíos de correo.
+>>    - *Configurar el registro SRV automáticamente* : permite la configuración automática de los parámetros de una cuenta de correo cuando la añade a un software de mensajería (Outlook, Mail para Mac, Thunderbird, etc.).
 >>
 >> ![zimbra](images/zimbra_domain_add_internal02.png){.thumbnail .w-500}
 >>
@@ -164,9 +166,10 @@ En la pestaña `Dominio`{.action} del servicio Zimbra, haga clic en el icono &#8
 
 - Haga clic en `Configurar`{.action} para modificar la organización asociada a su dominio.
 - Haga clic en `Diagnósticos`{.action} para ver la interfaz de diagnóstico de los registros DNS del dominio. Es necesario asegurarse de que no se muestran alertas para cada uno de los registros DNS mencionados en las fichas. Siga las instrucciones detalladas en cada ficha de alertas para configurar los registros DNS:
-    - **MX**: indispensable para recibir mensajes de correo.
+    - **MX**: Indispensable para recibir mensajes de correo.
     - **SPF**: Seguridad requerida por la mayoría de los servidores de correo de destino para legitimar los servidores de envío de correo de OVHcloud con su dominio.
     - **DKIM**: Permite implementar un sistema de firma para cada mensaje de correo electrónico enviado por su servicio Zimbra. El destinatario comprueba la firma con la clave pública visible en la zona DNS.
+     - **SRV** : Facilita la configuración de su cuenta Zimbra cuando la configura en un software de mensajería (Outlook, Mail para Mac, Thunderbird, etc.).
 
 ![zimbra](images/zimbra_domain_modify02.png){.thumbnail .w-500}
 
@@ -218,6 +221,26 @@ Haga clic en `Confirmar`{.action} para crear la cuenta.
 
 ![zimbra](images/zimbra_emailaccounts_add.png){.thumbnail .w-500}
 
+### Cambiar de plan <a name="emails-offer"></a>
+
+Es posible cambiar el plan de cualquier cuenta Zimbra por un plan superior o inferior.
+
+1. Inicie sesión en su [área de cliente de OVHcloud](/links/manager).
+1. Vaya a la sección `Web Cloud`{.action}.
+1. Haga clic en `Zimbra Mail`{.action}.
+1. Haga clic en la pestaña `Cuenta de correo`{.action}.
+1. A la derecha de la cuenta de correo para la que desea cambiar a un plan superior, haga clic en `⁝`{.action}.
+1. Haga clic en `Cambiar de plan`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+> [!warning]
+>
+> Antes de cambiar a un plan inferior, asegúrese de los siguientes puntos:
+>
+> - No hay ningún archivo almacenado en su volumen de almacenamiento "Maletín" si cambia a el plan Starter.
+> - El contenido de su cuenta de correo debe ser inferior a 15 Go si cambia a el plan Starter.
+
 ### Consultar su cuenta de correo <a name="mail-consult"></a>
 
 Para consultar su cuenta de correo:
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.fr-fr.md
index da41a5bc37c..5bf8aa99c31 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: "Premiers pas avec l'offre Zimbra"
 excerpt: "Découvrez comment débuter avec votre offre Zimbra depuis votre espace client OVHcloud"
-updated: 2025-05-19
+updated: 2025-11-04
 ---
 
 <style>
@@ -38,6 +38,7 @@ Avec l'offre Zimbra, OVHcloud vous propose une plateforme de messagerie collabor
     - [Modifier un nom de domaine](#domains-modify)
 - [Comptes e-mail](#emails)
     - [Créer un compte e-mail](#emails-create)
+    - [Changer d'offre](#emails-offer)
 - [Consulter son compte e-mail](#emails-consult)
 - [Redirections](#redirections)
 - [Alias](#alias)
@@ -133,6 +134,7 @@ Sélectionnez l'onglet correspondant à votre choix :
 >>    - *Configurer l'enregistrement MX automatiquement* : il permet de saisir automatiquement les serveurs de réception OVHcloud (s'applique à toutes les offres e-mail OVHcloud).
 >>    - *Configurer l'enregistrement SPF automatiquement* : il permet de saisir automatiquement l'enregistrement autorisant les serveurs e-mail d'envoi OVHcloud à transmettre vos e-mails. Cet enregistrement est valable pour l'ensemble des offres e-mail OVHcloud.
 >>    - *Configurer l'enregistrement DKIM automatiquement* : il permet de saisir automatiquement les enregistrements nécessaires pour authentifier vos envois d'e-mails.
+>>    - *Configurer l'enregistrement SRV automatiquement* : il permet la configuration automatique des paramètres d'un compte e-mail lorsque vous l'ajoutez sur un logiciel de messagerie (Outlook, Mail pour Mac, Thunderbird, etc.).
 >>
 >> ![zimbra](images/zimbra_domain_add_internal02.png){.thumbnail .w-500 .h400}
 >>
@@ -167,6 +169,7 @@ Depuis l'onglet `Domaine`{.action} de votre service Zimbra, cliquez sur l'icône
     - **MX** : indispensable pour la réception de vos e-mails.
     - **SPF** : sécurité exigée par la majorité des serveurs e-mail destinataires pour légitimer les serveurs d'envoi e-mail d'OVHcloud avec votre nom de domaine.
     - **DKIM** : permet de mettre en place un système de signature pour chaque e-mail envoyé par votre service Zimbra. La signature est vérifiée par le destinataire à l'aide de la clé publique visible dans votre zone DNS.
+    - **SRV** : facilite la configuration de votre compte Zimbra lorsque vous le configurez sur un logiciel de messagerie (Outlook, Mail pour Mac, Thunderbird, etc.).
 
 ![zimbra](images/zimbra_domain_modify02.png){.thumbnail .w-500 .h400}
 
@@ -218,6 +221,26 @@ Cliquez sur `Confirmer`{.action} pour lancer la création du compte.
 
 ![zimbra](images/zimbra_emailaccounts_add.png){.thumbnail .w-500}
 
+### Changer d'offre <a name="emails-offer"></a>
+
+Il est possible de changer l'offre de n'importe quel compte Zimbra pour une offre supérieure ou inférieure.
+
+1. Connectez-vous à votre [espace client OVHcloud](/links/manager).
+1. Rendez-vous dans la partie `Web Cloud`{.action}.
+1. Cliquez sur `Zimbra Mail`{.action}.
+1. Cliquez sur l'onglet `Compte email`{.action}.
+1. À droite du compte e-mail pour lequel vous souhaitez basculer vers l'offre supérieure, cliquez sur `⁝`{.action}.
+1. Cliquez sur `Changer d'offre`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+> [!warning]
+>
+> Avant de basculer vers une offre inférieure, assurez-vous des points suivants :
+>
+> - Aucun fichier n'est stocké sur votre volume de stockage « Malette » si vous changez vers l'offre Starter.
+> - Le contenu de votre compte e-mail doit être inférieur à 15 Go si vous basculez vers l'offre Starter.
+
 ### Consulter son compte e-mail <a name="emails-consult"></a>
 
 Pour consulter votre compte e-mail :
@@ -329,4 +352,4 @@ Pour des prestations spécialisées (référencement, développement, etc), cont
 
 Si vous souhaitez bénéficier d'une assistance à l'usage et à la configuration de vos solutions OVHcloud, nous vous proposons de consulter nos différentes [offres de support](/links/support).
 
-Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
+Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.it-it.md
index 926f1c49835..97b6bb8349e 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "Per iniziare con l'offerta Zimbra"
 excerpt: "Scopri come iniziare a utilizzare la soluzione Zimbra dallo Spazio Cliente OVHcloud"
-updated: 2025-05-19
+updated: 2025-11-04
 ---
 
 <style>
@@ -38,6 +38,7 @@ Con l'offerta Zimbra, OVHcloud ti propone una piattaforma di messaggeria collabo
     - [Modificare un dominio](#domains-modify)
 - [Account email](#emails)
     - [Crea un account email](#emails-create)
+    - [Modificare soluzione](#emails-offer)
 - [Visualizza il tuo account email](#emails-consult)
 - [Reindirizzamenti](#redirections)
 - [Alias](#alias)
@@ -133,6 +134,7 @@ Seleziona la scheda che preferisci:
 >>    - *Configurare la registrazione MX automaticamente*: permette di inserire automaticamente i server di posta in arrivo di OVHcloud (si applica a tutte le soluzioni di posta elettronica OVHcloud).
 >>    - *Configurare il record SPF automaticamente*: questa opzione permette di inserire automaticamente il record che autorizza i server di posta elettronica di invio OVHcloud a trasmettere le email. Questo record è valido per tutte le soluzioni di posta elettronica OVHcloud.
 >>    - *Configura il record DKIM automaticamente*: permette di inserire automaticamente i record necessari ad autenticare l’invio delle email.
+>>    - *Configura automaticamente l'entry SRV* : permette la configurazione automatica dei parametri di un account email quando lo aggiungi su un software di messaggistica (Outlook, Mail per Mac, Thunderbird, ecc.).
 >>
 >> ![zimbra](images/zimbra_domain_add_internal02.png){.thumbnail .w-500}
 >>
@@ -167,6 +169,7 @@ Dalla scheda `Dominio`{.action} del servizio Zimbra, clicca sull’icona "&#8285
     - **MX**: indispensabile per la ricezione delle tue email.
     - **SPF**: la sicurezza richiesta dalla maggior parte dei server di posta elettronica di destinazione per legittimare i server di posta elettronica di OVHcloud con il tuo dominio.
     - **DKIM**: permette di impostare un sistema di firma per ogni email inviata dal tuo servizio Zimbra. La firma viene verificata dal destinatario tramite la chiave pubblica visibile nella zona DNS.
+    - **SRV** : facilita la configurazione del tuo account Zimbra quando lo configuri su un software di messaggistica (Outlook, Mail per Mac, Thunderbird, ecc.).
 
 ![zimbra](images/zimbra_domain_modify02.png){.thumbnail .w-500}
 
@@ -218,6 +221,26 @@ Clicca su `Conferma`{.action} per avviare la creazione dell’account.
 
 ![zimbra](images/zimbra_emailaccounts_add.png){.thumbnail .w-500}
 
+### Modificare soluzione <a name="emails-offer"></a>
+
+È possibile cambiare piano per qualsiasi account Zimbra per un piano superiore o inferiore.
+
+1. Accedi al tuo [Spazio Cliente OVHcloud](/links/manager).
+1. Vai alla sezione `Web Cloud`{.action}.
+1. Clicca su `Zimbra Mail`{.action}.
+1. Clicca sulla scheda `Account email`{.action}.
+1. A destra dell'account email per cui desideri passare a un piano superiore, clicca su `⁝`{.action}.
+1. Clicca su `Modificare soluzione`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+> [!warning]
+>
+> Prima di passare a un piano inferiore, assicurati dei seguenti punti:
+>
+> - Nessun file è archiviato sul tuo volume di archiviazione "Valigetta" se passi all'offerta Starter.
+> - Il contenuto del tuo account email deve essere inferiore a 15 Go se passi all'offerta Starter.
+
 ### Consultare il proprio account email <a name="mail-consult"></a>
 
 Per consultare il tuo account email:
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.pl-pl.md
index 3cb6284621e..e32cc8ed9ee 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "Pierwsze kroki z ofertą Zimbra"
 excerpt: "Dowiedz się, jak rozpocząć korzystanie z oferty Zimbra z poziomu Panelu klienta OVHcloud"
-updated: 2025-05-19
+updated: 2025-11-04
 ---
 
 <style>
@@ -38,6 +38,7 @@ Z ofertą Zimbra OVHcloud oferuje platformę open source do przesyłania wiadomo
     - [Zmień domenę](#domains-modify)
 - [Konta e-mail](#emails)
     - [Utwórz konto e-mail](#emails-create)
+    - [Zmiana oferty](#emails-offer)
 - [Sprawdź konto e-mail](#emails-consult)
 - [Przekierowania](#redirections)
 - [Alias](#alias)
@@ -133,6 +134,7 @@ Wybierz kartę:
 >>    - *Skonfiguruj automatycznie rekord MX*: umożliwia automatyczne wpisanie serwerów poczty przychodzącej OVHcloud (dotyczy wszystkich ofert e-mail OVHcloud).
 >>    - *Skonfiguruj automatycznie rekord SPF*: umożliwia automatyczne wpisanie rekordu zezwalającego serwerom poczty elektronicznej OVHcloud na przesyłanie e-maili. Wpis ten dotyczy wszystkich ofert e-mail OVHcloud.
 >>    - *Automatyczna konfiguracja DKIM*: umożliwia automatyczne wprowadzenie rekordów niezbędnych do uwierzytelnienia wysyłanych wiadomości e-mail.
+>>    - *Automatyczna konfiguracja rekordu SRV* : umożliwia automatyczną konfigurację parametrów konta e-mail, gdy dodajesz go do programu pocztowego (Outlook, Mail dla Mac, Thunderbird itp.).
 >>
 >> ![Zimbra](images/zimbra_domain_add_internal02.png){.thumbnail .w-500}
 >>
@@ -167,6 +169,7 @@ W zakładce `Domena`{.action} Twojej usługi Zimbra kliknij na ikonę "&#8285;"
     - **MX**: niezbędne do odbierania e-maili.
     - **SPF**: bezpieczeństwo wymagane przez większość serwerów e-mail odbiorców, aby potwierdzić autoryzację serwerów poczty elektronicznej OVHcloud dla Twojej domeny.
     - **DKIM**: umożliwia uruchomienie systemu podpisywania wszystkich e-maili wysyłanych przez Twoją usługę Zimbra. Podpis jest weryfikowany przez odbiorcę za pomocą klucza publicznego widocznego w strefie DNS.
+    - **SRV** : Ułatwia konfigurację Twojego konta Zimbra, gdy go konfigurujesz w programie pocztowym (Outlook, Mail dla Mac, Thunderbird itp.).
 
 ![zimbra](images/zimbra_domain_modify02.png){.thumbnail .w-500}
 
@@ -218,6 +221,26 @@ Kliknij na `Potwierdź`{.action}, aby rozpocząć zakładanie konta.
 
 ![zimbra](images/zimbra_emailaccounts_add.png){.thumbnail .w-500}
 
+### Zmiana oferty <a name="emails-offer"></a>
+
+Można zmienić ofertę dowolnego konta Zimbra na wyższą lub niższą ofertę.
+
+1. Zaloguj się do [panelu klienta OVHcloud](/links/manager).
+1. Przejdź do sekcji `Web Cloud`{.action}.
+1. Kliknij `Zimbra Mail`{.action}.
+1. Kliknij zakładkę `Konto e-mail`{.action}.
+1. Po prawej stronie konta e-mail, dla którego chcesz przejść na wyższą ofertę, kliknij `⁝`{.action}.
+1. Kliknij `Zmień ofertę`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+> [!warning]
+>
+> Przed przejściem na niższą ofertę upewnij się, że:
+>
+> - Na Twoim wolumenie magazynowym "Aktówka" nie ma żadnych plików, jeśli zmieniasz ofertę na Starter.
+> - Zawartość Twojego konta e-mail musi być mniejsza niż 15 Go, jeśli przechodzisz na ofertę Starter.
+
 ### Sprawdź konto e-mail <a name="mail-consult"></a>
 
 Aby sprawdzić konto e-mail:
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.pt-pt.md
index 483e6b51792..89850c064e6 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "Primeiros passos com a oferta Zimbra"
 excerpt: "Descubra como começar com a sua oferta Zimbra a partir da Área de Cliente OVHcloud"
-updated: 2025-05-19
+updated: 2025-11-04
 ---
 
 <style>
@@ -38,6 +38,7 @@ Com a oferta Zimbra, a OVHcloud propõe-lhe uma plataforma de mensagens colabora
     - [Editar um domínio](#domains-modify)
 - [Contas de e-mail](#emails)
     - [Criar uma conta de e-mail](#emails-create)
+    - [Mudar de oferta](#emails-offer)
 - [Consultar a respetiva conta de e-mail](#emails-consult)
 - [Reencaminhamentos](#redirections)
 - [alias](#alias)
@@ -133,6 +134,7 @@ Selecione o separador correspondente à sua escolha:
 >>    - *Configurar o registo MX automaticamente*: permite introduzir automaticamente os servidores de receção OVHcloud (aplica-se a todos os serviços de e-mail OVHcloud).
 >>    - *Configurar o registo SPF automaticamente*: permite introduzir automaticamente o registo que autoriza os servidores de e-mail de envio da OVHcloud a reencaminhar os seus e-mails. Este registo é válido para o conjunto das ofertas de e-mail OVHcloud.
 >>    - *Configurar o registo DKIM automaticamente*: permite introduzir automaticamente os registos necessários para autenticar os seus envios de e-mails.
+>>    - *Configurar o registo SRV automaticamente* : permite a configuração automática dos parâmetros de uma conta de correio electrónico quando a adiciona num software de mensagens (Outlook, Mail para Mac, Thunderbird, etc.).
 >>
 >> ![zimbra](images/zimbra_domain_add_internal02.png){.thumbnail .w-500}
 >>
@@ -167,6 +169,7 @@ No separador `Domínio`{.action} do seu serviço Zimbra, clique no ícone «&#82
     - **MX**: indispensável para a receção dos seus e-mails.
     - **SPF**: segurança exigida pela maioria dos servidores de e-mail de destino para legitimar os servidores de envio de e-mail da OVHcloud com o seu nome de domínio.
     - **DKIM**: permite implementar um sistema de assinatura para cada e-mail enviado pelo seu serviço Zimbra. A assinatura é verificada pelo destinatário graças à chave pública visível na sua zona DNS.
+     - **SRV** : facilita a configuração da sua conta Zimbra quando a configura em um software de mensagens (Outlook, Mail para Mac, Thunderbird, etc.).
 
 ![zimbra](images/zimbra_domain_modify02.png){.thumbnail .w-500}
 
@@ -218,6 +221,26 @@ Clique em `Confirmar`{.action} para lançar a criação da conta.
 
 ![zimbra](images/zimbra_emailaccounts_add.png){.thumbnail .w-500}
 
+### Mudar de oferta <a name="emails-offer"></a>
+
+É possível alterar a oferta de qualquer conta Zimbra para uma oferta superior ou inferior.
+
+1. Inicie sessão na sua [área de cliente OVHcloud](/links/manager).
+1. Dirija-se à secção `Web Cloud`{.action}.
+1. Clique em `Zimbra Mail`{.action}.
+1. Clique no separador `Conta de e-mail`{.action}.
+1. À direita da conta de correio electrónico para a qual pretende passar para uma oferta superior, clique em `⁝`{.action}.
+1. Clique em `Mudar de oferta`{.action}.
+
+![Zimbra](images/zimbra-change-offer.png){.thumbnail .w-500}
+
+> [!warning]
+>
+> Antes de passar para uma oferta inferior, certifique-se dos seguintes pontos :
+>
+> - Nenhum ficheiro está armazenado no seu volume de armazenamento « Porta-documentos » se mudar para a oferta Starter.
+> - O conteúdo da sua conta de correio electrónico deve ser inferior a 15 Go se mudar para a oferta Starter.
+
 ### Consultar a conta de e-mail <a name="mail-consult"></a>
 
 Para consultar a sua conta de e-mail:
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra-change-offer.png b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra-change-offer.png
new file mode 100644
index 00000000000..aa6b9f86400
Binary files /dev/null and b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra-change-offer.png differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra_domain_add_internal02.png b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra_domain_add_internal02.png
index f4408109c63..30c9d84d223 100644
Binary files a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra_domain_add_internal02.png and b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra_domain_add_internal02.png differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra_domain_modify02.png b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra_domain_modify02.png
index bbb0e2c50b6..e001a835d02 100644
Binary files a/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra_domain_modify02.png and b/pages/web_cloud/email_and_collaborative_solutions/zimbra/getting_started_zimbra/images/zimbra_domain_modify02.png differ
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.es-es.md
index 8d7c49d1dae..dcb16e80852 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.es-es.md
@@ -23,7 +23,7 @@ Las cuentas de correo electrónico de Zimbra Pro pueden configurarse en un móvi
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Es su responsabilidad garantizar que estos servicios funcionen correctamente.
 >
-> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
+> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.fr-fr.md
index cc25b47f61c..935280d9c35 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes e-mail Zimbra Pro peuvent être configurés sur un mobile Android en
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il est de votre responsabilité d'assurer le bon fonctionnement de ces services.
 >
-> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
+> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.it-it.md
index 28adb49e577..304dc9d4f9c 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.it-it.md
@@ -23,7 +23,7 @@ Gli account email Zimbra Pro possono essere configurati su un cellulare Android
 >
 > OVHcloud mette a disposizione i servizi ma non si occupa della loro configurazione e gestione. Garantire il corretto funzionamento di questi servizi è responsabilità dell’utente.
 >
-> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
+> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](/links/partner) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
 
 ## Prerequisiti
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.pl-pl.md
index 8b1ac6d446c..0123e3515e0 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.pl-pl.md
@@ -23,7 +23,7 @@ Konta e-mail Zimbra Pro można skonfigurować na urządzeniu z systemem Android
 >
 > OVHcloud udostępnia różnorodne usługi, jednak to Ty odpowiadasz za ich konfigurację i zarządzanie nimi. Twoim obowiązkiem jest zapewnienie właściwego funkcjonowania tych usług.
 >
-> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](https://marketplace.ovhcloud.com/c/support-collaboration) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
+> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](/links/partner) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
 
 ## Wymagania początkowe
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.pt-pt.md
index 7820f005ba1..3e145682fec 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_gmail_app_android/guide.pt-pt.md
@@ -23,7 +23,7 @@ As contas de e-mail Zimbra Pro podem ser configuradas em dispositivos móveis An
 >
 > A OVHcloud oferece-lhe serviços cuja configuração, gestão e responsabilidade é da sua responsabilidade. É da sua responsabilidade assegurar o bom funcionamento destes serviços.
 >
-> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
+> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](/links/partner) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.es-es.md
index d70d36023ff..6d68439a463 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.es-es.md
@@ -23,7 +23,7 @@ Las cuentas Zimbra Pro pueden configurarse en un iPhone o iPad utilizando el pro
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Es su responsabilidad garantizar que estos servicios funcionen correctamente.
 >
-> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
+> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.fr-fr.md
index 31cacb10208..db9aed02b77 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes Zimbra Pro peuvent être configurés sur un iPhone ou un iPad en uti
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il est de votre responsabilité d'assurer le bon fonctionnement de ces services.
 >
-> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
+> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.it-it.md
index c5a18f34ba2..5251588b8ff 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.it-it.md
@@ -23,7 +23,7 @@ Gli account Zimbra Pro possono essere configurati su un iPhone o un iPad utilizz
 >
 > OVHcloud mette a disposizione i servizi ma non si occupa della loro configurazione e gestione. Garantire il corretto funzionamento di questi servizi è responsabilità dell’utente.
 >
-> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
+> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](/links/partner) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
 
 ## Prerequisiti
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.pl-pl.md
index 0d5777c9bc9..ef216d6ddb2 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.pl-pl.md
@@ -23,7 +23,7 @@ Konta Zimbra Pro można skonfigurować na urządzeniu iPhone lub iPad przy użyc
 >
 > OVHcloud udostępnia różnorodne usługi, jednak to Ty odpowiadasz za ich konfigurację i zarządzanie nimi. Twoim obowiązkiem jest zapewnienie właściwego funkcjonowania tych usług.
 >
-> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](https://marketplace.ovhcloud.com/c/support-collaboration) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
+> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](/links/partner) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
 
 ## Wymagania początkowe
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.pt-pt.md
index 4c0545ef269..d6b21849a1b 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_app_ios/guide.pt-pt.md
@@ -23,7 +23,7 @@ As contas Zimbra Pro podem ser configuradas num iPhone ou num iPad utilizando o
 >
 > A OVHcloud oferece-lhe serviços cuja configuração, gestão e responsabilidade é da sua responsabilidade. É da sua responsabilidade assegurar o bom funcionamento destes serviços.
 >
-> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
+> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](/links/partner) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.es-es.md
index 409bd00ad4d..aa026fb2d39 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.es-es.md
@@ -23,7 +23,7 @@ Las cuentas Zimbra Pro pueden configurarse en un macOS utilizando el protocolo E
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Es su responsabilidad garantizar que estos servicios funcionen correctamente.
 >
-> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
+> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.fr-fr.md
index b15282c6126..2ac07317f59 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes Zimbra Pro peuvent être configurés sur un macOS en utilisant le pr
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il est de votre responsabilité d'assurer le bon fonctionnement de ces services.
 >
-> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
+> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.it-it.md
index 8e404a534ee..82d35cd23e0 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.it-it.md
@@ -23,7 +23,7 @@ Gli account Zimbra Pro possono essere configurati su un macOS utilizzando il pro
 >
 > OVHcloud mette a disposizione i servizi ma non si occupa della loro configurazione e gestione. Garantire il corretto funzionamento di questi servizi è responsabilità dell’utente.
 >
-> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
+> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](/links/partner) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
 
 ## Prerequisiti
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.pl-pl.md
index 677fc684d8b..1ab0ae6893c 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.pl-pl.md
@@ -23,7 +23,7 @@ Konta Zimbra Pro można skonfigurować w systemie macOS przy użyciu protokołu
 >
 > OVHcloud udostępnia różnorodne usługi, jednak to Ty odpowiadasz za ich konfigurację i zarządzanie nimi. Twoim obowiązkiem jest zapewnienie właściwego funkcjonowania tych usług.
 >
-> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](https://marketplace.ovhcloud.com/c/support-collaboration) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
+> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](/links/partner) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
 
 ## Wymagania początkowe
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.pt-pt.md
index 4b7aae74ffb..b33677359b7 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_mail_macos/guide.pt-pt.md
@@ -23,7 +23,7 @@ As contas Zimbra Pro podem ser configuradas num macOS utilizando o protocolo EWS
 >
 > A OVHcloud oferece-lhe serviços cuja configuração, gestão e responsabilidade é da sua responsabilidade. É da sua responsabilidade assegurar o bom funcionamento destes serviços.
 >
-> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
+> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](/links/partner) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.es-es.md
index e45269f6231..ba022d8e31a 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.es-es.md
@@ -23,7 +23,7 @@ Las cuentas Zimbra Pro pueden configurarse en un móvil Android utilizando el pr
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Es su responsabilidad garantizar que estos servicios funcionen correctamente.
 >
-> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
+> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.fr-fr.md
index 6070a9c7674..69c3886dd5c 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes Zimbra Pro peuvent être configurés sur un mobile Android en utilis
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il est de votre responsabilité d'assurer le bon fonctionnement de ces services.
 >
-> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
+> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.it-it.md
index 9dedd745a78..004fba6d048 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.it-it.md
@@ -23,7 +23,7 @@ Gli account Zimbra Pro possono essere configurati su un cellulare Android utiliz
 >
 > OVHcloud mette a disposizione i servizi ma non si occupa della loro configurazione e gestione. Garantire il corretto funzionamento di questi servizi è responsabilità dell’utente.
 >
-> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
+> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](/links/partner) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
 
 ## Prerequisiti
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.pl-pl.md
index 30b94287055..bb037e06510 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.pl-pl.md
@@ -23,7 +23,7 @@ Konta Zimbra Pro można skonfigurować na urządzeniu z systemem Android przy u
 >
 > OVHcloud udostępnia różnorodne usługi, jednak to Ty odpowiadasz za ich konfigurację i zarządzanie nimi. Twoim obowiązkiem jest zapewnienie właściwego funkcjonowania tych usług.
 >
-> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](https://marketplace.ovhcloud.com/c/support-collaboration) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
+> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](/links/partner) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
 
 ## Wymagania początkowe
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.pt-pt.md
index 45f8f395d70..7ba050c7050 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_android/guide.pt-pt.md
@@ -23,7 +23,7 @@ As contas do Zimbra Pro podem ser configuradas em dispositivos móveis Android u
 >
 > A OVHcloud oferece-lhe serviços cuja configuração, gestão e responsabilidade é da sua responsabilidade. É da sua responsabilidade assegurar o bom funcionamento destes serviços.
 >
-> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
+> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](/links/partner) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.es-es.md
index 1bc9a6f46b1..f3084afeb8f 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.es-es.md
@@ -23,7 +23,7 @@ Las cuentas Zimbra Pro pueden configurarse en un iPhone utilizando el protocolo
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Es su responsabilidad garantizar que estos servicios funcionen correctamente.
 >
-> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
+> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.fr-fr.md
index 2bf82205206..ecc7e19f1c1 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes Zimbra Pro peuvent être configurés sur un iPhone en utilisant le p
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il est de votre responsabilité d'assurer le bon fonctionnement de ces services.
 >
-> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
+> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.it-it.md
index cb21a042105..c03da08fe8a 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.it-it.md
@@ -23,7 +23,7 @@ Gli account Zimbra Pro possono essere configurati su un iPhone utilizzando il pr
 >
 > OVHcloud mette a disposizione i servizi ma non si occupa della loro configurazione e gestione. Garantire il corretto funzionamento di questi servizi è responsabilità dell’utente.
 >
-> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
+> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](/links/partner) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
 
 ## Prerequisiti
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.pl-pl.md
index aab8f6f665b..3203b822255 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.pl-pl.md
@@ -23,7 +23,7 @@ Konta Zimbra Pro można skonfigurować na urządzeniu iPhone za pomocą protoko
 >
 > OVHcloud udostępnia różnorodne usługi, jednak to Ty odpowiadasz za ich konfigurację i zarządzanie nimi. Twoim obowiązkiem jest zapewnienie właściwego funkcjonowania tych usług.
 >
-> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](https://marketplace.ovhcloud.com/c/support-collaboration) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
+> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](/links/partner) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
 
 ## Wymagania początkowe
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.pt-pt.md
index b92f21875c6..70a526be275 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_app_ios/guide.pt-pt.md
@@ -23,7 +23,7 @@ As contas Zimbra Pro podem ser configuradas num iPhone utilizando o protocolo At
 >
 > A OVHcloud oferece-lhe serviços cuja configuração, gestão e responsabilidade é da sua responsabilidade. É da sua responsabilidade assegurar o bom funcionamento destes serviços.
 >
-> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
+> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](/links/partner) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.es_es.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.es_es.md
index 8d3cd7f3fe2..da5436d18e9 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.es_es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.es_es.md
@@ -23,7 +23,7 @@ Las cuentas Zimbra Pro pueden configurarse en un Mac utilizando el protocolo EWS
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Es su responsabilidad garantizar que estos servicios funcionen correctamente.
 >
-> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
+> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.fr-fr.md
index d8a870553ab..e9d08b9acfb 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes Zimbra Pro peuvent être configurés sur un Mac en utilisant le prot
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il est de votre responsabilité d'assurer le bon fonctionnement de ces services.
 >
-> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
+> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide .
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.it-it.md
index a7d241e25bb..f0ffa8c2497 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.it-it.md
@@ -23,7 +23,7 @@ Gli account Zimbra Pro possono essere configurati su un Mac utilizzando il proto
 >
 > OVHcloud mette a disposizione i servizi ma non si occupa della loro configurazione e gestione. Garantire il corretto funzionamento di questi servizi è responsabilità dell’utente.
 >
-> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
+> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](/links/partner) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
 
 ## Prerequisiti
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.pl-pl.md
index d36f1bf9e18..52550d07f05 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.pl-pl.md
@@ -23,7 +23,7 @@ Konta Zimbra Pro można skonfigurować na komputerze Mac za pomocą protokołu E
 >
 > OVHcloud udostępnia różnorodne usługi, jednak to Ty odpowiadasz za ich konfigurację i zarządzanie nimi. Twoim obowiązkiem jest zapewnienie właściwego funkcjonowania tych usług.
 >
-> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](https://marketplace.ovhcloud.com/c/support-collaboration) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
+> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](/links/partner) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
 
 ## Wymagania początkowe
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.pt-pt.md
index d7375902764..a23483b4eda 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_macos/guide.pt-pt.md
@@ -23,7 +23,7 @@ As contas Zimbra Pro podem ser configuradas num Mac utilizando o protocolo EWS (
 >
 > A OVHcloud oferece-lhe serviços cuja configuração, gestão e responsabilidade é da sua responsabilidade. É da sua responsabilidade assegurar o bom funcionamento destes serviços.
 >
-> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
+> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](/links/partner) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.es-es.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.es-es.md
index f948a91432b..2afbbee2d09 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.es-es.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.es-es.md
@@ -23,7 +23,7 @@ Las cuentas Zimbra Pro pueden configurarse en Windows utilizando el protocolo Ac
 >
 > OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. Es su responsabilidad garantizar que estos servicios funcionen correctamente.
 >
-> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](https://marketplace.ovhcloud.com/c/support-collaboration) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
+> Esta guía está diseñada para ayudarle a realizar tareas comunes. No obstante, si necesita ayuda, le recomendamos que contacte con un [partner especializado](/links/partner) o con el editor del servicio. Nosotros no podremos asistirle. Para más información, consulte la sección "[Más información](#go-further)" de esta guía.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.fr-fr.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.fr-fr.md
index 303af4b7606..717116adf70 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.fr-fr.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.fr-fr.md
@@ -23,7 +23,7 @@ Les comptes Zimbra Pro peuvent être configurés sur Windows en utilisant le pro
 >
 > OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il est de votre responsabilité d'assurer le bon fonctionnement de ces services.
 >
-> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](https://marketplace.ovhcloud.com/c/support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide.
+> Ce guide est conçu pour vous aider à accomplir des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [partenaire spécialisé](/links/transversal/marketplace-support-collaboration) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Pour plus d'informations, consultez la section « [Aller plus loin](#go-further) » de ce guide.
 
 ## Prérequis
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.it-it.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.it-it.md
index 25aae2ab747..e96888fcfba 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.it-it.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.it-it.md
@@ -23,7 +23,7 @@ Gli account Zimbra Pro possono essere configurati su Windows utilizzando il prot
 >
 > OVHcloud mette a disposizione i servizi ma non si occupa della loro configurazione e gestione. Garantire il corretto funzionamento di questi servizi è responsabilità dell’utente.
 >
-> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](https://marketplace.ovhcloud.com/c/support-collaboration) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
+> Questa guida è progettata per aiutarvi a svolgere le attività più comuni. Tuttavia, in caso di difficoltà o dubbi, ti consigliamo di contattare un [partner specializzato](/links/partner) o il fornitore del servizio. Non saremo infatti in grado di fornirti assistenza. Per maggiori informazioni, consulta la sezione "[Per saperne di più](#go-further)" di questa guida.
 
 ## Prerequisiti
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.pl-pl.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.pl-pl.md
index b1bb0fb7fab..172209dfad9 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.pl-pl.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.pl-pl.md
@@ -23,7 +23,7 @@ Konta Zimbra Pro można skonfigurować w systemie Windows za pomocą protokołu
 >
 > OVHcloud udostępnia różnorodne usługi, jednak to Ty odpowiadasz za ich konfigurację i zarządzanie nimi. Twoim obowiązkiem jest zapewnienie właściwego funkcjonowania tych usług.
 >
-> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](https://marketplace.ovhcloud.com/c/support-collaboration) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
+> Ten przewodnik ma na celu pomóc w wykonywaniu typowych zadań. Niemniej jednak, w przypadku trudności zalecamy skontaktowanie się z [partnerem wyspecjalizowanym](/links/partner) i/lub skontaktowanie się z wydawcą usługi. Niestety firma OVH nie jest w stanie udzielić Ci wsparcia w tym zakresie. Więcej informacji zawiera sekcja "[Sprawdź również](#go-further)" w tym przewodniku.
 
 ## Wymagania początkowe
 
diff --git a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.pt-pt.md b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.pt-pt.md
index c35d395db65..9623fc4092e 100644
--- a/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.pt-pt.md
+++ b/pages/web_cloud/email_and_collaborative_solutions/zimbra/zimbra_outlook_windows/guide.pt-pt.md
@@ -23,7 +23,7 @@ As contas Zimbra Pro podem ser configuradas no Windows utilizando o protocolo At
 >
 > A OVHcloud oferece-lhe serviços cuja configuração, gestão e responsabilidade é da sua responsabilidade. É da sua responsabilidade assegurar o bom funcionamento destes serviços.
 >
-> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](https://marketplace.ovhcloud.com/c/support-collaboration) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
+> Este manual foi concebido para o ajudar a realizar tarefas comuns. No entanto, se encontrar dificuldades, recomendamos que recorra a um [parceiro especializado](/links/partner) e/ou que contacte o editor do serviço. Não poderemos proporcionar-lhe assistência técnica. Para mais informações, consulte "[Quer saber mais?](#go-further)" deste guia.
 
 ## Requisitos
 
diff --git a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-asia.md b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-asia.md
index d44936c6c74..d3fcf72bb39 100644
--- a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-asia.md
+++ b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-asia.md
@@ -94,7 +94,7 @@ All diagnostics in step 1 must be performed **without exception** to determine w
 
 To ensure that your services (shared hosting **and** database) are not undergoing maintenance or an incident, retrieve the cluster and filer information of your web hosting as well as the general information relating to your database. You can then check their status at [status.ovhcloud.com](https://web-cloud.status-ovhcloud.com/).
 
-o find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
+To find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
 
 ![Retrieve Filer](/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/general-information/find-filer.png){.thumbnail}
 
diff --git a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-au.md b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-au.md
index d44936c6c74..d3fcf72bb39 100644
--- a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-au.md
+++ b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-au.md
@@ -94,7 +94,7 @@ All diagnostics in step 1 must be performed **without exception** to determine w
 
 To ensure that your services (shared hosting **and** database) are not undergoing maintenance or an incident, retrieve the cluster and filer information of your web hosting as well as the general information relating to your database. You can then check their status at [status.ovhcloud.com](https://web-cloud.status-ovhcloud.com/).
 
-o find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
+To find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
 
 ![Retrieve Filer](/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/general-information/find-filer.png){.thumbnail}
 
diff --git a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-ca.md b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-ca.md
index d44936c6c74..d3fcf72bb39 100644
--- a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-ca.md
+++ b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-ca.md
@@ -94,7 +94,7 @@ All diagnostics in step 1 must be performed **without exception** to determine w
 
 To ensure that your services (shared hosting **and** database) are not undergoing maintenance or an incident, retrieve the cluster and filer information of your web hosting as well as the general information relating to your database. You can then check their status at [status.ovhcloud.com](https://web-cloud.status-ovhcloud.com/).
 
-o find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
+To find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
 
 ![Retrieve Filer](/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/general-information/find-filer.png){.thumbnail}
 
diff --git a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-ie.md b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-ie.md
index 1079bbb93f9..a00c0b6df6e 100644
--- a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-ie.md
+++ b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-ie.md
@@ -94,7 +94,7 @@ All diagnostics in step 1 must be performed **without exception** to determine w
 
 To ensure that your services (shared hosting **and** database) are not undergoing maintenance or an incident, retrieve the cluster and filer information of your web hosting as well as the general information relating to your database. You can then check their status at [status.ovhcloud.com](https://web-cloud.status-ovhcloud.com/).
 
-o find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
+To find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
 
 ![Retrieve Filer](/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/general-information/find-filer.png){.thumbnail}
 
diff --git a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-sg.md b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-sg.md
index d44936c6c74..d3fcf72bb39 100644
--- a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-sg.md
+++ b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-sg.md
@@ -94,7 +94,7 @@ All diagnostics in step 1 must be performed **without exception** to determine w
 
 To ensure that your services (shared hosting **and** database) are not undergoing maintenance or an incident, retrieve the cluster and filer information of your web hosting as well as the general information relating to your database. You can then check their status at [status.ovhcloud.com](https://web-cloud.status-ovhcloud.com/).
 
-o find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
+To find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
 
 ![Retrieve Filer](/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/general-information/find-filer.png){.thumbnail}
 
diff --git a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-us.md b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-us.md
index d44936c6c74..d3fcf72bb39 100644
--- a/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-us.md
+++ b/pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-us.md
@@ -94,7 +94,7 @@ All diagnostics in step 1 must be performed **without exception** to determine w
 
 To ensure that your services (shared hosting **and** database) are not undergoing maintenance or an incident, retrieve the cluster and filer information of your web hosting as well as the general information relating to your database. You can then check their status at [status.ovhcloud.com](https://web-cloud.status-ovhcloud.com/).
 
-o find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
+To find out the cluster and filer of your hosting, log in to your [OVHcloud Control Panel](/links/manager), go to the `Web Cloud`{.action} section, click on `Hosting plans`{.action} then select the web hosting plan concerned. In the `General information`{.action} tab you can see the `Datacenter` and `Filer` of your web hosting.
 
 ![Retrieve Filer](/pages/assets/screens/control_panel/product-selection/web-cloud/web-hosting/general-information/find-filer.png){.thumbnail}
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.de-de.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.de-de.md
index 90d2ffbdb21..0935beceaee 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.de-de.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: "Webhosting - Ändern von mit einem Webhosting verbundenen Domainnamen"
 excerpt: "Erfahren Sie hier, wie Sie die Zuordnungseinstellungen von Domainnamen oder Subdomains ändern, die bereits auf Ihrem Webhosting deklariert sind"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Ziel
@@ -84,12 +84,6 @@ In diesem Formular müssen Sie also den Namen des vorausgefüllten Ordners durch
 
 #### Weitere Optionen verfügbar
 
-##### Die Option "SSL"
-
-Aktivieren/deaktivieren Sie diese Option nur, wenn Sie das kostenlose **Let's Encrypt** SSL für Ihre Domain/Subdomain aktivieren/deaktivieren möchten. Bei anderen SSL-Angeboten von OVHcloud muss diese Option nicht aktiviert werden.
-
-Weitere Informationen zu den verfügbaren SSL-Optionen/-Angeboten finden Sie in unserer Dokumentation „[SSL-Zertifikat auf einem Webhosting verwalten](/pages/web_cloud/web_hosting/ssl_on_webhosting)“.
-
 ##### Die Option "CDN aktivieren"
 
 Um diese Option nutzen zu können, müssen Sie zuerst ein CDN von OVHcloud abonniert haben oder über ein Performance Webhosting verfügen.
@@ -128,7 +122,7 @@ Wenn alle Einstellungen Ihren Wünschen entsprechen, klicken Sie auf `Bestätige
 
 Abhängig von den ausgewählten Optionen kann es einige Minuten bis zu einigen Stunden dauern, bis die Änderungen wirksam werden.
 
-Wenn die Änderungen für die Optionen **SSL**, **CDN**, **IP des Landes** und **Getrennte Logs** nach 24 Stunden nicht wirksam werden, nutzen Sie die entsprechenden Wissensressourcen für alle Optionen in [Schritt 1](#step1), um sicherzustellen, dass alle Anforderungen erfüllt wurden.
+Wenn die Änderungen für die Optionen **CDN**, **IP des Landes** und **Getrennte Logs** nach 24 Stunden nicht wirksam werden, nutzen Sie die entsprechenden Wissensressourcen für alle Optionen in [Schritt 1](#step1), um sicherzustellen, dass alle Anforderungen erfüllt wurden.
 
 ## Weiterführende Informationen
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-asia.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-asia.md
index df06959bc1a..1ea4769c0ca 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-asia.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: "Web Hosting - How to modify a domain name already associated to a hosting plan"
 excerpt: "Find out how to change the association settings for a domainname or subdomain already declared on your web hosting plan"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -84,12 +84,6 @@ In this form, replace the name of the pre-filled folder with the name of the new
 
 #### Other options available
 
-##### The "SSL" option
-
-Tick/untick this box only if you want to enable/disable free SSL **Let's Encrypt** for your domainname or subdomain. You do not need to tick this box for the other SSL solutions offered with OVHcloud.
-
-You can find more information on SSL options and offers in our dedicated documentation “[Managing SSL certificates on a web hosting plan](/pages/web_cloud/web_hosting/ssl_on_webhosting)”.
-
 ##### The "Activate the CDN" option
 
 To use this option, you must have already subscribed to an OVHcloud CDN solution, or have a Performance web hosting plan.
@@ -122,7 +116,7 @@ If all the settings are configured as you want, click the `Confirm`{.action} but
 
 Depending on the options you have selected, the changes may take between a few minutes and a few hours to be applied.
 
-If modifications of the **SSL**, **CDN**, **Country IP** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
+If modifications of the **CDN** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
 
 ## Go further
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-au.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-au.md
index df06959bc1a..1ea4769c0ca 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-au.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: "Web Hosting - How to modify a domain name already associated to a hosting plan"
 excerpt: "Find out how to change the association settings for a domainname or subdomain already declared on your web hosting plan"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -84,12 +84,6 @@ In this form, replace the name of the pre-filled folder with the name of the new
 
 #### Other options available
 
-##### The "SSL" option
-
-Tick/untick this box only if you want to enable/disable free SSL **Let's Encrypt** for your domainname or subdomain. You do not need to tick this box for the other SSL solutions offered with OVHcloud.
-
-You can find more information on SSL options and offers in our dedicated documentation “[Managing SSL certificates on a web hosting plan](/pages/web_cloud/web_hosting/ssl_on_webhosting)”.
-
 ##### The "Activate the CDN" option
 
 To use this option, you must have already subscribed to an OVHcloud CDN solution, or have a Performance web hosting plan.
@@ -122,7 +116,7 @@ If all the settings are configured as you want, click the `Confirm`{.action} but
 
 Depending on the options you have selected, the changes may take between a few minutes and a few hours to be applied.
 
-If modifications of the **SSL**, **CDN**, **Country IP** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
+If modifications of the **CDN** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
 
 ## Go further
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-ca.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-ca.md
index df06959bc1a..1ea4769c0ca 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-ca.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "Web Hosting - How to modify a domain name already associated to a hosting plan"
 excerpt: "Find out how to change the association settings for a domainname or subdomain already declared on your web hosting plan"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -84,12 +84,6 @@ In this form, replace the name of the pre-filled folder with the name of the new
 
 #### Other options available
 
-##### The "SSL" option
-
-Tick/untick this box only if you want to enable/disable free SSL **Let's Encrypt** for your domainname or subdomain. You do not need to tick this box for the other SSL solutions offered with OVHcloud.
-
-You can find more information on SSL options and offers in our dedicated documentation “[Managing SSL certificates on a web hosting plan](/pages/web_cloud/web_hosting/ssl_on_webhosting)”.
-
 ##### The "Activate the CDN" option
 
 To use this option, you must have already subscribed to an OVHcloud CDN solution, or have a Performance web hosting plan.
@@ -122,7 +116,7 @@ If all the settings are configured as you want, click the `Confirm`{.action} but
 
 Depending on the options you have selected, the changes may take between a few minutes and a few hours to be applied.
 
-If modifications of the **SSL**, **CDN**, **Country IP** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
+If modifications of the **CDN** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
 
 ## Go further
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-gb.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-gb.md
index b36c2e55c39..6937c1aae87 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-gb.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: "Web Hosting - How to modify a domain name already associated to a hosting plan"
 excerpt: "Find out how to change the association settings for a domainname or subdomain already declared on your web hosting plan"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -84,12 +84,6 @@ In this form, replace the name of the pre-filled folder with the name of the new
 
 #### Other options available
 
-##### The "SSL" option
-
-Tick/untick this box only if you want to enable/disable free SSL **Let's Encrypt** for your domainname or subdomain. You do not need to tick this box for the other SSL solutions offered with OVHcloud.
-
-You can find more information on SSL options and offers in our dedicated documentation “[Managing SSL certificates on a web hosting plan](/pages/web_cloud/web_hosting/ssl_on_webhosting)”.
-
 ##### The "Activate the CDN" option
 
 To use this option, you must have already subscribed to an OVHcloud CDN solution, or have a Performance web hosting plan.
@@ -128,7 +122,7 @@ If all the settings are configured as you want, click the `Confirm`{.action} but
 
 Depending on the options you have selected, the changes may take between a few minutes and a few hours to be applied.
 
-If modifications of the **SSL**, **CDN**, **Country IP** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
+If modifications of the **CDN**, **Country IP** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
 
 ## Go further
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-ie.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-ie.md
index b36c2e55c39..6937c1aae87 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-ie.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: "Web Hosting - How to modify a domain name already associated to a hosting plan"
 excerpt: "Find out how to change the association settings for a domainname or subdomain already declared on your web hosting plan"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -84,12 +84,6 @@ In this form, replace the name of the pre-filled folder with the name of the new
 
 #### Other options available
 
-##### The "SSL" option
-
-Tick/untick this box only if you want to enable/disable free SSL **Let's Encrypt** for your domainname or subdomain. You do not need to tick this box for the other SSL solutions offered with OVHcloud.
-
-You can find more information on SSL options and offers in our dedicated documentation “[Managing SSL certificates on a web hosting plan](/pages/web_cloud/web_hosting/ssl_on_webhosting)”.
-
 ##### The "Activate the CDN" option
 
 To use this option, you must have already subscribed to an OVHcloud CDN solution, or have a Performance web hosting plan.
@@ -128,7 +122,7 @@ If all the settings are configured as you want, click the `Confirm`{.action} but
 
 Depending on the options you have selected, the changes may take between a few minutes and a few hours to be applied.
 
-If modifications of the **SSL**, **CDN**, **Country IP** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
+If modifications of the **CDN**, **Country IP** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
 
 ## Go further
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-sg.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-sg.md
index df06959bc1a..1ea4769c0ca 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-sg.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: "Web Hosting - How to modify a domain name already associated to a hosting plan"
 excerpt: "Find out how to change the association settings for a domainname or subdomain already declared on your web hosting plan"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -84,12 +84,6 @@ In this form, replace the name of the pre-filled folder with the name of the new
 
 #### Other options available
 
-##### The "SSL" option
-
-Tick/untick this box only if you want to enable/disable free SSL **Let's Encrypt** for your domainname or subdomain. You do not need to tick this box for the other SSL solutions offered with OVHcloud.
-
-You can find more information on SSL options and offers in our dedicated documentation “[Managing SSL certificates on a web hosting plan](/pages/web_cloud/web_hosting/ssl_on_webhosting)”.
-
 ##### The "Activate the CDN" option
 
 To use this option, you must have already subscribed to an OVHcloud CDN solution, or have a Performance web hosting plan.
@@ -122,7 +116,7 @@ If all the settings are configured as you want, click the `Confirm`{.action} but
 
 Depending on the options you have selected, the changes may take between a few minutes and a few hours to be applied.
 
-If modifications of the **SSL**, **CDN**, **Country IP** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
+If modifications of the **CDN** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
 
 ## Go further
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-us.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-us.md
index df06959bc1a..1ea4769c0ca 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-us.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Web Hosting - How to modify a domain name already associated to a hosting plan"
 excerpt: "Find out how to change the association settings for a domainname or subdomain already declared on your web hosting plan"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objective
@@ -84,12 +84,6 @@ In this form, replace the name of the pre-filled folder with the name of the new
 
 #### Other options available
 
-##### The "SSL" option
-
-Tick/untick this box only if you want to enable/disable free SSL **Let's Encrypt** for your domainname or subdomain. You do not need to tick this box for the other SSL solutions offered with OVHcloud.
-
-You can find more information on SSL options and offers in our dedicated documentation “[Managing SSL certificates on a web hosting plan](/pages/web_cloud/web_hosting/ssl_on_webhosting)”.
-
 ##### The "Activate the CDN" option
 
 To use this option, you must have already subscribed to an OVHcloud CDN solution, or have a Performance web hosting plan.
@@ -122,7 +116,7 @@ If all the settings are configured as you want, click the `Confirm`{.action} but
 
 Depending on the options you have selected, the changes may take between a few minutes and a few hours to be applied.
 
-If modifications of the **SSL**, **CDN**, **Country IP** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
+If modifications of the **CDN** and **separate logs** options are not taken into account after 24 hours, please refer to the respective resources listed for all of the options described in [step 1](#step1), in order to check that all of the required conditions have been met.
 
 ## Go further
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.es-es.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.es-es.md
index 59d5f802e3f..b48bc78aed2 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.es-es.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "Web hosting - Modificar un dominio ya asociado a un alojamiento"
 excerpt: "Descubra cómo modificar la configuración de asociación de un dominio o subdominio ya declarado en su plan de hosting"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objetivo
@@ -84,12 +84,6 @@ Este formulario le pedirá que sustituya el nombre de la carpeta cumplimentada p
 
 #### Otras opciones disponibles
 
-##### La opción "SSL"
-
-Marque o desmarque esta casilla únicamente si quiere activar o desactivar el SSL gratuito **Let's Encrypt** para su dominio o subdominio. No es necesario marcar esta casilla para el resto de productos SSL de OVHcloud.
-
-Para más información sobre las opciones y servicios SSL, consulte nuestra documentación específica "[Gestionar un certificado SSL en un alojamiento web](/pages/web_cloud/web_hosting/ssl_on_webhosting)".
-
 ##### La opción "Activar la CDN"
 
 Para poder utilizar esta opción, es necesario haber contratado previamente un plan CDN de OVHcloud o disponer de un plan de hosting Performance.
@@ -128,7 +122,7 @@ Si todos los parámetros están configurados como desee, haga clic en el botón
 
 Según las opciones seleccionadas, los cambios pueden tardar desde unos minutos hasta unas horas en aplicarse.
 
-Si las opciones **SSL**, **CDN**, **IP del país** y **logs separados** no se aplican después de 24 horas, consulte las guías (y páginas) correspondientes para todas las opciones descritas en el [etapa 1](#step1), con el fin de comprobar que se han cumplido, cumplido y cumplido todos los requisitos.
+Si las opciones **CDN**, **IP del país** y **logs separados** no se aplican después de 24 horas, consulte las guías (y páginas) correspondientes para todas las opciones descritas en el [etapa 1](#step1), con el fin de comprobar que se han cumplido, cumplido y cumplido todos los requisitos.
 
 ## Más información
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.es-us.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.es-us.md
index b6fba2350d2..ea8a05dc1ba 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.es-us.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Web hosting - Modificar un dominio ya asociado a un alojamiento"
 excerpt: "Descubra cómo modificar la configuración de asociación de un dominio o subdominio ya declarado en su plan de hosting"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objetivo
@@ -84,12 +84,6 @@ Este formulario le pedirá que sustituya el nombre de la carpeta cumplimentada p
 
 #### Otras opciones disponibles
 
-##### La opción "SSL"
-
-Marque o desmarque esta casilla únicamente si quiere activar o desactivar el SSL gratuito **Let's Encrypt** para su dominio o subdominio. No es necesario marcar esta casilla para el resto de productos SSL de OVHcloud.
-
-Para más información sobre las opciones y servicios SSL, consulte nuestra documentación específica "[Gestionar un certificado SSL en un alojamiento web](/pages/web_cloud/web_hosting/ssl_on_webhosting)".
-
 ##### La opción "Activar la CDN"
 
 Para poder utilizar esta opción, es necesario haber contratado previamente un plan CDN de OVHcloud o disponer de un plan de hosting Performance.
@@ -122,7 +116,7 @@ Si todos los parámetros están configurados como desee, haga clic en el botón
 
 Según las opciones seleccionadas, los cambios pueden tardar desde unos minutos hasta unas horas en aplicarse.
 
-Si las opciones **SSL**, **CDN**, **IP del país** y **logs separados** no se aplican después de 24 horas, consulte las guías (y páginas) correspondientes para todas las opciones descritas en el [etapa 1](#step1), con el fin de comprobar que se han cumplido, cumplido y cumplido todos los requisitos.
+Si las opciones **CDN** y **logs separados** no se aplican después de 24 horas, consulte las guías (y páginas) correspondientes para todas las opciones descritas en el [etapa 1](#step1), con el fin de comprobar que se han cumplido, cumplido y cumplido todos los requisitos.
 
 ## Más información
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.fr-ca.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.fr-ca.md
index 67b745c4d15..8ec13fe664f 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.fr-ca.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: 'Hébergement web - Modifier un nom de domaine déjà associé à un hébergement'
 excerpt: "Découvrez comment modifier les paramètres d'association d'un nom de domaine/sous-domaine déjà déclaré sur votre offre d'hébergement web"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objectif
@@ -84,12 +84,6 @@ C'est donc dans ce formulaire que vous devrez remplacer le nom du dossier pré-r
 
 #### Autres options disponibles
 
-##### L'option « SSL »
-
-Cochez/décochez cette case uniquement si vous souhaitez activer/désactiver le SSL gratuit **Let's Encrypt** pour votre nom de domaine/sous-domaine. Il n'est pas nécessaire de cocher cette case pour les autres offres SSL proposées chez OVHcloud.
-
-Retrouvez plus d'informations sur les options/offres SSL disponibles dans notre documentation dédiée « [Gérer un certificat SSL sur son hébergement web](/pages/web_cloud/web_hosting/ssl_on_webhosting) ».
-
 ##### L'option « Activer CDN »
 
 Pour pouvoir utiliser cette option, vous devez avoir au préalable souscrit à une offre CDN OVHcloud ou disposer d'une offre d'hébergement web Performance.
@@ -122,7 +116,7 @@ Si l'ensemble des paramètres sont configurés selon vos souhaits, cliquez sur l
 
 En fonction des options sélectionnées, les modifications peuvent prendre de quelques minutes à quelques heures à être appliquées.
 
-Si, pour les options **SSL**, **CDN**, **IP du pays** et **logs séparés**, les modifications ne sont pas prises en compte au bout de 24 heures, nous vous invitons à consulter les guides (et pages) respectifs indiqués pour l'ensemble des options décrites dans l'[étape 1](#step1), afin de vérifier que toutes les conditions requises ont bien été suivies, respectées et réalisées.
+Si, pour les options **CDN** et **logs séparés**, les modifications ne sont pas prises en compte au bout de 24 heures, nous vous invitons à consulter les guides (et pages) respectifs indiqués pour l'ensemble des options décrites dans l'[étape 1](#step1), afin de vérifier que toutes les conditions requises ont bien été suivies, respectées et réalisées.
 
 ## Aller plus loin
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.fr-fr.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.fr-fr.md
index e976eee78cf..0dbe6c158d8 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.fr-fr.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: 'Hébergement web - Modifier un nom de domaine déjà associé à un hébergement'
 excerpt: "Découvrez comment modifier les paramètres d'association d'un nom de domaine/sous-domaine déjà déclaré sur votre offre d'hébergement web"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objectif
@@ -84,12 +84,6 @@ C'est donc dans ce formulaire que vous devrez remplacer le nom du dossier pré-r
 
 #### Autres options disponibles
 
-##### L'option « SSL »
-
-Cochez/décochez cette case uniquement si vous souhaitez activer/désactiver le SSL gratuit **Let's Encrypt** pour votre nom de domaine/sous-domaine. Il n'est pas nécessaire de cocher cette case pour les autres offres SSL proposées chez OVHcloud.
-
-Retrouvez plus d'informations sur les options/offres SSL disponibles dans notre documentation dédiée « [Gérer un certificat SSL sur son hébergement web](/pages/web_cloud/web_hosting/ssl_on_webhosting) ».
-
 ##### L'option « Activer CDN »
 
 Pour pouvoir utiliser cette option, vous devez avoir au préalable souscrit à une offre CDN OVHcloud ou disposer d'une offre d'hébergement web Performance.
@@ -128,7 +122,7 @@ Si l'ensemble des paramètres sont configurés selon vos souhaits, cliquez sur l
 
 En fonction des options sélectionnées, les modifications peuvent prendre de quelques minutes à quelques heures à être appliquées.
 
-Si, pour les options **SSL**, **CDN**, **IP du pays** et **logs séparés**, les modifications ne sont pas prises en compte au bout de 24 heures, nous vous invitons à consulter les guides (et pages) respectifs indiqués pour l'ensemble des options décrites dans l'[étape 1](#step1), afin de vérifier que toutes les conditions requises ont bien été suivies, respectées et réalisées.
+Si, pour les options **CDN**, **IP du pays** et **logs séparés**, les modifications ne sont pas prises en compte au bout de 24 heures, nous vous invitons à consulter les guides (et pages) respectifs indiqués pour l'ensemble des options décrites dans l'[étape 1](#step1), afin de vérifier que toutes les conditions requises ont bien été suivies, respectées et réalisées.
 
 ## Aller plus loin
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.it-it.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.it-it.md
index d55044372a9..3b312c8cae6 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.it-it.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "Hosting Web - Modificare un dominio già associato a un hosting"
 excerpt: "Questa guida ti mostra come modificare le impostazioni di associazione di un dominio/sottodominio già dichiarato sul tuo piano di hosting Web"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Obiettivo
@@ -84,12 +84,6 @@ In questo modulo è quindi necessario sostituire il nome della cartella precompi
 
 #### Altre opzioni disponibili
 
-##### L'opzione "SSL"
-
-Seleziona o deseleziona questa casella di controllo solo se vuoi attivare o disattivare il certificato SSL gratuito **Let's Encrypt** per il tuo dominio/sottodominio. Non è necessario spuntare questa casella per le altre offerte SSL proposte da OVHcloud.
-
-Per maggiori informazioni sulle opzioni e le offerte SSL disponibili, consulta la nostra documentazione dedicata "[Gestire un certificato SSL su un hosting Web](/pages/web_cloud/web_hosting/ssl_on_webhosting)".
-
 ##### L'opzione "Attiva la CDN"
 
 Per usufruire di questa opzione è necessario disporre di una soluzione CDN OVHcloud attiva o di un piano di hosting Web Performance attivo.
@@ -128,7 +122,7 @@ Se tutte le impostazioni sono configurate secondo le tue necessità, clicca sul
 
 In base alle opzioni selezionate, l'applicazione delle modifiche potrebbe richiedere da pochi minuti a diverse ore.
 
-Se, per le opzioni **SSL**, **CDN**, **IP del paese** e **log separati**, le modifiche non vengono applicate entro 24 ore, consulta le rispettive guide (e pagine) per tutte le opzioni descritte nello [step 1](#step1), per verificare che tutti i requisiti siano stati rispettati e rispettati.
+Se, per le opzioni **CDN**, **IP del paese** e **log separati**, le modifiche non vengono applicate entro 24 ore, consulta le rispettive guide (e pagine) per tutte le opzioni descritte nello [step 1](#step1), per verificare che tutti i requisiti siano stati rispettati e rispettati.
 
 ## Per saperne di più
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.pl-pl.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.pl-pl.md
index f18588c842f..531a9eda38b 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.pl-pl.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "Hosting WWW - Zmiana nazwy domeny powiązanej z hostingiem"
 excerpt: "Dowiedz się, jak zmienić parametry powiązania domeny/subdomeny zadeklarowanej wcześniej w Twojej usłudze hostingu"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Wprowadzenie
@@ -84,12 +84,6 @@ W związku z tym w formularzu należy zastąpić wstępnie wypełnioną nazwę f
 
 #### Więcej dostępnych opcji
 
-##### Opcja "SSL"
-
-Zaznacz/usuń zaznaczenie tego pola, jeśli chcesz włączyć/wyłączyć bezpłatny certyfikat SSL **Let's Encrypt** dla Twojej domeny/subdomeny. Nie musisz zaznaczać tego pola w przypadku innych ofert SSL oferowanych przez OVHcloud.
-
-Więcej informacji na temat opcji/ofert SSL znajdziesz w naszej dokumentacji "[Zarządzanie certyfikatem SSL na hostingu](/pages/web_cloud/web_hosting/ssl_on_webhosting)".
-
 ##### Opcja "Włącz CDN"
 
 Aby skorzystać z tej opcji, należy najpierw wykupić ofertę CDN OVHcloud lub wykupić hosting Performance.
@@ -128,7 +122,7 @@ Jeśli wszystkie parametry są skonfigurowane zgodnie z Twoimi potrzebami, klikn
 
 W zależności od wybranych opcji wprowadzenie zmian może potrwać od kilku minut do kilku godzin.
 
-Jeśli w przypadku opcji **SSL**, **CDN**, **Geolokalizacja IP** i **Rozdzielone logi** nie zostaną wprowadzone zmiany po 24 godzinach, zapoznaj się z przewodnikami (i stronami) dla wszystkich opcji opisanych w [etap 1](#step1), aby upewnić się, że wszystkie wymagane warunki zostały spełnione.
+Jeśli w przypadku opcji **CDN**, **Geolokalizacja IP** i **Rozdzielone logi** nie zostaną wprowadzone zmiany po 24 godzinach, zapoznaj się z przewodnikami (i stronami) dla wszystkich opcji opisanych w [etap 1](#step1), aby upewnić się, że wszystkie wymagane warunki zostały spełnione.
 
 ## Sprawdź również
 
diff --git a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.pt-pt.md b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.pt-pt.md
index fdf1c04b601..a2859602bab 100644
--- a/pages/web_cloud/web_hosting/multisites_modify_domain/guide.pt-pt.md
+++ b/pages/web_cloud/web_hosting/multisites_modify_domain/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "Alojamento web - Alterar um nome de domínio já associado a um alojamento"
 excerpt: "Saiba como alterar as configurações de associação de um domínio/subdomínio já declarado na sua oferta de alojamento web"
-updated: 2025-02-20
+updated: 2025-11-05
 ---
 
 ## Objetivo
@@ -84,12 +84,6 @@ Durante a utilização dos seus serviços, poderá ser necessário alterar a `Pa
 
 #### Outras opções disponíveis
 
-##### A opção "SSL"
-
-Selecione/desmarque esta caixa unicamente se deseja ativar/desativar o SSL gratuito **Let's Encrypt** para o seu nome de domínio/subdomínio. Não é necessário selecionar esta opção para as outras ofertas SSL disponibilizadas na OVHcloud.
-
-Encontre mais informações sobre as opções/ofertas SSL disponíveis na nossa documentação dedicada "[Gerir um certificado SSL num alojamento web](/pages/web_cloud/web_hosting/ssl_on_webhosting)".
-
 ##### A opção "Ativar o CDN"
 
 Para poder utilizar esta opção, deve ter previamente subscrito uma oferta CDN da OVHcloud ou dispor de um serviço de alojamento web Performance.
@@ -128,7 +122,7 @@ Se o conjunto dos parâmetros estiver configurado de acordo com os seus desejos,
 
 Dependendo das opções selecionadas, as alterações podem levar de alguns minutos ou algumas horas para serem aplicadas.
 
-Se, para as opções **SSL**, **CDN**, **IP do país** e **logs separados**, as modificações não forem aplicadas após 24 horas, consulte os respetivos manuais (e páginas) indicados para o conjunto das opções descritas no [etapa 1](#step1), a fim de verificar que todas as condições exigidas foram corretamente respeitadas e realizadas.
+Se, para as opções **CDN**, **IP do país** e **logs separados**, as modificações não forem aplicadas após 24 horas, consulte os respetivos manuais (e páginas) indicados para o conjunto das opções descritas no [etapa 1](#step1), a fim de verificar que todas as condições exigidas foram corretamente respeitadas e realizadas.
 
 ## Quer saber mais?