Merge pull request #286931 from MicrosoftDocs/main

Publish to Live Thursday 4AM PST, 9/18

Author: PMEds28

articles/azure-signalr/signalr-tutorial-build-blazor-server-chat-app.md

@@ -4,14 +4,14 @@ description: In this tutorial, you learn how to build and modify a Blazor Server
 author: vicancy
 ms.service: azure-signalr-service
 ms.topic: tutorial
-ms.date: 05/22/2022
+ms.date: 08/28/2024
 ms.author: lianwei
 ms.devlang: csharp
 ---
 
 # Tutorial: Build a Blazor Server chat app
 
-This tutorial shows you how to build and modify a Blazor Server app. You'll learn how to:
+This tutorial shows you how to build and modify a Blazor Server app. You learn how to:
 > [!div class="checklist"] 
 > * Build a simple chat room with the Blazor Server app template.
 > * Work with Razor components.
@@ -37,7 +37,10 @@ Ready to start?
 
 ## Build a local chat room in Blazor Server app
 
-Beginning in Visual Studio 2019 version 16.2.0, Azure SignalR Service is built into the web application publish process to make managing the dependencies between the web app and SignalR service much more convenient. You can work in a local SignalR instance in a local development environment and work in Azure SignalR Service for Azure App Service at the same time without any code changes.
+Beginning in Visual Studio 2019 version 16.2.0, Azure SignalR Service is built into the web application publish process to make managing the dependencies between the web app and SignalR service much more convenient. You can work without any code changes at the same time: 
+
+* in a local SignalR instance, in a local development environment.
+* in Azure SignalR Service for Azure App Service.
 
 1. Create a Blazor chat app:
    1. In Visual Studio, choose **Create a new project**. 
@@ -106,7 +109,7 @@ Beginning in Visual Studio 2019 version 16.2.0, Azure SignalR Service is built i
    dotnet add package Microsoft.AspNetCore.SignalR.Client --version 3.1.7
    ```
 
-1. Create a new [Razor component](/aspnet/core/blazor/components/) called `ChatRoom.razor` under the `Pages` folder to implement the SignalR client. Follow the steps below or use the [ChatRoom.razor](https://github.com/aspnet/AzureSignalR-samples/tree/master/samples/BlazorChat/Pages/ChatRoom.razor) file.
+1. To implement the SignalR client, create a new [Razor component](/aspnet/core/blazor/components/) called `ChatRoom.razor` under the `Pages` folder. Use the [ChatRoom.razor](https://github.com/aspnet/AzureSignalR-samples/tree/master/samples/BlazorChat/Pages/ChatRoom.razor) file or perform the following steps:
 
    1. Add the [`@page`](/aspnet/core/mvc/views/razor#page) directive and the using statements. Use the [`@inject`](/aspnet/core/mvc/views/razor#inject) directive to inject the [`NavigationManager`](/aspnet/core/blazor/fundamentals/routing#uri-and-navigation-state-helpers) service.
 
@@ -363,7 +366,7 @@ Beginning in Visual Studio 2019 version 16.2.0, Azure SignalR Service is built i
    }
    ```
 
