Skip to content
vambrisEIDGuard Docs
PagesUpdating EIDGuard

EIDGuard docs

On this page

Updating EIDGuard

When a new version of EIDGuard is released, your dashboard tells you: the megaphone at the top right gets a dot, and its panel names the release with two buttons — How to update, which opens this page, and Release notes.

EIDGuard is deployed from the Azure Marketplace into a resource group you own, and it does not update itself. Updating means deploying the new version from the marketplace over the existing deployment. Your recovery points, your dashboard settings and your onboarded tenants carry over.

How to update#

  1. Private networking only: if you enabled private networking, first re-enable public network access on the data storage account for the duration of the update — see Upgrading a private-networked deployment. The update stops rather than guess if it cannot read your settings.
  2. In the Azure portal, open the EIDGuard offer in the Azure Marketplace and select Create.
  3. On the first page choose the same subscription and the same resource group EIDGuard is already deployed in, and the same region.
  4. Enter the same resource name prefix you used the first time. The prefix is what makes the new version update the existing resources; a different one creates a second, separate EIDGuard in the same group.
  5. Leave the other settings as they are. Schedule, retention, alerting and verification are read back from your dashboard during the update, so the values on these pages only apply to a brand-new deployment — see which settings survive. Sign-in is re-applied from your existing setup; you do not need to fill in the sign-in fields again.
  6. Select Review + create, then Create, and wait for the deployment to finish.
  7. Open the dashboard. The version at the bottom of the left-hand navigation shows the new release, and the megaphone no longer announces it.
  8. If you re-enabled public network access in step 1, disable it again.

If the deployment fails, Deployment troubleshooting covers the common causes, including retrying with a deployment retry suffix.

Changing plan is not an update. Plans come from your SaaS subscription and change without redeploying anything — see Activating your subscription.

Release notes#

Each release is listed here, newest first, with what changed and anything you need to do.