diff --git a/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/viewing-push-logs.md b/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/viewing-push-logs.md
index 24ff12ec202c..0454c99767f8 100644
--- a/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/viewing-push-logs.md
+++ b/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/viewing-push-logs.md
@@ -44,5 +44,5 @@ For more information, see [AUTOTITLE](/repositories/viewing-activity-and-data-fo
 1. In the appropriate Git repository, open the audit log file:
 
    ```shell
-   ghe-repo OWNER/REPOSITORY -c "cat audit_log"
+   ghe-spokesctl ssh --primary OWNER/REPOSITORY -- cat audit_log
    ```
diff --git a/content/billing/using-the-new-billing-platform/about-the-billing-cycle.md b/content/billing/using-the-new-billing-platform/about-the-billing-cycle.md
index 70aa0217a0ff..144c256d9638 100644
--- a/content/billing/using-the-new-billing-platform/about-the-billing-cycle.md
+++ b/content/billing/using-the-new-billing-platform/about-the-billing-cycle.md
@@ -29,6 +29,8 @@ At the end of each month, your metered usage is calculated and scheduled to be b
 
 {% ifversion fpt %}For personal accounts and organizations, your bill cycle day is typically the day you started a paid plan (not necessarily when the account was created).{% elsif ghec %}Your bill cycle day is typically determined by when you converted from a trial to a paid enterprise account.{% endif %} For example, if you {% ifversion fpt %}started a paid plan{% elsif ghec %}converted from a trial{% endif %} on the 15th of a month, you will be billed on the 15th of each subsequent month.
 
+> [!NOTE] If you are paying via an Azure subscription ID, your **billing period** will run from the first day of each month to the last day of the month. To access your specific **bill cycle day**, please visit the Azure commerce portal.
+
 ## Billing cycles for volume-based products
 
 Volume-based licenses may follow a different billing cycle, even if your account is on the new billing platform. These products are often billed based on the anniversary date of your subscription rather than by calendar month.
diff --git a/data/features/push-rulesets.yml b/data/features/push-rulesets.yml
index efc10be70851..5c5f5448a5ec 100644
--- a/data/features/push-rulesets.yml
+++ b/data/features/push-rulesets.yml
@@ -3,4 +3,4 @@
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>=3.15'
+  ghes: '>=3.17'
diff --git a/data/reusables/enterprise-migration-tool/data-not-migrated.md b/data/reusables/enterprise-migration-tool/data-not-migrated.md
index a825fc965c83..80559e32d23d 100644
--- a/data/reusables/enterprise-migration-tool/data-not-migrated.md
+++ b/data/reusables/enterprise-migration-tool/data-not-migrated.md
@@ -9,6 +9,7 @@
 * {% data variables.product.prodname_actions %} secrets, variables, environments, self-hosted runners, {% data variables.actions.hosted_runner %}s, or workflow run history
 * GitHub Apps and GitHub App installations
 * {% data variables.large_files.product_name_short %} objects and large binaries (repositories using {% data variables.large_files.product_name_short %} are still supported, see [Limitations of {% data variables.product.prodname_importer_proper_name %}](#limitations-of-github-enterprise-importer))
+* Links from commits to pull requests that were rebase merged
 * Packages in {% data variables.product.prodname_registry %}
 * Projects (classic) at the organization level
 * {% data variables.product.prodname_projects_v2 %} (the new projects experience)