diff --git a/content/admin/backing-up-and-restoring-your-instance/backup-service-for-github-enterprise-server/configuring-the-backup-service.md b/content/admin/backing-up-and-restoring-your-instance/backup-service-for-github-enterprise-server/configuring-the-backup-service.md
index 51118d8f4235..5044ae322f15 100644
--- a/content/admin/backing-up-and-restoring-your-instance/backup-service-for-github-enterprise-server/configuring-the-backup-service.md
+++ b/content/admin/backing-up-and-restoring-your-instance/backup-service-for-github-enterprise-server/configuring-the-backup-service.md
@@ -27,9 +27,10 @@ To ensure reliable and performant backups, your storage must meet the following
   You can test whether your filesystem supports hardlinking symbolic links by running:
 
     ```shell
-    touch file
-    ln -s file symlink
-    ln symlink hardlink
+    cd /data/backup
+    sudo touch file
+    sudo ln -s file symlink
+    sudo ln symlink hardlink
     ls -la
     ```
 
@@ -127,7 +128,7 @@ If you're migrating from {% data variables.product.prodname_enterprise_backup_ut
 
 Once the service is configured, you can define a backup schedule.
 
-1. In the {% data variables.enterprise.management_console %}, open the "Backup Service" page.
+1. In the {% data variables.enterprise.management_console %}, open the "Backups" tab from the top menu.
 1. In the "Backup Schedule" section, choose a predefined schedule (e.g., Daily) or enter a custom cron expression.
 1. Click **Save** to apply the changes.
 
