diff --git a/content/product/operation_references/opennebula_services_configuration/fireedge.md b/content/product/operation_references/opennebula_services_configuration/fireedge.md
index 013746d2..82335594 100644
--- a/content/product/operation_references/opennebula_services_configuration/fireedge.md
+++ b/content/product/operation_references/opennebula_services_configuration/fireedge.md
@@ -110,19 +110,22 @@ In HA environments, `fireedge_key` needs to be copied from the first leader to t
 
 ### Branding FireEdge
 
-You can add your logo to the login, main, favicon, and loading screens by updating the `logo:` attribute as follows:
+You can add your logo to the login, main and loading screens by updating the `logo:` attribute as follows:
 
 - The logo configuration is done in the `/etc/one/fireedge/sunstone/views/sunstone-views.yaml` file.
 - The logo of the main UI screen is defined for each view.
 
 The logo image must be copied to `/usr/lib/one/fireedge/dist/client/assets/images/logos`.
 
-The following example shows how you can change the logo to a generic linux one (included by default in all FireEdge installations):
+Also, you can add you favicon by updating the `favicon:` attribute defined in the `/etc/one/fireedge/sunstone/views/sunstone-views.yaml` file. The favicon must be copied to `/usr/lib/one/fireedge/dist/client/assets/images/favicon`.
+
+The following example shows how you can change the logo and the favicon to a generic linux one (included by default in all FireEdge installations):
 
 ```yaml
 # /etc/one/fireedge/sunstone/views/sunstone-views.yaml
 ---
 logo: linux.png
+favicon: linux.png
 
 groups:
     oneadmin:
@@ -133,7 +136,11 @@ default:
 ```
 
 {{< alert title="Note" type="info" >}}
-The logo can be updated without having to restart the FireEdge server!{{< /alert >}} 
+If the attribute logo is defined and the attribute favicon is not defined, the logo attribute will be used as favicon.
+{{< /alert >}} 
+
+{{< alert title="Note" type="info" >}}
+The logo and the favicon can be updated without having to restart the FireEdge server!{{< /alert >}} 
 
 ![fireedge_sunstone_linux_login_logo](/images/fireedge_login_linux_logo.png) ![fireedge_sunstone_linux_drawer_logo](/images/fireedge_drawer_linux_logo.png)
 
diff --git a/content/software/release_information/release_notes/resolved_issues_721.md b/content/software/release_information/release_notes/resolved_issues_721.md
index 88dd0570..6cdd75e0 100644
--- a/content/software/release_information/release_notes/resolved_issues_721.md
+++ b/content/software/release_information/release_notes/resolved_issues_721.md
@@ -11,6 +11,8 @@ The following new features have been backported to 7.2.1:
 
 * Add option [`LOG_RESULT_LENGTH` to `oned.conf`](../../../product/operation_references/opennebula_services_configuration/oned#xml-rpc-server-configuration) to configure max length of API result log.
 * Add per-VM live migration options through [`MIGRATE_AUTO_CONVERGE` and `MIGRATE_COMPRESSED`](../../../product/operation_references/configuration_references/template#template-features) VM template attributes. Administrators can now tune auto-convergence and memory compression only for selected KVM VMs, improving migration reliability and bandwidth usage without changing global driver defaults.
+* [Allow the customization of the favicon](../../../product/operation_references/opennebula_services_configuration/fireedge.md#branding-fireedge).
+
 
 ## Resolved Issues