Merge pull request #308914 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-01 23:00 UTC

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

.openpublishing.redirection.json

@@ -1,5 +1,100 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/data-explorer-compare.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/data-explorer-compare",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/data-explorer-create-pool-portal.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/data-explorer-create-pool-portal",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/data-explorer-create-pool-studio.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/data-explorer-create-pool-studio",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/data-explorer-monitor-pools.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/data-explorer-monitor-pools",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/data-explorer-overview.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/data-explorer-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-one-click.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-one-click",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-overview.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-pipeline.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-pipeline",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-properties.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-properties",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-streaming.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-streaming",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-supported-formats.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-data-supported-formats",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-grid-overview.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-grid-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-grid-portal.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-grid-portal",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-csharp.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-csharp",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-one-click.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-one-click",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-overview.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-portal.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-portal",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-python.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-python",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-resource-manager.md",
+      "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-resource-manager",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/automation/change-tracking/enable-change-tracking-at-scale-machines-blade.md",
       "redirect_url": "/azure/azure-change-tracking-inventory/enable-change-tracking-at-scale-machines-blade",

articles/app-service/app-service-undelete.md

@@ -15,8 +15,10 @@ ms.custom:
 
 If you accidentally deleted an app in Azure App Service, you can now restore it by using the Azure portal or PowerShell.
 
-> [!IMPORTANT]
-> This feature isn't supported for apps hosted on App Service plans using the Free and Shared tiers.
+- This feature isn't supported for apps hosted on App Service plans using the Free and Shared tiers.
+- Deleted apps are purged from the system 30 days after the initial deletion. After an app is purged, it can't be recovered.
+- Undelete functionality isn't supported for function apps hosted on the Consumption plan or Elastic Premium plan.
+- If the app was hosted on and then deleted from an App Service Environment, it can be restored only if the corresponding App Service Environment still exists.
 
 ## Restore a deleted App Service app by using the Azure portal
 
@@ -34,10 +36,6 @@ If you deleted your app in Azure App Service, you can restore it from the portal
 
 If you deleted your app in Azure App Service, you can restore it by using the commands from the [`Az PowerShell module`](/powershell/azure/).
 
-> [!NOTE]
-> * Deleted apps are purged from the system 30 days after the initial deletion. After an app is purged, it can't be recovered.
-> * Undelete functionality isn't supported for function apps hosted on the Consumption plan or Elastic Premium plan.
-
 ## Re-register App Service resource provider
 
 Some customers might experience failure to retrieve the list of deleted apps. To resolve the issue, run the following command:
@@ -125,9 +123,6 @@ The inputs for command are:
 - **Slot**: Slot for the deleted app.
 - **RestoreContentOnly**: By default `Restore-AzDeletedWebApp` restores both your app configuration as well any content. If you want to only restore content, you can use the `-RestoreContentOnly` flag with this cmdlet.
 
-> [!NOTE]
-> If the app was hosted on and then deleted from an App Service Environment, it can be restored only if the corresponding App Service Environment still exists.
-
 ## Restore deleted Azure Functions app
 
 If a function app was hosted on a Dedicated App Service plan, it can be restored, as long as it used the default App Service storage.

articles/app-service/configure-error-pages.md

@@ -19,7 +19,7 @@ In this tutorial, we're adding a custom 403 error page to our web app hosted on
 - an html file under 10 kb in size
 
 ## Upload an error page
-For this example, we're uploading and testing a 403 error page to present to the user. Name your html file to match the error code (for example, `403.html`). Once you have your html file prepared, you can upload it to your web app. In the configuration blade, you should see an **Error pages (preview)** tab. Click on this tab to view the error page options. If the options are greyed out, you need to upgrade to at least a Premium SKU to use this feature.
+For this example, we're uploading and testing a 403 error page to present to the user. Name your html file to match the error code (for example, `403.html`). Once you have your html file prepared, you can upload it to your web app. In the configuration blade, you should see an **Error pages** tab. Click on this tab to view the error page options. If the options are greyed out, you need to upgrade to at least a Premium SKU to use this feature.
 
 Select the error code that you'd like to upload an error page for and click **Edit**. On the next screen, click the folder icon to select your html file. The file must be in html format and within the 10 kb size limit. Find your .html file and click on the **Upload** button at the bottom of the screen. Notice the Status in the table updates from Not Configured to Configured. Then click **Save** to complete the upload. 
 

articles/azure-functions/TOC.yml

@@ -136,8 +136,6 @@
       href: functions-identity-based-connections-tutorial-2.md
     - name: Access Azure SQL with managed identity
       href: functions-identity-access-azure-sql-with-managed-identity.md
-    - name: Access MCP server with agent identity
-      href: ../app-service/overview-agent-identity.md?toc=/azure/azure-functions/toc.json
   - name: Low-latency Blob trigger using Event Grid
     displayName: storage, ngrok, local
     href: functions-event-grid-blob-trigger.md
@@ -558,6 +556,8 @@
       href: ../app-service/app-service-ip-restrictions.md?toc=/azure/azure-functions/toc.json
     - name: Use a managed identity
       href: ../app-service/overview-managed-identity.md?toc=/azure/azure-functions/toc.json
+    - name: Use an agent identity
+      href: ../app-service/overview-agent-identity.md?toc=/azure/azure-functions/toc.json
     - name: Reference secrets from Key Vault
       href: ../app-service/app-service-key-vault-references.md?toc=/azure/azure-functions/toc.json
     - name: Encrypt site data

