Merge pull request #241206 from MicrosoftDocs/main

6/12/2023 OOB Publishing at 9AM

Author: huypub

articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-prepare-app.md

@@ -14,7 +14,7 @@ ms.date: 06/09/2023
 #Customer intent: As a developer, I want to learn how to configure vanilla JavaScript single-page app (SPA) to sign in and sign out users with my Azure AD for customers tenant.
 ---
 
-# Tutorial: Prepare a vanilla JavaScript single-page app (SPA) for authentication in a customer tenant
+# Tutorial: Prepare a vanilla JavaScript single-page app for authentication in a customer tenant
 
 In the [previous article](./how-to-single-page-app-vanillajs-prepare-tenant.md), you registered an application and configured user flows in your Azure Active Directory (AD) for customers tenant. This article shows you how to create a vanilla JavaScript (JS) single-page app (SPA) and configure it to sign in and sign out users with your customer tenant.
 

articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-prepare-tenant.md

@@ -14,7 +14,7 @@ ms.date: 06/09/2023
 #Customer intent: As a developer, I want to learn how to configure a vanilla JavaScript single-page app (SPA) to sign in and sign out users with my Azure Active Directory (AD) for customers tenant.
 ---
 
-# Tutorial: Prepare your customer tenant to authenticate a vanilla JavaScript single-page app (SPA)
+# Tutorial: Prepare your customer tenant to authenticate a vanilla JavaScript single-page app
 
 This tutorial series demonstrates how to build a vanilla JavaScript single-page application (SPA) and prepare it for authentication using the Microsoft Entra admin center. You'll use the [Microsoft Authentication Library for JavaScript](/javascript/api/overview/msal-overview) library to authenticate your app with your Azure Active Directory (Azure AD) for customers tenant. Finally, you'll run the application and test the sign-in and sign-out experiences.
 

articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-sign-in-sign-out.md

@@ -12,7 +12,7 @@ ms.date: 05/25/2023
 #Customer intent: As a developer, I want to learn how to configure Vanilla JavaScript single-page app (SPA) to sign in and sign out users with my Azure Active Directory (AD) for customers tenant.
 ---
 
-# Tutorial: Add sign-in and sign-out to a Vanilla JavaScript single-page app (SPA) for a customer tenant
+# Tutorial: Add sign-in and sign-out to a vanilla JavaScript single-page app for a customer tenant
 
 In the [previous article](how-to-single-page-app-vanillajs-configure-authentication.md), you edited the popup and redirection files that handle the sign-in page response. This tutorial demonstrates how to build a responsive user interface (UI) that contains a **Sign-In** and **Sign-Out** button and run the project to test the sign-in and sign-out functionality.
 

articles/active-directory/external-identities/customers/includes/register-app/add-platform-redirect-url-vanilla-js.md

@@ -10,7 +10,7 @@ To specify your app type to your app registration, follow these steps:
 
 1. Under **Manage**, select **Authentication**.
 1. On the **Platform configurations** page, select **Add a platform**, and then select **SPA** option.
-1. For the **Redirect URIs** enter `http://localhost:3000/auth/redirect`
+1. For the **Redirect URIs** enter `http://localhost:3000/redirect`
 1. Select **Configure** to save your changes.
 1. Back on the **Platform configurations** page, in the new **Single-page application** that has appeared, select **Add URI**, then enter `http://localhost:3000/`
 1. Select **Save** to save your changes, and ensure that both URIs are listed.

articles/automation/change-tracking/media/overview-monitoring-agent/frequency-slider-expanded.png

@@ -3,13 +3,13 @@ title: Azure Automation Change Tracking and Inventory overview using Azure Monit
 description: This article describes the Change Tracking and Inventory feature using Azure monitoring agent (Preview), which helps you identify software and Microsoft service changes in your environment.
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 02/23/2023
+ms.date: 05/29/2023
 ms.topic: conceptual
 ---
 
 # Overview of change tracking and inventory using Azure Monitoring Agent (Preview)
 
-**Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: Windows Registry :heavy_check_mark: Windows Files :heavy_check_mark: Linux Files :heavy_check_mark: Windows Software
+**Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: Windows Registry :heavy_check_mark: Windows Files :heavy_check_mark: Linux Files :heavy_check_mark: Windows Software :heavy_check_mark: Windows Services & Linux Daemons
 
 > [!Important]
 > Currently, Change tracking and inventory uses Log Analytics Agent and this is scheduled to retire by 31.August.2024. We recommend that you use Azure Monitoring Agent as the new supporting agent.
@@ -39,6 +39,8 @@ Change Tracking and Inventory using Azure Monitoring Agent (Preview) doesn't sup
 - If network traffic is high, change records can take up to six hours to display.
 - If you modify a configuration while a machine or server is shut down, it might post changes belonging to the previous configuration.
 - Collecting Hotfix updates on Windows Server 2016 Core RS3 machines.
