Merge pull request #288863 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 10/21

Author: ttorble

articles/automation/change-tracking/enable-vms-monitoring-agent.md

@@ -3,7 +3,7 @@ title: Enable Azure Automation Change Tracking for single machine and multiple m
 description: This article tells how to enable the Change Tracking feature for single machine and multiple machines at scale from the Azure portal.
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 09/09/2024
+ms.date: 10/10/2024
 ms.topic: how-to
 ms.service: azure-automation
 ---
@@ -41,6 +41,8 @@ This section provides detailed procedure on how you can enable change tracking o
 
    :::image type="content" source="media/enable-vms-monitoring-agent/deployment-success-inline.png" alt-text="Screenshot showing the notification of deployment." lightbox="media/enable-vms-monitoring-agent/deployment-success-expanded.png":::
 
+> [!NOTE]
+> It usually takes up to two to three minutes to successfully onboard and enable the virtual machine(s). After you enable a virtual machine for change tracking, you can make changes to the files, registries, or software for the specific VM.
 
 #### [Multiple Azure VMs - portal](#tab/multiplevms)
 
@@ -66,6 +68,22 @@ This section provides detailed procedure on how you can enable change tracking o
 1. Select **Enable** to initiate the deployment.
 1. A notification appears on the top right corner of the screen indicating the status of deployment.
 
