Upgrade - Upgrade - Alfresco - Alfresco Content Connector for Azure - Alfresco/Alfresco-Content-Connector-for-Azure/4.0/Alfresco-Content-Connector-for-Azure/Alfresco-Content-Connector-for-Azure/Install-the-Azure-Connector/Upgrade - 4.0

Alfresco Content Connector for Azure
Platform
Alfresco
Product
Alfresco Content Connector for Azure
Release
4.0
ft:lastPublication
2026-05-06T14:44:59.414000
ft:locale
en-US
ArchiveStatus
Archived

Use this information to upgrade the Azure Connector from a previous version for Tomcat-based deployments only.

  1. Stop the Content Services server.

  2. Navigate to the root directory of your installation.

  3. Use the following command to check for the module you wish to delete:

    java -jar bin/alfresco-mmt.jar list tomcat/webapps/alfresco.war

    This displays a list of the installed modules. Make a note of the module ID of the module you wish to uninstall, for example, org_alfresco_integrations_AzureConnector.

  4. Use the Module Management Tool (MMT) to uninstall the AMP from the repository WAR (alfresco.war). For example:

    java -jar bin/alfresco-mmt.jar uninstall  org_alfresco_integrations_AzureConnector tomcat/webapps/alfresco.war

    For more information, see Using the Module Management Tool (MMT) and Uninstall an AMP file.

  5. Navigate to the amps directory.

  6. Delete any previously installed Azure Connector AMP.

  7. Copy the AMP file you downloaded during installation to the amps directory.

  8. Use the Module Management Tool (MMT) to install the AMP into the repository WAR (alfresco.war).

    For more information, see Using the Module Management Tool (MMT) and Uninstall an AMP file.

    Note

    You must install the Azure Connector AMP using -force.

  9. Check that the Configuration is set up correctly for your environment.

    Note

    When upgrading from Azure Connector 1.0, make sure you define the Azure authentication mode and a supported value in your alfresco-global.properties file.

    !!! Note To upgrade a system that's never used the file system (for example, an on-premises installation without locally saved binaries), we recommend that you choose a pure Azure content store. See Azure content store subsystems for more details.

  10. Start the server.

    Note

    Starting from version 1.2, the Azure Connector has the deleted content store disabled by default, since this feature is already present in Microsoft's Azure Storage services. For details on how to re-enable it see Azure Connector deleted content store.