Merge pull request #289394 from MicrosoftDocs/main

10/29/2024 AM Publish

Author: Taojunshen

articles/azure-functions/start-stop-vms/troubleshoot.md

@@ -9,7 +9,7 @@ ms.topic: conceptual
 
 # Troubleshoot common issues with Start/Stop VMs
 
-This article provides information on troubleshooting and resolving issues that may occur while attempting to install and configure Start/Stop VMs. For general information, see [Start/Stop VMs overview](overview.md).
+This article provides information on troubleshooting and resolving issues that may occur while attempting to install and configure Start/Stop VMs.
 
 ## General validation and troubleshooting
 

articles/azure-maps/add-custom-protocol-pmtiles.md

@@ -20,45 +20,28 @@ By using the `addProtocol` function, which registers a callback triggered before
 The first step is to add a reference to the protocol. The following example references the `pmtiles` library:
 
 ```html
-  <script src="https://unpkg.com/pmtiles@3.0.5/dist/pmtiles.js"></script>
+  <script src="https://unpkg.com/pmtiles@3.2.0/dist/pmtiles.js"></script>
 ```
 
 Next, initialize the MapLibre PMTiles protocol.
 
 ```js
-//Initialize the plugin.
-      const protocol = new pmtiles.Protocol();
-      atlas.addProtocol("pmtiles", (request) => {
-        return new Promise((resolve, reject) => {
-          const callback = (err, data) => {
-            if (err) {
-              reject(err);
-            } else {
-              resolve({ data });
-            }
-          };
-          protocol.tile(request, callback);
-        });
-      });
-```
-
-## Add PMTiles protocol
-
-To add the PMTiles protocol, hook the data source with the specified protocol URI scheme. The following sample uses the [Overture] building dataset to add building data over the basemap.
-
-```js
-const PMTILES_URL = "https://overturemaps-tiles-us-west-2-beta.s3.amazonaws.com/2024-07-22/buildings.pmtiles";
-protocol.add(new pmtiles.PMTiles(PMTILES_URL));
+  //Initialize the plugin.
+  const protocol = new pmtiles.Protocol();
+  atlas.addProtocol("pmtiles", protocol.tile);
 ```
 
 ## Add PMTiles as a map source
 
+The following sample uses the [Overture] building dataset to add building data over the basemap.
+
 PMTiles are added as a map source during the map event. Once added, the specified URI scheme is available to the Azure Maps Web SDK. In the following sample, the PMTiles URL is added as a `VectorTileSource`.
 
 ```js
+const PMTILES_URL = "https://overturemaps-tiles-us-west-2-beta.s3.amazonaws.com/2024-07-22/buildings.pmtiles";
 //Add the source to the map.
 map.sources.add(
-  new atlas.source.VectorTileSource("pmtiles", {
+  new atlas.source.VectorTileSource("my_source", {
     type: "vector",
     url: `pmtiles://${PMTILES_URL}`,
   })
@@ -77,7 +60,7 @@ The following sample uses the building theme's properties (for example, building
 ```js
 //Create a polygon extrusion layer.
 layer = new atlas.layer.PolygonExtrusionLayer(
-  "pmtiles",
+  "my_source",
   "building",
   {
     sourceLayer: "building",

articles/azure-resource-manager/management/move-resource-group-and-subscription.md

@@ -479,6 +479,10 @@ When you receive this error, you have two options. Either move your resources to
 
 No, you can't move a resource group to a new subscription. But, you can move all of the resources in the resource group to a resource group in another subscription. Settings such as tags, role assignments, and policies aren't automatically transferred from the original resource group to the destination resource group. You need to reapply these settings to the new resource group. For more information, see [Move resources to new resource group or subscription](./move-support-resources.md).
 
+### Unsupported scenarios
+
+The platform blocks a scenario where resources from Subscription A are migrated to Subscription B when *at the same time* resources from Subscription B are migrated to Subscription C. This is by design.
+
 ## Next steps
 
 For a list of which resources support move, see [Move operation support for resources](move-support-resources.md).

articles/communication-services/concepts/privacy.md

@@ -104,7 +104,7 @@ Audio and video communication is ephemerally processed by the service and no cal
 
 ### Call Recording
 
-Call recordings are stored temporarily in the same geography that was selected for ```Data Location``` during resource creation for 48 hours. After this the recording is deleted and you are responsible for storing the recording in a secure and compliant location.
+Call recordings are stored temporarily in the same geography that was selected for ```Data Location``` during resource creation for 24 hours. After this the recording is deleted and you are responsible for storing the recording in a secure and compliant location.
 
 ### Email
 Email message content is ephemerally stored for processing in the resource's ```Data Location``` specified by you during resource provisioning. Email message delivery logs are available in Azure Monitor Logs, where you are in control to define the workspace to store logs. Domain sender usernames (or MailFrom) values are stored in the resource's ```Data Location``` until explicitly deleted. Recipient's email addresses that result in hard bounced messages are temporarily retained for spam and abuse prevention and detection.

articles/container-apps/ingress-overview.md

@@ -83,7 +83,7 @@ With TCP ingress enabled, your container app:
 In addition to the main HTTP/TCP port for your container apps, you might expose additional TCP ports to enable applications that accept TCP connections on multiple ports.
 
 > [!NOTE]
-> This feature requires using the latest preview version of the container apps CLI extension.
+> To use this feature, you must have the container apps CLI extension. Run `az extension add -n containerapp` in order to install the latest version of the container apps CLI extension.
 
 The following apply to additional TCP ports:
 - Additional TCP ports can only be external if the app itself is set as external and the container app is using a custom VNet.

articles/data-factory/connector-office-365.md

@@ -6,10 +6,10 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 10/29/2024
 ms.author: jianleishen
 ---
-# Copy and transform data from Microsoft 365 (Office 365) into Azure using Azure Data Factory or Synapse Analytics
+# Copy from Microsoft 365 (Office 365) into Azure using Azure Data Factory or Synapse Analytics
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 Azure Data Factory and Synapse Analytics pipelines integrate with [Microsoft Graph data connect](/graph/data-connect-concept-overview), allowing you to bring the rich organizational data in your Microsoft 365 (Office 365) tenant into Azure in a scalable way and build analytics applications and extract insights based on these valuable data assets. Integration with Privileged Access Management provides secured access control for the valuable curated data in Microsoft 365 (Office 365).  Refer to [this link](/graph/data-connect-concept-overview) for an overview of Microsoft Graph data connect.
@@ -332,33 +332,5 @@ To copy data from Microsoft 365 (Office 365), the following properties are suppo
 ]
 ```
 
