Merge pull request #314387 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-07 11:00 UTC

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

articles/azure-maps/release-notes-map-control.md

@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: Release notes for the Azure Maps Web SDK. 
 author: sinnypan
 ms.author: sipa
-ms.date: 12/17/2025
+ms.date: 04/07/2026
 ms.topic: reference
 ms.service: azure-maps
 ms.subservice: web-sdk
@@ -16,6 +16,12 @@ This document contains information about new features and other changes to the M
 
 ## v3 (latest)
 
+### [3.7.4] (CDN: April 7, 2026, npm: TBD)
+
+#### Bug fixes
+* Fixed an issue where style asset URL rewriting could produce a duplicated https:// when the configured service domain already included a protocol.
+* Fixed an issue where the Style Control's list layout wasn't scrollable on small canvases.
+
 ### [3.7.2] (CDN: December 15, 2025, npm: December 17, 2025)
 
 #### New features

articles/data-factory/TOC.yml

@@ -1308,6 +1308,9 @@ items:
       - name: SharePoint Online list
         displayName: troubleshooting
         href: connector-troubleshoot-sharepoint-online-list.md
+      - name: Shopify
+        displayName: troubleshooting
+        href: connector-troubleshoot-shopify.md
       - name: Snowflake
         displayName: troubleshooting
         href: connector-troubleshoot-snowflake.md

articles/data-factory/connector-microsoft-fabric-lakehouse.md

@@ -6,7 +6,7 @@ ms.author: jianleishen
 author: jianleishen
 ms.subservice: data-movement
 ms.topic: how-to
-ms.date: 01/30/2026
+ms.date: 04/06/2026
 ms.custom:
   - synapse
   - sfi-image-nochange
