removing the note

snehaamicrosoft · snehaamicrosoft · commit d0350188ec44 · 2019-11-18T15:13:34.000+05:30
diff --git a/articles/migrate/how-to-create-group-machine-dependencies-agentless.md b/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
@@ -1,27 +1,24 @@
 ---
-title: Group machines in Azure Migrate using agentless dependency visualization 
+title: Group machines in Azure Migrate using agentless dependency visualization
 description: Describes how to create groups using machine dependencies in an agentless manner.
 author: rayne-wiselman
 ms.service: azure-migrate
 ms.topic: article
-ms.date: 10/23/2019
+ms.date: 11/18/2019
 ms.author: hamusa
 ---
 
 
 # Set up agentless dependency visualization for assessment
 
-> [!NOTE]
-> If you don't yet see this feature in the Azure Migrate portal, hang on. It will appear over the next week or so.
-
 This article describes how to set up agentless dependency mapping in Azure Migrate: Server Assessment. This capability is currently available in preview for VMware machines discovered using an Azure Migrate appliance. 
 
 > [!IMPORTANT]
 > Agentless dependency visualization is currently in preview for Azure VMware VMs discovered using an Azure Migrate appliance.
-> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. 
+> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
 > For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-## About dependency mapping 
+## About dependency mapping
 
 Dependency mapping helps you to visualize dependencies across machines that you want to assess and migrate. You typically use dependency mapping when you want to assess machines with higher levels of confidence.
 
@@ -43,7 +40,7 @@ Agentless dependency visualization doesn't require you to install any agents on
 ## Current limitations
 
 - Agentless dependency visualization is currently available for VMware VMs only.
-- Right now you can't add or remove a server from a group, in the dependency analysis view. 
+- Right now you can't add or remove a server from a group, in the dependency analysis view.
 - Dependency map for a group of servers is currently not available.
 - Currently, the dependency data cannot be downloaded in tabular format.
 
@@ -57,12 +54,12 @@ Agentless dependency visualization doesn't require you to install any agents on
 
 
 ### Supported operating systems
- 
+
 Supported operating systems for agentless dependency visualization are as follows.
 
 **Type** | **Supported operating systems**
---- | --- 
-**Windows** | Microsoft Windows Server 2016 <br/> Microsoft Windows Server 2012 R2 <br/> Microsoft Windows Server 2012 <br/> Microsoft Windows Server 2008 R2 (64-bit) 
+--- | ---
+**Windows** | Microsoft Windows Server 2016 <br/> Microsoft Windows Server 2012 R2 <br/> Microsoft Windows Server 2012 <br/> Microsoft Windows Server 2008 R2 (64-bit)
 **Linux** | Red Hat Enterprise Linux 7, 6, 5 <br/> Ubuntu Linux 14.04, 16.04 <br/> Debian 7, 8 <br/> Oracle Linux 6, 7 <br/> CentOS 5, 6, 7  
 
 
@@ -81,7 +78,7 @@ Add the account as follows:
 
 1. Open the appliance management app. Navigate to the **Provide vCenter details** panel.
 2. In the **Discover application and dependencies on VMs** section, click **Add credentials**
-3. Choose the **Operating system**. 
+3. Choose the **Operating system**.
 4. Provide a friendly name for the account.
 5. Provide the **User name** and **Password**
 6. Click **Save**.
@@ -110,8 +107,8 @@ You will be able to visualize dependencies 6 hours after starting dependency dis
 2. Search for the machine for which you want to view the dependency map.
 3. Click **View dependencies** in the **Dependencies** column.
 4. Change the time period for which you want to view the map using the **Time duration** dropdown.
-5. Expand the **Client** group to list the machines that have a dependency on the selected machine. 
-6. Expand the **Port** group to list the machines that have a dependency from the selected machine. 
+5. Expand the **Client** group to list the machines that have a dependency on the selected machine.
+6. Expand the **Port** group to list the machines that have a dependency from the selected machine.
 7. To navigate to the map view of any of the dependent machines, click on the machine name, and then click **Load server map**
 
     ![Expand Server port group and load server map](./media/how-to-create-group-machine-dependencies-agentless/load-server-map.png)
diff --git a/articles/migrate/how-to-discover-applications.md b/articles/migrate/how-to-discover-applications.md
@@ -4,20 +4,17 @@ description: Describes how to discover apps, roles, and features on on-premises
 author: snehaamicrosoft
 ms.service: azure-migrate
 ms.topic: article
