Merge pull request #211459 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/saas-apps/confluencemicrosoft-tutorial.md

@@ -57,7 +57,7 @@ As of now, following versions of Confluence are supported:
 
 - Confluence: 5.0 to 5.10
 - Confluence: 6.0.1 to 6.15.9
-- Confluence: 7.0.1 to 7.17.0
+- Confluence: 7.0.1 to 7.19.0
 
 > [!NOTE]
 > Please note that our Confluence Plugin also works on Ubuntu Version 16.04

articles/active-directory/saas-apps/ms-confluence-jira-plugin-adminguide.md

@@ -64,7 +64,7 @@ The plug-in supports the following versions of Jira and Confluence:
 * JIRA also supports 5.2. For more details, click [Microsoft Azure Active Directory single sign-on for JIRA 5.2](./jira52microsoft-tutorial.md)
 * Confluence: 5.0 to 5.10
 * Confluence: 6.0.1 to 6.15.9
-* Confluence: 7.0.1 to 7.17.0
+* Confluence: 7.0.1 to 7.19.0
 
 ## Installation
 
@@ -171,7 +171,7 @@ The plug-in supports these versions:
 * JIRA also supports 5.2. For more details, click [Microsoft Azure Active Directory single sign-on for JIRA 5.2](./jira52microsoft-tutorial.md)
 * Confluence: 5.0 to 5.10
 * Confluence: 6.0.1 to 6.15.9
-* Confluence: 7.0.1 to 7.17.0
+* Confluence: 7.0.1 to 7.19.0
 
 ### Is the plug-in free or paid?
 

articles/azure-arc/data/plan-azure-arc-data-services.md

@@ -26,6 +26,12 @@ In order to experience Azure Arc-enabled data services, you'll need to complete
    The details in this article will guide your plan.
 
 1. [Install client tools](install-client-tools.md).
+
+1. Register the Microsoft.AzureArcData provider for the subscription where the Azure Arc-enabled data services will be deployed, as follows:
+   ```console
+   az provider register --namespace Microsoft.AzureArcData
+   ```  
+
 1. Access a Kubernetes cluster.
 
    For demonstration, testing, and validation purposes, you can use an Azure Kubernetes Service cluster. To create a cluster, follow the instructions at [Quickstart: Deploy Azure Arc-enabled data services - directly connected mode - Azure portal](create-complete-managed-instance-directly-connected.md) to walk through the entire process.
@@ -62,6 +68,7 @@ Verify that:
    kubectl cluster-info
    ```  
 - You have an Azure subscription that resources such as an Azure Arc data controller, Azure Arc-enabled SQL managed instance, or Azure Arc-enabled PostgreSQL server will be projected and billed to.
+- The Microsoft.AzureArcData provider is registered for the subscription where the Azure Arc-enabled data services will be deployed.
 
 After you're prepared the infrastructure, deploy Azure Arc-enabled data services in the following way:
 1. Create an Azure Arc-enabled data controller on one of the validated distributions of a Kubernetes cluster.

articles/azure-arc/kubernetes/private-link.md

@@ -132,10 +132,6 @@ The Private Endpoint on your virtual network allows it to reach Azure Arc-enable
     1. Let validation pass.
     1. Select **Create**.
 
-    :::image type="content" source="media/private-link/create-private-endpoint-2.png" alt-text="Screenshot of the Configuration step to create a private endpoint in the Azure portal.":::
-
-    > [!NOTE]
-    > If you choose **No** and prefer to manage DNS records manually, first complete setting up your Private Link, including this private endpoint and the Private Scope configuration. Next, configure your DNS according to the instructions in [Azure Private Endpoint DNS configuration](/azure/private-link/private-endpoint-dns). Make sure not to create empty records as preparation for your Private Link setup. The DNS records you create can override existing settings and impact your connectivity with Arc-enabled Kubernetes clusters.
 
 ## Configure on-premises DNS forwarding
 

articles/azure-monitor/alerts/proactive-email-notification.md

@@ -8,7 +8,7 @@ ms.reviewer: yagil
 # Smart Detection e-mail notification change
 
 >[!NOTE]
->You can migrate your Application Insight resources to alerts-bases smart detection (preview). The migration creates alert rules for the different smart detection modules. Once created, you can manage and configure these rules just like any other Azure Monitor alert rules. You can also configure action groups for these rules, thus enabling multiple methods of taking actions or triggering notification on new detections.
+>You can migrate your Application Insight resources to alerts-based smart detection (preview). The migration creates alert rules for the different smart detection modules. Once created, you can manage and configure these rules just like any other Azure Monitor alert rules. You can also configure action groups for these rules, thus enabling multiple methods of taking actions or triggering notification on new detections.
 >
 > See [Smart Detection Alerts migration](./alerts-smart-detections-migration.md) for more details on the migration process and the behavior of smart detection after the migration.