Epona365 Office certificate renewal

Based on version 25.1.114-162, updated 12 March 2026

The Epona365 containers use a certificate based connection to the Epona365 API and Epona365 APP Entra apps. Certificates expire after 2 years and need to be renewed.

Running the Assert-Epona365Apps.ps1 script again will now test the certificate lifetime and offer you a path to add an extra certificate. the script is automatically deployed to the {prefix}-ep-web /setup webpage.

If the certificate is valid for more than 6 months, the script will display a confirmation stating the number of days the certificate is valid

If the certificate will expire in less than 6 months, then the script will offer to recreate a new certificate with an expiration of 2 years by default

An extra certificate is placed and connected to the Entra ID Apps

A new certificate is placed and set in Entra ID, the old certificate is still present. Running containers will remain running using the old certificate untill they are restarted. All containers will restart regularly, except for the {prefix}-ep-web which will need a manual restart or a new revision to restart and reload the new certificate.

Tips The script updates the APP with new certificates, it does not delete the Old certificate Hence the Certificate expiration warning will still be visible after the update

Ensure that the workstation running Powershell is IP whitelisted to the Environment keyvault

Check the names of the Epona365 API and Epona365 APP apps used, the Assert script assumes default APP names, but the client could be running with different names.
There is a parameter for using alternative APP names. In this case we used:

.\Assert-Epona365Apps.ps1 -Prefix "ep{prefix}" -ApiAppName "Epona365 self-hosted api (prd)" -SpaAppName "Epona365 self-hosted app (prd)" -ApplicationUrl "https://ep{prefix{-ep-web.bluepond-1234567.westeurope.azurecontainerapps.io (opens new window)"