diff --git a/content/admin/managing-iam/reconfiguring-iam-for-enterprise-managed-users/migrating-your-enterprise-to-a-new-identity-provider-or-tenant.md b/content/admin/managing-iam/reconfiguring-iam-for-enterprise-managed-users/migrating-your-enterprise-to-a-new-identity-provider-or-tenant.md
index bb503a47afec..f7fbff1092d9 100644
--- a/content/admin/managing-iam/reconfiguring-iam-for-enterprise-managed-users/migrating-your-enterprise-to-a-new-identity-provider-or-tenant.md
+++ b/content/admin/managing-iam/reconfiguring-iam-for-enterprise-managed-users/migrating-your-enterprise-to-a-new-identity-provider-or-tenant.md
@@ -44,7 +44,7 @@ To migrate to a new configuration for authentication and provisioning, you must
   * If the normalized SCIM `userName` values will change after the migration, {% data variables.product.company_short %} will need to help with your migration. For more information, see [Migrating when the normalized SCIM `userName` values will change](#migrating-when-the-normalized-scim-username-values-will-change).
 * Do not remove any users or groups from the application for {% data variables.product.prodname_emus %} on your identity management system until after your migration is complete.
 * {% data variables.product.github %} will delete any {% data variables.product.pat_generic_plural %} or SSH keys associated with your enterprise's {% data variables.enterprise.prodname_managed_users %}. Plan for a migration window after reconfiguration during which you can create and provide new credentials to any external integrations.
-* As part of the migration steps below, {% data variables.product.github %} will delete all of the SCIM-provisioned groups in your enterprise when authentication is disabled for the enterprise. For more information, see [AUTOTITLE](/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/disabling-authentication-and-provisioning-for-enterprise-managed-users#about-disabled-authentication-for-enterprise-managed-users).
+* As part of the migration steps below, {% data variables.product.github %} will delete all of the SCIM-provisioned groups in your enterprise when authentication is disabled for the enterprise. Users will be removed from an organization if they were added via any of the SCIM-provisioned groups. For more information, see [AUTOTITLE](/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/disabling-authentication-and-provisioning-for-enterprise-managed-users#about-disabled-authentication-for-enterprise-managed-users).
 
 If any of these SCIM-provisioned IdP groups are linked to teams in your enterprise, this will remove the link between these teams on {% data variables.product.prodname_dotcom %} and IdP groups, and these links are not automatically reinstated after the migration. {% data variables.product.prodname_dotcom %} will also remove all members from the previously linked teams. You may experience disruption if you use groups on your identity management system to manage access to organizations or licenses. {% data variables.product.github %} recommends that you use the REST API to list team connections and group membership before you migrate, and to reinstate connections afterwards. For more information, see [AUTOTITLE](/rest/teams/external-groups) in the REST API documentation.
 
diff --git a/src/graphql/data/fpt/changelog.json b/src/graphql/data/fpt/changelog.json
index 33d4805ba016..6f7918d549f6 100644
--- a/src/graphql/data/fpt/changelog.json
+++ b/src/graphql/data/fpt/changelog.json
@@ -1,4 +1,17 @@
 [
+  {
+    "schemaChanges": [
+      {
+        "title": "The GraphQL schema includes these changes:",
+        "changes": [
+          "<p>Enum value <code>SY</code> was added to enum <code>SponsorsCountryOrRegionCode</code></p>"
+        ]
+      }
+    ],
+    "previewChanges": [],
+    "upcomingChanges": [],
+    "date": "2025-09-10"
+  },
   {
     "schemaChanges": [
       {
diff --git a/src/graphql/data/fpt/schema.docs.graphql b/src/graphql/data/fpt/schema.docs.graphql
index 4706bc555fb0..f7234dcc468d 100644
--- a/src/graphql/data/fpt/schema.docs.graphql
+++ b/src/graphql/data/fpt/schema.docs.graphql
@@ -57941,6 +57941,11 @@ enum SponsorsCountryOrRegionCode {
   """
   SX
 
+  """
+  Syria
+  """
+  SY
+
   """
   Swaziland
   """
diff --git a/src/graphql/data/fpt/schema.json b/src/graphql/data/fpt/schema.json
index 3c939b351ad3..456d96c7e4ff 100644
--- a/src/graphql/data/fpt/schema.json
+++ b/src/graphql/data/fpt/schema.json
@@ -94405,6 +94405,10 @@
           "name": "SX",
           "description": "<p>Sint Maarten (Dutch part).</p>"
         },
+        {
+          "name": "SY",
+          "description": "<p>Syria.</p>"
+        },
         {
           "name": "SZ",
           "description": "<p>Swaziland.</p>"
diff --git a/src/graphql/data/ghec/schema.docs.graphql b/src/graphql/data/ghec/schema.docs.graphql
index 4706bc555fb0..f7234dcc468d 100644
--- a/src/graphql/data/ghec/schema.docs.graphql
+++ b/src/graphql/data/ghec/schema.docs.graphql
@@ -57941,6 +57941,11 @@ enum SponsorsCountryOrRegionCode {
   """
   SX
 
+  """
+  Syria
+  """
+  SY
+
   """
   Swaziland
   """
diff --git a/src/graphql/data/ghec/schema.json b/src/graphql/data/ghec/schema.json
index 3c939b351ad3..456d96c7e4ff 100644
--- a/src/graphql/data/ghec/schema.json
+++ b/src/graphql/data/ghec/schema.json
@@ -94405,6 +94405,10 @@
           "name": "SX",
           "description": "<p>Sint Maarten (Dutch part).</p>"
         },
+        {
+          "name": "SY",
+          "description": "<p>Syria.</p>"
+        },
         {
           "name": "SZ",
           "description": "<p>Swaziland.</p>"
diff --git a/src/secret-scanning/data/public-docs.yml b/src/secret-scanning/data/public-docs.yml
index c01480ecbedd..8c5e1dbdc91a 100644
--- a/src/secret-scanning/data/public-docs.yml
+++ b/src/secret-scanning/data/public-docs.yml
@@ -6,7 +6,7 @@
     ghec: '*'
   isPublic: false
   isPrivateWithGhas: true
-  hasPushProtection: false
+  hasPushProtection: true
   hasValidityCheck: false
   base64Supported: false
   isduplicate: false
@@ -121,7 +121,7 @@
     ghec: '*'
   isPublic: false
   isPrivateWithGhas: true
-  hasPushProtection: false
+  hasPushProtection: true
   hasValidityCheck: false
   base64Supported: false
   isduplicate: false
@@ -199,7 +199,6 @@
   isPrivateWithGhas: true
   hasPushProtection: true
   hasValidityCheck: '{% ifversion fpt or ghes %}false{% else %}true{% endif %}'
-  ismultipart: true
   base64Supported: false
   isduplicate: false
 - provider: Amazon AWS
@@ -1502,7 +1501,7 @@
     ghec: '*'
   isPublic: true
   isPrivateWithGhas: true
-  hasPushProtection: false
+  hasPushProtection: true
   hasValidityCheck: false
   base64Supported: false
   isduplicate: false
@@ -3842,7 +3841,7 @@
     ghes: '*'
   isPublic: false
   isPrivateWithGhas: true
-  hasPushProtection: false
+  hasPushProtection: true
   hasValidityCheck: '{% ifversion fpt or ghes %}false{% else %}true{% endif %}'
   base64Supported: false
   isduplicate: false
@@ -5712,7 +5711,7 @@
     ghec: '*'
   isPublic: false
   isPrivateWithGhas: true
-  hasPushProtection: false
+  hasPushProtection: true
   hasValidityCheck: false
   base64Supported: false
   isduplicate: false
diff --git a/src/secret-scanning/lib/config.json b/src/secret-scanning/lib/config.json
index ea0204bae18a..fe90868fff4e 100644
--- a/src/secret-scanning/lib/config.json
+++ b/src/secret-scanning/lib/config.json
@@ -1,5 +1,5 @@
 {
-  "sha": "7d3e136cc0b0bc945f61287764dca2db9fb99494",
-  "blob-sha": "4aeb765d8bcffdaf9063e38b779b126b276c9f75",
+  "sha": "ae0af3739bfc23949e0cf24101edb7952cbdf8a8",
+  "blob-sha": "ec6452075cc3fa2334a2677e3492d59c1bfa4cdf",
   "targetFilename": "code-security/secret-scanning/introduction/supported-secret-scanning-patterns"
 }
\ No newline at end of file