-## Transform data with the Microsoft 365 connector
-
-Microsoft 365 datasets can be used as a source with mapping data flows. The data flow will transform the data by flattening the dataset automatically. This allows users to concentrate on leveraging the flattened dataset to accelerate their analytics scenarios.
-
-### Mapping data flow properties
-
-To create a mapping data flow using the Microsoft 365 connector as a source, complete the following steps:
-
-1.	In ADF Studio, go to the **Data flows** section of the **Author** hub, select the **…** button to drop down the **Data flow actions** menu, and select the **New data flow** item. Turn on debug mode by using the **Data flow debug** button in the top bar of data flow canvas.
-
-    :::image type="content" source="media/connector-office-365/connector-office-365-mapping-data-flow-data-flow-debug.png" alt-text="Screenshot of the data flow debug button in mapping data flow.":::
-
-2. In the mapping data flow editor, select **Add Source**.
-
-    :::image type="content" source="media/connector-office-365/connector-office-365-mapping-data-flow-add-source.png" alt-text="Screenshot of add source in mapping data flow.":::
-
-3. On the tab **Source settings**, select **Inline** in the **Source type** property, **Microsoft 365 (Office 365)** in the **Inline dataset type**, and the Microsoft 365 linked service that you have created earlier.
-
-    :::image type="content" source="media/connector-office-365/connector-office-365-mapping-data-flow-select-dataset.png" alt-text="Screenshot of the select dataset option in source settings of mapping data flow source.":::
-
-4. On the tab **Source options** select the **Table name** of the Microsoft 365 table that you would like to transform. Also select the **Auto flatten** option to decide if you would like data flow to auto flatten the source dataset.
-
-    :::image type="content" source="media/connector-office-365/connector-office-365-mapping-data-flow-source-options.png" alt-text="Screenshot of the source options of mapping data flow source.":::
-
-5. For the tabs **Projection**, **Optimize** and **Inspect**, please follow [mapping data flow](concepts-data-flow-overview.md).
-
-6. On the tab **Data preview** click on the **Refresh** button to fetch a sample dataset for validation.
-
 ## Related content
 For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).

articles/devtest-labs/how-to-move-labs.md

@@ -8,13 +8,14 @@ author: RoseHJM
 ms.date: 09/30/2023
 ---
 
-# Move DevTest Labs and schedules to another region
+# Move DevTest Labs and Schedules
 
-You can move DevTest Labs and their associated schedules to another region. To move a lab, create a copy of an existing lab in another region. When you've moved your lab, and you have a virtual machine (VM) in the target region, you can move your lab schedules.
+You can move DevTest Labs and their associated schedules to another region or resource group. You can move resource groups through the Azure Portal. To move a lab, create a copy of an existing lab in another region. When you've moved your lab, and you have a virtual machine (VM) in the target region, you can move your lab schedules..
 
 In this article, you learn how to:
 > [!div class="checklist"]
 > >
+> - Move resources to different resource groups.
 > - Export an Azure Resource Manager (ARM) template of your lab.
 > - Modify the template by adding or updating the target region and other parameters.
 > - Deploy the template to create the new lab in the target region.
