datastax · aimurphy · Jan 22, 2026 · skedwards88 · Jan 26, 2026
diff --git a/antora.yml b/antora.yml
@@ -10,7 +10,7 @@ asciidoc:
   attributes:
     #General attributes
     company: 'DataStax'
-    support-url: 'https://support.datastax.com'
+    support-url: 'https://www.ibm.com/mysupport/s/'
     #Other product attributes
     cass-reg: 'Apache Cassandra(R)'
     cass: 'Apache Cassandra'

diff --git a/local-preview-playbook.yml b/local-preview-playbook.yml
@@ -71,7 +71,7 @@ asciidoc:
     scb-brief: 'Secure Connect Bundle'
     astra-streaming-examples-repo: 'https://raw.githubusercontent.com/datastax/astra-streaming-examples/master'
     luna-streaming-examples-repo: 'https://raw.githubusercontent.com/datastaxdevs/luna-streaming-examples/main'
-    support_url: 'https://support.datastax.com'
+    support_url: 'https://www.ibm.com/mysupport/s/'
     glossary-url: 'https://docs.datastax.com/en/glossary/docs/index.html#'
     emoji-tada: "&#127881;"
     emoji-rocket: "&#128640;"

diff --git a/modules/ROOT/pages/astra-migration-paths.adoc b/modules/ROOT/pages/astra-migration-paths.adoc
@@ -4,7 +4,7 @@
 The {astra} migration toolkit includes all xref:ROOT:components.adoc[{company} migration tools] that are designed to help you xref:astra-db-serverless:databases:migration-path-serverless.adoc[migrate your data to {astra-db}].
 
 Use the following table to learn which tools are compatible with your current database provider or service.
-If you have questions about migrating from a specific source to {astra-db}, contact your {company} account representative or {support-url}[{company} Support].
+If you have questions about migrating from a specific source to {astra-db}, contact your {company} account representative or {support-url}[IBM Support].
 
 .Migration tool compatibility
 [cols="2,1,1,1,1"]

diff --git a/modules/ROOT/pages/deployment-infrastructure.adoc b/modules/ROOT/pages/deployment-infrastructure.adoc
@@ -31,7 +31,7 @@ If you have a multi-datacenter cluster with multiple set of client application i
 In the configuration for each {product-proxy} deployment, specify only the contact points that belong to that datacenter, and set the `xref:ROOT:deploy-proxy-monitoring.adoc#_advanced_configuration_optional[origin_local_datacenter]` and `xref:ROOT:deploy-proxy-monitoring.adoc#_advanced_configuration_optional[target_local_datacenter]` properties as needed.
 
 If your origin and target clusters are both multi-datacenter clusters, this configuration will be more complicated to correctly orchestrate traffic routing through {product-proxy}.
-{company} recommends contacting {support-url}[{company} Support] for assistance with complex multi-region and multi-datacenter migrations.
+{company} recommends contacting {support-url}[IBM Support] for assistance with complex multi-region and multi-datacenter migrations.
 
 === Don't deploy {product-proxy} as a sidecar
 
@@ -116,7 +116,7 @@ Additionally, make sure that your origin and target clusters can handle high tra
 
 Test migrations in a lower environment before you proceed with production migrations.
 
-If you need assistance with your migration, contact {support-url}[{company} Support].
+If you need assistance with your migration, contact {support-url}[IBM Support].
 ====
 --
 

diff --git a/modules/ROOT/pages/dse-migration-paths.adoc b/modules/ROOT/pages/dse-migration-paths.adoc
@@ -58,7 +58,7 @@ For database-specific connection information, see the documentation for your tar
 
 == Get support for your migration
 
-If you have questions about your {dse-short} migration, contact your {company} account representative or {support-url}[{company} Support].
+If you have questions about your {dse-short} migration, contact your {company} account representative or {support-url}[IBM Support].
 
 == See also
 

diff --git a/modules/ROOT/pages/faqs.adoc b/modules/ROOT/pages/faqs.adoc
@@ -103,7 +103,7 @@ You can have the confidence that you are using tools designed specifically to ha
 
 == Where can I get help with my migration?
 
-Technical assistance with the {product-short} process is available from {support-url}[{company} Support] for {dse-short} users, https://www.ibm.com/docs/en/esfac[IBM Elite Support for {cass}] subscribers, and {astra} organizations on an **Enterprise** plan.
+Technical assistance with the {product-short} process is available from {support-url}[IBM Support] for {dse-short} users, https://www.ibm.com/docs/en/esfac[IBM Elite Support for {cass}] subscribers, and {astra} organizations on an **Enterprise** plan.
 
 For any observed problems with {product-proxy} or the other open-source {product-short} and data migration tools, you can report an issue in their respective GitHub repositories:
 

diff --git a/modules/ROOT/pages/feasibility-checklists.adoc b/modules/ROOT/pages/feasibility-checklists.adoc
@@ -317,7 +317,7 @@ As a managed database-as-a-service (DBaaS) offering, {astra} implements xref:ast
 Make sure your application workloads and CQL statements are compatible with these limitations.
 +
 In self-managed clusters, such as {dse-short} and {cass-short}, you can configure the database limits in `cassandra.yml`.
-Many of these limits aren't configurable in {astra}, and those that can be changed require intervention by {company} Support.
+However, the xref:astra-db-serverless:databases:database-limits.adoc#cassandra-configuration-properties[{astra} `cassandra.yml`] cannot be changed unless explicitly approved and implemented by {company}.
 
 {astra} doesn't support consistency level ONE::
 `CL.ONE` isn't supported by {astra}, and read and write requests sent through {product-proxy} with `CL.ONE` to {astra-db} databases always fail.

