Updating Versions

Keeping CIPP up-to-date ensures you have the latest features, security patches, and bug fixes.

Note (Hosted / Sponsored Clients) If you’re using a CyberDrain-hosted instance of CIPP, updates happen automatically—generally within 48 hours of a new release. You can safely skip the rest of this page; however, it is important to perform a permissions check via CIPP > Application Settings > Permissions to ensure any newly added permissions are accounted for via an automated Permissions Repair in v7+.

Update your self-hosted CIPP instance to the latest release using the following instructions:

Note (Self-Hosted Clients Updating from v6 or earlier)

A few more steps are required to upgrade versions 6 to 7. See the release notes for v7.0.1 and review the steps in option 2 below for how to successfully update in these scenarios.

---

1. Sync Your Fork(s) in GitHub

For typical updates (e.g., moving from any v7+ patch releases):

1

Open Your CIPP Fork

• Go to your fork of the CIPP repo on GitHub.

• Click Sync fork (or sometimes Fetch upstream).

• Choose Update branch—be careful not to discard any commits.

IMPORTANT: If prompted with a question asking "Do you want to Discard (X) Commits" or "Update Branch", ensure you click on "Update Branch" AND DO NOT PRESS DISCARD

2

Repeat for CIPP-API

• Do the same steps in your CIPP-API fork so both the front-end and API stay in sync.

3

Wait for Deployment

• If you’ve connected your Azure Function App to GitHub Actions (Run From Package mode), the updates should roll out automatically within about 30 minutes.

• Check your Azure Logs or GitHub Actions to confirm a successful deployment

4

Clear Browser Cache

• If you see an older version in your browser, try a Hard Refresh: open DevTools (F12), then right-click the refresh icon beside the URL bar and select Hard reload and empty cache.

5

Permissions Check

• Updates to CIPP can often include additional permissions required as new features are added or existing features get updated for new requirements from Microsoft. Go into CIPP > Application Settings > Permissions and perform a Permissions Check. If any roles are missing, you'll be presented with the option to Repair Permissions in v7+.

---

2. Updating from v6 (or Older) to v7+

The v7 front-end introduced a Next.js + Material-UI stack, so older forks might need an extra step:

If your "Sync fork" options button presents you with an error that there are conflicts that must be resolved, skip to Option 3.

1

Check Your Workflow File(s)

• In your CIPP repo, open:

  .github/workflows

• Look for filenames starting with azure-static-web-apps (e.g., azure-static-web-apps-main.yml).

• Important: If you discarded commits previously, you might not see such a file at all—or it might be renamed.

2

Set the output_location to "/out" (If Missing)

• In older v7 instructions, we had to manually change:

  output_location: "" 

  to:

  output_location: "/out"

• However, newer versions of the workflow may already include "/out". Double-check your file before making changes.

3

Commit and Redeploy

• After editing, commit directly to your main branch.

• A GitHub Actions run should trigger automatically, building and redeploying the Static Web App.

4

Wait & Verify

• Give Azure a few minutes to pick up changes. Check the Actions tab or the Azure Logs for success.

• Clear your cache or try a different browser to confirm the new version is live.

5

Permissions Check

• Updates to CIPP can often include additional permissions required as new features are added or existing features get updated for new requirements from Microsoft. Go into CIPP > Application Settings > Permissions and perform a Permissions Check. If any roles are missing, you'll be presented with the option to Repair Permissions in v7+.

3. Updating from v6 (or Older) to v7+ (Merge Conflicts)

In many cases, there are so many changes to the repo that GitHub doesn't know how to properly merge your repo with the upstream repo. Follow these instructions to get your branch to update.

1

Locate your workflow file

• In your CIPP repo, open:

  .github/workflows

• Look for filenames starting with azure-static-web-apps (e.g., azure-static-web-apps-main.yml).

• Open this file in a new browser tab.

2

Discard Commits

• Return to your main repo view

• Click "Sync fork"

• Click "Discard XXX commits"

3

Recreate Workflow File

• In your CIPP repo, open:

  .github/workflows

• Click "Add file" in the top right of the page

• Select "Create new file"

• Name the file the same as the azure-static-web-apps file open in your other browser tab

• Copy the contents of the file in your other tab to the new file

4

Resume with Step 2 from Option 2

---

“I Accidentally Discarded Changes” (The Common GitHub Pitfall)

If you accidentally chose Discard (X) Commits while syncing your fork, you might have lost the original azure-static-web-apps workflow file. This often leads to:

• “No changes to commit” messages,

• A stuck or outdated front-end version,

• Confusion about missing .yml files.

Recreate the Workflow File

If you're comfortable with GitHub, the easiest way to ensure you have the appropriate values for your token is to review your Actions tab on your CIPP repo for the most recent successfully run update. The contents of your old workflow file will be found by clicking "Workflow file" in the left side column of the Build and Deploy task. You'll still need to ensure the /out changes have been made to the file.

1

Check Repository Secrets

• In your CIPP fork, go to Settings → Secrets and variables → Actions.

• Note the name of your Azure Static Web Apps deployment token (e.g., AZURE_STATIC_WEB_APPS_API_TOKEN_SOMENAME_12345).

2

Create a New .yml in .github/workflows

• The filename can be anything (azure-static-web-apps-fix.yml, deploy.yml, etc.)—just make sure it ends in .yml.

• Use this example file as the contents

3

2KB

cipp-workflow.yml

Example file

Update References to Your Secrets

• In that new file, look for lines referencing the token (e.g., AZURE_STATIC_WEB_APPS_API_TOKEN_...).

• Replace them with your token name from Step 1.

4

Commit

• Once you commit, GitHub Actions should fire off a new build if the on: triggers are present (typically push or pull_request).

• Check the Actions tab to see if it’s running.

5

Confirm Deployment

• After the workflow succeeds, your Static Web App should serve the updated version.

• If you still see the old UI, do a Hard Refresh (Open DevTools, then Right Click Refresh Button) or wait up to 30 minutes for Azure’s distribution/CDN to update

6

Permissions Check

• Updates to CIPP can often include additional permissions required as new features are added or existing features get updated for new requirements from Microsoft. Go into CIPP > Application Settings > Permissions and perform a Permissions Check. If any roles are missing, you'll be presented with the option to Repair Permissions in v7+.

Done & Dusted

At this point, your CIPP front-end and API should be updated to the latest release. Keep these key points in mind:

1. Never click “Discard Commits” when syncing.

2. Watch for the .github/workflows files if you suspect deployment issues.

3. Hard-refresh or wait for CDN caches to clear for a truly up-to-date view

Congratulations! You’re now up-to-date and ready to use the newest features.