Merge pull request #291879 from MicrosoftDocs/main

v-ccolin · web-flow · commit fa5a183b971a · 2024-12-12T12:18:20.000Z
Merge main to live, 4 AM
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -5,6 +5,11 @@
       "redirect_url": "/previous-versions/azure/partner-solutions/split-experimentation/create",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/migrate/context/vmware-context.yml",
+      "redirect_url": "articles/migrate/context/migrate-context",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/partner-solutions/split-experimentation/how-to-set-up-data-access.md",
       "redirect_url": "/previous-versions/azure/partner-solutions/split-experimentation/how-to-set-up-data-access",
diff --git a/articles/azure-resource-manager/management/azure-subscription-service-limits.md b/articles/azure-resource-manager/management/azure-subscription-service-limits.md
@@ -4,7 +4,7 @@ description: Provides a list of common Azure subscription and service limits, qu
 ms.topic: conceptual
 ms.custom:
   - ignite-2024
-ms.date: 07/19/2024
+ms.date: 12/12/2024
 ---
 
 # Azure subscription and service limits, quotas, and constraints
diff --git a/articles/backup/backup-azure-enhanced-soft-delete-about.md b/articles/backup/backup-azure-enhanced-soft-delete-about.md
@@ -3,7 +3,7 @@ title: Overview of enhanced soft delete for Azure Backup
 description: This article gives an overview of enhanced soft delete for Azure Backup.
 ms.topic: overview
 ms.custom: references_regions
-ms.date: 07/18/2024
+ms.date: 12/12/2024
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
@@ -48,7 +48,7 @@ The key benefits of enhanced soft delete are:
 ## Supported scenarios
 
 - Enhanced soft delete is supported for Recovery Services vaults and Backup vaults. Also, it's supported for new and existing vaults.