diff --git a/modules/ROOT/pages/hcd-migration-paths.adoc b/modules/ROOT/pages/hcd-migration-paths.adoc
@@ -70,7 +70,7 @@ For more information about connecting to {hcd-short} databases, see the xref:hyp
 
 == Get support for your migration
 
-If you have questions about your {hcd-short} migration, contact your {company} account representative or {support-url}[{company} Support].
+If you have questions about your {hcd-short} migration, contact your {company} account representative or {support-url}[IBM Support].
 
 == See also
 

diff --git a/modules/ROOT/pages/troubleshooting-tips.adoc b/modules/ROOT/pages/troubleshooting-tips.adoc
@@ -5,7 +5,7 @@
 
 This page provides general troubleshooting advice and describes some common issues you might encounter with {product} ({product-short}).
 
-For additional assistance, you can <<report-an-issue,report an issue>>, contact your {company} account representative, or contact {support-url}[{company} Support].
+For additional assistance, you can <<report-an-issue,report an issue>>, contact your {company} account representative, or contact {support-url}[IBM Support].
 
 [#proxy-logs]
 == Check {product-proxy} logs

diff --git a/modules/ROOT/pages/zdm-proxy-migration-paths.adoc b/modules/ROOT/pages/zdm-proxy-migration-paths.adoc
@@ -18,7 +18,7 @@ Make sure you transform or prepare the data to comply with the target cluster's
 For more complex migrations, such as RDBMS-to-NoSQL migrations, it is likely that your migration will require downtime for additional processing, such as extract, transform, and load (ETL) operations.
 For example, see the data modeling and compatibility considerations for xref:6.9@dse:managing:operations/migrate-data.adoc[migrating to {dse-short}].
 
-{company} recommends that you contact your {company} account representative or {support-url}[{company} Support] for guidance on incompatible or partially compatible migrations.
+{company} recommends that you contact your {company} account representative or {support-url}[IBM Support] for guidance on incompatible or partially compatible migrations.
 
 == See also
 

diff --git a/modules/ROOT/partials/multi-region-migrations.adoc b/modules/ROOT/partials/multi-region-migrations.adoc
@@ -12,4 +12,4 @@ This strategy allows {astra-db}'s eventual consistency model to replicate the da
 However, this approach isn't suitable for all migrations.
 
 It is difficult to provide a one-size-fits-all solution for multi-region migrations due to the potential complexity and variability of these scenarios.
-For assistance planning a multi-region migration, contact your {company} account representative or {support-url}[{company} Support].
+For assistance planning a multi-region migration, contact your {company} account representative or {support-url}[IBM Support].
diff --git a/modules/sideloader/pages/prepare-sideloader.adoc b/modules/sideloader/pages/prepare-sideloader.adoc
@@ -60,12 +60,12 @@ Target database is a {db-serverless} database::
 * Maximum capacity: Greater than the minimum by several units to allow autoscaling during resource intensive stages of the migration.
 +
 For non-trivial migrations, consider setting the maximum to 10.
-For extremely large migrations, contact your {company} account representative or {support-url}[{company} Support] to request more than 10 units to support your migration.
+For extremely large migrations, contact your {company} account representative or {support-url}[IBM Support] to request more than 10 units to support your migration.
 
 Target database is a {db-serverless-vector} database::
 +
 By default, {db-serverless-vector} databases can have no more than one unit per PCU group.
-For any non-trivial migration, contact your {company} account representative or {support-url}[{company} Support] for assistance configuring a PCU group for your target {db-serverless-vector} database.
+For any non-trivial migration, contact your {company} account representative or {support-url}[IBM Support] for assistance configuring a PCU group for your target {db-serverless-vector} database.
 ====
 
 After the migration, you can move your target database out of the flexible capacity PCU group, and then park or delete the group.
@@ -104,14 +104,14 @@ If the minimum is greater than the reserved capacity, the surplus capacity is pr
 * Maximum capacity: Greater than the minimum by several units to allow autoscaling during resource intensive stages of the migration.
 +
 For non-trivial migrations, consider setting the maximum to 10.
-For extremely large migrations, contact your {company} account representative or {support-url}[{company} Support] to request more than 10 units to support your migration.
+For extremely large migrations, contact your {company} account representative or {support-url}[IBM Support] to request more than 10 units to support your migration.
 +
 After the migration, you can reduce the minimum and maximum capacity down to the levels required for normal database operations.
 
 Target database is a {db-serverless-vector} database::
 +
 By default, {db-serverless-vector} databases can have no more than one unit per PCU group.
-For any non-trivial migration, contact your {company} account representative or {support-url}[{company} Support] for assistance configuring a PCU group for your target {db-serverless-vector} database.
+For any non-trivial migration, contact your {company} account representative or {support-url}[IBM Support] for assistance configuring a PCU group for your target {db-serverless-vector} database.
 ====
 --
 ======

diff --git a/modules/sideloader/pages/troubleshoot-sideloader.adoc b/modules/sideloader/pages/troubleshoot-sideloader.adoc
@@ -97,4 +97,4 @@ In this case, if the migration _didn't_ fail due to a problem with the snapshot
 +
 This starts a fresh migration with a new migration directory, a migration ID, and upload credentials.
 
-. If the migration fails again and you are unable to determine the cause of the failure, contact {support-url}[{company} Support].
+. If the migration fails again and you are unable to determine the cause of the failure, contact {support-url}[IBM Support].