Pausing Scappman Updates

Every time a new version of a 3rd party application is released, it is tested by Scappman then released to our customers. By default, when the Scappman portal detects this release it will automatically update the app in your tenant.

You can disable these automatic updates, which can be useful in a few scenarios, for example:

• Pinning an app version

• Delaying a release when using update rings

Disabling updates only instructs Scappman to no longer update that app in Intune; Disabling updates has no bearing on the assignments of your existing Intune applications, or the assignments configured on them, meaning your devices and users will still evaluate those updates if they are a member of the assigned group(s).

In the following examples, we will focus on Google Chrome but the logic applies to all apps

Example 1 - Updates enabled

Scappy watches for new versions of Google Chrome being released, packages it and publishes it to the Fast update ring application in Intune, after which devices and users in that ring will evaluate it.

Here we see that Updates are enabled for the Fast ring of Google Chrome and that ring is assigned to a group named Patching - Day 1 (ASAP)

We can also see this same assignment when we look at the app directly in the Intune portal.

Example 2 - Updates disabled

Scappy watches for new versions of Google Chrome being released, but because the Slow update ring has updates disabled it will indefinitely remain on version 113.0.5672.172.

Here we see that Updates are disabled for the Slow ring of Google Chrome and that ring is assigned to a group named Patching - Day 3

We can also see this same assignment when we look at the app directly in the Intune portal.

Summary

If you disable updates within the Scappman portal, existing applications assignments will still continue to be evaluated. If you wish to no longer deploy a specific update, delete that update.