> For the complete documentation index, see [llms.txt](https://docs.dorg.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dorg.pro/install-dorg/upgrade-an-existing-dorg/upgrade-procedure.md). # Upgrade procedure When a new version of Dorg is available, the installer can be downloaded from the [Dorg Agency portal](https://portal.dorg.pro/): click on ***Dorg squad*** link on left menu, then click **Download** on the card of your Dorg. ### Reusing Previous Installation Settings If you run the new installer from the same user account on the same local machine, it will detect your previous installations and offer to pre-populate the configuration with your prior settings. If you are installing from a different user or machine, you will need to re-enter all configuration values manually. ### What Can Be Changed During an Upgrade The following fields can be modified from your previous installation, and the installer will handle the changes automatically: * Anthropic API Keys * Service availability scheduling *(available from version 3.1)* * High Availability level *(available from version 3.1)* * License file ### What Cannot Be Changed During an Upgrade The following fields must be preserved with their original values and cannot be modified when upgrading: * Subscription ID and Resource Group name (otherwise the installer will execute a fresh installation on the new provided Subscription ID or Resource Group) * Dorg name * Dorg email * Dorg base domain name ### Upgrade Detection If you enter the same **Subscription ID** and **Resource Group name** as the original installation, the installer will automatically detect that an upgrade is being performed rather than a fresh installation. ### Upgrade Duration Upgrades are significantly faster than fresh installations, typically completing in around **30-45 minutes**. ## Additional notes for specific version upgrades ### Upgrade from version 3.0 to 3.1 * **Dorg must be regisered in Dorg Agency**\ From 3.1 the dorgs must be properly purchased in Dorg Agency Portal and the license file provided by the Agency must be used. * **New permission at Subscription level**\ On the 3.1 the operator that runs the installer needs also the "User Access Administrator" permission at Subscription level. On 3.0 this was a requirement only on the Resource Group. * **Anthropic Admin Key (new requirement)**\ Version 3.1 requires an Anthropic Admin Key. Generate it from the Anthropic portal and provide it in the appropriate field in the Installer before starting the installation. * **Dorg scheduling configuration**\ The 3.1 installer allows configuration of Dorg working hours. If you previously customized Dorg office hours, you must reapply those values in the Installer under the **Advanced** panel. ### Upgrade from version 3.1 to 3.2 Starting from **version 3.2**, the installer allows you to choose the **Apps Environment tier** from the **Advanced** section of the installer UI.
For **version 3.2**, the default tier is **D4**. This provides a smoother installation experience and reduces the risk of Azure capacity issues. However, it has a higher cost and is not required unless you plan to make heavy use of Dorg capabilities. Version **3.1 and earlier** were installed using the cheaper **Consumption** tier. Therefore, when upgrading from 3.1 or an earlier version, select **Consumption** here if you want to keep using the lower-cost option. ### Upgrade from version 3.2 to 3.3 **Azure Speech configuration**\ Azure allows **only one F0 per region per subscription** so this option is important if you are installing more than one Dorg in the same subscription.\ Voice features for the orchestrator are configured in Advanced → Azure Speech:
Choose Automatic (recommended) to let the installer reuse an existing Speech account in your subscription or create a free F0 account. Use F0, S0, or Reuse if you need to force a specific SKU or attach an account from another resource group. If your subscription already has an F0 in the same region, review this section before installing — Azure allows only one F0 per region per subscription. **New grant needed for a new permission on Entra ID App Registration**\ This release requires the new permission ***Presence.ReadWrite (delegated)*** on the Entra ID App Registration called *DorgGraphAuth*.\ Ensure to ask you Azure administrator to **grant** this new permission on the DorgGraphAuth after the installation. **Preview changes before deploy**\ The installer now offers a Preview changes button on the Inputs screen. It runs a read-only Pulumi preview across all stacks and shows what would change in Azure without creating, updating, or deleting resources. To run the actual deployment after a preview, close and reopen the installer; your form values are remembered. For troubleshooting, enable verbose preview output under Advanced → Preview. ### Upgrade from version 3.3 to 3.4 **Configuration for online meetings transcripts**\ This version introduce the feature to allow Dorg to attend online meetings on Teams and be able to archive and remind meeting transcript. This requires a special post install configuration (one time) that is described [here](/install-dorg/install-a-new-dorg/post-install-configurations.md#configure-teams-meeting-transcript-access). **New grant needed for a new permission on Entra ID App Registration**\ This release requires new permissions: \- **OnlineMeetings.Read**\ \- **OnlineMeetings.Read.All**\ **- OnlineMeetingTranscript.Read.All** on the Entra ID App Registration called *DorgGraphAuth*.\ Ensure to ask you Azure administrator to **grant** this new permission on the DorgGraphAuth after the installation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dorg.pro/install-dorg/upgrade-an-existing-dorg/upgrade-procedure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.