Merge pull request #232611 from v-ksreedevan/29Mar-CFDateUpdate

v-regandowner · web-flow · commit 2e8f3adc52b9 · 2023-03-31T10:40:57.000-04:00
Content Freshness - Update date of last commit - Mar 2023
diff --git a/articles/migrate/common-questions-discovery-dependency-analysis.md b/articles/migrate/common-questions-discovery-dependency-analysis.md
@@ -5,7 +5,8 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 12/13/2022
+ms.date: 02/28/2023
+ms.custom: engagement-fy23
 ---
 
 # Discovery and dependency analysis - Common questions
diff --git a/articles/migrate/common-questions-server-migration.md b/articles/migrate/common-questions-server-migration.md
@@ -5,7 +5,7 @@ author: piyushdhore-microsoft
 ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: conceptual
-ms.date: 12/12/2022
+ms.date: 03/06/2023
 ms.custom: engagement-fy23
 ---
 
diff --git a/articles/migrate/concepts-azure-sql-assessment-calculation.md b/articles/migrate/concepts-azure-sql-assessment-calculation.md
@@ -4,7 +4,7 @@ description: Learn about Azure SQL assessments in Azure Migrate Discovery and as
 author: rashi-ms
 ms.author: rajosh
 ms.topic: conceptual
-ms.date: 02/24/2023
+ms.date: 03/15/2023
 ms.custom: engagement-fy23
 ---
 
@@ -97,7 +97,7 @@ Azure SQL Database sizing | **Purchase model** | Defaulted to *vCore*.
 Azure SQL Database sizing | **Compute tier** | Defaulted to *Provisioned*.
 High availability and disaster recovery properties | **Disaster recovery region** | Defaulted to the [cross-region replication pair](../reliability/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) of the Target location. In an unlikely event when the chosen Target location doesn't yet have such a pair, the specified Target location itself is chosen as the default disaster recovery region.
 High availability and disaster recovery properties | **Multi-subnet intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you want asynchronous data replication where some replication delays are tolerable. This allows higher durability using geo-redundancy. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you desire the data replication to be synchronous and no data loss due to replication delay is allowable. This setting allows assessment to leverage built-in high availability options in Azure SQL Databases and Azure SQL Managed Instances, and availability zones and zone-redundancy in Azure Virtual Machines to provide higher availability. In the event of failover, no data is lost.  