articles/azure-functions/scenario-host-mcp-server-sdks.md

@@ -210,9 +210,9 @@ You can view the complete project template in the [Azure Functions .NET MCP SDK
 ::: zone-end  
 ::: zone pivot="programming-language-python"
 The MCP server code is defined in the `weather.py` file. The server uses the official Python MCP SDK to define weather-related tools:
-
+<!--
 :::code language="python" source="~/functions-host-mcp-sdk-python/weather.py" :::
-
+-->
 You can view the complete project template in the [Azure Functions Python MCP SDK hosting](https://github.com/Azure-Samples/mcp-sdk-functions-hosting-python) GitHub repository.
 ::: zone-end   
 ::: zone pivot="programming-language-typescript"

articles/data-factory/TOC.yml

@@ -310,6 +310,10 @@ items:
     href: /azure/reliability/reliability-data-factory?toc=/azure/data-factory/toc.json
 - name: How-to guides
   items:
+  - name: Migration
+    items:
+    - name: Pipeline assessment tool
+      href: how-to-assess-your-azure-data-factory-to-fabric-data-factory-migration.md
   - name: Create a data factory in UI
     href: quickstart-create-data-factory.md
   - name: Create Data Factory Programmatically

articles/data-factory/how-to-assess-your-azure-data-factory-to-fabric-data-factory-migration.md

@@ -0,0 +1,81 @@
+---
+title: Assess your Azure Data Factory pipelines for migration to Fabric
+description: Learn how to check which pipelines are ready to migrate and which ones need attention 
+author: ssindhub
+ms.author: ssrinivasara
+ms.topic: conceptual
+ms.date: 11/18/2024
+ms.custom: pipelines
+---
+
+# How to assess your Azure Data Factory to Fabric Data Factory Migration
+Use the built-in upgrade assessment to quickly check pipeline readiness and identify activity compatibility issues before migrating to Fabric.
+
+In [Azure Data Factory](https://adf.azure.com), open the factory you want to migrate. On the authoring canvas toolbar, select Run upgrade assessment (preview).
+
+:::image type="content" source="media/how-to-assess-your-azure-data-factory-to-fabric-data-factory-migration/run-upgrade-assessment.png" alt-text="Screenshot showing how to run the Assessment tool.":::
+
+This opens a side pane with the preview of list of pipelines and expandable list of activities within the pipeline.
+
+:::image type="content" source="media/how-to-assess-your-azure-data-factory-to-fabric-data-factory-migration/pipeline-assessment.png" alt-text="Screenshot showing how to view the assessment in the side pane.":::
+
+You can export the assessment results as a .csv file, which lists pipeline names, activity-level statuses, and compatibility notes.
+
+Some results point to features that are still in progress or out of scope. Use the results to prioritize the fixes and to decide whether to migrate now using existing tools such as [PowerShell upgrade module](/fabric/data-factory/migrate-pipelines-powershell-upgrade-module-for-azure-data-factory-to-fabric) or wait for upcoming support.
+
+
+## Understand the results
+You’ll see one of the four results for each pipeline (and summarized at the factory level):
+
+| Status            | Meaning                                                 |
+|-------------------|---------------------------------------------------------|
+| **Ready**         | Good to go for migration                                |
+| **Needs review**  | Requires changes before migration eg: Global parameters |
+| **Coming soon**   | Support in progress; migrate later                      |
+| **Not compatible**| No equivalent in Fabric; refactor required              |
+
+
+### Drill into details
+In the assessment side pane, expand each pipeline to see:
+
+- Activity‑level status (which activities block migration).
+- A summary of Ready/Needs review/Not compatible counts across pipelines.
+
+ :::image type="content" source="media/how-to-assess-your-azure-data-factory-to-fabric-data-factory-migration/detailed-assessment-drilldown.png" alt-text="Diagram showing a drill-down of the assessment details.":::
+  
+Use this list to build your to‑do plan (what to fix, what to defer, and what to replace).
+
+### Next steps
+When your assessment shows acceptable readiness:
+1. Use migration flow when available in the future.
+1. Use [PowerShell upgrade tool](/fabric/data-factory/migrate-pipelines-powershell-upgrade-module-for-azure-data-factory-to-fabric) for early migration.
+1. Refer to planning guides for best practices.
+
+
+## FAQ
+**Does the assessment change my factory?**
+
+Answer: No. It only scans your configuration and lists findings in the side pane. You can safely run it to understand impact before migration.
+
+**Why do I see Coming soon?**
+
+Answer: It means the product team is actively adding support for those items. 
+If they’re critical to your pipeline, see if you could use [PowerShell upgrade tool](/fabric/data-factory/migrate-pipelines-powershell-upgrade-module-for-azure-data-factory-to-fabric) or plan to migrate later or redesign the affected steps.
+
+**What if only one activity is Not compatible?**
+
+Answer: You can still migrate the pipeline after you refactor or replace that activity. The assessment helps you identify exactly where to focus.
+
+**Can I rerun the assessment after making changes?**
+
+Answer: Yes, you can rerun anytime to validate updates.
+
+## Related content
+
+[Compare Azure Data Factory and Fabric Data Factory](/fabric/data-factory/compare-fabric-data-factory-and-azure-data-factory)
+
+[Migration best practices](/fabric/data-factory/migration-best-practices)
+
+[Connector parity](/fabric/data-factory/connector-parity)
+
+