When a new version of a SendSafely connector template is released — or you need to apply a configuration change — you redeploy using the same ARM template rather than tearing down and rebuilding your resource group. Because the template supports both new and existing deployments, updating in place preserves your resource group's identity, its outputs, and any resources that don't need to change.

Note: Fields such as the SendSafely validation key and Salesforce credentials can be left blank when updating an existing deployment. Leaving them blank preserves the current values already stored in Key Vault.

Before beginning the update process please contact your account representative or Support for an updated Azure Resource Manager (ARM) template (JSON file).

Step 1: Deploy from to an existing resource group

From the Azure portal search bar, search for “deploy a custom template” and then select it from the available options.

Click “Build your own template in the editor”.

Then click “Load file” from the ribbon menu. 

After uploading the ARM template (which you received from your SendSafely Support representative), click “Save”.

On the “Custom Deployment” screen, select the Azure subscription and resource group that your Function App is deployed under. 

For the Deployment Type select “existing” and enter the Resource Name Suffix e.g. '3lkyy2suub33u'. 

You can find the Resource Name Suffix from the Function App overview -- it is a string of letters and numbers at the end of the name of your Function App. 

For the existing Key Vault secrets, leave these BLANK to preserve the current value:

• SendSafely Validation Key
• Salesforce Consumer Key
• Salesforce Consumer Secret

If you want to over-write the existing values in Key Vault, enter the new values in the relevant input field.

There are also some optional fields, which you should ensure are set to the existing values of your currently deployed Function App.

• Comment Submitter Matches Requester: When ticket is updated with a dropzone submission, and the submitter email MATCHES the original ticket requester email, the comment is either public or private.
• Comment Submitter Does Not Match Requester: If the submitter email does NOT match the original ticket requester email, a private comment is added to the ticket. You also have the option to disallow such submissions and email the dropzone connector owner.

Step 2: Review and deploy

Once you have entered the required information, click “Review and create”.

A validation step will run, and once it is complete, click “Create” to begin the deployment.

Once deployment is complete, you will see a "Success" message -- a test submission to the connected Dropzone is advised to verify expected behavior.