> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexagon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Flexagon SaaS upgrade process

> Answers to common questions about Flexagon SaaS upgrades, Config Management adds, and maintenance windows.

### What sort of access will Flexagon need to perform the upgrade?

Flexagon does not require any access to your environment to perform the upgrade. Our support team handles the software upgrade and CM installation directly on the platform via automated deployment pipelines.

### What if we need to add Config Management application to our existing Flex Deploy application?

Our support team handles the CM installation directly on the platform via automated deployment pipelines.

> [!NOTE]
>
> If the new CM application will be connecting to your on-prem environments, the one watchout will be ensuring the network connectivity is setup to those target endpoints. Azure Relay is the preferred option. If you already use site-to-site (S2S) VPN, we just need to make sure routing is enabled to those target endpoints.

### How long is the physical upgrade expected to take, is this a matter of hours?

While the physical upgrade and addition of the new environment generally take less than an hour, we request scheduling a 60-minute maintenance outage window for the deployment. During this window, the application will experience downtime while backend services are updated and restarted. Once our team completes the deployment within the maintenance window, we recommend post-upgrade checkout and validation.