Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into remUni

Author: roygara

articles/active-directory-domain-services/tutorial-create-replica-set.md

@@ -111,6 +111,7 @@ To delete a replica set, complete the following steps:
 1. Choose your managed domain, such as *aaddscontoso.com*.
 1. On the left-hand side, select **Replica sets**. From the list of replica sets, select the **...** context menu next to the replica set you want to delete.
 1. Select **Delete** from the context menu, then confirm you want to delete the replica set.
+1. In the Azure ADDS management VM, access the DNS console and manually delete DNS records for the domain controllers from the deleted replica set.
 
 > [!NOTE]
 > Replica set deletion may be a time-consuming operation.

articles/active-directory/develop/scenario-web-app-sign-user-app-configuration.md

@@ -307,9 +307,6 @@ In the code above:
 
 You can find more details about how Microsoft.Identity.Web enables you to create web apps in <https://aka.ms/ms-id-web/webapp>
 
-> [!WARNING]
-> Currently, Microsoft.Identity.Web does not support the scenario of **Individual User Accounts** (storing user accounts in-app) when using Azure AD as and external login provider. For details, see: [AzureAD/microsoft-identity-web#133](https://github.com/AzureAD/microsoft-identity-web/issues/133)
-
 # [ASP.NET](#tab/aspnet)
 
 The code related to authentication in an ASP.NET web app and web APIs is located in the [App_Start/Startup.Auth.cs](https://github.com/Azure-Samples/ms-identity-aspnet-webapp-openidconnect/blob/a2da310539aa613b77da1f9e1c17585311ab22b7/WebApp/App_Start/Startup.Auth.cs#L17-L61) file.

articles/active-directory/reports-monitoring/howto-download-logs.md

@@ -12,7 +12,7 @@ ms.service: active-directory
 ms.topic: how-to
 ms.workload: identity
 ms.subservice: report-monitor
-ms.date: 05/14/2021
+ms.date: 02/25/2022
 ms.author: markvi
 ms.reviewer: besiler 
 
@@ -39,8 +39,6 @@ This article explains how to download activity logs in Azure AD.
 
 - By downloading the logs, you can control for how long logs are stored. 
 
-- You can download up to 250 000 records. If you want to download more data, use the reporting API.
-
 - Your download is based on the filter you have set. 
 
 - Azure AD supports the following formats for your download:
@@ -51,6 +49,7 @@ This article explains how to download activity logs in Azure AD.
 
 - The timestamps in the downloaded files are always based on UTC.
 
+- For large data sets (> 250 000 records), you should use the reporting API to download the data.
 
 
 ## What license do you need?

articles/aks/private-clusters.md

@@ -97,11 +97,6 @@ The following parameters can be leveraged to configure Private DNS Zone.
 ```azurecli-interactive
 az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <ResourceId> --private-dns-zone [system|none]
 ```
-### Create a private AKS cluster with a BYO Private DNS SubZone
-
-Prerequisites:
-
-* Azure CLI >= 2.32.0 or later.
 
 ### Create a private AKS cluster with Custom Private DNS Zone or Private DNS SubZone
 

articles/automation/automation-solution-vm-management.md

@@ -15,7 +15,7 @@ The Start/Stop VMs during off-hours feature start or stops enabled Azure VMs. It
 > [!NOTE]
 > Before you install this version (v1), we would like you to know about the [next version](../azure-functions/start-stop-vms/overview.md), which is in preview right now. This new version (v2) offers all the same functionality as this one, but is designed to take advantage of newer technology in Azure. It adds some of the commonly requested features from customers, such as multi-subscription support from a single Start/Stop instance. 
 >
-> Start/Stop VMs during off-hours (v1) will deprecate on 5/21/2022. 
+> Start/Stop VMs during off-hours (v1) will be deprecated soon and the date will be announced once V2 moves to general availability (GA). 
 
 This feature uses [Start-AzVm](/powershell/module/az.compute/start-azvm) cmdlet to start VMs. It uses [Stop-AzVM](/powershell/module/az.compute/stop-azvm) for stopping VMs.
 

articles/azure-arc/data/managed-instance-high-availability.md

@@ -72,7 +72,7 @@ After all containers within the pod have recovered, you can connect to the manag
 
 ## High availability in Business Critical service tier
 
-In the Business Critical service tier, in addition to what is natively provided by Kubernetes orchestration, there is a new technology called Contained availability group that provides higher levels of availability. Azure Arc-enabled SQL managed instance deployed with `Business Critical` service tier can be deployed with either 2 or 3 replicas. These replicas are always kept in sync with each other. Contained availability group is built on SQL Server Always On availability groups. With contained availability groups, any pod crashes or node failures are transparent to the application as there is at least one other pod that has the SQL managed instance that has all the data from the primary and ready to take on connections.  
+In the Business Critical service tier, in addition to what is natively provided by Kubernetes orchestration, Azure SQL Managed Instance for Azure Arc provides a contained availability group. The contained availability group is built on SQL Server Always On technology. It provides higher levels of availability. Azure Arc-enabled SQL managed instance deployed with *Business Critical* service tier can be deployed with either 2 or 3 replicas. These replicas are always kept in sync with each other. With contained availability groups, any pod crashes or node failures are transparent to the application as there is at least one other pod that has the instance that has all the data from the primary and is ready to take on connections.  
 
 ## Contained availability groups
 
@@ -241,11 +241,14 @@ Additional steps are required to restore a database into an availability group.
 
 1. Expose the primary instance external endpoint by creating a new Kubernetes service.
 
-    Determine the pod that hosts the primary replica by connecting to the managed instance and run:
+    Determine the pod that hosts the primary replica. Connect to the managed instance and run:
 
     ```sql
     SELECT @@SERVERNAME
     ```
+
+    The query returns the pod that hosts the primary replica.
+
     Create the Kubernetes service to the primary instance by running the command below if your Kubernetes cluster uses nodePort services. Replace `podName` with the name of the server returned at previous step, `serviceName` with the preferred name for the Kubernetes service created.
 
     ```console
@@ -269,6 +272,7 @@ Additional steps are required to restore a database into an availability group.
     ```console
     kubectl get services -n <namespaceName>
     ```
+
 2. Restore the database to the primary instance endpoint.
 
     Add the database backup file into the primary instance container.
@@ -326,7 +330,7 @@ Additional steps are required to restore a database into an availability group.
     ```
 
 > [!IMPORTANT]
-> As a best practice, you should cleanup by deleting the Kubernetes service created above by running this command:
+> As a best practice, you should delete the Kubernetes service created above by running this command:
 >
 >```console
 >kubectl delete svc sql2-0-p -n arc

articles/azure-arc/data/release-notes.md

@@ -7,7 +7,7 @@ ms.reviewer: mikeray
 services: azure-arc
 ms.service: azure-arc
 ms.subservice: azure-arc-data
-ms.date: 01/27/2022
+ms.date: 02/25/2022
 ms.topic: conceptual
 ms.custom: references_regions, devx-track-azurecli
 # Customer intent: As a data professional, I want to understand why my solutions would benefit from running with Azure Arc-enabled data services so that I can leverage the capability of the feature.
@@ -17,10 +17,47 @@ ms.custom: references_regions, devx-track-azurecli
 
 This article highlights capabilities, features, and enhancements recently released or improved for Azure Arc-enabled data services.
 
+## February 2022
+
+This release is published February 25, 2022.
+
+### Image tag
+
+`v1.4.0_2022-02-25`
+
+For complete release version information, see [Version log](version-log.md).
+
+### SQL Managed Instance
+
+- Support for readable secondary replicas:
+    - To set readable secondary replicas use `--readable-secondaries` when you create or update an Arc-enabled SQL Managed Instance deployment. 
+    - Set `--readable secondaries` to any value between 0 and the number of replicas minus 1.
+    - `--readable-secondaries` only applies to Business Critical tier. 
+- Automatic backups are taken on the primary instance in a Business Critical service tier when there are multiple replicas. When a failover happens, backups move to the new primary. 
+- RWX capable storage class is required for backups, for both General Purpose and Business Critical service tiers.
+- Billing support when using multiple read replicas.
+
+For additional information about service tiers, see [High Availability with Azure Arc-enabled SQL Managed Instance (preview)](managed-instance-high-availability.md).
+
+### User experience improvements
+
+The following improvements are available in [Azure Data Studio](/sql/azure-data-studio/download-azure-data-studio).
+
+- Azure Arc and Azure CLI extensions now generally available. 
+- Changed edit commands for SQL Managed Instance for Azure Arc dashboard to use `update`, reflecting Azure CLI changes. This works in indirect or direct mode. 
+- Data controller deployment wizard step for connectivity mode is now earlier in the process.
+- Removed an extra backups field in SQL MI deployment wizard.
+
 ## January 2022
 
 This release is published January 27, 2022.
 
+### Image tag
+
+`v1.3.0_2022-01-27`
+
+For complete release version information, see [Version log](version-log.md).
+
 ### Data controller
 
 - Initiate an upgrade of the data controller from the portal in the direct connected mode

articles/azure-arc/data/version-log.md

@@ -7,7 +7,7 @@ ms.reviewer: mikeray
 services: azure-arc
 ms.service: azure-arc
 ms.subservice: azure-arc-data
-ms.date: 12/16/2021
+ms.date: 02/25/2022
 ms.topic: conceptual
 # Customer intent: As a data professional, I want to understand what versions of components align with specific releases.
 ---
@@ -16,6 +16,17 @@ ms.topic: conceptual
 
 This article identifies the component versions with each release of Azure Arc-enabled data services.
 
+### February 25, 2022
+
+|Component  |Value  |
+|--------------------------------------------------------|---------|
+|Container images tag |`v1.4.0_2022-02-25`
+|CRD names and versions	|`datacontrollers.arcdata.microsoft.com`: v1beta1, v1, v2, v3</br>`exporttasks.tasks.arcdata.microsoft.com`: v1beta1, v1, v2</br>`kafkas.arcdata.microsoft.com`: v1beta1</br>`monitors.arcdata.microsoft.com`: v1beta1, v1, v2</br>`sqlmanagedinstances.sql.arcdata.microsoft.com`: v1beta1, v1, v2, v3, v4</br>`postgresqls.arcdata.microsoft.com`: v1beta1, v1beta2</br>`sqlmanagedinstancerestoretasks.tasks.sql.arcdata.microsoft.com`: v1beta1, v1</br>`dags.sql.arcdata.microsoft.com`: v1beta1, v2beta2</br>`activedirectoryconnectors.arcdata.microsoft.com`: v1beta1|
+|ARM API version|2021-11-01|
+|`arcdata` Azure CLI extension version|	1.2.1|
+|Arc enabled Kubernetes helm chart extension version|1.1.18791000|
+|Arc Data extension for Azure Data Studio|1.0|
+
 ### January 27, 2022
 
 |Component  |Value  |

articles/azure-monitor/essentials/data-collection-rule-overview.md

@@ -12,9 +12,9 @@ ms.date: 02/21/2022
 ## Types of data collection rules
 There are currently two types of data collection rule in Azure Monitor:
 
-- **Standard DCR**. Used with different workflows that send data to Azure Monitor. Workflows currently supported are [Azure Monitor agent](../agents/azure-monitor-agent-overview.md) and [custom logs](../logs/custom-logs-overview.md).
+- **Standard DCR**. Used with different workflows that send data to Azure Monitor. Workflows currently supported are [Azure Monitor agent](../agents/azure-monitor-agent-overview.md) and [custom logs (preview)](../logs/custom-logs-overview.md).
 
-- **Workspace transformation DCR**. Used with a Log Analytics workspace to apply transformations to workflows that don't currently support DCRs.
+- **Workspace transformation DCR)**. Used with a Log Analytics workspace to apply [ingestion-time transformations (preview)](../logs/ingestion-time-transformations.md) to workflows that don't currently support DCRs.
 
 ## Structure of a data collection rule
 Data collection rules are formatted in JSON. While you may not need to interact with them directly, there are scenarios where you may need to directly edit a data collection rule. See [Data collection rule structure](data-collection-rule-structure.md) for a description of this structure and different elements.

articles/azure-monitor/insights/solution-targeting.md

@@ -9,6 +9,10 @@ ms.date: 04/27/2017
 ---
 
 # Targeting monitoring solutions in Azure Monitor (Preview)
+
+> [!IMPORTANT]
+> This feature has been deprecated as the Log Analytics agent is being replaced with the Azure Monitor agent and solutions in Azure Monitor are being replaced with insights. You can continue to use it if you already have it configured, but it's being removed from regions where it is not already being used. The feature will longer be supported after August 31, 2024. 
+
 When you add a monitoring solution to your subscription, it's automatically deployed by default to all Windows and Linux agents connected to your Log Analytics workspace.  You may want to manage your costs and limit the amount of data collected for a solution by limiting it to a particular set of agents.  This article describes how to use **Solution Targeting** which is a feature that allows you to apply a scope to your solutions.
 
 [!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-log-analytics-rebrand.md)]