SI and ADA updates

Author: v-ksreedevan

articles/migrate/common-questions-discovery-assessment.md

@@ -5,7 +5,7 @@ author: rashijoshi
 ms.author: rajosh
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 11/24/2022
+ms.date: 12/12/2022
 ms.custom: engagement-fy23
 ---
 
@@ -305,7 +305,7 @@ The differences between agentless visualization and agent-based visualization ar
 
 **Requirement** | **Agentless** | **Agent-based**
 --- | --- | ---
-Support |Available for VMware VMs in general availability (GA).<br/><br/> Available for Hyper-V VMs and physical servers in public preview. | In General Availability (GA).
+Support | Generally available for VMware VMs, Hyper-V VMs, bare-metal servers, and servers running on other public clouds like AWS, GCP etc. | In General Availability (GA).
 Agent | No need to install agents on machines you want to cross-check. | Agents to be installed on each on-premises machine that you want to analyze: The [Microsoft Monitoring agent (MMA)](../azure-monitor/agents/agent-windows.md), and the [Dependency agent](../azure-monitor/vm/vminsights-dependency-agent-maintenance.md). 
 Prerequisites | [Review](concepts-dependency-visualization.md#agentless-analysis) the prerequisites and deployment requirements. | [Review](concepts-dependency-visualization.md#agent-based-analysis) the prerequisites and deployment requirements.
 Log Analytics | Not required. | Azure Migrate uses the [Service Map](../azure-monitor/vm/service-map.md) solution in [Azure Monitor logs](../azure-monitor/logs/log-query-overview.md) for dependency visualization. [Learn more](concepts-dependency-visualization.md#agent-based-analysis).

articles/migrate/concepts-dependency-visualization.md

@@ -5,7 +5,7 @@ ms.topic: conceptual
 author: vineetvikram
 ms.author: vivikram
 ms.manager: abhemraj
-ms.date: 08/04/2022
+ms.date: 12/12/2022
 ms.custom: engagement-fy23
 ---
 
@@ -39,7 +39,6 @@ Agentless dependency analysis works by capturing TCP connection data from server
 After discovery of dependency data begins, polling begins:
 
 - The Azure Migrate appliance polls TCP connection data from servers every five minutes to gather data.
-- Data is collected from guest servers via vCenter Server, using vSphere APIs.
 - Polling gathers this data:
 
     - Name of processes that have active connections.

articles/migrate/how-to-create-group-machine-dependencies-agentless.md

@@ -40,7 +40,7 @@ This article describes how to set up agentless dependency analysis using Azure M
 2. As you configure the appliance, you need to specify the following in the appliance configuration manager:
     - The details of the source environment (vCenter Server(s)/Hyper-V host(s) or cluster(s)/physical servers) which you want to discover.
     - Server credentials, which can be domain/ Windows (non-domain)/ Linux (non-domain) credentials. [Learn more](add-server-credentials.md) about how to provide credentials and how the appliance handles them.
-    - Verify the permissions required to perform agentless dependency analysis. For Windows servers, you need to provide domain or non-domain (local) account with administrative permissions. For Linux servers, you need to provide root user account, or an account with these permissions on /bin/netstat and /bin/ls files: CAP_DAC_READ_SEARCH and CAP_SYS_PTRACE.<br/><br/> You can set these capabilities using the following commands: <br/> sudo setcap CAP_DAC_READ_SEARCH,CAP_SYS_PTRACE=ep /bin/ls<br/> sudo setcap CAP_DAC_READ_SEARCH,CAP_SYS_PTRACE=ep /bin/netstat
+    - Verify the permissions required to perform agentless dependency analysis. For Windows servers, you need to provide domain or non-domain (local) account with administrative permissions. For Linux servers, provide a sudo user account with permissions to execute ls and netstat commands or create a user account that has the CAP_DAC_READ_SEARCH and CAP_SYS_PTRACE permissions on /bin/netstat and /bin/ls files. <br/><br/>If you're providing a sudo user account, ensure that you have enabled NOPASSWD for the account to run the required commands without prompting for a password every time sudo command is invoked.
 
 ### Add credentials and initiate discovery
 

articles/migrate/how-to-set-up-appliance-hyper-v.md

@@ -5,7 +5,7 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: how-to
-ms.date: 04/30/2022
+ms.date: 12/12/2022
 ms.custom: engagement-fy23
 ---
 
@@ -174,7 +174,7 @@ Connect from the appliance to Hyper-V hosts or clusters, and start discovery.
 
 ### Provide server credentials
 
-In **Step 3: Provide server credentials to perform software inventory and agentless dependency analysis.**, you can provide multiple server credentials. If you don't want to use any of these appliance features, you can skip this step and proceed with discovery of servers running on Hyper-V hosts/clusters. You can change this option at any time.
+In **Step 3: Provide server credentials to perform software inventory and agentless dependency analysis and to discover SQL Server instances and databases**, you can provide multiple server credentials. If you don't want to use any of these appliance features, you can skip this step and proceed with discovery of servers running on Hyper-V hosts/clusters. You can change this option at any time.
 
 :::image type="content" source="./media/tutorial-discover-hyper-v/appliance-server-credentials-mapping.png" alt-text="Screenshot that shows providing credentials for software inventory and dependency analysis.":::
 

articles/migrate/how-to-set-up-appliance-physical.md

@@ -156,6 +156,8 @@ Now, connect from the appliance to the physical servers to be discovered, and st
 
     ![Screenshot of SSH private key supported format.](./media/tutorial-discover-physical/key-format.png)
 1. If you want to add multiple credentials at once, click on **Add more** to save and add more credentials. Multiple credentials are supported for physical servers discovery.
+   > [!Note]
+   > By default, the credentials will be used to gather data about the installed applications, roles, and features, and also to collect dependency data from Windows and Linux servers, unless you disable the slider to not perform these features (as instructed in the last step).
 1. In **Step 2:Provide physical or virtual server details​**, click on **Add discovery source** to specify the server **IP address/FQDN** and the friendly name for credentials to connect to the server.
 1. You can either **Add single item** at a time or **Add multiple items** in one go. There is also an option to provide server details through **Import CSV**.
 
@@ -173,6 +175,10 @@ Now, connect from the appliance to the physical servers to be discovered, and st
 
 :::image type="content" source="./media/tutorial-discover-physical/disable-slider.png" alt-text="Screenshot that shows where to disable the slider.":::
 
+1. To perform discovery of SQL Server instances and databases, you can add additional credentials (Windows domain/non-domain, SQL authentication credentials) and the appliance will attempt to automatically map the credentials to the SQL servers. If you add domain credentials, the appliance will authenticate the credentials against Active Directory of the domain to prevent any user accounts from locking out. To check validation of the domain credentials, follow these steps:
+  - In the configuration manager credentials table, see **Validation status** for domain credentials. Only the domain credentials are validated.
+  - If validation fails, you can select a Failed status to see the validation error. Fix the issue, and then select **Revalidate credentials** to reattempt validation of the credentials.
+
 ### Start discovery
 
 Click on **Start discovery**, to kick off discovery of the successfully validated servers. After the discovery has been successfully initiated, you can check the discovery status against each server in the table.

articles/migrate/migrate-appliance.md

@@ -5,7 +5,7 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 10/28/2022
+ms.date: 12/12/2022
 ms.custom: engagement-fy23
 ---
 
@@ -53,7 +53,7 @@ The appliance has the following services:
 - **Web apps discovery and assessment agent**: sends the web apps configuration data to Azure.
 
 > [!Note]
-> The last 3 services are only available in the appliance used for discovery and assessment of servers running in your VMware environment.
+> The last 3 services are available in the appliance used for discovery and assessment of servers running in your VMware VMs, Hyper-V VMs, bare-metal servers, and servers running on other public clouds like AWS, GCP etc.
 
 ## Appliance - VMware
 

articles/migrate/tutorial-discover-aws.md

@@ -5,7 +5,7 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: tutorial
-ms.date: 11/13/2022
+ms.date: 12/12/2022
 ms.custom: mvc, subject-rbac-steps
 #Customer intent: As a server admin I want to discover my AWS instances.
 ---
@@ -264,6 +264,8 @@ Now, connect from the appliance to the physical servers to be discovered, and st
 
 
 1. If you want to add multiple credentials at once, select **Add more** to save and add more credentials. Multiple credentials are supported for physical servers discovery.
+   > [!Note]
+   > By default, the credentials will be used to gather data about the installed applications, roles, and features, and also to collect dependency data from Windows and Linux servers, unless you disable the slider to not perform these features (as instructed in the last step).
 1. In **Step 2:Provide physical or virtual server details​**, select **Add discovery source** to specify the server **IP address/FQDN** and the friendly name for credentials to connect to the server.
 1. You can either **Add single item** at a time or **Add multiple items** in one go. There is also an option to provide server details through **Import CSV**.
 
@@ -280,6 +282,10 @@ Now, connect from the appliance to the physical servers to be discovered, and st
 
     :::image type="content" source="./media/tutorial-discover-physical/disable-slider.png" alt-text="Screenshot that shows where to disable the slider.":::
 
+1. To perform discovery of SQL Server instances and databases, you can add additional credentials (Windows domain/non-domain, SQL authentication credentials) and the appliance will attempt to automatically map the credentials to the SQL servers. If you add domain credentials, the appliance will authenticate the credentials against Active Directory of the domain to prevent any user accounts from locking out. To check validation of the domain credentials, follow these steps:
+  - In the configuration manager credentials table, see **Validation status** for domain credentials. Only the domain credentials are validated.
+  - If validation fails, you can select a Failed status to see the validation error. Fix the issue, and then select **Revalidate credentials** to reattempt validation of the credentials.
+
 ### Start discovery
 
 Select **Start discovery**, to kick off discovery of the successfully validated servers. After the discovery has been successfully initiated, you can check the discovery status against each server in the table.

articles/migrate/tutorial-discover-gcp.md

@@ -5,7 +5,7 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: tutorial
-ms.date: 11/13/2022
+ms.date: 12/12/2022
 ms.custom: mvc, subject-rbac-steps
 #Customer intent: As a server admin I want to discover my GCP instances.
 ---
@@ -270,6 +270,8 @@ Now, connect from the appliance to the GCP servers to be discovered, and start t
 
 
 2. If you want to add multiple credentials at once, select **Add more** to save and add more credentials. 
+   > [!Note]
+   > By default, the credentials will be used to gather data about the installed applications, roles, and features, and also to collect dependency data from Windows and Linux servers, unless you disable the slider to not perform these features (as instructed in the last step).
 3. In **Step 2:Provide physical or virtual server details​**, select **Add discovery source** to specify the server **IP address/FQDN** and the friendly name for credentials to connect to the server.
 4. You can either **Add single item** at a time or **Add multiple items** in one go. There's also an option to provide server details through **Import CSV**.
 
@@ -284,6 +286,9 @@ Now, connect from the appliance to the GCP servers to be discovered, and start t
 1. Before initiating discovery, you can choose to disable the slider to not perform software inventory and agentless dependency analysis on the added servers. You can change this option at any time.
 
     :::image type="content" source="./media/tutorial-discover-physical/disable-slider.png" alt-text="Screenshot that shows where to disable the slider.":::
+1. To perform discovery of SQL Server instances and databases, you can add additional credentials (Windows domain/non-domain, SQL authentication credentials) and the appliance will attempt to automatically map the credentials to the SQL servers. If you add domain credentials, the appliance will authenticate the credentials against Active Directory of the domain to prevent any user accounts from locking out. To check validation of the domain credentials, follow these steps:
+  - In the configuration manager credentials table, see **Validation status** for domain credentials. Only the domain credentials are validated.
+  - If validation fails, you can select a Failed status to see the validation error. Fix the issue, and then select **Revalidate credentials** to reattempt validation of the credentials.
 
 ### Start discovery
 

articles/migrate/tutorial-discover-physical.md

@@ -5,7 +5,7 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: tutorial
-ms.date: 11/13/2022
+ms.date: 12/12/2022
 ms.custom: mvc, subject-rbac-steps
 #Customer intent: As a server admin I want to discover my on-premises server inventory.
 ---
@@ -286,6 +286,8 @@ Now, connect from the appliance to the physical servers to be discovered, and st
     ![Screenshot of SSH private key supported format.](./media/tutorial-discover-physical/key-format.png)
 
 1. If you want to add multiple credentials at once, select **Add more** to save and add more credentials. Multiple credentials are supported for physical servers discovery.
+   > [!Note]
+   > By default, the credentials will be used to gather data about the installed applications, roles, and features, and also to collect dependency data from Windows and Linux servers, unless you disable the slider to not perform these features (as instructed in the last step).
 1. In **Step 2:Provide physical or virtual server details​**, select **Add discovery source** to specify the server **IP address/FQDN** and the friendly name for credentials to connect to the server.
 1. You can either **Add single item** at a time or **Add multiple items** in one go. There's also an option to provide server details through **Import CSV**.
 
@@ -301,6 +303,11 @@ Now, connect from the appliance to the physical servers to be discovered, and st
 1. Before initiating discovery, you can choose to disable the slider to not perform software inventory and agentless dependency analysis on the added servers. You can change this option at any time.
 
     :::image type="content" source="./media/tutorial-discover-physical/disable-slider.png" alt-text="Screenshot that shows where to disable the slider.":::
+1. To perform discovery of SQL Server instances and databases, you can add additional credentials (Windows domain/non-domain, SQL authentication credentials) and the appliance will attempt to automatically map the credentials to the SQL servers. If you add domain credentials, the appliance will authenticate the credentials against Active Directory of the domain to prevent any user accounts from locking out. To check validation of the domain credentials, follow these steps:
+  - In the configuration manager credentials table, see **Validation status** for domain credentials. Only the domain credentials are validated.
+  - If validation fails, you can select a Failed status to see the validation error. Fix the issue, and then select **Revalidate credentials** to reattempt validation of the credentials.
+
+
 
 ### Start discovery
 

articles/migrate/whats-new.md

@@ -5,7 +5,7 @@ ms.topic: overview
 author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
-ms.date: 11/21/2022
+ms.date: 12/12/2022
 ms.custom: mvc
 ---
 
@@ -17,12 +17,15 @@ ms.custom: mvc
 - Public Preview: Build business case using Azure Migrate for servers and workloads running in your VMware environment. It helps you eliminate guess work in your cost planning process and adds data driven insights to understand how Azure can bring the most value to your business. 
 
 Key highlights:
+ - On-premises vs Azure total cost of ownership.
+ - Year on year cashflow analysis.
+ - Resource utilization based insights to identify servers and workloads that are ideal for cloud.
+ - Quick wins for migration and modernization including end of support Windows OS and SQL versions.
+ - Long term cost savings by moving from a capital expenditure model to an Operating expenditure model, by paying for only what you use.
+
+- General Availability: Perform software inventory and agentless dependency analysis at-scale for Hyper-V virtual machines and bare metal servers or servers running on other clouds like AWS, GCP etc.
+Learn more on how to perform [software inventory](how-to-discover-applications.md) and [agentless dependency analysis](how-to-create-group-machine-dependencies-agentless.md). 
 
-- On-premises vs Azure total cost of ownership.
-- Year on year cashflow analysis.
-- Resource utilization based insights to identify servers and workloads that are ideal for cloud.
-- Quick wins for migration and modernization including end of support Windows OS and SQL versions.
-- Long term cost savings by moving from a capital expenditure model to an Operating expenditure model, by paying for only what you use.
 
 ## Update (November 2022)