Merge branch 'MicrosoftDocs:main' into heidist-fix

Author: HeidiSteen

articles/communication-services/quickstarts/telephony/get-phone-number.md

@@ -10,7 +10,7 @@ ms.topic: quickstart
 ms.service: azure-communication-services
 ms.subservice: pstn
 ms.custom: references_regions, mode-other, devx-track-extended-java, devx-track-js, devx-track-python
-zone_pivot_groups: acs-azcli-azp-azpnew-java-net-python-csharp-js
+zone_pivot_groups: acs-azcli-azp-java-net-python-csharp-js
 ---
 
 # Quickstart: Get and manage phone numbers
@@ -27,10 +27,6 @@ zone_pivot_groups: acs-azcli-azp-azpnew-java-net-python-csharp-js
 [!INCLUDE [Azure portal](./includes/phone-numbers-portal.md)]
 ::: zone-end
 
-::: zone pivot="platform-azp-new"
-[!INCLUDE [Azure portal (new)](./includes/phone-numbers-portal-new.md)]
-::: zone-end
-
 ::: zone pivot="programming-language-csharp"
 [!INCLUDE [Azure portal](./includes/phone-numbers-net.md)]
 ::: zone-end

articles/communication-services/tutorials/migrating-to-azure-communication-services-calling.md

@@ -67,6 +67,9 @@ The following tables describe how to configure a collection of NSG allow rules.
 
 # [Consumption only environment](#tab/consumption-only)
 
+>[!Note]
+> When using Consumption only environments, all [outbound ports required by Azure Kubernetes Service](/azure/aks/outbound-rules-control-egress#required-outbound-network-rules-and-fqdns-for-aks-clusters) are also required for your container app.
+
 | Protocol | Source | Source ports | Destination | Destination ports | Description |
 |--|--|--|--|--|--|
 | TCP | Your container app's subnet<sup>1</sup> | \* | Your Container Registry | Your container registry's port | This is required to communicate with your container registry. For example, when using ACR, you need `AzureContainerRegistry` and `AzureActiveDirectory` for the destination, and the port will be your container registry's port unless using private endpoints.<sup>2</sup> |

articles/container-apps/firewall-integration.md

@@ -145,9 +145,9 @@ Follow these steps to get started:
 
    # Installs Node and the npm packages saved in your package.json file in the build
 
-   - task: NodeTool@0
+   - task: UseNode@1
      inputs:
-       versionSpec: '14.x'
+       version: '18.x'
      displayName: 'Install Node.js'
 
    - task: Npm@1

articles/data-factory/continuous-integration-delivery-improvements.md

@@ -170,6 +170,11 @@ For other scenarios than binary file copy, copy activity rerun starts from the b
 
 While copying data from source to sink, in scenarios like data lake migration, you can also choose to preserve the metadata and ACLs along with data using copy activity. See [Preserve metadata](copy-activity-preserve-metadata.md) for details.
 
+## Add metadata tags to file based sink
+When the sink is Azure Storage based (Azure data lake storage or Azure Blob Storage), we can opt to add some metadata to the files. These metadata will be appearing as part of the file properties as Key-Value pairs. 
+For all the types of file based sinks, you can add metadata involving dynamic content using the pipeline parameters, system variables, functions and variables. 
+In addition to this, for binary file based sink, you have the option to add Last Modified datetime (of the source file) using the keyword $$LASTMODIFIED, as well as custom values as a metadata to the sink file. 
+
 ## Schema and data type mapping
 
 See [Schema and data type mapping](copy-activity-schema-and-type-mapping.md) for information about how the Copy activity maps your source data to your sink.

articles/data-factory/copy-activity-overview.md

@@ -24,8 +24,8 @@ The in-place migration provides a highly resilient and self-healing offline migr
 > [!NOTE]
 > In-place migration is only for Single Server database workloads with Basic or GP SKU, data storage used < 10 GiB and no complex features (CMK, AAD, Read Replica, Private Link) enabled. All other Single Server workloads are recommended to use user-initiated migration tooling offered by Azure - Azure DMS, Azure MySQL Import to migrate.
 
-## What's new?
-* If you own a Single Server workload with Basic or GP SKU, data storage used <= 20 GiB and no complex features (CMK, AAD, Read Replica, Private Link) enabled, you can now nominate yourself (if not already scheduled by the service) for auto-migration by submitting your server details through this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4lhLelkCklCuumNujnaQ-ZUQzRKSVBBV0VXTFRMSDFKSUtLUDlaNTA5Wi4u). (Sept 2023)
+## Eligibility
+* If you own a Single Server workload with Basic or GP SKU, data storage used <= 20 GiB and no complex features (CMK, AAD, Read Replica, Private Link) enabled, you can now nominate yourself (if not already scheduled by the service) for auto-migration by submitting your server details through this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4lhLelkCklCuumNujnaQ-ZUQzRKSVBBV0VXTFRMSDFKSUtLUDlaNTA5Wi4u).
 
 ## Configure migration alerts and review migration schedule
 

