Revise application management documentation

Updated the article to reflect changes in application definition and management processes, including automatic discovery and CSV import limitations.

Author: Vikram1988

articles/migrate/define-manage-applications.md

@@ -14,12 +14,12 @@ ms.custom:
 ---
 
 # Explore application inventory
-This article describes how you can use Azure Migrate to define applications running in your datacenter by logically grouping servers and workloads as an application entity. These applications can be used to plan and execute the migrations more efficiently.
+This article describes how you can use Azure Migrate to define applications running in your datacenter by logically grouping servers and workloads as an application entity. These applications can be used to plan and execute the migrations more efficiently. Azure Migrate now supports the automatic discovery of applications by grouping of inventory discovered using [Collector](how-to-discover-using-collector.md).
 
 ## Current limitations
 
 - Defining applications using CSV import is currently not supported for projects set up with private endpoint connectivity.
-- Updating application details and properties using CSV imported is currently not supported.
+- Auto discovery of applications is currently only supported for collector-based inventory and not appliance or CSV import based inventory.
 
 
 ## Before you start
@@ -72,19 +72,20 @@ After you initiate discovery, appliance performs the discovery of configuration
 - The visualization shows logically spread server nodes with their connections, indicating their network affinity to help you identify applications running in your datacenter. [Learn more](how-to-create-group-machine-dependencies-agentless.md)
 - You can **add or edit tags** on the servers, you identify to be part of the same application group. Tags can help you define application entity in the Azure Migrate project.
 
-## Define applications
+## Add applications
 
-You can start defining the applications running in your datacenter. Here are the steps you can follow to get started:
+You can start identifying the applications running in your datacenter. Here are the steps you can follow to get started:
 
-1. You can either go to **Overview** and select **Define application** from the All inventory summary card or you can go to **Applications** under **Explore applications** and select **Define application** from there.
-2. You can start in one of the two ways- select **Define application** if you want to define application through Portal or select **Import > Import applications** to import the application details at scale using a CSV file.
+1. You can either go to **Overview** and select **Add application** from the All inventory summary card or you can go to **Applications** under **Explore applications** and select **Add application** from there.
+2. The applications can be inventoried in one of three ways- select **Add application** if you want to define application through Portal or select **Import > Import applications** to import the application details at scale using a CSV file.
+3. If you have performed the discovery using the [Collector](how-to-discover-using-collector.md), discovery of the applications will be automatically triggered and you can review the system-defined applications in the **Applications** view. 
 
-### Define new application
+### Create new application
 
-1. Select **New application**, start by providing basic details of an application like **Name**, **Description** and **Type**. You can choose to provide same name for the application as on-premises, add a description that helps the service understand about the application and choose between **Custom** or **Packaged** for application type. 
+1. Select **Add applications> Create new application**, start by providing basic details of an application like **Name**, **Description** and **Type**. You can choose to provide same name for the application as on-premises, add a description that helps the service understand about the application and choose between **Custom** or **Packaged** for application type. 
 
     >[!Note]
-    > The type **Packaged** refers to the Commercial-off-the-shelf (COTS) applications you are running in your datacenter.
+    > The application **Name** also allows for alphanumeric and special characters except ',' and '\'. The type **Packaged** refers to the Commercial-off-the-shelf (COTS) applications you are running in your datacenter.
 
 2. In the next step, you can link the workloads that are hosting this application. You can select **Link workloads** to go to the All inventory view, which helps you select the workloads that you want to add to this new application. 
 3. You can scope the All inventory view by searching for specific workloads or filtering workloads by Category, Type, OS name etc. and **Add** the selected workloads.
@@ -114,17 +115,17 @@ If you want to define applications at scale, you can select **Import> Import app
 
 1. You can define applications by adding the application names against the discovered servers and workloads in the prescribed template which is an export of all discovered inventory. 
 2. You can select **Export all inventory** which downloads a CSV file with the details of all discovered inventory across servers, databases and web applications.
-3. In the exported CSV, you can add names of the applications, a workload is a part of. You can add more than one name if the workload is shared amongst multiple applications. For instance, if a database- "SQLDB01" is shared by 2 applications, then you can add- "App01, App02" under Application name column in the same row.
+3. In the exported CSV, you can add names of the applications, a workload is a part of. You can add more than one name if the workload is shared amongst multiple applications. For instance, if a database- "SQLDB01" is shared by 2 applications, then you can add- "App01, App02" under Application name column in the same row. 
 
     >[!Note]
-    > The **Application names** are case-sensitive. You can add applications in multiple import operations but it is recommended to not trigger multiple import operations in parallel. 
+    > The **Application name(s)** are case-sensitive. The application name also allows for alphanumeric and special characters except ',' and '\'. You can add applications in multiple import operations but it is recommended to not trigger multiple import operations in parallel. 
 
 4. After adding the application names to the file, you can browse and select the CSV file. 
 5. If the selected file passes the validation checks, you can select **Import** to upload the details of the applications, as added in the CSV file.
 6. After the import is complete, you can see the import status and review the **no of applications created** and check the **error** file if any failures occur. 
 
     >[!Note]
-    > Currently, import applications only supports adding workloads to an application and not to removing any associated workloads from existing applications. To remove a workload, use the portal experience to review and edit the specific application.
+    > The All inventory export contains a column named 'App ARM ID Name(s)' which is the ARM representation of the application resource- do not add/edit any values in the column as that can lead to errors in importing the application grouping. Currently, import applications only supports adding workloads to an application and not to removing any associated workloads from existing applications. To remove a workload, use the portal experience to review and edit the specific application.
 
 ### Import application properties
 When the application is defined using import, a warning icon appears next to the application name to indicate that mandatory properties need to be updated. You can update these properties individually by selecting the application in the Applications view, or update them at scale using **Import> Import application properties**. 
@@ -151,7 +152,6 @@ After defining the applications, you can review the applications any time from t
 - You can scope the view using **search** or by applying **filter** on one or more application attributes.
 - You can also select one or more applications to **Create assessment**, **Sync code changes**, **Add or edit tags** or **Delete** applications.
 
-
 ## Update applications
 
  You can select any application name to review and update the basic details, added workloads, properties or tags. Here are the steps you can follow:
@@ -162,6 +162,15 @@ After defining the applications, you can review the applications any time from t
 4. You can review the **Workloads** to add or remove any workloads any time after the application was defined.
 5. You can also review and update the **Properties** or **Tags** associated with the application.
 
+## Auto-discovered applications
+
+Azure Migrate now supports the automatic discovery of applications by grouping of inventory discovered using [Collector](how-to-discover-using-collector.md). Currently the process of automatically creating applications is performed only once after the inventory from collector is imported. Each auto-discovered application represents a logical grouping of servers (and workloads running on those servers) automatically identified using server-naming patterns, inferred environments, and derived server roles. You can review these applications from the **Applications** view. 
+
+- The view shows Applications which are either **Managed by** system (auto-discovered applications) or user (manually added applications through portal or import).
+- You can scope the system-defined applications from the view and filter by **Confidence score** which is a system assigned score to represent the accuracy of the application grouping. The user-defined (manually created) applications do not have a confidence score value so it is set to '-'.
+- Just like user-defined (manually created) applications, you can review and update the auto-discovered applications as well.
+- If you update the application grouping, basic details, properties or tags, the **Managed by** property will be changed from 'system' to 'user'.
+- You can select one or more auto-discovered applications to **Create assessment**, **Add or edit tags** or **Delete** applications.
 
 ## Delete applications