+
+#### [Single Azure Arc VM - portal](#tab/singlearcvm)
+
+1. Sign in to [Azure portal](https://portal.azure.com). Search for and select **Machines-Azure Arc**.
+
+   :::image type="content" source="media/enable-vms-monitoring-agent/select-arc-machines-portal.png" alt-text="Screenshot showing how to select Azure Arc machines from the portal." lightbox="media/enable-vms-monitoring-agent/select-arc-machines-portal.png":::
+
+1. Select the Azure-Arc machine for which you want to enable Change Tracking.
+1. Under **Operations**, select **Change tracking** to view the change tracking and inventory page.
+1. In the **Stay up-to-date with all changes** layout, select **Enable using AMA agent (Recommended)** option and **Enable**. 
+
+   :::image type="content" source="media/enable-vms-monitoring-agent/select-change-tracking-arc-vm.png" alt-text="Screenshot showing to select change tracking option for a single Azure arc virtual machine from the portal." lightbox="media/enable-vms-monitoring-agent/select-change-tracking-arc-vm.png":::
+
+   It will initiate the deployment and the notification appears on the top right corner of the screen.
+   
+
 #### [Arc-enabled VMs - portal/CLI](#tab/arcvms)
 
 To enable the Change Tracking and Inventory on Arc-enabled servers, ensure that the custom Change Tracking Data collection rule is associated to the Arc-enabled VMs. 
@@ -101,8 +119,6 @@ Follow these steps to associate the data collection rule to the Arc-enabled VMs:
    ```   
 --- 
 
->[!NOTE]
->It usually takes up to two to three minutes to successfully onboard and enable the virtual machine(s). After you enable a virtual machine for change tracking, you can make changes to the files, registries, or software for the specific VM.
 
 ## Enable Change Tracking at scale using Azure Monitoring Agent
 

articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md

@@ -5,7 +5,7 @@ author: snehasudhirG
 services: automation
 ms.subservice: change-inventory-management
 ms.topic: how-to
-ms.date: 09/27/2024
+ms.date: 10/10/2024
 ms.author: sudhirsneha
 ms.custom:
 ms.service: azure-automation
@@ -29,10 +29,7 @@ Using the Azure portal, you can migrate from Change Tracking & Inventory with LA
 
 ## Onboarding to Change tracking and inventory using Azure Monitoring Agent
 
-### [Using Azure portal - Azure single VM](#tab/ct-single-vm)
-
-> [!NOTE]
-> To onboard Arc-enabled VMs, use the PowerShell Script. For more information, see the steps listed in tab Using PowerShell script - Arc-enabled VMs.
+### [Single Azure VM - Azure portal](#tab/ct-single-vm)
 
 To onboard through Azure portal, follow these steps:
 
@@ -46,14 +43,14 @@ To onboard through Azure portal, follow these steps:
 
    :::image type="content" source="media/guidance-migration-log-analytics-monitoring-agent/switch-versions-inline.png" alt-text="Screenshot that shows switching between log analytics and Azure Monitoring Agent after a successful migration." lightbox="media/guidance-migration-log-analytics-monitoring-agent/switch-versions-expanded.png":::
 
-### [Using Azure portal - Automation account](#tab/ct-at-scale)
+### [Automation account - Azure portal](#tab/ct-at-scale)
 
 1. Sign in to [Azure portal](https://portal.azure.com) and select your Automation account.
 1. Under **Configuration Management**, select **Change tracking** and then select **Configure with AMA**.
 
    :::image type="content" source="media/guidance-migration-log-analytics-monitoring-agent/onboarding-at-scale-inline.png" alt-text="Screenshot of onboarding at scale to Change tracking and inventory using Azure monitoring agent." lightbox="media/guidance-migration-log-analytics-monitoring-agent/onboarding-at-scale-expanded.png":::
 
-1. On the **Onboarding to Change Tracking with Azure Monitoring** page, you can view your automation account and list of machines that are currently on Log Analytics and ready to be onboarded to Azure Monitoring Agent of Change Tracking and inventory.
+1. On the **Onboarding to Change Tracking with Azure Monitoring** page, you can view your automation account and list of both Azure and Azure Arc machines that are currently on Log Analytics and ready to be onboarded to Azure Monitoring Agent of Change Tracking and inventory.
 
    :::image type="content" source="media/guidance-migration-log-analytics-monitoring-agent/onboarding-from-log-analytics-inline.png" alt-text="Screenshot of onboarding multiple virtual machines to Change tracking and inventory from log analytics to Azure monitoring agent." lightbox="media/guidance-migration-log-analytics-monitoring-agent/onboarding-from-log-analytics-expanded.png":::
 
@@ -69,7 +66,21 @@ To onboard through Azure portal, follow these steps:
 
    :::image type="content" source="media/guidance-migration-log-analytics-monitoring-agent/switch-versions-inline.png" alt-text="Screenshot that shows switching between log analytics and Azure Monitoring Agent after a successful migration." lightbox="media/guidance-migration-log-analytics-monitoring-agent/switch-versions-expanded.png":::
 
-### [Using PowerShell script - Arc-enabled VMs](#tab/ps-policy)
+### [Single Azure Arc VM - Azure portal](#tab/ct-single-arcvm)
+
+1. Sign in to the [Azure portal](https://portal.azure.com). Search for and select **Machines-Azure Arc**.
+
+   :::image type="content" source="media/enable-vms-monitoring-agent/select-arc-machines-portal.png" alt-text="Screenshot showing how to select Azure Arc machines from the portal." lightbox="media/enable-vms-monitoring-agent/select-arc-machines-portal.png":::
+
+1. Select the specific Arc machine with Change Tracking V1 enabled that needs to be migrated to Change Tracking V2.
+
+1. Select **Migrate to Change Tracking with AMA** and in the **Configure with Azure monitor agent**,  provide the resource id in the **Log analytics workspace** and select **Migrate** to initiate the deployment.
+
+   :::image type="content" source="media/guidance-migration-log-analytics-monitoring-agent/onboarding-single-arc-vm.png" alt-text="Screenshot of onboarding a single Arc VM to Change tracking and inventory using Azure monitoring agent." lightbox="media/guidance-migration-log-analytics-monitoring-agent/onboarding-single-arc-vm.png":::
+
+1. Select **Manage Activity log connection** to evaluate the incoming events and logs across LA agent and AMA version.
+
+### [Arc-enabled VMs - PowerShell script](#tab/ps-policy)
 
 To onboard Arc-enabled VMs, follow the steps:
 
@@ -173,7 +184,7 @@ To obtain the Log Analytics Workspace resource ID, follow these steps:
 ### [Using PowerShell script](#tab/limit-policy)
 
 1. For File Content changes-based settings, you must migrate manually from LA version to AMA version of Change Tracking & Inventory. Follow the guidance listed in [Track file contents](manage-change-tracking.md#track-file-contents).
-1. Any VM with > 100 file/registry settings for migration via Azure Portal isn't supported.
+1. Any VM with > 100 file/registry settings for migration via Azure portal isn't supported.
 1. Alerts that you configure using the Log Analytics Workspace must be [manually configured](configure-alerts.md).
 
 ---

articles/automation/change-tracking/media/enable-vms-monitoring-agent/monitor-menu-data-collection-rules.png

@@ -1,7 +1,7 @@
 ---
 title: Create functions in Azure using the Azure Developer CLI
 description: "Learn how to use the Azure Developer CLI (azd) to create resources and deploy the local project to a Flex Consumption plan on Azure."
-ms.date: 09/04/2024
+ms.date: 10/19/2024
 ms.topic: quickstart
 zone_pivot_groups: programming-languages-set-functions
 #Customer intent: As a developer, I need to know how to use the Azure Developer CLI to create and deploy my function code securely to a new function app in the Flex Consumption plan in Azure by using azd templates and the azd up command.
@@ -249,19 +249,26 @@ py -m venv .venv
 
 1. Run this command from your app folder in a terminal or command prompt:
 
-    ::: zone pivot="programming-language-csharp, programming-language-powershell,programming-language-python,programming-language-javascript" 
+    ::: zone pivot="programming-language-csharp, programming-language-powershell,programming-language-python" 
     ```console
     func start
     ``` 
     ::: zone-end  
-    ::: zone pivot="programming-language-java"
+    ::: zone pivot="programming-language-java"  
     ```console
     mvn clean package
     mvn azure-functions:run
     ```
     ::: zone-end  
-    ::: zone pivot="programming-language-typescript"
+    ::: zone pivot="programming-language-javascript"  
     ```console
+    npm install
+    func start  
+    ```
+    ::: zone-end  
+    ::: zone pivot="programming-language-typescript"  
+    ```console
+    npm install
     npm start  
     ```
     ::: zone-end  
@@ -273,11 +280,16 @@ py -m venv .venv
     <http://localhost:7071/api/httpget>
 
 1. From a new terminal or command prompt window, run this `curl` command to send a POST request with a JSON payload to the `httppost` endpoint: 
-
+    ::: zone pivot="programming-language-csharp, programming-language-powershell,programming-language-python" 
     ```console
     curl -i http://localhost:7071/api/httppost -H "Content-Type: text/json" -d @testdata.json
     ```
-
+    ::: zone-end  
+    ::: zone pivot="programming-language-javascript,programming-language-typescript" 
+    ```console
+    curl -i http://localhost:7071/api/httppost -H "Content-Type: text/json" -d "@src/functions/testdata.json"
+    ```
+    ::: zone-end  
     This command reads JSON payload data from the `testdata.json` project file. You can find examples of both HTTP requests in the `test.http` project file. 
 
 1. When you're done, press Ctrl+C in the terminal window to stop the `func.exe` host process.

articles/automation/change-tracking/media/enable-vms-monitoring-agent/select-arc-machines-portal.png

@@ -4,7 +4,7 @@ metadata:
   description: In this article, discover answers to common questions about backing up Azure VMs with the Azure Backup service.
   ms.topic: faq
   ms.service: azure-backup
-  ms.date: 09/10/2024
+  ms.date: 10/21/2024
   author: AbhishekMallick-MS
   ms.author: v-abhmallick
 
@@ -296,7 +296,7 @@ sections:
         answer: |
           Yes, it's supported for [Cross Zonal Restore](backup-azure-arm-restore-vms.md#restore-options).
 
-      - question: How do I clear iSCSI session and it's processes after running the Python script for Linux ILR?
+      - question: How do I clear iSCSI session and its processes after running the Python script for Linux ILR?
         answer: |
           After you unmount disks from the Azure portal, run the Python script with `clean` parameter (`python scriptName.py clean`) to clear the session and remove the mount paths of the recovery point from the machine.     
 
@@ -404,5 +404,31 @@ sections:
         answer: |
           The expiry time for the latest recovery point doesn't appear because it has infinite retention until a newer one gets created. The expiry time of other recovery points will be available in the Azure Portal after 24 hours of creation, depending on when the garbage collection runs (that will be within 24 hours).
 
+      - question: Will an Azure VM restore operation to original or alternate location affect a scheduled backup?
+        answer: |
+          No, the restore operation (to  the original or an alternate location) doesn't affect scheduled backups.
+
+          - **Restore to Original Location**: Azure Backup replaces the existing VM’s disks with the ones from the restore point. This process includes [taking a snapshot of the current VM before the restore ensuring that the backup schedule remains](backup-azure-arm-restore-vms.md).
+          - **Restore to Alternate Location**: Azure Backup creates a new VM using the restore point. This new VM won't have the same backup schedule as the original VM; you need to configure the Backup policy manually. Learn [about Azure VM restore](about-azure-vm-restore.md).
 
+          In these restore scenarios, the original backup policy and schedule for the original VM remain unaffected. However, if you want the restored VM (in the alternate location) to have a backup schedule, you need to set up the Backup policy.
       
+      - question: What happens to the backup configuration if I do Original/Alternate Location Restore of Azure VMs?
+        answer: |
+          In case of an Original Location Restore (OLR) or an Alternate Location Restore (ALR) for Azure VMs, Azure Backup performs the backup configuration as:
+
+          | Restore type | Backup configuration | Backup data |
+          | --- | --- | --- |
+          | **Original Location Restore (OLR)** | The backup configuration remains the same. The restored VM uses the same backup policy and schedule as the original VM. | The existing backup data is preserved, and new backups are triggered as per the original backup schedule. |
+          | **Alternate Location Restore (ALR)** | The new VM created in the alternate location doesn't inherit the backup configuration of the original VM. You need to configure a new backup policy for this VM manually. | The backup data for the original VM remains unaffected. However, the new VM starts with a fresh backup history once you configure its backup. |
+
+          >[!Note]
+          >- **OLR**: Provides a seamless continuation of backups with the same policy.
+          >- **ALR**: Requires manual setup of backup policies for the new VM.
+
+      - question: Why VMs with the Storage Spaces direct and Storage Spaces are not supported with the Azure VM Backup? 
+        answer: |    
+          Storage Spaces Direct is not supported since it has data spread across two different virtual machines.
+
+          Storage spaces in a single VM not supported for application consistent VM backup. For application consistent VM backup, VSS freezes the I/O and ensures that disk snapshots are consistent. Storage Spaces can still perform writes in the background, breaking the application consistent guarantee. This can result in a small probability that the backup taken is not application consistent. Today, backup and recovery of VM with storage spaces is not blocked in the product.
+

articles/automation/change-tracking/media/enable-vms-monitoring-agent/select-change-tracking-arc-vm.png

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 10/21/2024
 ms.author: cshoe
 ---
 
@@ -227,6 +227,11 @@ Arm64 based clusters aren't supported at this time.
   - Updated Dapr-Metrics image to v0.6.8 to resolve network timeout issue
   - Resolved issue in Log Processor which prevented MDSD container from starting when cluster is connected behind a Proxy
 
+ ### Container Apps extension v1.37.7 (October 2024)
+
+  - Resolved issue with MDM Init container which caused container to crash in event it couldn't be pulled
+  - Added support for [Logic Apps Hybrid Deployment Model (Public Preview)](https://techcommunity.microsoft.com/t5/azure-integration-services-blog/announcement-introducing-the-logic-apps-hybrid-deployment-model/ba-p/4271568)
+
 ## Next steps
 
 [Create a Container Apps connected environment (Preview)](azure-arc-enable-cluster.md)

articles/automation/change-tracking/media/guidance-migration-log-analytics-monitoring-agent/onboarding-single-arc-vm.png

@@ -27,6 +27,8 @@ This article describes the following device authentication options:
 - [SAS enrollment group](#sas-enrollment-group)
 - [Individual enrollment](#individual-enrollment)
 
+Each of these authentication options requires that each device has a unique device ID. The device ID is a unique identifier for the device that you use to manage the device in your IoT Central application.
+
 ## X.509 enrollment group
 
 In a production environment, using X.509 certificates is the recommended device authentication mechanism for IoT Central. To learn more, see [Device Authentication using X.509 CA Certificates](../../iot-hub/iot-hub-x509ca-overview.md).
@@ -68,6 +70,9 @@ To connect a device with device SAS token to your application:
     az iot central device compute-device-key --primary-key <enrollment group primary key> --device-id <device ID>
     ```
 
+    > [!TIP]
+    > Each device that connects to your IoT Central application must have a unique device ID. The previous command generates a unique token for each device.
+
 1. Use the generated device token when the device connects to your IoT Central application.
 
 > [!NOTE]