Merge pull request #298839 from Clare-Zheng82/0424-Update_oracle_GA_and_upgrade_connector

[Doc update] Update Oracle, Cassandra GA and upgrade doc dates

Author: ttorble

articles/data-factory/connector-cassandra.md

@@ -6,7 +6,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 04/02/2025
+ms.date: 05/06/2025
 ms.author: jianleishen
 ---
 # Copy data from Cassandra using Azure Data Factory or Synapse Analytics
@@ -30,7 +30,7 @@ For a list of data stores that are supported as sources/sinks, see the [Supporte
 
 Specifically, this Cassandra connector supports:
 
-- Cassandra **versions 3.x.x and 4.x.x** for version 2.0 (Preview). 
+- Cassandra **versions 3.x.x and 4.x.x** for version 2.0. 
 - Cassandra **versions 2.x and 3.x** for version 1.0. 
 - Copying data using **Basic** or **Anonymous** authentication.
 
@@ -81,7 +81,7 @@ The following properties are supported for Cassandra linked service:
 | Property | Description | Required |
 |:--- |:--- |:--- |
 | type |The type property must be set to: **Cassandra** |Yes |
-| version | The version that you specify. | Yes for version 2.0 (Preview). |
+| version | The version that you specify. | Yes for version 2.0. |
 | host |One or more IP addresses or host names of Cassandra servers.<br/>Specify a comma-separated list of IP addresses or host names to connect to all servers concurrently. |Yes |
 | port |The TCP port that the Cassandra server uses to listen for client connections. |No (default is 9042) |
 | authenticationType | Type of authentication used to connect to the Cassandra database.<br/>Allowed values are: **Basic**, and **Anonymous**. |Yes |
@@ -92,7 +92,7 @@ The following properties are supported for Cassandra linked service:
 >[!NOTE]
 >Currently connection to Cassandra using TLS is not supported.
 
-**Example: version 2.0 (Preview)**
+**Example: version 2.0**
 
 ```json
 {
@@ -180,7 +180,7 @@ For a full list of sections and properties available for defining activities, se
 
 ### Cassandra as source
 
-If you use version 2.0 (Preview) to copy data from Cassandra, set the source type in the copy activity to **CassandraSource**. The following properties are supported in the copy activity **source** section:
+If you use version 2.0 to copy data from Cassandra, set the source type in the copy activity to **CassandraSource**. The following properties are supported in the copy activity **source** section:
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
@@ -233,7 +233,7 @@ If you use version 1.0 to copy data from Cassandra, set the source type in the c
 
 When copying data from Cassandra, the following mappings are used from Cassandra data types to interim data types used internally within the service. See [Schema and data type mappings](copy-activity-schema-and-type-mapping.md) to learn about how copy activity maps the source schema and data type to the sink.
 
-| Cassandra data type | Interim service data type (for version 2.0 (Preview)) | Interim service data type (for version 1.0) |
+| Cassandra data type | Interim service data type (for version 2.0) | Interim service data type (for version 1.0) |
 |:--- |:--- |:--- |
 | ASCII |String |String |
 | BIGINT |Int64 |Int64 |
@@ -262,9 +262,9 @@ When copying data from Cassandra, the following mappings are used from Cassandra
 > The length of Binary Column and String Column lengths cannot be greater than 4000.
 >
 
-## Work with collections when using version 2.0 (Preview)
+## Work with collections when using version 2.0
 
-When using version 2.0 (Preview) to copy data from your Cassandra database, no virtual tables for collection types are created. You can copy a source table to the sink in its original type in JSON format.
+When using version 2.0 to copy data from your Cassandra database, no virtual tables for collection types are created. You can copy a source table to the sink in its original type in JSON format.
 
 ### Example
 
@@ -351,21 +351,21 @@ To learn details about the properties, check [Lookup activity](control-flow-look
 
 Here are steps that help you upgrade the Cassandra connector:
 
-1. In **Edit linked service** page, select version 2.0 (Preview) and configure the linked service by referring to [Linked service properties](#linked-service-properties).
+1. In **Edit linked service** page, select version 2.0 and configure the linked service by referring to [Linked service properties](#linked-service-properties).
 
-2. In version 2.0 (Preview), the `query` in the copy activity source supports only CQL query, not SQL-92 query. For more information, see [Cassandra as source](#cassandra-as-source).
+2. In version 2.0, the `query` in the copy activity source supports only CQL query, not SQL-92 query. For more information, see [Cassandra as source](#cassandra-as-source).
 
-3. The data type mapping for version 2.0 (Preview) is different from that for version 1.0. To learn the latest data type mapping, see [Data type mapping for Cassandra](#data-type-mapping-for-cassandra). 
+3. The data type mapping for version 2.0 is different from that for version 1.0. To learn the latest data type mapping, see [Data type mapping for Cassandra](#data-type-mapping-for-cassandra). 
 
-## Differences between Cassandra version 2.0 (Preview) and version 1.0 
+## Differences between Cassandra version 2.0 and version 1.0 
 
-The Cassandra connector version 2.0 (Preview) offers new functionalities and is compatible with most features of version 1.0. The table below shows the feature differences between version 2.0 (Preview) and version 1.0. 
+The Cassandra connector version 2.0 offers new functionalities and is compatible with most features of version 1.0. The table below shows the feature differences between version 2.0 and version 1.0. 
 
-| Version 2.0 (Preview) | Version 1.0 |
+| Version 2.0 | Version 1.0 |
 | --- | --- |
 | Support CQL query. | Support SQL-92 query or CQL query. |
 | Support specifying `keyspace` and `tableName` separately in dataset. | Support editing `keyspace` when you select enter manually table name in dataset. |
-| No virtual tables are created for collection types. For more information, see [Work with collections when using version 2.0 (Preview)](#work-with-collections-when-using-version-20-preview).  | Virtual tables are created for collection types. For more information, see [Work with Cassandra collection types using virtual table when using version 1.0](#work-with-collections-using-virtual-table-when-using-version-10). |
+| No virtual tables are created for collection types. For more information, see [Work with collections when using version 2.0](#work-with-collections-when-using-version-20).  | Virtual tables are created for collection types. For more information, see [Work with Cassandra collection types using virtual table when using version 1.0](#work-with-collections-using-virtual-table-when-using-version-10). |
 | The following mappings are used from Cassandra data types to interim service data type. <br><br> SMALLINT -> Short <br> TINYINT -> SByte | The following mappings are used from Cassandra data types to interim service data type. <br><br> SMALLINT -> Int16 <br> TINYINT -> Int16 | 
 
 ## Related content

articles/data-factory/connector-deprecation-plan.md

@@ -7,7 +7,7 @@ ms.service: azure-data-factory
 ms.subservice: data-movement
 ms.topic: concept-article
 ms.custom: references_regions
-ms.date: 04/14/2025
+ms.date: 04/24/2025
 ---
 
 # Upgrade plan for Azure Data Factory connectors
@@ -22,20 +22,20 @@ This article describes future upgrades for some connectors of Azure Data Factory
 | Connector|Upgrade Guidance|Release stage |End of Support Date  |Disabled Date  | 
 |:-- |:-- |:-- |:-- | :-- | 
 | [Azure Database for PostgreSQL (version 1.0)](connector-azure-database-for-postgresql.md)   | [Link](connector-azure-database-for-postgresql.md#upgrade-the-azure-database-for-postgresql-connector) | GA version available | To be determined | /  | 
-| [Cassandra (version 1.0)](connector-cassandra.md) |[Link](connector-cassandra.md#upgrade-the-cassandra-connector) | Preview version available | To be determined | / | 
+| [Cassandra (version 1.0)](connector-cassandra.md) |[Link](connector-cassandra.md#upgrade-the-cassandra-connector) | GA version available |July 31, 2025 | September 30, 2025 | 
 | [Google BigQuery (V1)](connector-google-bigquery-legacy.md)  | [Link](connector-google-bigquery.md#upgrade-the-google-bigquery-linked-service) |End of support and GA version available | October 31, 2024 | September 30, 2025| 
 | [Greenplum (version 1.0)](connector-greenplum.md)  | [Link](connector-greenplum.md#upgrade-the-greenplum-connector) |Preview version available | To be determined | /| 
 | [MariaDB (version 1.0)](connector-mariadb.md)  | [Link](connector-mariadb.md#upgrade-the-mariadb-driver-version) | End of support and GA version available | October 31, 2024 | September 30, 2025| 
 | [MySQL (version 1.0)](connector-mysql.md)  | [Link](connector-mysql.md#upgrade-the-mysql-driver-version) |End of support and GA version available | October 31, 2024| September 30, 2025|
-| [Oracle (version 1.0)](connector-oracle.md) |[Link](connector-oracle.md#upgrade-the-oracle-connector) | Preview version available | To be determined| / |  
-| [Salesforce (V1)](connector-salesforce-legacy.md)   | [Link](connector-salesforce.md#upgrade-the-salesforce-linked-service) | GA version available | To be determined | /| 
-| [Salesforce Service Cloud (V1)](connector-salesforce-service-cloud-legacy.md)   | [Link](connector-salesforce-service-cloud.md#upgrade-the-salesforce-service-cloud-linked-service) | GA version available | To be determined |/ | 
+| [Oracle (version 1.0)](connector-oracle.md) |[Link](connector-oracle.md#upgrade-the-oracle-connector) | GA version available | July 31, 2025| October 31, 2025 |  
 | [PostgreSQL (V1)](connector-postgresql-legacy.md)   | [Link](connector-postgresql.md#upgrade-the-postgresql-linked-service)| End of support and GA version available |October 31, 2024 | September 30, 2025| 
 | [Presto (version 1.0)](connector-presto.md)   | [Link](connector-presto.md#upgrade-the-presto-connector)| Preview version available |To be determined | /  | 
-| [ServiceNow (V1)](connector-servicenow-legacy.md)   | [Link](connector-servicenow.md#upgrade-your-servicenow-linked-service) | GA version available | To be determined | / | 
-| [Snowflake (V1)](connector-snowflake-legacy.md)   | [Link](connector-snowflake.md#upgrade-the-snowflake-linked-service) | GA version available | To be determined | /  | 
+| [Salesforce (V1)](connector-salesforce-legacy.md)   | [Link](connector-salesforce.md#upgrade-the-salesforce-linked-service) | GA version available | June 30, 2025 | September 30, 2025| 
+| [Salesforce Service Cloud (V1)](connector-salesforce-service-cloud-legacy.md)   | [Link](connector-salesforce-service-cloud.md#upgrade-the-salesforce-service-cloud-linked-service) | GA version available | June 30, 2025  |September 30, 2025 | 
+| [ServiceNow (V1)](connector-servicenow-legacy.md)   | [Link](connector-servicenow.md#upgrade-your-servicenow-linked-service) | GA version available | June 30, 2025 | September 30, 2025 | 
+| [Snowflake (V1)](connector-snowflake-legacy.md)   | [Link](connector-snowflake.md#upgrade-the-snowflake-linked-service) | GA version available | June 30, 2025  | September 30, 2025  | 
 | [Spark (version 1.0)](connector-spark.md)   | [Link](connector-spark.md#upgrade-the-spark-connector)| Preview version available |To be determined | /  | 
-| [Vertica (version 1.0)](connector-vertica.md)| [Link](connector-vertica.md#upgrade-the-vertica-version) | GA version available | July 31, 2025 | /  | 
+| [Vertica (version 1.0)](connector-vertica.md)| [Link](connector-vertica.md#upgrade-the-vertica-version) | GA version available | July 31, 2025 | September 30, 2025  | 
 | [Azure Database for MariaDB](connector-azure-database-for-mariadb.md) |/ | End of support |December 31, 2024 | December 31, 2024 | 
 | [Concur (Preview)](connector-concur.md) |/ | End of support | December 31, 2024 | December 31, 2024 | 
 | [Couchbase (Preview)](connector-couchbase.md) |/ | End of support | December 31, 2024 | December 31, 2024 | 
@@ -52,7 +52,7 @@ This article describes future upgrades for some connectors of Azure Data Factory
 | [Zoho (Preview)](connector-zoho.md) |/ | End of support | December 31, 2024 | December 31, 2024 | 
 | [Amazon Marketplace Web Service](connector-amazon-marketplace-web-service.md)|/ | Disabled |/  |/  | 
 
-If you need upgrade help, contact us via the way provided in the [FAQ article](connector-deprecation-frequently-asked-questions.md#what-should-i-do-if-i-encounter-the-feature-gaps-and-errors-bugs-that-are-preventing-me-from-migrating-to-the-new-connectors). 
+If you encounter any gaps while upgrading your connector to the latest version, please contact for help via the way provided in the [FAQ article](connector-deprecation-frequently-asked-questions.md#what-should-i-do-if-i-encounter-the-feature-gaps-and-errors-bugs-that-are-preventing-me-from-migrating-to-the-new-connectors). 
 
 ## Release stages and support
 
@@ -110,13 +110,10 @@ The following connectors are at End of Support stage. You should migrate to [alt
 - [Salesforce Marketing Cloud](connector-salesforce-marketing-cloud.md)
 - [Zoho (Preview)](connector-zoho.md)
 
-
-## Connectors that are deprecated
-
-The following connector was deprecated.
-
+The following connector is at End of Support stage.
 - [Amazon Marketplace Web Service](connector-amazon-marketplace-web-service.md)
 
+
 ## Options to replace deprecated connectors
 
 If V1 connectors are deprecated with no updated connectors available, you can still use the
@@ -134,6 +131,19 @@ Here's the steps to get your objects which still rely on the deprecated connecto
 
 :::image type="content" source="media/connector-deprecation-plan/linked-services-page.png" alt-text="Screenshot of the linked services page." lightbox="media/connector-deprecation-plan/linked-services-page.png":::
 
+## How to find notifications in Azure Service Health portal
+
+Regular notifications are sent to you to help you upgrade related connectors, or notify you the connectors' End of Support or disabled dates. You can find the notification under Service Health portal - Health advisories tab. 
+
+Here's the steps to help you find the notification: 
+
+1. Navigate to [Service Health portal](https://portal.azure.com/#view/Microsoft_Azure_Health/AzureHealthBrowseBlade/%7E/serviceIssues) or you can select **Service Health** icon on your Azure portal dashboard.
+1. Go to **Health advisories** tab and you can see the notification related to your connectors in the list. You can also go to **Health history** tab to check historical notifications.
+
+    :::image type="content" source="media/connector-deprecation-plan/service-health-health-advisories.png" alt-text="Screenshot of service health.":::
+
+To learn more about the Service Health portal, see this [article](/azure/service-health/service-health-overview).
+
 ## Related content
 
 - [Azure Data Factory connectors overview](connector-overview.md)