-ms.date: 10/16/2019
+ms.date: 11/18/2019
 ms.author: snehaa
 ---
- 
-# Discover machine apps, roles, and features 
 
-> [!NOTE]
-> If you don't yet see this feature in the Azure Migrate portal, hang on. It will appear over the next week or so.
+# Discover machine apps, roles, and features
 
 This article describes how to discover applications, roles, and features on on-premises servers, using Azure Migrate: Server Assessment.
 
-Discovering the inventory of apps, and roles/features running on your on-premises machines helps you to identify and plan a migration path to Azure that's tailored for your workloads. 
+Discovering the inventory of apps, and roles/features running on your on-premises machines helps you to identify and plan a migration path to Azure that's tailored for your workloads.
 
-App discovery using Azure Migrate: Server Assessment is agentless. Nothing needs to be installed on machines and VMs. Server Assessment uses the Azure Migrate appliance to perform discovery along with machine guest credentials. The appliance remotely accesses machines using WMI and SSH calls. 
+App discovery using Azure Migrate: Server Assessment is agentless. Nothing needs to be installed on machines and VMs. Server Assessment uses the Azure Migrate appliance to perform discovery along with machine guest credentials. The appliance remotely accesses machines using WMI and SSH calls.
 
 > [!NOTE]
 > App discovery is currently supported for VMware VMs only, and is limited to discovery only. We don't yet offer app-based assessment.  Right now Server Assessment currently assesses on-premises VMware VMs, Hyper-V VMs, and physical servers at the machine level, for lift-and-shift migrations.
@@ -45,7 +42,7 @@ After the appliance is deployed and you've provided credentials, the appliance s
 
 ## Review and export the inventory
 
-After discovery finishes, if you provided credentials for app discovery, you can review and export the app inventory in the Azure portal. 
+After discovery finishes, if you provided credentials for app discovery, you can review and export the app inventory in the Azure portal.
 
 1. In **Azure Migrate - Servers** > **Azure Migrate: Server Assessment**, click the displayed count to open the **Discovered servers** page.
 
diff --git a/articles/migrate/tutorial-assess-import.md b/articles/migrate/tutorial-assess-import.md
@@ -11,10 +11,7 @@ ms.author: raynew
 
 # Assess servers using imported data
 