articles/machine-learning/how-to-create-attach-compute-cluster.md

@@ -1,16 +1,16 @@
 ---
 title: Collation support
-description: Collation types support for Synapse SQL in Azure Synapse Analytics
+description: Collation types support for Synapse SQL in Azure Synapse Analytics.
 author: filippopovic
-ms.service: synapse-analytics 
-ms.topic: reference
-ms.subservice: sql
-ms.date: 02/15/2023
 ms.author: fipopovi
 ms.reviewer: wiassaf, kecona
+ms.date: 01/30/2024
+ms.service: synapse-analytics
+ms.subservice: sql
+ms.topic: reference
 ---
 
-# Database collation support for Synapse SQL in Azure Synapse Analytics 
+# Database collation support for Synapse SQL in Azure Synapse Analytics
 
 Collations provide the locale, code page, sort order, and character sensitivity rules for character-based data types. Once chosen, all columns and expressions requiring collation information inherit the chosen collation from the database setting. The default inheritance can be overridden by explicitly stating a different collation for a character-based data type.
 
@@ -37,10 +37,10 @@ The following table shows which collation types are supported by which service.
 |:-----------------------------------------:|:-------------------:|:-----------------------:|:------------------:|:------------------:|
 | Non-UTF-8 Collations                      | Yes                 | Yes                     | Yes                | Yes                |
 | UTF-8                                     | Yes                 | Yes                     | No                 | No                 |
-| Japanese_Bushu_Kakusu_140_*               | Yes                 | Yes                     | No                 | No                 |
-| Japanese_XJIS_140_*                       | Yes                 | Yes                     | No                 | No                 |
-| SQL_EBCDIC1141_CP1_CS_AS                  | No                  | No                      | No                 | No                 |
-| SQL_EBCDIC277_2_CP1_CS_AS                 | No                  | No                      | No                 | No                 |
+| `Japanese_Bushu_Kakusu_140_*`               | Yes                 | Yes                     | No                 | No                 |
+| `Japanese_XJIS_140_*`                       | Yes                 | Yes                     | No                 | No                 |
+| `SQL_EBCDIC1141_CP1_CS_AS`                  | No                  | No                      | No                 | No                 |
+| `SQL_EBCDIC277_2_CP1_CS_AS`                 | No                  | No                      | No                 | No                 |
 
 
 ## Check the current collation
@@ -53,9 +53,21 @@ SELECT DATABASEPROPERTYEX(DB_NAME(), 'Collation') AS Collation;
 
 When passed 'Collation' as the property parameter, the DatabasePropertyEx function returns the current collation for the database specified. For more information, see [DATABASEPROPERTYEX](/sql/t-sql/functions/databasepropertyex-transact-sql?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json&view=azure-sqldw-latest&preserve-view=true).
 
-## Next steps
+## Check supported collation
+
+To check the list of supported collations in your dedicated SQL pool:
+
+```sql
+USE master
+GO
+SELECT * FROM sys.fn_helpcollations();
+```
+
+Run the [sys.fn_helpcollations](/sql/relational-databases/system-functions/sys-fn-helpcollations-transact-sql?view=azure-sqldw-latest&preserve-view=true) function from the `master` database.
+
+## Related content
 
 Additional information on best practices for dedicated SQL pool and serverless SQL pool can be found in the following articles:
 
-- [Best practices for dedicated SQL pool](./best-practices-dedicated-sql-pool.md)
-- [Best practices for serverless SQL pool](./best-practices-serverless-sql-pool.md)
+- [Best practices for dedicated SQL pools in Azure Synapse Analytics](best-practices-dedicated-sql-pool.md)
+- [Best practices for serverless SQL pool in Azure Synapse Analytics](best-practices-serverless-sql-pool.md)