-1. Press <kbd>F5</kbd> to run the app. Now, you can initiate the chat:
+1. To run the app, press <kbd>F5</kbd>. Now, you can initiate the chat:
 
    [ ![An animated chat between Bob and Alice is shown. Alice says Hello, Bob says Hi.](media/signalr-tutorial-build-blazor-server-chat-app/blazor-chat.gif) ](media/signalr-tutorial-build-blazor-server-chat-app/blazor-chat.gif#lightbox)
 
@@ -374,7 +377,7 @@ Beginning in Visual Studio 2019 version 16.2.0, Azure SignalR Service is built i
 When you deploy the Blazor app to Azure App Service, we recommend that you use [Azure SignalR Service](/aspnet/core/signalr/scale#azure-signalr-service). Azure SignalR Service allows for scaling up a Blazor Server app to a large number of concurrent SignalR connections. In addition, the SignalR service's global reach and high-performance datacenters significantly aid in reducing latency due to geography.
 
 > [!IMPORTANT]
-> In a Blazor Server app, UI states are maintained on the server side, which means a sticky server session is required to preserve state. If there is a single app server, sticky sessions are ensured by design. However, if there are multiple app servers, there are chances that the client negotiation and connection may go to different servers which may lead to an inconsistent UI state management in a Blazor app. Hence, it is recommended to enable sticky server sessions as shown below in *appsettings.json*:
+> In a Blazor Server app, UI states are maintained on the server side, which means a sticky server session is required to preserve state. If there is a single app server, sticky sessions are ensured by design. However, if multiple app servers are in use, the client negotiation and connection may be redirected to different servers, which may lead to an inconsistent UI state management in a Blazor app. Hence, it is recommended to enable sticky server sessions as shown in *appsettings.json*:
 >
 > ```json
 > "Azure:SignalR:ServerStickyMode": "Required"
@@ -393,7 +396,7 @@ When you deploy the Blazor app to Azure App Service, we recommend that you use [
 
    [ ![On Publish, the link to Configure is highlighted.](media/signalr-tutorial-build-blazor-server-chat-app/blazor-chat-dependency.png) ](media/signalr-tutorial-build-blazor-server-chat-app/blazor-chat-dependency.png#lightbox)
 
-   The service dependency will carry out the following activities to enable your app to automatically switch to Azure SignalR Service when on Azure:
+   The service dependency carries out the following activities to enable your app to automatically switch to Azure SignalR Service when on Azure:
 
    * Update [`HostingStartupAssembly`](/aspnet/core/fundamentals/host/platform-specific-configuration) to use Azure SignalR Service.
    * Add the Azure SignalR Service NuGet package reference.
@@ -422,7 +425,7 @@ When you deploy the Blazor app to Azure App Service, we recommend that you use [
    dotnet add package Microsoft.Azure.SignalR
    ```
 
-1. Add a call to `AddAzureSignalR()` in `Startup.ConfigureServices()` as demonstrated below.
+1. Add a call to `AddAzureSignalR()` in `Startup.ConfigureServices()` as shown in the following example:
 
    ```cs
    public void ConfigureServices(IServiceCollection services)
@@ -444,7 +447,7 @@ When you deploy the Blazor app to Azure App Service, we recommend that you use [
 >     "Azure": {
 >       "SignalR": {
 >         "Enabled": true,
->         "ConnectionString": <your-connection-string>       
+>         "ConnectionString": <your-connection-string> 
 >       }
 >     }
 >    

articles/backup/backup-mabs-unattended-install.md

@@ -3,7 +3,7 @@ title: Silent installation of Azure Backup Server V4
 description: Use a PowerShell script to silently install Azure Backup Server V4. This kind of installation is also called an unattended installation.
 ms.service: azure-backup
 ms.topic: how-to
-ms.date: 04/18/2024
+ms.date: 09/18/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
@@ -28,6 +28,9 @@ To install the Backup Server, run the following command:
 3. On the server that hosts Azure Backup Server V4 or later, create a text file. (You can create the file in Notepad or in another text editor.) Save the file as MABSSetup.ini.
 4. Paste the following code in the MABSSetup.ini file. Replace the text inside the brackets (\< \>) with values from your environment. The following text is an example:
 
+   >[!Caution]
+   >Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. Ensure that you delete the **MABSSetup.ini** file once the installation is complete.
+
    ```text
    [OPTIONS]
    UserName=administrator

articles/defender-for-iot/organizations/cli-ot-sensor.md

@@ -60,7 +60,6 @@ Use the following commands to restart the OT sensor appliance.
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
 |**admin**     |   `system reboot`      |   No attributes     |
-|**cyberx**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   `sudo reboot`      |   No attributes      |
 |**cyberx_host**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   `sudo reboot`      |   No attributes      |
 
 For example, for the *admin* user:
@@ -76,7 +75,6 @@ Use the following commands to shut down the OT sensor appliance.
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
 |**admin**     |   `system shutdown`      |   No attributes      |
-|**cyberx**  , or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)    |   `sudo shutdown -r now`      |   No attributes      |
 |**cyberx_host**, or **admin** with [root access](references-work-with-defender-for-iot-cli-commands.md#access-the-system-root-as-an-admin-user)     |   `sudo shutdown -r now`      |   No attributes      |
 
 For example, for the *admin* user:

articles/migrate/azure-monitor-agent-migration.md

@@ -0,0 +1,69 @@
+---
+title: Migrate to Azure Monitor Agent from Log Analytics agent 
+description: Procedure to migrate to Azure Monitor Agent from MMA
+author: v-sreedevank
+ms.author: prijaisw
+ms.topic: how-to
+ms.date: 09/18/2024
+
+# Customer intent: As an azure administrator, I want to understand the process of migrating from the MMA agent to the AMA agent.
+
+---
+
+# Agent-based dependency analysis using Azure monitor agent (AMA)
+
+Dependency analysis helps you to identify and understand dependencies across servers that you want to assess and migrate to Azure. We currently perform agent-based dependency analysis by downloading the  [MMA agent and associating a Log Analytics workspace](concepts-dependency-visualization.md) with the Azure Migrate project.
+
+[Azure Monitor Agent (AMA)](/azure/azure-monitor/agents/azure-monitor-agent-overview) replaces the Log Analytics agent, also known as Microsoft Monitor Agent (MMA) and OMS, for Windows and Linux machines, in Azure and non-Azure environments, on-premises, and other clouds. 
+
+This article describes the impact on agent-based dependency analysis because of Azure Monitor Agent (AMA) replacing the Log Analytics agent (also known as Microsoft Monitor agent (MMA)) and provides guidance to migrate from the Log Analytics agent to Azure Monitor Agent.
+
+> [!IMPORTANT]
+> The Log Analytics agent will be [retired on **August 31, 2024**](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). You can expect the following when you use the MMA or OMS agent after this date.
+> - **Data upload:** Cloud ingestion services will gradually reduce support for MMA agents, which may result in decreased support and potential compatibility issues for MMA agents over time.  Ingestion for MMA will be unchanged until February 1 2025.
+> - **Installation:** The ability to install the legacy agents will be removed from the Azure portal and installation policies for legacy agents will be removed. You can still install the MMA agents extension as well as perform offline installations.
+> - **Customer Support:** You will not be able to get support for legacy agent issues.
+> - **OS Support:** Support for new Linux or Windows distros, including service packs, won't be added after the deprecation of the legacy agents.
+
+> [!Note]
+>  Starting July 1, 2024, [Standard Log Analytics charges](https://go.microsoft.com/fwlink/?linkid=2278207) are applicable for Agent-based dependency visualization. We suggest moving to [agentless dependency analysis](how-to-create-group-machine-dependencies-agentless.md) for a seamless experience.
+
+> [!Note]
+> The pricing estimation has been covered in [Estimate the price change](#estimate-the-price-change) section.
+
+## Migrate from Log analytics agent (MMA) to Azure Monitor agent (AMA)
+
+If you already set up MMA and the associated Log Analytics workspace with your Azure Migrate project, you can migrate from the existing Log analytics agent to Azure Monitor agent without breaking/changing the association of the Log Analytics workspace with the Azure Migrate project by following these steps.
+
+1. To deploy the Azure Monitor agent, it's recommended to first clean up the existing Service Map to avoid duplicates. [Learn more](/azure/azure-monitor/vm/vminsights-migrate-from-service-map#remove-the-service-map-solution-from-the-workspace).
+
+1. Review the [prerequisites](/azure/azure-monitor/agents/azure-monitor-agent-manage#prerequisites) to install the Azure Monitor Agent. 
+
+1. Download and run the script on the host machine as detailed in [Installation options](/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal#installation-options). To get the Azure Monitor agent and the Dependency agent deployed on the guest machine, create the [Data collection rule (DCR)](/azure/azure-monitor/agents/azure-monitor-agent-data-collection) that maps to the Log analytics workspace ID. 
+
+In the transition scenario, the Log analytics workspace would be the same as the one that was configured for Service Map agent. DCR allows you to enable the collection of Processes and Dependencies. By default, it's disabled. 
+
+## Estimate the price change
+
+You'll now be charged for associating a Log Analytics workspace with Azure Migrate project. This was earlier free for the first 180 days.
+As per the pricing change, you'll be billed against the volume of data gathered by the AMA agent and transmitted to the workspace. To review the volume of data you're gathering, follow these steps:
+
+1. Sign in to the Log analytics workspace. 
+1. Navigate to the **Logs** section and run the following query: 
+ 
+   ```
+    let AzureMigrateDataTables = dynamic(["ServiceMapProcess_CL","ServiceMapComputer_CL","VMBoundPort","VMConnection","VMComputer","VMProcess","InsightsMetrics"]); Usage  
+
+    | where StartTime >= startofday(ago(30d)) and StartTime < startofday(now()) 
+
+    | where DataType in (AzureMigrateDataTables)  
+
+    | summarize AzureMigateGBperMonth=sum(Quantity)/1000 
+    ```
+
+## Support for Azure Monitor agent in Azure Migrate 
+
+Install and manage Azure Monitor agent as mentioned [here](/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal). Currently, you can download the Log Analytics agent through the Azure Migrate portal. 
+
+## Next steps
+[Learn](how-to-create-group-machine-dependencies.md) how to create dependencies for a group.

articles/migrate/toc.yml

@@ -228,6 +228,8 @@ items:
       href: how-to-discover-applications.md
     - name: Discover SQL instances and web apps in an existing project
       href: how-to-discover-sql-existing-project.md
+    - name: Migrate to Azure Monitor agent
+      href: azure-monitor-agent-migration.md
     - name: Analyze machine dependencies (agent-based)
       href: how-to-create-group-machine-dependencies.md
     - name: Analyze machine dependencies (agentless)

articles/site-recovery/azure-stack-site-recovery.md

@@ -1,8 +1,8 @@
 ---
 title: Replicate Azure Stack VMs to Azure using Azure Site Recovery
 description: Learn how to set up disaster recovery to Azure for Azure Stack VMs with the Azure Site Recovery service.
-ms.topic: conceptual
-ms.date: 02/20/2024
+ms.topic: how-to
+ms.date: 09/11/2024
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 ms.service: azure-site-recovery