@@ -763,6 +763,23 @@ sink(allowSchemaDrift: true,
 ```
 For Fabric Lakehouse table-based connector in inline dataset type, you only need to use Delta as dataset type. This will allow you to read and write data from Fabric Lakehouse tables.
 
+
+The following table depicts the behavior of Mapping Data Flows when interacting with Fabric Lakehouse tables, based on whether the Lakehouse is schema-enabled or schema-less, and whether a schema is explicitly defined.
+
+> **Note:** All scenarios are supported when selecting the table name using the dropdown.
+
+| Fabric Lakehouse Type | Role   | Schema Provided | Behavior |
+|----------------------|--------|-----------------|----------|
+| **Schema-less Lakehouse** | Source | Yes | Operation fails |
+|                      | Source | No  | Operation succeeds |
+|                      | Sink   | Yes | Operation fails or may result in unexpected behavior |
+|                      | Sink   | No  | Operation succeeds |
+| **Schema-enabled Lakehouse** | Source | Yes | Operation succeeds |
+|                      | Source | No  | Operation fails |
+|                      | Sink   | Yes | Operation succeeds |
+|                      | Sink   | No  | Operation fails or may result in unexpected behavior |
+
+
 ## Lookup activity properties
 
 To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).

articles/data-factory/connector-shopify.md

@@ -7,7 +7,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: how-to
 ms.custom: synapse
-ms.date: 10/12/2025
+ms.date: 03/30/2026
 ---
 
 # Copy data from Shopify using Azure Data Factory or Synapse Analytics
@@ -182,7 +182,7 @@ To copy data from Shopify, set the source type in the copy activity to **Shopify
 | Property | Description | Required |
 |:--- |:--- |:--- |
 | type | The type property of the copy activity source must be set to: **ShopifySource** | Yes |
-| query |For version 2.0, use the GraphQL query to read data. To learn more about this query, see this [article](https://shopify.dev/docs/api/admin-graphql). Note that the pagination query is only supported for outer tables, and each record in the outer table can include up to 250 inner table records. <br><br>For version 1.0, use the custom SQL query to read data. For example: `"SELECT * FROM "Products" WHERE Product_Id = '123'"`. | No (if "tableName" in dataset is specified) |
+| query |For version 2.0, use the GraphQL query to read data. To learn more about this query, see this [article](https://shopify.dev/docs/api/admin-graphql). Note that pagination is only supported for outer tables, and each record in the outer table can include up to 250 inner table records. In addition, pagination is not supported for nested tables. <br><br>For version 1.0, use the custom SQL query to read data. For example: `"SELECT * FROM "Products" WHERE Product_Id = '123'"`. | No (if "tableName" in dataset is specified) |
 
 **Example:**
 

articles/data-factory/connector-troubleshoot-shopify.md

@@ -0,0 +1,39 @@
+---
+title: Troubleshoot the Shopify connector
+titleSuffix: Azure Data Factory & Azure Synapse
+description: Learn how to troubleshoot issues with the Shopify connector in Azure Data Factory and Azure Synapse Analytics. 
+author: jianleishen
+ms.subservice: data-movement
+ms.topic: troubleshooting
+ms.date: 03/30/2026
+ms.author: jianleishen
+ms.custom: has-adal-ref, synapse
+---
+
+# Troubleshoot the Shopify connector in Azure Data Factory and Azure Synapse
+
+[!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
+
+This article provides suggestions to troubleshoot common problems with the Shopify connector in Azure Data Factory and Azure Synapse. 
+
+### Error message: Object reference not set to an instance of an object
+
+- **Symptoms**: Copy activity fails with the following error:
+
+    `'Type=System.NullReferenceException,Message=Object reference not set to an instance of an object.,Source=Microsoft.DI.Driver.Shopify,StackTrace=   at Microsoft.DI.Driver.Shopify.Context.ShopifyContext.GetEdgeNodeNameFromTableName(String tableNameGraphTypeName)`
+
+- **Cause**: The table name specified in the source configuration is not valid. This usually happens when upgrading from Shopify connector version 1.0 to 2.0, as the table name formats are different in version 2.0.
+
+- **Resolution**: Check and update the table name to ensure it follows the Shopify connector version 2.0 naming conventions. For more information, see this [article](connector-shopify.md#dataset-properties). 
+ 
+## Related content
+
+For more troubleshooting help, try these resources:
+
+- [Connector troubleshooting guide](connector-troubleshoot-guide.md)
+- [Data Factory blog](https://techcommunity.microsoft.com/t5/azure-data-factory-blog/bg-p/AzureDataFactoryBlog)
+- [Data Factory feature requests](https://feedback.azure.com/d365community/forum/1219ec2d-6c26-ec11-b6e6-000d3a4f032c)
+- [Azure videos](/shows/data-exposed/?products=azure&terms=data-factory)
+- [Microsoft Q&A page](/answers/topics/azure-data-factory.html)
+- [Stack Overflow forum for Data Factory](https://stackoverflow.com/questions/tagged/azure-data-factory)
+- [X information about Data Factory](https://x.com/hashtag/DataFactory)

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md

@@ -170,9 +170,6 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
    > [!TIP]
    > The `init` command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.8.0 deployed on it, you can skip this step.
 
-    > [!IMPORTANT]
-    > When you initialize your Azure IoT Operations instance on a VKS cluster with its [pod security admission controller running in restricted mode](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kuberenetes-service-clusters-and-workloads/managing-security-for-tkg-service-clusters/configure-psa-for-tkr-1-25-and-later.html) you must include the `--cm-config global.telemetry.logs.enabled=false` flag when you run `az iot ops init`.
-
    This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
 
 1. Deploy Azure IoT Operations. Copy and run the provided [az iot ops create](/cli/azure/iot/ops#az-iot-ops-create) command. This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-test-operations.md

@@ -155,9 +155,6 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
 
     This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
 
-    > [!IMPORTANT]
-    > When you initialize your Azure IoT Operations instance on a VKS cluster with its [pod security admission controller running in restricted mode](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kuberenetes-service-clusters-and-workloads/managing-security-for-tkg-service-clusters/configure-psa-for-tkr-1-25-and-later.html) you must include the `--cm-config global.telemetry.logs.enabled=false` flag when you run `az iot ops init`.
-
 1. To deploy Azure IoT Operations, copy and run the provided [az iot ops create](/cli/azure/iot/ops#az-iot-ops-create) command. This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
 
 1. Once all of the Azure CLI commands complete successfully, you can close the **Install Azure IoT Operations** wizard.

articles/iot-operations/deploy-iot-ops/howto-prepare-cluster.md

@@ -12,19 +12,19 @@ ms.date: 10/23/2024
 
 # Prepare your Azure Arc-enabled Kubernetes cluster
 
-An Azure Arc-enabled Kubernetes cluster is a prerequisite for deploying Azure IoT Operations. This article describes how to prepare a cluster before you deploy Azure IoT Operations. This article includes guidance for Ubuntu, Windows, Azure Local, and vSphere Kubernetes Service (VKS), formerly Tanzu Kubernetes Grid Service.
+An Azure Arc-enabled Kubernetes cluster is a prerequisite for deploying Azure IoT Operations. This article describes how to prepare a cluster before you deploy Azure IoT Operations. This article includes guidance for Ubuntu, Windows, Azure Local, and Tanzu Kubernetes Grid (TKG).
 
 If you want to deploy Azure IoT Operations quickly and run a sample workload in a test environment, see the [Quickstart: Run Azure IoT Operations in GitHub Codespaces with K3s](../get-started-end-to-end-sample/quickstart-deploy.md).
 
 ## Prerequisites
 
-For multi-node deployments, K3s for deployments on Ubuntu, AKS deployments on Azure Local, and VKS. Azure Kubernetes Service (AKS) Edge Essentials for Windows only supports single-node deployments.
+For multi-node deployments, K3s for deployments on Ubuntu, AKS deployments on Azure Local, and Tanzu Kubernetes release (TKr) on TKG. Azure Kubernetes Service (AKS) Edge Essentials for Windows only supports single-node deployments.
 
 ### [Ubuntu](#tab/ubuntu)
 
 To prepare an Azure Arc-enabled Kubernetes cluster, you need:
 
-[!INCLUDE [Cluster prerequisites for Ubuntu and VKS](../includes/cluster-prerequisites.md)]
+[!INCLUDE [Cluster prerequisites for Ubuntu and Tanzu](../includes/cluster-prerequisites.md)]
 
 * Hardware that meets the system requirements:
 
@@ -60,20 +60,20 @@ To prepare an Azure Arc-enabled Kubernetes cluster, you need:
   * [Azure IoT Operations supported environments](./overview-deploy.md#supported-environments).
   * [Azure Arc-enabled Kubernetes system requirements](/azure/azure-arc/kubernetes/system-requirements).
 
-### [VKS](#tab/vks)
+### [TKG with a management cluster](#tab/tkgm)
 
-To prepare a VKS cluster, you need:
+To prepare a TKG workload cluster, you need:
 
-[!INCLUDE [Cluster prerequisites for Ubuntu and VKS](../includes/cluster-prerequisites.md)]
+[!INCLUDE [Cluster prerequisites for Ubuntu and Tanzu](../includes/cluster-prerequisites.md)]
 
-- [vSphere Kubernetes Service](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/release-notes/vmware-tanzu-kubernetes-grid-service-release-notes.html)
+- [TKG with a standalone management cluster.](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-kubernetes-grid/2-5/tkg/mgmt-index.html)
 
 - Hardware that meets the system requirements:
 
   - [Azure IoT Operations supported environments](./overview-deploy.md#supported-environments).
   - [Azure Arc-enabled Kubernetes system requirements](/azure/azure-arc/kubernetes/system-requirements).
 
-  - [Requirements for running VKS clusters](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kubernetes-service/running-tkg-service-clusters.html)
+  - [TKG standalone management cluster requirements.](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-kubernetes-grid/2-5/tkg/mgmt-reqs-index.html)
 
 ---
 
@@ -239,12 +239,21 @@ By default, a Kubernetes cluster is created with a node pool that can run Linux
 
 Then, once you have an Azure Arc-enabled Kubernetes cluster, you can [deploy Azure IoT Operations](howto-deploy-iot-operations.md).
 
-### [VKS](#tab/vks)
+### [TKG with a management cluster](#tab/tkgm)
 
-For guidance on setting up a VKS cluster, see [Deploying VKS Service Clusters](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kubernetes-service/running-tkg-service-clusters/deploying-tkg-service-clusters.html).
+To prepare a TKG workload cluster, you need:
 
-> [!IMPORTANT]
-> When you initialize your Azure IoT Operations instance on a VKS cluster with its [pod security admission controller running in restricted mode](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kuberenetes-service-clusters-and-workloads/managing-security-for-tkg-service-clusters/configure-psa-for-tkr-1-25-and-later.html) you must include the `--cm-config global.telemetry.logs.enabled=false` flag when you run `az iot ops init`.
+- A single-node or multi-node TKG workload cluster. For guidance, see the [Tanzu documentation](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-kubernetes-grid/2-5/tkg/workload-clusters-index.html).
+
+### Update pod security admission settings
+
+Before deploying Azure IoT Operations, you will need to update the Pod Security Admission settings on your TKG cluster. Applying this file will pre-create namespace labels and set pod security to `privileged`.
+
+
+
+```azurecli
+kubectl apply -f https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/main/samples/tanzu-config/psa.yaml
+```
 
 ### Arc-enable your cluster
 
@@ -299,7 +308,7 @@ Connect your cluster to Azure Arc so that it can be managed remotely.
 
   Save the output of this command to use in the next steps.
 
-1. Connect to the VKS cluster. Edit the custom resource for the workload cluster with the issuer URL from the previous step.
+1. Connect to the TKG management cluster. Edit the custom resource for the workload cluster with the issuer URL from the previous step.
 
    ```azurecli
    kubectl edit cluster <CLUSTER_NAME> 

articles/iot-operations/includes/cluster-prerequisites.md

@@ -1,6 +1,6 @@
 ---
 title: include file
-description: include file with cluster prerequisites for Ubuntu and VKS
+description: include file with cluster prerequisites for Ubuntu and Tanzu
 author: dominicbetts
 ms.topic: include
 ms.date: 06/16/2025

articles/iot-operations/includes/supported-environments-table.md

@@ -24,7 +24,7 @@ Microsoft supports the following Kubernetes distributions for Azure IoT Operatio
 | Kubernetes distribution           | Architecture         | Support level        | *Minimum validated version*         | *Minimum validated OS*                |
 |-----------------------------------|----------------------|----------------------|-------------------------------------|---------------------------------------|
 | [K3s](https://www.rancher.com/products/k3s)                             | x86_64               | General availability | *1.33.6*                            | *Ubuntu 24.04*, <br> Red Hat Enterprise Linux (RHEL) 9.x                        |
-| [vSphere Kubernetes Service (VKS)](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/release-notes/vmware-tanzu-kubernetes-grid-service-release-notes.html)    | x86_64               | General availability | *1.32.7*                           | *VKS*         |
+| [Tanzu Kubernetes release (TKr)](https://www.vmware.com/products/app-platform/tanzu-kubernetes-grid)    | x86_64               | General availability | *1.28.11*                           | *Tanzu Kubernetes Grid 2.5.2*         |
 | [RKE2](https://docs.rke2.io/)                             | x86_64               | General availability | *v1.35.0+rke2r1*                   | [Operating systems](https://docs.rke2.io/install/requirements#operating-systems)    |
 
 * The *minimum validated version* is the lowest version of the Kubernetes distribution that Microsoft uses to validate Azure IoT Operations deployments.