@@ -7,6 +7,8 @@
     - /preparing-to-upgrade
     - /performing-an-upgrade
     - /troubleshooting-upgrades
-    - /automation-via-cli-api
   shortTitle: Upgrade your instance
+  redirect_from:
+    - /admin/upgrading-your-instance/automation-via-cli-api
+    - /admin/upgrading-your-instance/automation-via-cli-api/enterprise-server-upgrade-automation
 ---
@@ -37,10 +37,10 @@ For example, if you started a paid plan or converted from a trial on the 15th of
 
 ## Billing cycle for {% data variables.copilot.sandbox %} during public preview
 
-During {% data variables.release-phases.public_preview %}, eligible accounts receive a **$10 monthly entitlement** for cloud sandbox usage in **June 2026**. The entitlement applies as follows:
+During {% data variables.release-phases.public_preview %}, eligible accounts receive a **$10 monthly entitlement** for cloud sandbox usage through the end of **July 2026**. The entitlement applies as follows:
 
 * Usage above the entitlement is metered against your standard billing cycle and billed on your normal billing date.
-* The entitlement is discontinued after June 2026. Pricing and packaging after the preview is subject to change.
+* The entitlement is discontinued after July 2026. Pricing and packaging after the preview is subject to change.
 
 ## Billing cycles for volume-based products
 
 
@@ -40,7 +40,7 @@ For more information about {% data variables.copilot.sandbox %}, see [AUTOTITLE]
 
 ## Free and billed use
 
-During public preview, eligible {% data variables.product.github %} accounts receive a **$10 monthly entitlement** to try cloud sandboxes. This entitlement is available for June 2026. Any usage beyond the monthly entitlement is billed to your account.
+During public preview, eligible {% data variables.product.github %} accounts receive a **$10 monthly entitlement** to try cloud sandboxes. This entitlement is available through the end of July 2026. Any usage beyond the monthly entitlement is billed to your account.
 
 After the preview period ends, the entitlement no longer applies and all usage is billed.
 
 
@@ -39,7 +39,7 @@ Metrics are available through:
 
 In addition, {% data variables.product.prodname_copilot_short %} usage metrics incorporate **server-side telemetry** to identify active users that client-side telemetry alone may miss. Network conditions, proxy configurations, and client settings can prevent client telemetry from reaching {% data variables.product.github %}, so server-side signals ensure those users still appear in your reports.
 
-Users surfaced through server-side telemetry are fully counted toward your active user totals (such as daily active users), but their dimensional breakdowns—such as `totals_by_ide`, `totals_by_feature`, and lines-of-code metrics—remain empty until richer telemetry is available for them. Top-level totals and breakdowns for users already captured by client telemetry are unchanged.
+Users surfaced through server-side telemetry are fully counted toward your active user totals (such as daily active users, `daily_active_users` ). When available, they may also appear in `totals_by_ide` (including the most recently detected IDE and {% data variables.product.prodname_copilot_short %} extension versions in per-user reports). However, other dimensional breakdowns—such as `totals_by_feature` and lines-of-code metrics—remain empty until richer telemetry is available for them. Top-level totals and breakdowns for users already captured by client telemetry are unchanged.
 
 The data **does not include** activity from other {% data variables.product.prodname_copilot_short %} surfaces, such as:
 
 
@@ -81,6 +81,6 @@ The value `Unknown` appears in some API or export breakdowns when telemetry from
 
 ## Users surfaced by server-side telemetry
 
-{% data variables.product.prodname_copilot_short %} usage metrics combine client-side and server-side telemetry to identify active users. Users confirmed as active through server-side telemetry, but for whom no client telemetry was received, are included in your active user totals (such as `daily_active_users`). However, their dimensional breakdowns (`totals_by_ide`, `totals_by_feature`, `totals_by_language_feature`, `totals_by_language_model`, `totals_by_model_feature`) and lines-of-code metrics will be empty.
+{% data variables.product.prodname_copilot_short %} usage metrics combine client-side and server-side telemetry to identify active users. Users confirmed as active through server-side telemetry, but for whom no client telemetry was received, are included in your active user totals (such as `daily_active_users`). When available, these users may also appear in `totals_by_ide` (and in per-user reports this includes the most recently detected IDE and {% data variables.product.prodname_copilot_short %} extension versions). However, other dimensional breakdowns (`totals_by_feature`, `totals_by_language_feature`, `totals_by_language_model`, `totals_by_model_feature`) and lines-of-code metrics will still be empty.
 
 This means your top-level active user counts may be higher than the sum of users reflected in the breakdown arrays. This is expected behavior and does not indicate a data error.