+- Linux daemons might show a changed state even though no change has occurred. This issue arises because of how the `SvcRunLevels` data in the Azure Monitor [ConfigurationChange](https://learn.microsoft.com/azure/azure-monitor/reference/tables/configurationchange) table is written. 
+
 
 ## Limits
 
@@ -51,6 +53,8 @@ The following table shows the tracked item limits per machine for change trackin
 |Registry|250||
 |Windows software|250|Doesn't include software updates.|
 |Linux packages|1,250||
+|Windows Services |250||
+|Linux Daemons | 250|| 
 
 ## Supported operating systems
 
@@ -119,21 +123,58 @@ The next table shows the data collection frequency for the types of changes supp
 | Windows registry | 50 minutes |
 | Windows file | 30 to 40 minutes |
 | Linux file | 15 minutes |
-| Windows services | 10 seconds to 30 minutes</br> Default: 30 minutes |
+| Windows services | 10 minutes to 30 minutes</br> Default: 30 minutes |
 | Windows software | 30 minutes |
 | Linux software | 5 minutes |
+| Linux Daemons | 5 minutes | 
 
 The following table shows the tracked item limits per machine for Change Tracking and Inventory.
 
 | **Resource** | **Limit** |
-|---|---|---|
+|---|---|
 |File|500|
 |Registry|250|
 |Windows software (not including hotfixes) |250|
 |Linux packages|1250|
+|Windows Services | 250 |
+|Linux Daemons| 500| 
+
+### Windows services data
+
+#### Prerequisites
+
+To enable tracking of Windows Services data, you must upgrade CT extension and use extension more than or equal to 2.11.0.0
+
+#### [For Windows Azure VMs](#tab/win-az-vm)
+
+```powershell-interactive
+- az vm extension set --publisher Microsoft.Azure.ChangeTrackingAndInventory --version 2.11.0 --ids /subscriptions/<subscriptionids>/resourceGroups/<resourcegroupname>/providers/Microsoft.Compute/virtualMachines/<vmname> --name ChangeTracking-Windows --enable-auto-upgrade true
+```
+#### [For Linux Azure VMs](#tab/lin-az-vm)
+
+```powershell-interactive
+– az vm extension set --publisher Microsoft.Azure.ChangeTrackingAndInventory --version 2.11.0 --ids /subscriptions/<subscriptionids>/resourceGroups/<resourcegroupname>/providers/Microsoft.Compute/virtualMachines/<vmname> --name ChangeTracking-Linux --enable-auto-upgrade true
+```
+#### [For Arc-enabled Windows VMs](#tab/win-arc-vm)
+
+```powershell-interactive
+– az connectedmachine extension create --name ChangeTracking-Linux --publisher Microsoft.Azure.ChangeTrackingAndInventory --type ChangeTracking-Linux --machine-name <arc-server-name> --resource-group <resource-group-name> --location <arc-server-location> --enable-auto-upgrade true
+```
+
+#### [For Arc-enabled Linux VMs](#tab/lin-arc-vm)
+
+```powershell-interactive
+- az connectedmachine extension create --name ChangeTracking-Windows --publisher Microsoft.Azure.ChangeTrackingAndInventory --type ChangeTracking-Windows --machine-name <arc-server-name> --resource-group <resource-group-name> --location <arc-server-location> --enable-auto-upgrade true
+```
+---
+
+#### Configure frequency
+
+The default collection frequency for Windows services is 30 minutes. To configure the frequency:
+- under **Edit** Settings, use a slider on the **Windows services** tab.
+
+:::image type="content" source="media/overview-monitoring-agent/frequency-slider-inline.png" alt-text="Screenshot of frequency slider." lightbox="media/overview-monitoring-agent/frequency-slider-expanded.png":::
 
-> [!NOTE]
-> Change Tracking with Support Windows Services & Daemons will be supported by GA.
 
 ## Support for alerts on configuration state
 

articles/automation/change-tracking/media/overview-monitoring-agent/frequency-slider-inline.png

@@ -115,7 +115,7 @@ ms.author: eur
 | `mr-IN` | Marathi (India) | Plain text |
 | `ms-MY` | Malay (Malaysia) | Audio + human-labeled transcript<br/><br/>Plain text |
 | `mt-MT` | Maltese (Malta) | Plain text |
-| `my-MM` | Burmese (Myanmar) | Not supported |
+| `my-MM` | Burmese (Myanmar) | Plain text |
 | `nb-NO` | Norwegian Bokmål (Norway) | Audio + human-labeled transcript<br/><br/>Plain text |
 | `ne-NP` | Nepali (Nepal) | Plain text |
 | `nl-BE` | Dutch (Belgium) | Plain text |