-- Enhanced soft delete applies to all vaulted workloads alike and is supported for Recovery Services vaults and Backup vaults. However, it currently doesn't support operational tier workloads, such as Azure Files backup, Operational backup for Blobs, Disk and VM snapshot backups.
+- Enhanced soft delete applies to all vaulted workloads alike and is supported for Recovery Services vaults and Backup vaults. However, for Operational tier workloads, such as operational backup of [Azure Files](azure-file-share-backup-overview.md?tabs=snapshot#architecture-for-azure-file-share-backup), [Azure Blobs](blob-backup-overview.md?tabs=operational-backup#how-the-azure-blobs-backup-works), [Azure Disks](disk-backup-overview.md), soft delete won't be completely applicable as you can delete the underlying storage account that is part of your own subscription.
 - Always-on feature for soft delete is currently not supported for SQL database backups.
 
 ## States of soft delete settings
diff --git a/articles/communication-services/concepts/interop/guest/meeting-capabilities.md b/articles/communication-services/concepts/interop/guest/meeting-capabilities.md
@@ -124,8 +124,10 @@ This article describes which capabilities Azure Communication Services SDKs supp
 | | Apply [Watermark](/microsoftteams/watermark-meeting-content-video) over received video and screen sharing  | ❌ |
 | Recording & transcription | Manage Teams cloud recording | ❌[6] |
 | | Receive information of call being cloud recorded  | ✔️ |
+| |	Give explicit consent to Teams cloud recording | ✔️ |
 | | Manage Teams transcription | ❌[6] |
 | | Receive information of call being transcribed | ✔️ |
+| |	Give explicit consent to Teams transcription |✔️ |
 | | Manage Teams closed captions  | ✔️ |
 | | Support for compliance recording  | ✔️ |
 | | [Azure Communication Services recording](../../voice-video-calling/call-recording.md) | ❌ |
diff --git a/articles/communication-services/concepts/telephony/certified-session-border-controllers.md b/articles/communication-services/concepts/telephony/certified-session-border-controllers.md
@@ -32,7 +32,6 @@ If you have any questions about the SBC certification program for Communication
 
 |Vendor|Product|Software version|
 |:--- |:--- |:--- 
-|[Microsoft](https://azure.microsoft.com/products/communications-gateway/)|Azure Communications Gateway|2023-01-31|
 |[AudioCodes](https://www.audiocodes.com/media/lbjfezwn/mediant-sbc-with-microsoft-azure-communication-services.pdf)|Mediant Virtual Edition SBC|7.40A|
 ||Mediant 500 SBC|7.40A|
 ||Mediant 800 SBC|7.40A|
diff --git a/articles/migrate/context/vmware-context.yml b/articles/migrate/context/vmware-context.yml
diff --git a/articles/migrate/toc.yml b/articles/migrate/toc.yml
@@ -62,7 +62,7 @@ items:
       - name: Assess SQL instances for migration to Azure SQL
         href: tutorial-assess-sql.md
       - name: Assess servers for migration to AVS
-        href: tutorial-assess-vmware-azure-vmware-solution.md
+        href: ./vmware/tutorial-assess-vmware-azure-vmware-solution.md
     - name: Assess servers in Hyper-V environment 
       items:
       - name: Assess servers for migration to Azure VMs
diff --git a/articles/migrate/vmware/prepare-for-agentless-migration.md b/articles/migrate/vmware/prepare-for-agentless-migration.md
@@ -22,7 +22,7 @@ Azure Migrate automatically handles these configuration changes for the followin
 **Operating system versions supported for hydration**
 
 - Windows Server 2008 or later
-- Red Hat Enterprise Linux 9.x, 8.x, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.0, 6.x
+- Red Hat Enterprise Linux 9.x, 8.x, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.0, 6.x
 - CentOS Stream
 - SUSE Linux Enterprise Server 15 SP4, 15 SP3, 15 SP2, 15 SP1, 15 SP0, 12, 11 SP4, 11 SP3
 - Ubuntu 22.04, 21.04, 20.04, 19.04, 19.10, 18.04LTS, 16.04LTS, 14.04LTS
diff --git a/articles/migrate/vmware/toc.yml b/articles/migrate/vmware/toc.yml
diff --git a/articles/synapse-analytics/sql/reference-collation-types.md b/articles/synapse-analytics/sql/reference-collation-types.md
@@ -3,8 +3,8 @@ title: Collation support
 description: Collation types support for Synapse SQL in Azure Synapse Analytics.
 author: filippopovic
 ms.author: fipopovi
-ms.reviewer: wiassaf, kecona
-ms.date: 01/30/2024
+ms.reviewer: wiassaf
+ms.date: 12/11/2024
 ms.service: azure-synapse-analytics
 ms.subservice: sql
 ms.topic: reference
@@ -28,7 +28,7 @@ You can specify the default serverless SQL pool database collation at creation t
 To change the default collation for dedicated SQL pool database, update to the **Collation** field in the provisioning experience. For example, if you wanted to change the default collation to case sensitive, you would change the collation from `SQL_Latin1_General_CP1_CI_AS` to `SQL_Latin1_General_CP1_CS_AS`. 
 
 > [!NOTE]
-> Collation cannot be changed on an existing dedicated SQL pool database. If you need to have a different collation at the dedicated SQL pool level, create a new dedicated SQL pool with the required collation.
+> Collation cannot be changed on an existing dedicated SQL pool database. If you need to have a different collation at the dedicated SQL pool level, create a new dedicated SQL pool with the required collation. To specify a non-default collation when creating a dedicated SQL pool, use the Azure portal or PowerShell.
 
 To change the default collation for a serverless SQL pool database, you can use ALTER DATABASE statement.
 
diff --git a/includes/azure-data-factory-limits.md b/includes/azure-data-factory-limits.md
@@ -4,7 +4,7 @@ description: include file
 author: chez-charlie
 ms.service: azure-data-factory
 ms.topic: include
-ms.date: 03/19/2024
+ms.date: 12/12/2024
 ms.author: chez
 ms.custom: include file
 ---
@@ -13,17 +13,17 @@ Azure Data Factory is a multitenant service that has the following default limit
 
 | Resource | Default limit | Maximum limit |
 | -------- | ------------- | ------------- |
-| Total number of entities, such as pipelines, data sets, triggers, linked services, Private Endpoints, and integration runtimes, within a data factory | 5,000 | [Find out how to request a quota increase from support](https://azure.microsoft.com/blog/azure-limits-quotas-increase-requests/). |
+| Total number of entities, such as pipelines, data sets, triggers, linked services, Private Endpoints, and integration runtimes, within a data factory | 5,000 |5,000   |
 | Total CPU cores for Azure-SSIS Integration Runtimes under one subscription | 64 | [Find out how to request a quota increase from support](https://azure.microsoft.com/blog/azure-limits-quotas-increase-requests/). |
 | Concurrent pipeline runs per data factory that's shared among all pipelines in the factory | 10,000  | 10,000 |
 | Concurrent External activity runs per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#azure-ir-location)<br>External activities are managed on integration runtime but execute on linked services, including Databricks, stored procedure, Web, and others. This limit doesn't apply to Self-hosted IR. | 3,000 | 3,000 |
 | Concurrent Pipeline activity runs per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#azure-ir-location) <br>Pipeline activities execute on integration runtime, including Lookup, GetMetadata, and Delete. This limit doesn't apply to Self-hosted IR. | 1,000 | 1,000                                                        |
 | Concurrent authoring operations per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#azure-ir-location)<br>Including test connection, browse folder list and table list, preview data. This limit doesn't apply to Self-hosted IR. | 200 | 200                                                          |
 | Concurrent Data Integration Units<sup>1</sup> consumption per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#integration-runtime-location)| Region group 1<sup>2</sup>: 6,000<br>Region group 2<sup>2</sup>: 3,000<br>Region group 3<sup>2</sup>: 1,500 | Region group 1<sup>2</sup>: 6,000<br/>Region group 2<sup>2</sup>: 3,000<br/>Region group 3<sup>2</sup>: 1,500 |
-| Concurrent Data Integration Units<sup>1</sup> consumption per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#integration-runtime-location) in managed virtual network|  2,400 | [Find out how to request a quota increase from support](https://azure.microsoft.com/blog/azure-limits-quotas-increase-requests/). |
+| Concurrent Data Integration Units<sup>1</sup> consumption per subscription per [Azure Integration Runtime region](../articles/data-factory/concepts-integration-runtime.md#integration-runtime-location) in managed virtual network|  2,400 | 2,400 |
 | Maximum activities per pipeline, which includes inner activities for containers | 80 | 120 |
 | Maximum number of linked integration runtimes that can be created against a single self-hosted integration runtime | 100 | 100 |
-| Maximum number of nodes that can be created against a single self-hosted integration runtime | 4 | [Find out how to request a quota increase from support](https://azure.microsoft.com/blog/azure-limits-quotas-increase-requests/). |
+| Maximum number of nodes that can be created against a single self-hosted integration runtime | 4 | 4 |
 | Maximum parameters per pipeline | 50 | 50 |
 | ForEach items | 100,000 | 100,000 |
 | ForEach parallelism | 20 | 50 |
@@ -40,11 +40,11 @@ Azure Data Factory is a multitenant service that has the following default limit
 | Read API calls | 12,500/h | 12,500/h<br/><br/> This limit is imposed by Azure Resource Manager, not Azure Data Factory. |
 | Monitoring queries per minute | 1,000 | 1,000 |
 | Maximum time of data flow debug session | 8 hrs | 8 hrs |
-| Concurrent number of data flows per integration runtime | 50 | [Find out how to request a quota increase from support](https://azure.microsoft.com/blog/azure-limits-quotas-increase-requests/). |
-| Concurrent number of data flows per integration runtime in managed vNet| 50 | [Find out how to request a quota increase from support](https://azure.microsoft.com/blog/azure-limits-quotas-increase-requests/). |
+| Concurrent number of data flows per integration runtime | 50 | 50 |
+| Concurrent number of data flows per integration runtime in managed vNet| 50 | 50 |
 | Concurrent number of data flow debug sessions per user per factory | 3 | 3 |
 | Data Flow Azure IR TTL limit | 4 hrs |  4 hrs |
-| Meta Data Entity Size limit in a factory | 2 GB | [Find out how to request a quota increase from support](https://azure.microsoft.com/blog/azure-limits-quotas-increase-requests/). |
+| Meta Data Entity Size limit in a factory | 2 GB | 2 GB |
 
 <sup>1</sup> The data integration unit (DIU) is used in a cloud-to-cloud copy operation. Learn more from [Data integration units (version 2)](../articles/data-factory/copy-activity-performance.md#data-integration-units). For information on billing, see [Azure Data Factory pricing](https://azure.microsoft.com/pricing/details/data-factory/).
 
