# Deploy code changes

## Overview

Sitefinity Cloud provides out-of-the-box Continuous Integration (CI) and Continuous Delivery (CD) processes that enable you to test and release new functionality at the click of a button. Releases can be easily traced and there is an interface for manual approval of deployment to specific environments. Moreover, in cases where the system fails to start after a package has been deployed, an automatic rollback is triggered to restore the system to the previously running state.

The following preconfigured CI/CD pipelines are available for the different applications that are part of the Sitefinity Cloud setup:

* For **ASP.NET Core Renderer**  : `DotNetCoreRenderer.CI.CD`
* For **Next.js Renderer**  : `NextJsRenderer.CI.CD`
* For **Sitefinity CMS**  : `CI.CD`

  > info **NOTE**: This pipeline is available if the [Developer Extensions](https://www.progress.com/documentation/sitefinity-cms/cloud/platform-overview/developer-extensions--sitefinity-cloud-paas-) toggle is enabled.
* For **Sitefinity backend UI extensions**  : `Extensions.CI.CD`
  For more information, see [Decoupled extensibility for your backend UI](https://www.progress.com/documentation/sitefinity-cms/cloud/develop-and-deploy/decoupled-extensibility-for-your-backend-ui).

> info **NOTE**: Each of these applications can be built from a repository hosted outside your Sitefinity Cloud project. For more information, see [Use an external source code repository](https://www.progress.com/documentation/sitefinity-cms/cloud/develop-and-deploy/use-an-external-source-code-repository).

## Develop code locally

By default, the deployment workflow is in line with the software development practice of Continuous Delivery (CD) for deploying new changes across environments. During this process, the deployment package is prepared from the main/master branch of the repository and is then subsequently deployed to each environment, following an approval/verification/testing step until reaching *Production*. By following these best practices, committing your changes directly to the *main/master* branch is restricted. Instead, all code development must be done in a dedicated feature branch, which you create from *main/master* branch, and then you merge your changes into *main/master* via pull request from the feature branch.

This flow can be customized according to the customer needs. For example, you may need a different branch or set of branches configured for each environment. The process of merging pull requests between branches will trigger a build and deploy to the environment of the target branch. In addition, you can configure deployments to any environment to be triggered manually.

The same is valid for the repositories of the ASP.NET Core Renderer, Next.js Renderer, and Sitefinity backend UI extensions applications.

## Deploy your code

Once your feature branch with the desired code changes has been pushed to the origin, you can proceed by merging these changes to the *main/master* branch and deploying them.

### Create a pull request to push your code to the main/master branch

Perform the following steps:

1. Log in to your Sitefinity Cloud project Management Portal.
2. Navigate to *Repos » Pick the repository from the dropdown » Pull requests* and click *New pull request*.
3. From the source branch selection dropdown, select the feature branch you want to merge changes from. From the target branch selection dropdown, select *main/master*.
4. Fill in the pull request details and click *Create*.

### Approve and merge pull requests

Each pull request must be approved before merging the changes to the main/master branch. By default, all users who are in the *Contributors* role can approve pull requests. To view pull requests that are pending approval and approve them, follow these steps:

1. In your Sitefinity Cloud Management Portal, navigate to *Repos » Pick the repository from the dropdown » Pull requests* and click the *Active* tab.
2. Click the name of the desired pull request from the list.
3. On the next screen, you can review the pull request and approve it by clicking *Approve*.

As a result, all policy requirements are marked as met and an automated CI build is triggered to test the changes against the *main/master* branch. To complete merging the changes, click *Complete* (located next to the *Approve* button).

> info **NOTE**: Once the merge is successfully completed, the feature branch is automatically deleted as it is no longer needed.

Approving a merge triggers an automated CI build and upon successful completion, the changes are merged in the *main/master* branch and a deployment is triggered to apply the changes on the corresponding non-Production environment(s). You can browse the non-Production environment(s) where the changes have been deployed to verify your newly deployed functionality is working as expected.

### Promote your code to the Production environment

Once you have verified that your code works as expected on the non-Production environment(s), you can promote it to the *Production* environment. By default, deploying to *Production* requires approval from a user with *Promote to Production* role. You can view deployments pending approval to *Production*, and promote them by following these steps:

1. In your Sitefinity Cloud Management Portal, navigate to *Pipelines » All*.
2. Select the CI/CD pipeline for the application.
3. Locate the Run that is pending approval to *Production* and open it.
4. Click *Review* next to the message `1 approval needs your review before this run can continue to Production`.
5. In the dialog box that opens, click *Approve* or *Reject*.

The non-Production environment(s) can also be configured to require approval from users in a *Promote to {Environment Name}* group.

## Deploy to selected environments only

When you start a CI/CD pipeline manually, you can choose which Sitefinity Cloud environments the run deploys to. You have the option to exclude environments intentionally, so the run skips them and deploys only to the remaining selected environments.

This is useful when a change must reach a later stage without redeploying to environments that already received it. For example, use this option to promote a fix directly to *Production* after it has been verified on *Staging*.

To deploy to selected environments only, perform the following:

1. Log in to your Sitefinity Cloud Management Portal.
2. Navigate to *Pipelines » All*.
3. Select the CI/CD pipeline for the application.
4. In the upper-right corner, click *Run pipeline*.\
   A dialog box opens.
5. Expand *Stages to run*.\
   By default, all listed stages appear as pre-selected.
6. Deselect the environments you want to skip for this run.\
   Note that if you exclude the *CI* stage, no environment will be deployed, because every environment depends on the package that the *CI* stage produces.
7. Click *Use selected stages* to confirm your choice.
8. Click *Run*.

Approvals are **not bypassed**. If an environment requires approval from a *Promote to {Environment Name}* group, it still waits for that approval even when the preceding environments are skipped.

> info **NOTE**: Only environments you explicitly exclude in the *Stages to run* dialog are treated as intentionally skipped. Stages skipped for another reason - for example, because the branch does not match the stage's branch filter, or because an earlier stage fails - also cause any dependent environments to be skipped.

## NuGet package cache

> info **NOTE**: NuGet package cache is available only with the `CI.CD` pipeline for Sitefinity CMS application, if the [Developer Extensions](https://www.progress.com/documentation/sitefinity-cms/cloud/platform-overview/developer-extensions--sitefinity-cloud-paas-) toggle is enabled.

The CI stage of the pipeline uses the built-in Azure DevOps Cache task to cache NuGet packages across builds.\
For more information, see Azure DevOps documentation » [Cache task](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/cache?view=azure-devops).

This reduces the time it takes to execute the CI stage, because NuGet packages are downloaded from the cache, instead of restored from scratch on each run. The cache key is based on the contents of all `packages.config` files. This way, the cache is not being used in case packages change.

## Preview deployment for Production

> info **NOTE**: Preview deployment tasks are available only with the `CI.CD` pipeline for Sitefinity CMS application, if the [Developer Extensions](https://www.progress.com/documentation/sitefinity-cms/cloud/platform-overview/developer-extensions--sitefinity-cloud-paas-) toggle is enabled.

The preview deployment functionality checks that the newly deployed version of the application on *Production* can start up using a DB copy from *Production* before switching to the actual Production DB. This is important in case of DB schema changes and Sitefinity upgrades that come with the new deployment package, because if the application fails to start or corrupts the DB copy, the **actual** Production DB will not be affected.

## Default configuration values

A set of default configuration values are applied to the Renderer application and Sitefinity CMS application when deployed to a Sitefinity Cloud environment, as specified in the respective tables below.

### Sitefinity CMS application

<table class="DocTable custom-table k-table" cellspacing="0" cellpadding="0" align="center">
    <tbody>
        <tr>
            <td><strong>Configuration Path</strong></td>
            <td><strong>Value</strong></td>
            <td><strong>Condition</strong></td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>System Default Settings</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf:enableFileSystemCacheDependencies</td>
            <td>"False"</td>
            <td>Developer Extensions toggle is enabled</td>
        </tr>
        <tr>
            <td>sf:blockingOperationExecutionDelayInSeconds</td>
            <td>"20"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf:enableBlobStorageChunkUpload</td>
            <td>"True"</td>
            <td>Developer Extensions toggle is disabled</td>
        </tr>
        <tr>
            <td>sf:AppStatusPageMode</td>
            <td>"Disabled"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf:HealthCheckApiEndpoint</td>
            <td>"/restapi/health"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf:HealthCheckUnhealthyStatusCode</td>
            <td>"500"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf:lastCodeModifiedDateTimeInUTC</td>
            <td>Deployment time in UTC</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf:serviceStackEnableFeatures</td>
            <td>"Json,Html"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:ValidationKey</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:DecryptionKey</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Warmup</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/applicationModules/Warmup:startupType</td>
            <td>"Disabled"</td>
            <td>Developer Extensions toggle is enabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Output Cache Settings</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:outputCacheConfig:optionalHeaders</td>
            <td>"Status,Key"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings:defaultWebservicesProfile</td>
            <td>"Long Caching"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings:waitForPageOutputCacheToFill</td>
            <td>"True"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings/cacheProvidersSettings/redisSettings:ConnectionString</td>
            <td>Redis connection string</td>
            <td>Environment has distributed output cache</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings:defaultOutputCacheProvider</td>
            <td>"Redis"</td>
            <td>Environment has distributed output cache</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings/cacheService:authenticationKey</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings/cacheService:requireHttpsForAllRequests</td>
            <td>"False"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings/cacheService:enabled</td>
            <td>"True"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings/pageCacheInvalidation:cacheDependencyAggregationTreshold</td>
            <td>"300"</td>
            <td>Developer Extensions toggle is enabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings:defaultClientProfile</td>
            <td>"Long Caching"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings:defaultDocumentProfile</td>
            <td>"Long Caching"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings:defaultProfile</td>
            <td>"Long Caching"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings:defaultVideoProfile</td>
            <td>"Long Caching"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:publishingConfig:feedsOutputCacheProfileName</td>
            <td>"RSS Feed Caching"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings/pageCacheInvalidation:maxParallelTasks</td>
            <td>"2"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings/pageCacheInvalidation:cacheItemHostHeaderName</td>
            <td>"X-Original-Host"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/outputCacheSettings/pageCacheInvalidation:warmup</td>
            <td>"Light"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Health Check Service</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/NoBlockingOperations:enabled</td>
            <td>"True"</td>
            <td>Developer Extensions toggle is disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/NoBlockingOperations:timeoutSeconds</td>
            <td>"30"</td>
            <td>Developer Extensions toggle is disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/NoBlockingOperations:critical</td>
            <td>"True"</td>
            <td>Developer Extensions toggle is disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/Modules:critical</td>
            <td>"True"</td>
            <td>Developer Extensions toggle is disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/SaasMode:critical</td>
            <td>"True"</td>
            <td>Developer Extensions toggle is disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig:enabled</td>
            <td>"True"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/Database access:enabled</td>
            <td>"True"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/Database access:timeoutSeconds</td>
            <td>"30"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/Database access:critical</td>
            <td>"True"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/Redis:enabled</td>
            <td>Variable</td>
            <td>Environment has distributed output cache OR has NLB</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/Redis:timeoutSeconds</td>
            <td>"60"</td>
            <td>Environment has distributed output cache OR has NLB</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/Redis:critical</td>
            <td>"False"</td>
            <td>Environment has distributed output cache OR has NLB</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/healthCheckConfig/healthChecks/Search service:enabled</td>
            <td>Variable</td>
            <td>Environment search service matches "AzureSearchService"</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Packaging</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:packagingConfig:packagingMode</td>
            <td>"Target"</td>
            <td>Developer Extensions toggle is enabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Pages</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:pagesConfig/errorPages:mode</td>
            <td>"Disabled"</td>
            <td>Developer Extensions toggle is disabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Labels and Messages</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:resourcesConfig:LabelsAndMessagesReadOnly</td>
            <td>"True"</td>
            <td>Developer Extensions toggle is enabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Libraries</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:librariesConfig:sizeOfChunk</td>
            <td>"5000000"</td>
            <td>Always (5MB chunks)</td>
        </tr>
        <tr>
            <td>sf-env:librariesConfig/blobStorage:defaultProvider</td>
            <td>"AzureStorage"</td>
            <td>Developer Extensions toggle is disabled</td>
        </tr>
        <tr>
            <td>sf-env:librariesConfig/blobStorage/providers/AzureStorage:enableRelativeUrls</td>
            <td>"True"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:librariesConfig/blobStorage/providers/AzureStorage:connectionString</td>
            <td>Azure connection string</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:librariesConfig/blobStorage/providers/AzureStorage:containerName</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:librariesConfig/blobStorage/providers/AzureStorage:enabled</td>
            <td>"True"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:librariesConfig/blobStorage/providers/AzureStorage:siteSyncBlobTransferEnabled</td>
            <td>"True"/"False"</td>
            <td>"True" for Site Sync target environment</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Load Balancing</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/loadBalancingConfig/redisSettings:ConnectionString</td>
            <td>Redis connection string</td>
            <td>Environment has NLB</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/loadBalancingConfig/redisSettings:KeyPrefix</td>
            <td>Key prefix with org/project/env</td>
            <td>Environment has NLB</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Authentication - Common Settings</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:authenticationConfig/securityTokenServiceSettings/authenticationProviders/{provider}:OpenIdConnectNonceMode</td>
            <td>Enabled</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:authenticationConfig/securityTokenServiceSettings/authenticationProviders/{provider}:authority</td>
            <td>Azure AD authority URL</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:authenticationConfig/securityTokenServiceSettings/authenticationProviders/{provider}:autoAssignedRoles</td>
            <td>""</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:authenticationConfig/securityTokenServiceSettings/authenticationProviders/{provider}:clientId</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:authenticationConfig/securityTokenServiceSettings/authenticationProviders/{provider}:enabled</td>
            <td>"True"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:authenticationConfig/securityTokenServiceSettings/authenticationProviders/{provider}:title</td>
            <td>"Log in with SSO"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Authentication - Response Type</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:authenticationConfig/securityTokenServiceSettings/authenticationProviders/{provider}:responseType</td>
            <td>"id_token"</td>
            <td>Developer Extensions toggle is disabled</td>
        </tr>
        <tr>
            <td>sf-env:authenticationConfig/securityTokenServiceSettings/authenticationProviders/{provider}:redirectUri</td>
            <td>"/Sitefinity/Authenticate/OpenID/signin-custom"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Authentication - Sitefinity Cloud Authentication</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:sitefinityCloudAuthenticationConfig:OrganizationId</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityCloudAuthenticationConfig:ProjectId</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityCloudAuthenticationConfig:Environment</td>
            <td>Environment name</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityCloudAuthenticationConfig:ClaimToRolesMappingIdentityProvider</td>
            <td>Identity provider ("OpenIDConnect")</td>
            <td>Developer Extensions toggle enabled AND authentication package version &gt;= 2.0.0</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityCloudAuthenticationConfig:ClaimToRolesMappingNamePrefix</td>
            <td>"SitefinityCloud_"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityCloudAuthenticationConfig:SitefinityCloudApiBaseUrl</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityCloudAuthenticationConfig:AccessKeyId</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityCloudAuthenticationConfig:AccessKeySecret</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Licensing</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/licensing:defaultLicenseProvider</td>
            <td>"AzureProvider"</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/licensing/licenseProviders/AzureProvider:providerType</td>
            <td>Azure license provider type</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/licensing/licenseProviders/AzureProvider:clientId</td>
            <td>Environment variable</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/licensing/licenseProviders/AzureProvider:clientSecret</td>
            <td>Environment variable</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/licensing/licenseProviders/AzureProvider:azureTenant</td>
            <td>Environment variable</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/licensing/licenseProviders/AzureProvider:keyVaultUrl</td>
            <td>Environment variable</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/licensing/licenseProviders/AzureProvider:name</td>
            <td>"AzureProvider"</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>SSL Offloading</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/sslOffloadingSettings:EnableSslOffloading</td>
            <td>"True"</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/sslOffloadingSettings:HttpHeaderFieldName</td>
            <td>"X-Forwarded-Proto"</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/sslOffloadingSettings:HttpHeaderFieldValue</td>
            <td>"https"</td>
            <td>Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Search</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:searchConfig/searchServices/LuceneSearchService:luceneServiceIndexFolder</td>
            <td>"~/search"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:searchConfig/searchServices/AzureSearchService:azureSearchServiceName</td>
            <td>Environment variable</td>
            <td>Environment search service matches "AzureSearchService"</td>
        </tr>
        <tr>
            <td>sf-env:searchConfig/searchServices/AzureSearchService:azureServiceAdminKey</td>
            <td>Environment variable</td>
            <td>Environment search service matches "AzureSearchService"</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Site Sync</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/applicationModules/Synchronization:startupType</td>
            <td>"OnApplicationStart"</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND (environment is site sync target OR has site sync target)</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig:publishingSnapInSyncEnabled</td>
            <td>"True"</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND (environment is site sync target OR has site sync target)</td>
        </tr>
        <tr>
            <td>sf-env:dataConfig:incrementalGuidRange</td>
            <td>Site key value</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND site sync site key is not null</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig:enabledAsTarget</td>
            <td>"True"</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND environment is site sync target</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig:apiKey</td>
            <td>Environment variable</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND environment is site sync target AND Sitefinity version &gt;= 15.1.8300</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig/receivingServers/{targetServerId}:apiKey</td>
            <td>Environment variable</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND has site sync target AND Sitefinity version &gt;= 15.1.8300</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig/receivingServers/{targetServerId}:userName</td>
            <td>Environment variable</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND has site sync target AND Sitefinity version &lt; 15.1.8300</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig/receivingServers/{targetServerId}:password</td>
            <td>Environment variable</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND has site sync target AND Sitefinity version &lt; 15.1.8300</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig/receivingServers/{targetServerId}:serverAddress</td>
            <td>Environment variable</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND has site sync target</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig/receivingServers/{targetServerId}:serverUserFriendlyName</td>
            <td>Production</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND has site sync target</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig/dynamicFieldContainerSync:AllowStructureOnlySyncPropName</td>
            <td>"True"/"False"</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND has site sync target (based on sync mode)</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig/dynamicFieldContainerSync:AllowStructureAndDataSyncPropName</td>
            <td>"True"/"False"</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND has site sync target (based on sync mode)</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig/dynamicFieldContainerSync:AllowDataOnlySyncSyncPropName</td>
            <td>"True"/"False"</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND has site sync target (based on sync mode)</td>
        </tr>
        <tr>
            <td>sf-env:siteSyncConfig:disablePermissionsSync</td>
            <td>"False"</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.SiteSync.Impl" AND has site sync target</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Audit Trail</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/applicationModules/AuditTrail:startupType</td>
            <td>"OnApplicationStart"</td>
            <td>Sitefinity modules contain "Telerik.Sitefinity.AuditTrail" OR Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Image Optimization</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf:disableImageOptimization</td>
            <td>"True"/"False"</td>
            <td>Sitefinity modules contain "Progress.Sitefinity.ImageOptimization" AND image optimization is enabled</td>
        </tr>
        <tr>
            <td>sf-env:imageOptimizationConfig:enableImageOptimization</td>
            <td>"True"</td>
            <td>Sitefinity modules contain "Progress.Sitefinity.ImageOptimization" AND image optimization is enabled</td>
        </tr>
        <tr>
            <td>sf-env:imageOptimizationConfig:enableDetailLogging</td>
            <td>"True"</td>
            <td>Sitefinity modules contain "Progress.Sitefinity.ImageOptimization" AND image optimization is enabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Service Hooks - Output Cache Invalidation</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/applicationModules/ServiceHooksModule:startupType</td>
            <td>"OnApplicationStart"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/cb90ac17-d9cb-4C89-ba2e-fb09076388b2/actions/3e013be1-354D-47F5-ae52-3c3ddf7e6aaa:Url</td>
            <td>CDN purge URL for output cache</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/cb90ac17-d9cb-4C89-ba2e-fb09076388b2/actions/3e013be1-354D-47F5-ae52-3c3ddf7e6aaa:Secret</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/cb90ac17-d9cb-4C89-ba2e-fb09076388b2/actions/3e013be1-354D-47F5-ae52-3c3ddf7e6aaa:Headers</td>
            <td>JSON headers array</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Service Hooks - Document Changed</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/c92e6cc2-359a-4fd9-85b4-de29d1146224/actions/f7110cd4-965e-43cb-bec8-12c45f278262:Url</td>
            <td>CDN purge URL for media</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/c92e6cc2-359a-4fd9-85b4-de29d1146224/actions/f7110cd4-965e-43cb-bec8-12c45f278262:Secret</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/c92e6cc2-359a-4fd9-85b4-de29d1146224/actions/f7110cd4-965e-43cb-bec8-12c45f278262:Headers</td>
            <td>JSON headers array</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/c92e6cc2-359a-4fd9-85b4-de29d1146224/actions/f7110cd4-965e-43cb-bec8-12c45f278262:Headers</td>
            <td>JSON headers array with environment</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Service Hooks - Image Changed</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/42e890f0-3e93-4b3b-8d01-b437db847360/actions/a2a55163-d029-410d-bb6f-60d06728b363:Url</td>
            <td>CDN purge URL for media</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/42e890f0-3e93-4b3b-8d01-b437db847360/actions/a2a55163-d029-410d-bb6f-60d06728b363:Secret</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/42e890f0-3e93-4b3b-8d01-b437db847360/actions/a2a55163-d029-410d-bb6f-60d06728b363:Headers</td>
            <td>JSON headers array</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/42e890f0-3e93-4b3b-8d01-b437db847360/actions/a2a55163-d029-410d-bb6f-60d06728b363:Headers</td>
            <td>JSON headers array with environment</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Service Hooks - Video Changed</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/607ea2f6-560a-4605-beeb-77f6223f149d/actions/1e1849d6-eb2c-42d9-9b36-a45a15fb4979:Url</td>
            <td>CDN purge URL for media</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/607ea2f6-560a-4605-beeb-77f6223f149d/actions/1e1849d6-eb2c-42d9-9b36-a45a15fb4979:Secret</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/607ea2f6-560a-4605-beeb-77f6223f149d/actions/1e1849d6-eb2c-42d9-9b36-a45a15fb4979:Headers</td>
            <td>JSON headers array</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:serviceHooksConfig/triggers/607ea2f6-560a-4605-beeb-77f6223f149d/actions/1e1849d6-eb2c-42d9-9b36-a45a15fb4979:Headers</td>
            <td>JSON headers array with environment</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Integration Hub</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/applicationModules/IntegrationHub:startupType</td>
            <td>"OnApplicationStart"</td>
            <td>Sitefinity modules contain "Progress.Sitefinity.IntegrationHub" OR Developer Extensions toggle disabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Admin App Extensions</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:adminAppExtensionsConfig:featureEnabled</td>
            <td>"True"</td>
            <td>Sitefinity version &gt;= 15.2.8421</td>
        </tr>
        <tr>
            <td>sf-env:adminAppExtensionsConfig:customFieldsEnabled</td>
            <td>"True"</td>
            <td>Sitefinity version &gt;= 15.2.8421</td>
        </tr>
        <tr>
            <td>sf-env:adminAppExtensionsConfig:rteEnabled</td>
            <td>"True"</td>
            <td>Sitefinity version &gt;= 15.2.8421</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Diagnostic Module</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:systemConfig/applicationModules/Diagnostics:startupType</td>
            <td>"Disabled"</td>
            <td>Developer Extensions toggle enabled AND Sitefinity modules contain "Telerik.Sitefinity.Diagnostics"</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Feather</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:featherConfig:disablePrecompilation</td>
            <td>"False"</td>
            <td>Developer Extensions toggle enabled</td>
        </tr>
        <tr>
            <td>sf-env:featherConfig:logPrecompiledViewUsage</td>
            <td>"False"</td>
            <td>Developer Extensions toggle enabled</td>
        </tr>
        <tr>
            <td>sf:featherFileSystemWatcherBehaviour</td>
            <td>"True"</td>
            <td>Developer Extensions toggle enabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>AI Services</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:aIServicesConfig:DefaultAIService</td>
            <td>"SitefinityAIClient"</td>
            <td>AI services enabled (Developer Extensions enabled requires Sitefinity modules contain "Telerik.Sitefinity.AIServiceConnector")</td>
        </tr>
        <tr>
            <td>sf-env:aIConfig/aIServiceConnections/SitefinityAIService:accessKeyId</td>
            <td>Environment variable</td>
            <td>AI services enabled (Developer Extensions enabled requires Sitefinity modules contain "Telerik.Sitefinity.AIServiceConnector" AND Sitefinity version &gt;= 15.4.8625)</td>
        </tr>
        <tr>
            <td>sf-env:aIConfig/aIServiceConnections/SitefinityAIService:accessKeySecret</td>
            <td>Environment variable</td>
            <td>AI services enabled (Developer Extensions enabled requires Sitefinity modules contain "Telerik.Sitefinity.AIServiceConnector" AND Sitefinity version &gt;= 15.4.8625)</td>
        </tr>
        <tr>
            <td>sf-env:aIConfig/aIServiceConnections/SitefinityAIService:baseUrl</td>
            <td>API endpoint URL</td>
            <td>AI services enabled (Developer Extensions enabled requires Sitefinity modules contain "Telerik.Sitefinity.AIServiceConnector" AND Sitefinity version &gt;= 15.4.8625)</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>AI Hybrid Search Services</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf:hybridSearch:Endpoint</td>
            <td>API endpoint URL</td>
            <td>AI search enabled</td>
        </tr>
        <tr>
            <td>sf:hybridSearch:ApiKeyId</td>
            <td>Environment variable;</td>
            <td>AI search enabled</td>
        </tr>
        <tr>
            <td>sf:hybridSearch:ApiKey</td>
            <td>Environment variable</td>
            <td>AI search enabled</td>
        </tr>
        <tr>
            <td>sf:hybridSearch:Indexes</td>
            <td>"backend-search"</td>
            <td>AI search enabled</td>
        </tr>
        <tr>
            <td>sf:cloud:Environment</td>
            <td>Environment name</td>
            <td>AI search enabled</td>
        </tr>
        <tr>
            <td>sf:cloud:OrganizationId</td>
            <td>Environment variable</td>
            <td>AI search enabled</td>
        </tr>
        <tr>
            <td>sf:cloud:ProjectId</td>
            <td>Environment variable;</td>
            <td>AI search enabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>AI Assistant</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:sitefinityAssistantConfig:connectionString</td>
            <td>Environment variable</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityAssistantConfig:adminApiBaseUrl</td>
            <td>Environment variable</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityAssistantConfig:adminFrontendBaseUrl</td>
            <td>Environment variable with /ui/ suffix</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityAssistantConfig:featureState</td>
            <td>"enabled"</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityAssistantConfig:aiServiceBaseUrl</td>
            <td>Environment variable</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityAssistantConfig:aiServiceAccessKeyId</td>
            <td>Environment variable</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityAssistantConfig:aiServiceAccessKeySecret</td>
            <td>Environment variable</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>sf-env:sitefinityAssistantConfig:cdnHostName</td>
            <td>"cdn.assistant.cloud.sitefinity.com"</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Dynamically Generated Experience (DGE)</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:dynamicExperienceConfig:adminFrontendBaseUrl</td>
            <td>Environment variable</td>
            <td>Dynamic Experience enabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Sitefinity Insight</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:digitalExperienceCloudConnectorConfig:accessKey</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:digitalExperienceCloudConnectorConfig:connected</td>
            <td>"True"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>sf-env:digitalExperienceCloudConnectorConfig/siteToApiKeyMappings/{siteName}:dataCenterApiKey</td>
            <td>Environment variable</td>
            <td>For each site with Insight configured</td>
        </tr>
        <tr>
            <td>sf-env:digitalExperienceCloudConnectorConfig/disableTracking</td>
            <td>"True"</td>
            <td>Has site sync target</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Web Services</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>sf-env:webServicesConfig/Routes/Frontend/services/default:access</td>
            <td>"Anonymous"</td>
            <td>Always</td>
        </tr>
    </tbody>
</table>

### ASP.NET Core Renderer application

<table class="DocTable custom-table k-table" cellspacing="0" cellpadding="0" align="center">
    <tbody>
        <tr>
            <td><strong>Configuration Path</strong></td>
            <td><strong>Value</strong></td>
            <td><strong>Condition</strong></td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>System Default Settings</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>Sitefinity__Url</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>Sitefinity__OutputCacheAuthKey</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>Sitefinity__OutputCacheDuration</td>
            <td>"0"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>Sitefinity__WebServicePath</td>
            <td>"api/default"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>Sitefinity__RemoteValidationKey</td>
            <td>Environment variable</td>
            <td>Environment is not "Production"</td>
        </tr>
        <tr>
            <td>Sitefinity__LocalValidationKey</td>
            <td>""</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>Logging__LogLevel__Default</td>
            <td>"Warning"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>ApplicationInsights__ConnectionString</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>ApplicationInsights__EnableDependencyTrackingTelemetryModule</td>
            <td>"false"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>AI Assistant</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>SitefinityAssistant__CdnHostName</td>
            <td>"cdn.assistant.cloud.sitefinity.com"</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>SitefinityAssistant__CdnRootFolderRelativePath</td>
            <td>""</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>SitefinityAssistant__AssistantsAdminApiBaseUrl</td>
            <td>Environment variable</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>Blazor SignalR</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>Azure__SignalR__ConnectionString</td>
            <td>Environment variable</td>
            <td>ASP.NET Core Renderer is enabled</td>
        </tr>
        <tr>
            <td>Azure__SignalR__Endpoint</td>
            <td>Environment variable</td>
            <td>ASP.NET Core Renderer is enabled</td>
        </tr>
    </tbody>
</table>

### Next.js Renderer application

<table class="DocTable k-table" cellspacing="0" cellpadding="0" align="center">
    <tbody>
        <tr>
            <td><strong>Configuration Path</strong></td>
            <td><strong>Value</strong></td>
            <td><strong>Condition</strong></td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>System Default Settings</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>SF_CMS_URL</td>
            <td>Environment variable</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>SF_LOCAL_VALIDATION_KEY</td>
            <td>""</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>SF_NEXTJS_SET_CACHE_CONTROL_METATAG</td>
            <td>"true"</td>
            <td>Always</td>
        </tr>
        <tr>
            <td>SF_REMOTE_VALIDATION_KEY</td>
            <td>Environment variable</td>
            <td>Environment is not "Production"</td>
        </tr>
        <tr>
            <td class="accent-cell"><strong>AI Assistant</strong></td>
            <td class="accent-cell"></td>
            <td class="accent-cell"></td>
        </tr>
        <tr>
            <td>SF_ASSISTANT_ADMIN_API_BASE_URL</td>
            <td>Environment variable</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>SF_ASSISTANT_CDN_HOSTNAME</td>
            <td>"cdn.assistant.cloud.sitefinity.com"</td>
            <td>AI assistant enabled</td>
        </tr>
        <tr>
            <td>SF_ASSISTANT_CDN_ROOT_FOLDER_RELATIVE_PATH</td>
            <td>""</td>
            <td>AI assistant enabled</td>
        </tr>
    </tbody>
</table>

## Extend CI/CD pipelines with custom tasks

To facilitate the needs of customizing the CI/CD process, Sitefinity Cloud offers a mechanism for extending the existing `CI.CD` pipeline and include custom tasks for the following events:

* Pre-build tasks in CI stage
* Post-build tasks in CI stage
* Post-deployment tasks in CD stage

  > info **NOTE**: Post-deployment tasks are available only for the `CI.CD` pipeline of Sitefinity CMS application, if [Developer Extensions](https://www.progress.com/documentation/sitefinity-cms/cloud/platform-overview/developer-extensions--sitefinity-cloud-paas-) toggle is enabled.

### Customize CI stage in CI.CD pipeline for Sitefinity CMS application

1. Open the `CICD.yaml` file located in the repository of the respective application (Sitefinity CMS, ASP.NET Core, Next.js).
2. Locate the `parameters` element for the extended YAML template.
3. Add a new parameter of type `stepList` called `preBuildSteps` or `postBuildSteps`, and add tasks using the standard YAML task/step syntax.

The example below demonstrates custom pre-build steps installing and building frontend assets with `npm`, and post-build steps for running unit tests in the `CI.CD` pipeline for Sitefinity CMS application:

```yaml

    extends:
      template: CICDTemplate.yaml@SitefinityCloudPipelines
      parameters:
        preBuildSteps:
        - task: Npm@1
          displayName: npm install
          inputs:
            workingDir: $(Build.Repository.LocalPath)\Frontend
            verbose: false
        - task: Npm@1
          displayName: npm custom
          inputs:
            command: custom
            workingDir: $(Build.Repository.LocalPath)\Frontend
            verbose: false
            customCommand: run deploy --verbose
        postBuildSteps:
        - task: VSTest@2
          displayName: 'Test Assemblies'
          inputs:
            testAssemblyVer2: |
              **\$(BuildConfiguration)\*test*.dll
              !**\obj\**
            searchFolder: '$(Build.Repository.LocalPath)'
            runTestsInIsolation: true
            codeCoverageEnabled: true
            testRunTitle: 'Default Test Run'
            platform: '$(BuildPlatform)'
            configuration: '$(BuildConfiguration)'
            diagnosticsEnabled: True
```

The example below demonstrates custom pre-build steps for adding custom NuGet sources and post-build steps for running unit tests in the `DotNetCoreRenderer.CI.CD` pipeline:

```yaml

    extends:
       template: CICDDotNetCoreRendererTemplateV2.yaml@SitefinityCloudPipelines
       parameters:
         preBuildSteps:
         - task : NuGetAuthenticate@1
           inputs:
             forceReinstallCredentialProvider: true
         - task : DotNetCoreCLI@2
           displayName: Add NucleusNugetFeed
           inputs:
             command: custom
             custom: nuget
             arguments: 'add source https://pkgs.dev.azure.com/OrgName-SfCloud/SomeProjectName/_packaging/SomeProjectNameNugetFeed/nuget/v3/index.json -n SomeProjectNameNugetFeed'
             workingDirectory: '$(Build.Repository.LocalPath)'
         postBuildSteps:
         - task : VSTest@2
           displayName: 'Test Assemblies'
           inputs:
             testAssemblyVer2: |
               **\$(BuildConfiguration)\*test*.dll
               !**\obj\**
             searchFolder: '$(Build.Repository.LocalPath)'
             runTestsInIsolation: true
             codeCoverageEnabled: true
             testRunTitle: 'Default Test Run'
             platform: '$(BuildPlatform)'
             configuration: '$(BuildConfiguration)'
             diagnosticsEnabled: true
```

### Use custom variables and secrets in the CI stage

If your custom pre-build or post-build tasks need configuration values, such as a feature flag, an API URL, or a token for a private package registry, store any custom variables in the *Build Settings* variable group of the respective application instead of adding them directly to the `CICD.yaml` file. The variables in this group are available in the CI stage of the `CI.CD` pipeline.

Sitefinity Cloud creates the following variable groups for the respective application in your project:

<table>
    <thead>
        <tr>
            <th>Application</th>
            <th>Variable group</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>Sitefinity CMS</td>
            <td><i>Custom Build Settings</i></td>
        </tr>
        <tr>
            <td>ASP.NET Core Renderer</td>
            <td><i>Custom DotNetCoreRenderer Build Settings</i></td>
        </tr>
        <tr>
            <td>Next.js Renderer</td>
            <td><i>Custom NextJsRenderer Build Settings</i></td>
        </tr>
    </tbody>
</table>

To add a custom variable or a secret, perform the following:

1. Log in to Sitefinity Cloud Management Portal.
2. Navigate to *Pipelines* » *Library*.
3. Open the *Build Settings* variable group of the respective application.
4. Add a new variable and fill out the following:
   * *Name* - the name of the variable, for example `ApiUrl`
   * *Value* - the value of the variable, for example `https://api.example.com`
5. If the value holds sensitive data, such as a token or a password, click the lock icon next to the value to mark the variable as secret. After you save the group, the value is masked in the pipeline logs and cannot be read back in the Management Portal.
6. Click *Save*.
7. In the `CICD.yaml` file, reference the variable in your custom tasks in the following way: a variable named `ApiUrl` is referenced as `$(ApiUrl)`.

The example below demonstrates a custom pre-build step in the `DotNetCoreRenderer.CI.CD` pipeline that passes the `ApiUrl` variable from the *Custom DotNetCoreRenderer Build Settings* variable group to an `npm` command:

```yaml

    extends:
      template: CICDDotNetCoreRendererTemplateV2.yaml@SitefinityCloudPipelines
      parameters:
        preBuildSteps:
        - task: Npm@1
          displayName: npm run build
          inputs:
            command: custom
            workingDir: $(Build.Repository.LocalPath)\Frontend
            verbose: false
            customCommand: run build -- --api-url $(ApiUrl)
```

> info **NOTE**: The *Build Settings* variable groups are used only in the CI stage. To configure the settings of the running application, use the *AppSettings* variable groups. For more information, see [Manage the configurations](https://www.progress.com/documentation/sitefinity-cms/cloud/develop-and-deploy/manage-the-configurations).

> info **NOTE**: If the type of your project limits the task types that you can use in the CI stage, the same limits apply to the tasks that use variables from the *Build Settings* variable groups.

### Customize CD stage in CI.CD pipeline for Sitefinity CMS application

> info **NOTE**: Post-deployment tasks are available only for the `CI.CD` pipeline of Sitefinity CMS application, if [Developer Extensions](https://www.progress.com/documentation/sitefinity-cms/cloud/platform-overview/developer-extensions--sitefinity-cloud-paas-) toggle is enabled.

1. Open the `CICD.yaml` file located in the repository of the Sitefinity project.
2. Locate the `parameters` element for the extended `CICDTemplate.yaml`.
3. Define environments collection and list the environments where CD stage needs to be customized.
4. Add a new parameter of type `stepList` called `postReleaseSteps` as part of the environment object, and add tasks using the standard YAML task/step syntax.

The custom steps are defined per environment and only an allowed list of task types can be used. Currently the allowed task types are:

* `DownloadPipelineArtifact@2`
* `VisualStudioTestPlatformInstaller@1`
* `VSTest@2`

The example below demonstrates a custom post-release task to run web tests, based on an artifact called `tests`:

```yaml

    extends:
      template: CICDTemplate.yaml@SitefinityCloudPipelines
      parameters:
        environments:
        - name: 'Staging'
          postReleaseSteps:
          - task: DownloadPipelineArtifact@2
            displayName: 'Download tests'
            inputs:
              source: 'current'
              artifact: 'tests'
          - task: VisualStudioTestPlatformInstaller@1
            displayName: 'Visual Studio Test Platform Installer'
            inputs:
              versionSelector: 'latestStable'
          - task: VSTest@2
            displayName: 'VsTest - testAssemblies'
            inputs:
              testSelector: 'testAssemblies'
              testAssemblyVer2: |
                **\*test*.dll
                !**\*TestAdapter.dll
                !**\obj\**
              searchFolder: '$(Pipeline.Workspace)'
              runTestsInIsolation: true
              codeCoverageEnabled: true
              testRunTitle: 'Default Test Run'
              diagnosticsEnabled: true
              vsTestVersion: 'toolsInstaller'
```

### Customize CD stage in CI.CD pipeline for ASP.NET Core / Next.js Renderer

> info **NOTE**: Post-deployment tasks are available only for the `CI.CD` pipeline of the ASP.NET Core / Next.js Renderer, if [Developer Extensions](https://www.progress.com/documentation/sitefinity-cms/cloud/platform-overview/developer-extensions--sitefinity-cloud-paas-) toggle is enabled.

1. Open the `CICD.yaml` file located in the repository of the Sitefinity project.
2. Locate the `parameters` element for the extended `CICDTemplate.yaml`.
3. Define environments collection and list the environments where CD stage needs to be customized.
4. Add a new parameter of type `stepList` called `postReleaseSteps` as part of the environment object, and add tasks using the standard YAML task/step syntax.

The example below demonstrates a custom post-release task to notify upon deployment completion:

```yaml

extends:
    template: CICDDotNetCoreRendererTemplateV2.yaml@SitefinityCloudPipelines
    parameters:
      postReleaseSteps:
        - task: PowerShell@2
          displayName: 'Send Test Deployment Notification'
          inputs:
            targetType: 'inline'
            pwsh: true
            script: |
              Write-Host "Deployment to $(Build.SourceBranchName) completed successfully"
              Write-Host "Build Number: $(Build.BuildNumber)"
```