-> [!NOTE]
-> If you don't yet see this feature in the Azure Migrate portal, hang on. It will appear over the next week or so.
-
-This article explains how to assess on-premises servers with [Azure Migrate: Server Assessment](migrate-services-overview.md#azure-migrate-server-assessment-tool), by importing server metadata using CSV. With this method of assessment, you don't need to set up the Azure Migrate appliance to create an assessment. This is useful if: 
+This article explains how to assess on-premises servers with [Azure Migrate: Server Assessment](migrate-services-overview.md#azure-migrate-server-assessment-tool), by importing server metadata using CSV. With this method of assessment, you don't need to set up the Azure Migrate appliance to create an assessment. This is useful if:
 
 - You want to create a quick initial assessment before you deploy the appliance.
 - You can't deploy the Azure Migrate appliance in your organization.
@@ -44,7 +41,7 @@ In this tutorial, you learn how to:
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/free-trial/) before you begin.
 
 
-## Set Azure permissions for Azure Migrate 
+## Set Azure permissions for Azure Migrate
 
 Your Azure account needs permissions to create an Azure Migrate project.
 
@@ -111,7 +108,7 @@ The following table summarizes the file fields to fill in.
 
 **Field name** | **Mandatory** | **Details**
 --- | --- | ---
-**Server name** | Yes | We recommend specifying the FQDN. 
+**Server name** | Yes | We recommend specifying the FQDN.
 **IP address** | No | Server address.
 **Number of cores** | Yes | The number of processor cores allocated to the server.
 **Memory** | Yes | Total RAM (MB) allocated to the server.
@@ -139,7 +136,7 @@ The following table summarizes the file fields to fill in.
 **Virtual machine manager ID** | No | This is the **InstanceUUid** for VMWare vCenter. Not needed for Hyper-V.
 **MAC address**| No | Server MAC address.
 **BIOS ID** | No | Server BIOS ID.
-**Custom server ID**| No | Local unique server IDs on-premises. <br/> Useful for tracking the imported server by local ID. 
+**Custom server ID**| No | Local unique server IDs on-premises. <br/> Useful for tracking the imported server by local ID.
 **Application 1 name** | No | Name of workloads running on the server.<br/> You can add details for more apps by [adding columns](#add-multiple-applications) in the template. You can add up to five applications.
 **Application 1 type** | No | Type of workload running in the server
 **Application 1 version** | No | Version of the workload running on the server.
@@ -157,7 +154,7 @@ Assessment recognizes specific operating system names. Any operating system name
 
 ### Add multiple disks
 
-The template provides default fields for the first disk.  You can add similar columns for up to 8 disks. 
+The template provides default fields for the first disk.  You can add similar columns for up to 8 disks.
 
 For example, to specify all fields for a second disk, add the columns:
 
@@ -194,10 +191,10 @@ After adding information to the CSV template, import the servers into Azure Migr
 
 1. In Azure Migrate > **Discover machines**, browse to the filled out template.
 2. Click **Import**.
-3. The import status is shown. 
+3. The import status is shown.
     - If warnings appear in the status, you can either fix them, or continue without addressing them.
     - Improving server information as suggested in warnings improves assessment accuracy.
-    - To view and fix warnings if they appear, click **Download warning details .CSV**. This downloads the CSV, with warnings added. You can review the warnings, and fix issues as needed. 
+    - To view and fix warnings if they appear, click **Download warning details .CSV**. This downloads the CSV, with warnings added. You can review the warnings, and fix issues as needed.
     If errors appear in the status (the import status is **Failed**), you need to fix these before you can continue with the import. To do this, download the CSV, that now has error details added. Review and address the errors as needed. Then upload the modified file again.
 4. When the import status is **Completed**, the server information is imported.
 
@@ -207,7 +204,7 @@ After adding information to the CSV template, import the servers into Azure Migr
 
 ## Updating server information
 
-You can update a server information by uploading the data for the server again with the same **Server name**. You cannot modify the **Server name** field. 
+You can update a server information by uploading the data for the server again with the same **Server name**. You cannot modify the **Server name** field.
 
 Deleting servers is currently not supported.
 
@@ -302,21 +299,21 @@ This view shows the estimated compute and storage cost of running VMs in Azure.
 
 Name | Name
 --- | ---
-**A - H** | 
+**A - H** |
 Apple Mac OS X 10 | Asianux 3<br/>Asianux 4<br/>Asianux 5
-CentOS<br/>CentOS 4/5 | CoreOS Linux 
-Debian GNU/Linux 4<br/>Debian GNU/Linux 5<br/>Debian GNU/Linux 6<br/>Debian GNU/Linux 7<br/>Debian GNU/Linux 8 | FreeBSD 
-**I - R** | 
+CentOS<br/>CentOS 4/5 | CoreOS Linux
+Debian GNU/Linux 4<br/>Debian GNU/Linux 5<br/>Debian GNU/Linux 6<br/>Debian GNU/Linux 7<br/>Debian GNU/Linux 8 | FreeBSD
+**I - R** |
 IBM OS/2 | MS-DOS |
-Novell NetWare 5<br/>Novell NetWare 6 | Oracle Linux<br/> Oracle Linux 4/5<br/>Oracle Solaris 10<br/> Oracle Solaris 11 
-Red Hat Enterprise Linux 2<br/>Red Hat Enterprise Linux 3<br/>Red Hat Enterprise Linux 4<br/>Red Hat Enterprise Linux 5<br/>Red Hat Enterprise Linux 6<br/>Red Hat Enterprise Linux 7<br/>Red Hat Fedora | 
-**S-T** | 
+Novell NetWare 5<br/>Novell NetWare 6 | Oracle Linux<br/> Oracle Linux 4/5<br/>Oracle Solaris 10<br/> Oracle Solaris 11
+Red Hat Enterprise Linux 2<br/>Red Hat Enterprise Linux 3<br/>Red Hat Enterprise Linux 4<br/>Red Hat Enterprise Linux 5<br/>Red Hat Enterprise Linux 6<br/>Red Hat Enterprise Linux 7<br/>Red Hat Fedora |
+**S-T** |
 SCO OpenServer 5<br/>SCO OpenServer 6<br/>SCO UnixWare 7 | Serenity Systems eComStation 1<br/>Serenity Systems eComStation 2
 Sun Microsystems Solaris 8<br/>Sun Microsystems Solaris 9 | SUSE Linux Enterprise 10<br/> SUSE Linux Enterprise 11<br/>SUSE Linux Enterprise 12<br/>SUSE Linux Enterprise 8/9<br/>SUSE Linux Enterprise 11<br/>SUSE openSUSE
-**U-Z** | 
+**U-Z** |
 Ubuntu Linux | VMware ESXi 4<br/>VMware ESXi 5<br/>VMware ESXi 6
 Windows 10<br/>Windows 2000<br/>Windows 3<br/>Windows 7<br/>Windows 8<br/>Windows 95<br/>Windows 98<br/>Windows NT<br/>Windows Server (R) 2008<br/>Windows Server 2003 | Windows Server 2008<br/>Windows Server 2008 R2<br/>Windows Server 2012<br/>Windows Server 2012 R2<br/>Windows Server 2016<br/>Windows Server 2019<br/>Windows Server Threshold<br/>Windows Vista<br/>Windows Web Server 2008 R2<br/>Windows XP Professional
-    
+
 
 ## Next steps
 
diff --git a/articles/migrate/tutorial-assess-physical.md b/articles/migrate/tutorial-assess-physical.md
@@ -11,10 +11,6 @@ ms.author: raynew
 
 # Assess physical servers with Azure Migrate: Server Assessment
 
-> [!NOTE]
-> If you don't yet see this feature in the Azure Migrate portal, hang on. It will appear over the next week or so.
-
-
 This article shows you how to assess on-premises physical servers, using the Azure Migrate: Server Assessment tool.
 
 [Azure Migrate](migrate-services-overview.md) provides a hub of tools that help you to discover, assess, and migrate apps, infrastructure, and workloads to Microsoft Azure. The hub includes Azure Migrate tools, and third-party independent software vendor (ISV) offerings.
diff --git a/articles/migrate/tutorial-prepare-physical.md b/articles/migrate/tutorial-prepare-physical.md
@@ -14,10 +14,6 @@ ms.custom: mvc
 
 This article describes how to prepare for assessment of on-premises physical servers with [Azure Migrate](migrate-services-overview.md).
 
-
-> [!NOTE]
-> If you don't yet see some of these features in the Azure Migrate portal, hang on. They will appear over the next week or so.
-
 [Azure Migrate](migrate-overview.md) provides a hub of tools that help you to discover, assess, and migrate apps, infrastructure, and workloads to Microsoft Azure. The hub includes Azure Migrate tools, and third-party independent software vendor (ISV) offerings. 
 
 This tutorial is the first in a series that shows you how to assess physical servers with Azure Migrate. In this tutorial, you learn how to:
@@ -40,7 +36,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 
 You need set up permissions for Azure Migrate deployment.
 
-- Permissions for your Azure account to create an Azure Migrate project. 
+- Permissions for your Azure account to create an Azure Migrate project.
 - Permissions for your account to register the Azure Migrate appliance. The appliance is used for Hyper-V discovery and migration. During appliance registration, Azure Migrate creates two Azure Active Directory (Azure AD) apps that uniquely identify the appliance:
     - The first app communicates with Azure Migrate service endpoints.
     - The second app accesses an Azure Key Vault that's created during registration, to store Azure AD app info and appliance configuration settings.
@@ -68,7 +64,7 @@ You can assign permissions for Azure Migrate to create the Azure AD apps creatin
 It's worth noting that:
 
 - The apps don't have any other access permissions on the subscription other than those described above.
-- You only need these permissions when you register a new appliance. You can remove the permissions after the appliance is set up. 
+- You only need these permissions when you register a new appliance. You can remove the permissions after the appliance is set up.
 
 
 #### Grant account permissions
@@ -83,7 +79,7 @@ The tenant/global admin can grant permissions as follows:
 > [!NOTE]
 > This is a default setting that isn't sensitive. [Learn more](https://docs.microsoft.com/azure/active-directory/develop/active-directory-how-applications-are-added#who-has-permission-to-add-applications-to-my-azure-ad-instance).
 
-#### Assign Application Developer role 
+#### Assign Application Developer role
 
 The tenant/global admin can assign the Application Developer role to an account. [Learn more](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal).
 
@@ -122,12 +118,12 @@ Azure Migrate needs permissions to discover on-premises servers.
 ## Next steps
 
 In this tutorial, you:
- 
-> [!div class="checklist"] 
+
+> [!div class="checklist"]
 > * Set up Azure account permissions.
 > * Prepared physical servers for assessment.
 
 Continue to the next tutorial to create an Azure Migrate project, and assess physical servers for migration to Azure
 
-> [!div class="nextstepaction"] 
-> [Assess physical servers](./tutorial-assess-physical.md) 
+> [!div class="nextstepaction"]
+> [Assess physical servers](./tutorial-assess-physical.md)
diff --git a/articles/migrate/whats-new.md b/articles/migrate/whats-new.md
