Deployment Steps - 2025_MAY_02
Deployment
Potential Issues
- If the deployment admin does not have access to Storage Accounts, the Storage Account deployment part will fail. There are no changes to the storage accounts in this release, so this can be ignored
- The Custom Functions Function App (npobp_common) tends to have trouble with deployment and may need to be manually deployed
- The Seed Data step may not work if APIM is secured within a vnet. In that instance, the #Manual Steps below will allow the same changes to be added manually
Prerequisites
We will follow the deployment instructions from: Hosted Model Deployment Guide Please read and understand the additional prerequisites below before continuing:
- Ensure the logged in user has access to the following storage accounts. If the storage account is part of a VNet, the user's IP address needs to be explicitly added:
- Do the same for the following, for both the Main site and Advanced Tools site:
- In your existing customerconfig.json file, ensure the following settings are correct:
- prerequisutes.validateEnabled
- otherSettings.downloadAdditionalScripts
- otherSettings.downloadArtifacts
- The Custom Functions Function App (npobp_common) function app tends to fail when run manually through the script, so it may need to be manually redeployed
$resourceGroupName = 'NAME_OF_YOUR_RESOURCE_GROUP' $functionAppName = 'NAME_OF_YOUR_COMMON_FUCNTION_APP' $deployZipPath = 'PATH_TO_THE_ARTIFACTS_ZIP_FILE_IN_ARTIFACT_FOLDER_34' az account set --subscription "" az functionapp deployment source config-zip ` --resource-group $resourceGroupName ` --name $functionAppName ` --src $deployZipPath
Manual Steps:
None
Smoke Tests
- Open existing Flow and Edit the flow via the edit button and save