-High availability and disaster recovery properties | **Internet Access** | Defaulted to Available.<br/><br/> Select **Available** if you allow outbound Internet access from Azure VMs. This allows the use of [Cloud Witness](/azure/azure-sql/virtual-machines/windows/hadr-cluster-quorum-configure-how-to#cloud-witness) which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines. <br/><br/> Select **Not available** if the Azure VMs have no outbound Internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. 
+High availability and disaster recovery properties | **Internet Access** | Defaulted to Available.<br/><br/> Select **Available** if you allow outbound Internet access from Azure VMs. This allows the use of [Cloud Witness](https://learn.microsoft.com/azure/azure-sql/virtual-machines/windows/hadr-cluster-quorum-configure-how-to?view=azuresql&tabs=powershell) which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines. <br/><br/> Select **Not available** if the Azure VMs have no outbound Internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. 
 High availability and disaster recovery properties | **Async commit mode intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you're using asynchronous commit availability mode to enable higher durability for the data without affecting performance. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you're using asynchronous commit data availability mode to improve availability and scale out read traffic. This setting allows assessment to leverage built-in high availability features in Azure SQL Databases, Azure SQL Managed Instances, and Azure Virtual Machines to provide higher availability and scale out.  
 
 [Review the best practices](best-practices-assessment.md) for creating an assessment with Azure Migrate.
@@ -113,7 +113,7 @@ High availability and disaster recovery properties | **Async commit mode intent*
 Readiness checks for different migration strategies: 
 
 #### Recommended deployment, Instances to SQL Server on Azure VM, Instances to Azure SQL MI, Database to Azure SQL DB:
-Azure SQL readiness for SQL instances and databases is based on a feature compatibility check with SQL Server on Azure VM, [Azure SQL Database](/azure/azure-sql/migration-guides/database/sql-server-to-sql-database-assessment-rules), and [Azure SQL Managed Instance](/azure/azure-sql/migration-guides/managed-instance/sql-server-to-sql-managed-instance-assessment-rules):
+Azure SQL readiness for SQL instances and databases is based on a feature compatibility check with SQL Server on Azure VM, [Azure SQL Database](https://learn.microsoft.com/azure/azure-sql/migration-guides/database/sql-server-to-sql-database-assessment-rules?view=azuresql), and [Azure SQL Managed Instance](https://learn.microsoft.com/azure/azure-sql/migration-guides/managed-instance/sql-server-to-sql-managed-instance-assessment-rules?view=azuresql):
 1. The Azure SQL assessment considers the SQL Server instance features that are currently used by the source SQL Server workloads (SQL Agent jobs, linked servers, etc.) and the user databases schemas (tables, views, triggers, stored procedures etc.) to identify compatibility issues.
 1. If there are no compatibility issues found, the instance is marked as **Ready** for the target deployment type (SQL Server on Azure VM or Azure SQL Database or Azure SQL Managed Instance)
 1. If there are non-critical compatibility issues, such as deprecated or unsupported features that don't block the migration to a specific target deployment type, the instance is marked as **Ready** (hyperlinked) with **warning** details and recommended remediation guidance. This includes the situation where the source data has an Always On Availability Group configuration and the required replicas exceed those available with the specific target deployment type. 
diff --git a/articles/migrate/concepts-dependency-visualization.md b/articles/migrate/concepts-dependency-visualization.md
@@ -5,7 +5,7 @@ ms.topic: conceptual
 author: vineetvikram
 ms.author: vivikram
 ms.manager: abhemraj
-ms.date: 12/12/2022
+ms.date: 03/08/2023
 ms.custom: engagement-fy23
 ---
 
diff --git a/articles/migrate/concepts-migration-webapps.md b/articles/migrate/concepts-migration-webapps.md
@@ -5,7 +5,7 @@ author: vineetvikram
 ms.author: vivikram
 ms.service: azure-migrate
 ms.topic: conceptual
-ms.date: 07/14/2022
+ms.date: 02/28/2023
 ms.custom: template-concept, engagement-fy23
 ---
 
diff --git a/articles/migrate/how-to-create-azure-sql-assessment.md b/articles/migrate/how-to-create-azure-sql-assessment.md
@@ -4,7 +4,7 @@ description: Learn how to assess SQL instances for migration to Azure SQL Manage
 author: rashi-ms
 ms.author: rajosh
 ms.topic: tutorial
-ms.date: 02/24/2023
+ms.date: 03/15/2023
 ms.custom: engagement-fy23
 ---
 
@@ -70,7 +70,7 @@ Run an assessment as follows:
    Azure SQL Database sizing | **Compute tier** | Defaulted to *Provisioned*.
    High availability and disaster recovery properties | **Disaster recovery region** | Defaulted to the [cross-region replication pair](../reliability/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) of the Target Location. In the unlikely event that the chosen Target Location doesn't yet have such a pair, the specified Target Location itself is chosen as the default disaster recovery region.
    High availability and disaster recovery properties | **Multi-subnet intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you want asynchronous data replication where some replication delays are tolerable. This allows higher durability using geo-redundancy. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you desire the data replication to be synchronous and no data loss due to replication delay is allowable. This setting allows assessment to leverage built-in high availability options in Azure SQL Databases and Azure SQL Managed Instances, and availability zones and zone-redundancy in Azure Virtual Machines to provide higher availability. In the event of failover, no data is lost.  
-   High availability and disaster recovery properties | **Internet Access** | Defaulted to Available.<br/><br/> Select **Available** if you allow outbound internet access from Azure VMs. This allows the use of [Cloud Witness](/azure/azure-sql/virtual-machines/windows/hadr-cluster-quorum-configure-how-to.md?view=azuresql&tabs=powershell#cloud-witness) which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines. <br/><br/> Select **Not available** if the Azure VMs have no outbound internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. 
+   High availability and disaster recovery properties | **Internet Access** | Defaulted to Available.<br/><br/> Select **Available** if you allow outbound internet access from Azure VMs. This allows the use of [Cloud Witness](https://learn.microsoft.com/azure/azure-sql/virtual-machines/windows/hadr-cluster-quorum-configure-how-to?view=azuresql&tabs=powershell) which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines. <br/><br/> Select **Not available** if the Azure VMs have no outbound internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. 
    High availability and disaster recovery properties | **Async commit mode intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you're using asynchronous commit availability mode to enable higher durability for the data without affecting performance. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you're using asynchronous commit data availability mode to improve availability and scale out read traffic. This setting allows assessment to leverage built-in high availability features in Azure SQL Databases, Azure SQL Managed Instances, and Azure Virtual Machines to provide higher availability and scale out.
 
 1. Select **Save** if you made changes.
diff --git a/articles/migrate/how-to-create-group-machine-dependencies.md b/articles/migrate/how-to-create-group-machine-dependencies.md
@@ -5,7 +5,7 @@ author: rashi-ms
 ms.author: rajosh
 ms.manager: abhemraj
 ms.topic: how-to
-ms.date: 10/05/2021
+ms.date: 03/08/2023
 ms.custom: engagement-fy23
 ---
 
diff --git a/articles/migrate/migrate-support-matrix-hyper-v.md b/articles/migrate/migrate-support-matrix-hyper-v.md
@@ -5,7 +5,8 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 03/03/2023
+ms.date: 03/08/2023
+ms.cutom: engagement-fy23
 ---
 
 # Support matrix for Hyper-V assessment
diff --git a/articles/migrate/migrate-support-matrix-vmware.md b/articles/migrate/migrate-support-matrix-vmware.md
@@ -5,7 +5,8 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 02/24/2023
+ms.date: 03/08/2023
+ms.custom: engagement-fy23
 ---
 
 # Support matrix for VMware discovery 
diff --git a/articles/migrate/migrate-v1.md b/articles/migrate/migrate-v1.md
@@ -5,7 +5,7 @@ author: v-ksreedevan
 ms.author: v-ksreedevan
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 05/02/2022
+ms.date: 03/08/2023
 ms.custom: mvc, engagement-fy23
 ---
 
diff --git a/articles/migrate/onboard-to-azure-arc-with-azure-migrate.md b/articles/migrate/onboard-to-azure-arc-with-azure-migrate.md
@@ -4,7 +4,7 @@ description: Onboard on-premises servers in VMware virtual environment to Azure
 author: vijain
 ms.author: vijain
 ms.topic: how-to
-ms.date: 10/10/2022
+ms.date: 01/31/2023
 ms.custom: engagement-fy23
 ---
 
diff --git a/articles/migrate/troubleshoot-dependencies.md b/articles/migrate/troubleshoot-dependencies.md
@@ -5,7 +5,7 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: troubleshooting
-ms.date: 10/17/2022
+ms.date: 03/08/2023
 ms.custom: engagement-fy23
 ---
 
diff --git a/articles/migrate/troubleshoot-webapps-migration.md b/articles/migrate/troubleshoot-webapps-migration.md
@@ -4,7 +4,7 @@ description: Troubleshoot web apps migration issues
 author: vineetvikram
 ms.author: vivikram
 ms.service: azure-migrate
-ms.date: 12/01/2022
+ms.date: 02/28/2023
 ms.topic: troubleshooting
 ms.custom: engagement-fy23
 ---
diff --git a/articles/migrate/tutorial-assess-sql.md b/articles/migrate/tutorial-assess-sql.md
@@ -4,7 +4,7 @@ description: Learn how to create assessment for Azure SQL in Azure Migrate
 author: rashi-ms
 ms.author: rajosh
 ms.topic: tutorial
-ms.date: 08/05/2022
+ms.date: 03/15/2023
 ms.custom: engagement-fy23
 ---
 
@@ -74,7 +74,7 @@ Run an assessment as follows:
    Azure SQL Database sizing | **Compute tier** | Defaulted to *Provisioned*.
    High availability and disaster recovery properties | **Disaster recovery region** | Defaulted to the [cross-region replication pair](../reliability/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) of the Target Location. In the unlikely event that the chosen Target Location doesn't yet have such a pair, the specified Target Location itself is chosen as the default disaster recovery region.
    High availability and disaster recovery properties | **Multi-subnet intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you want asynchronous data replication where some replication delays are tolerable. This allows higher durability using geo-redundancy. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you desire the data replication to be synchronous and no data loss due to replication delay is allowable. This setting allows assessment to leverage built-in high availability options in Azure SQL Databases and Azure SQL Managed Instances, and availability zones and zone-redundancy in Azure Virtual Machines to provide higher availability. In the event of failover, no data is lost.  
-   High availability and disaster recovery properties | **Internet Access** | Defaulted to Available.<br/><br/> Select **Available** if you allow outbound internet access from Azure VMs. This allows the use of [Cloud Witness](/azure/azure-sql/virtual-machines/windows/hadr-cluster-quorum-configure-how-to#cloud-witness) which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines. <br/><br/> Select **Not available** if the Azure VMs have no outbound internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. 
+   High availability and disaster recovery properties | **Internet Access** | Defaulted to Available.<br/><br/> Select **Available** if you allow outbound internet access from Azure VMs. This allows the use of [Cloud Witness](https://learn.microsoft.com/azure/azure-sql/virtual-machines/windows/hadr-cluster-quorum-configure-how-to?view=azuresql&tabs=powershell) which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines. <br/><br/> Select **Not available** if the Azure VMs have no outbound internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. 
    High availability and disaster recovery properties | **Async commit mode intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you're using asynchronous commit availability mode to enable higher durability for the data without affecting performance. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you're using asynchronous commit data availability mode to improve availability and scale out read traffic. This setting allows assessment to leverage built-in high availability features in Azure SQL Databases, Azure SQL Managed Instances, and Azure Virtual Machines to provide higher availability and scale out.
 
 1. Select **Save** if you made changes.
diff --git a/articles/migrate/tutorial-assess-vmware-azure-vmware-solution.md b/articles/migrate/tutorial-assess-vmware-azure-vmware-solution.md
@@ -5,7 +5,7 @@ author: rashi-ms
 ms.author: rajosh
 ms.manager: abhemraj
 ms.topic: tutorial
-ms.date: 5/2/2022
+ms.date: 03/15/2023
 ms.custom: MVC
 #Customer intent: As a VMware VM admin, I want to assess my VMware VMs in preparation for migration to Azure VMware Solution (AVS)
 ---
@@ -98,7 +98,7 @@ Run an assessment as follows:
    Azure SQL Database sizing | **Compute tier** | Defaulted to *Provisioned*.
    High availability and disaster recovery properties | **Disaster recovery region** | Defaulted to the [cross-region replication pair](../reliability/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) of the Target Location. In the unlikely event that the chosen Target Location doesn't yet have such a pair, the specified Target Location itself is chosen as the default disaster recovery region.
    High availability and disaster recovery properties | **Multi-subnet intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you want asynchronous data replication where some replication delays are tolerable. This allows higher durability using geo-redundancy. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you desire the data replication to be synchronous and no data loss due to replication delay is allowable. This setting allows assessment to leverage built-in high availability options in Azure SQL Databases and Azure SQL Managed Instances, and availability zones and zone-redundancy in Azure Virtual Machines to provide higher availability. In the event of failover, no data is lost.  
-   High availability and disaster recovery properties | **Internet Access** | Defaulted to Available.<br/><br/> Select **Available** if you allow outbound internet access from Azure VMs. This allows the use of [Cloud Witness](/azure/azure-sql/virtual-machines/windows/hadr-cluster-quorum-configure-how-to#cloud-witness) which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines. <br/><br/> Select **Not available** if the Azure VMs have no outbound internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. 
+   High availability and disaster recovery properties | **Internet Access** | Defaulted to Available.<br/><br/> Select **Available** if you allow outbound internet access from Azure VMs. This allows the use of [Cloud Witness](https://learn.microsoft.com/azure/azure-sql/virtual-machines/windows/hadr-cluster-quorum-configure-how-to?view=azuresql&tabs=powershell) which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines. <br/><br/> Select **Not available** if the Azure VMs have no outbound internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. 
    High availability and disaster recovery properties | **Async commit mode intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you're using asynchronous commit availability mode to enable higher durability for the data without affecting performance. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you're using asynchronous commit data availability mode to improve availability and scale out read traffic. This setting allows assessment to leverage built-in high availability features in Azure SQL Databases, Azure SQL Managed Instances, and Azure Virtual Machines to provide higher availability and scale out.
 
 1. Select **Save** if you make changes.
diff --git a/articles/migrate/tutorial-assess-webapps.md b/articles/migrate/tutorial-assess-webapps.md
@@ -4,7 +4,7 @@ description: Learn how to create assessment for Azure App Service in Azure Migra
 author: rashi-ms
 ms.author: rajosh
 ms.topic: tutorial
-ms.date: 06/27/2022
+ms.date: 02/28/2023
 ms.custom: engagement-fy23
 ---
 
diff --git a/articles/migrate/tutorial-modernize-asp-net-aks.md b/articles/migrate/tutorial-modernize-asp-net-aks.md
@@ -5,7 +5,7 @@ author: anraghun
 ms.author: anraghun
 ms.service: azure-migrate
 ms.topic: tutorial
-ms.date: 01/01/2023
+ms.date: 02/28/2023
 ms.custom: template-tutorial
 ---
 
diff --git a/articles/migrate/tutorial-modernize-asp-net-appservice-code.md b/articles/migrate/tutorial-modernize-asp-net-appservice-code.md
@@ -5,7 +5,7 @@ author: vineetvikram
 ms.author: vivikram
 ms.service: azure-migrate
 ms.topic: tutorial
-ms.date: 08/09/2022
+ms.date: 02/28/2023
 ms.custom: template-tutorial
 ---
 
diff --git a/articles/migrate/whats-new.md b/articles/migrate/whats-new.md
@@ -5,7 +5,7 @@ ms.topic: overview
 author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
-ms.date: 02/16/2023
+ms.date: 03/03/2023
 ms.custom: mvc, engagement-fy23
 ---
 