@@ -39,11 +40,18 @@ In this article, you learn how to:
 
 ## Move a lab
 
-The following section describes how to create and customize an ARM template to move a lab from one region to another. 
+The following section describes how to move resources to a different resource group and create and customize an ARM template to move a lab from one region to another.  
 
 You can move a schedule without moving a lab, if you have a VM in the target region. If you want to move a schedule without moving a lab, see [Move a schedule](#move-a-schedule).
 
-### Prepare to move a lab
+### Move Resource Groups using Azure Portal
+Moving resources between resource groups in different locations is now seamlessly enabled in DevTest Labs. You can effortlessly transfer any resource from one group to another within the same subscription.
+
+To begin, select the resource you wish to move. On the resource's **Overview** page, you'll find the current **Resource Group** displayed at the top. Next to the resource group name, you'll see the word `(move)` in parentheses.
+
+Click the hyperlinked `move` text, which will direct you to a new page where you can relocate the resource to any other resource group within the same subscription. Please note that moving the resource will not change its location, even if the destination resource group is in a different location. If you're not moving resources through the Azure Portal or if you're transferring to a resource group in a different subscription, alternative methods using ARM are outlined below.
+
+### Move Labs to a Different Region
 
 When you move a lab, there are some steps you must take to prepare for the move. You need to:
 
@@ -314,7 +322,7 @@ Use the following steps to export and redeploy your schedule in another Azure re
 
 ## Discard or clean up
 
-After the deployment, if you want to start over, you can delete the target lab, and repeat the steps described in the [Prepare](#prepare-to-move-a-lab) and [Move](#deploy-the-template-to-move-the-lab) sections of this article.
+After the deployment, if you want to start over, you can delete the target lab, and repeat the steps described in the [Prepare](#move-labs-to-a-different-region) and [Move](#deploy-the-template-to-move-the-lab) sections of this article.
 
 To commit the changes and complete the move, you must delete the original lab.
 

articles/event-hubs/transport-layer-security-audit-minimum-version.md

@@ -37,7 +37,7 @@ To create a policy with an audit effect for the minimum TLS version with the Azu
             },
             {
               "not": {
-                "field": " Microsoft.EventHub/namespaces/minimumTlsVersion",
+                "field": "Microsoft.EventHub/namespaces/minimumTlsVersion",
                 "equals": "1.2"
               }
             }
@@ -122,4 +122,4 @@ See the following documentation for more information.
 
 - [Enforce a minimum required version of Transport Layer Security (TLS) for requests to an Event Hubs namespace](transport-layer-security-enforce-minimum-version.md)
 - [Configure the minimum TLS version for an Event Hubs namespace](transport-layer-security-configure-minimum-version.md)
-- [Configure Transport Layer Security (TLS) for an Event Hubs client application](transport-layer-security-configure-client-version.md)
+- [Configure Transport Layer Security (TLS) for an Event Hubs client application](transport-layer-security-configure-client-version.md)

articles/event-hubs/transport-layer-security-enforce-minimum-version.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Event Hubs
 description: Configure a service bus namespace to require a minimum version of Transport Layer Security (TLS) for clients making requests against Azure Event Hubs.
 author: EldertGrootenboer
 ms.topic: article
-ms.date: 06/24/2024
+ms.date: 10/28/2024
 ms.author: egrootenboer
 ---
 
@@ -17,7 +17,7 @@ Azure Event Hubs supports choosing a specific TLS version for namespaces. Curren
 Azure Event Hubs namespaces permit clients to send and receive data with TLS 1.0 and above. To enforce stricter security measures, you can configure your Event Hubs namespace to require that clients send and receive data with a newer version of TLS. If an Event Hubs namespace requires a minimum version of TLS, then any requests made with an older version will fail.
 
 > [!WARNING]
-> As of 31 October 2024, TLS 1.0 and TLS 1.1 will no longer be supported on Azure. [TLS 1.0 and TLS 1.1 end of support announcement](https://azure.microsoft.com/updates/azure-support-tls-will-end-by-31-october-2024-2/) The minimum TLS version will be 1.2 for all Event Hubs deployments.
+> As of 28 February 2025, TLS 1.0 and TLS 1.1 will no longer be supported on Azure Event Hubs. The minimum TLS version will be 1.2 for all Event Hubs deployments.
 
 > [!IMPORTANT]
 > On 31 October 2024, TLS 1.3 will be enabled for AMQP traffic. TLS 1.3 is already enabled for Kafka and HTTPS traffic. Java clients may have a problem with TLS 1.3 due to a dependency on an older version of Proton-J. For more details, read [Java client changes to support TLS 1.3 with Azure Service Bus and Azure Event Hubs](https://techcommunity.microsoft.com/t5/messaging-on-azure-blog/java-client-changes-to-support-tls-1-3-with-azure-service-bus/ba-p/4089355)