Merge pull request #307987 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-07 12:00 UTC

Author: learn-build-service-prod[bot]

articles/iot-operations/connect-to-cloud/howto-create-dataflow.md

@@ -654,7 +654,7 @@ sourceSettings:
 
 To learn more, see [Understand message schemas](concept-schema-registry.md).
 
-## Request disk persistence (preview)
+## Request disk persistence
 
 Request disk persistence lets data flows keep state across restarts. When you enable this feature, the graph recovers processing state if the connected broker restarts. This feature is useful for stateful processing scenarios where losing intermediate data is a problem. When you enable request disk persistence, the broker persists the MQTT data, like messages in the subscriber queue, to disk. This approach makes sure your data flow's data source doesn't lose data during power outages or broker restarts. The broker maintains optimal performance because persistence is configured per data flow, so only the data flows that need persistence use this feature.
 
@@ -687,10 +687,10 @@ Add the `requestDiskPersistence` property to your data flow configuration file:
 
 # [Bicep](#tab/bicep)
 
-Add the `requestDiskPersistence` property to your data flow resource. The API version is `2025-07-01-preview` or later:
+Add the `requestDiskPersistence` property to your data flow resource. The API version is `2025-10-01` or later:
 
 ```bicep
-resource dataflow 'Microsoft.IoTOperations/instances/dataflowProfiles/dataflows@2025-07-01-preview' = {
+resource dataflow 'Microsoft.IoTOperations/instances/dataflowProfiles/dataflows@2025-10-01' = {
   parent: defaultDataflowProfile
   name: dataflowName
   extendedLocation: {
@@ -1868,4 +1868,4 @@ To ensure the data flow is working as expected, verify the following:
 - [Convert data by using data flows](concept-dataflow-conversions.md)
 - [Enrich data by using data flows](concept-dataflow-enrich.md)
 - [Understand message schemas](concept-schema-registry.md)
-- [Manage data flow profiles](howto-configure-dataflow-profile.md)
+- [Manage data flow profiles](howto-configure-dataflow-profile.md)

articles/migrate/whats-new.md

@@ -18,6 +18,11 @@ ms.custom: mvc, engagement-fy25
 
 ## Update (November 2025)
 
+- Public preview: Azure Migrate now supports adding code insights using GitHub Copilot assessment to enhance web app assessments. This capability helps you evaluate migration readiness more accurately and get recommend migration strategy for Azure Kubernetes Service (AKS) or Azure App Service. You can add code insights by either uploading a ZIP file of reports or requesting a report through a GitHub connection. [Learn more](add-copilot-code-insights.md).
+
+- Public preview: Azure Migrate now supports Arc-based discovery, enabling you to assess on-premises servers and SQL Server instances that are already Azure Arc-enabled—without deploying additional infrastructure. This integration accelerates migration planning by leveraging existing Arc data to generate business cases and assessments within an hour. [Learn more](concepts-arc-resource-discovery.md). 
+    - The VM extension is an optional component that collects performance data from Arc-enabled servers to provide right sized recommendations in assessments and business cases. [Learn more](migrate-virtual-machine-extension-reference.md).
+
 Public preview: Wave Planning in Azure Migrate provides a structured approach to cloud migration and modernization. It helps organizations break down large-scale migrations into manageable **waves** of workloads and applications. This capability accelerates timelines, reduces uncertainty, and minimizes risks through phased execution and logical grouping. [Learn more](overview.md).
 
 - Distribute workloads and applications into waves for high-fidelity planning, leveraging Azure Migrate’s discovery and assessment information. 
@@ -34,6 +39,7 @@ Public preview: Wave Planning in Azure Migrate provides a structured approach to
 
 Wave Planning in Azure Migrate provides a scalable, transparent, and risk-aware migration experience, enabling organizations to modernize infrastructure with confidence and control. 
 
+
 ## Update (October 2025)
 
 ### Public Preview - Insights in Azure Migrate

articles/partner-solutions/datadog/manage.md

@@ -67,6 +67,15 @@ The column **Logs to Datadog** indicates whether the resource is sending logs to
 
 ## Monitor multiple subscriptions
 
+When you add or remove subscriptions for Datadog monitoring, the system updates the Monitoring Reader role assignment on the System Managed Identity linked to the resource.
+
+**Prerequisites**
+
+To perform these actions, you must have both of the following Azure permissions:
+
+- `Microsoft.Authorization/roleAssignments/write`
+- `Microsoft.Authorization/roleAssignments/delete`
+
 To monitor multiple subscriptions:
 
 1. Select **Datadog organization configurations > Monitored Subscriptions**.