Merge pull request #188303 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit 3a1e3a231833 · 2022-02-11T09:47:19.000-08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/active-directory-domain-services/tutorial-create-replica-set.md b/articles/active-directory-domain-services/tutorial-create-replica-set.md
@@ -103,7 +103,7 @@ The replica set reports as *Provisioning* as deployment continues, as shown in t
 A managed domain is currently limited to four replicas - the initial replica set, and three additional replica sets. If you don't need a replica set anymore, or if you want to create a replica set in another region, you can delete unneeded replica sets.
 
 > [!IMPORTANT]
-> You can't delete the last replica set in a managed domain.
+> You can't delete either the last replica set or the initial replica set in a managed domain.
 
 To delete a replica set, complete the following steps:
 
diff --git a/articles/active-directory/authentication/certificate-based-authentication-faq.yml b/articles/active-directory/authentication/certificate-based-authentication-faq.yml
@@ -46,7 +46,7 @@ sections:
           No, sign-in using a non-UPN value, such as an alternate email, isn't supported now.
           
       - question: |
-          Can I have more than one CertificateDistributionPoint (CDP) for a Certificate Authority (CA)?
+          Can I have more than one CRL Distribution Point (CDP) for a Certificate Authority (CA)?
         answer: |
           No, only one CDP is supported per CA.
 
@@ -72,7 +72,7 @@ sections:
       - question: |
           Is there a limit for CRL size?
         answer: |
-          Today as part of the public preview CRL sizes are limited as follows:
+          Today, as part of the public preview, CRL sizes are limited as follows:
           
           - 20 MB in commercial (Microsoft 365, GCC)
           - 45 MB in US Government (GCC High, Dept. of Defense)
diff --git a/articles/active-directory/authentication/concept-certificate-based-authentication-limitations.md b/articles/active-directory/authentication/concept-certificate-based-authentication-limitations.md
@@ -39,8 +39,8 @@ The following scenarios aren't supported:
 - Public Key Infrastructure for creating client certificates. Customers need to configure their own Public Key Infrastructure (PKI) and provision certificates to their users and devices. 
 - Certificate Authority hints aren't supported, so the list of certificates that appears for users in the UI isn't scoped.
 - Windows login using smart cards on Windows devices.
-- Only one Certificate Distribution Point for a trusted CA is supported.
-- The Certificate Distribution Point can be only HTTP URLs. We don't support Online Certificate Status Protocol (OSCP), or Lightweight Directory Access Protocol (LDAP) URLs.
+- Only one CRL Distribution Point (CDP) for a trusted CA is supported.
+- The CDP can be only HTTP URLs. We don't support Online Certificate Status Protocol (OCSP), or Lightweight Directory Access Protocol (LDAP) URLs.
 - Configuring other certificate-to-user account bindings, such as using the **subject field**, or **keyid** and **issuer**, aren’t available in this release.
 - Currently, password can't be disabled when CBA is enabled and the option to sign in using a password is displayed.
 
diff --git a/articles/active-directory/authentication/concept-certificate-based-authentication.md b/articles/active-directory/authentication/concept-certificate-based-authentication.md
@@ -27,7 +27,7 @@ This feature enables customers to adopt a phishing resistant authentication and
 
 ## What is Azure AD CBA?
 
-Before this feature brought cloud-managed support for CBA to Azure AD, customers had to implement federated certificate-based authentication. Federated CBA requires deploying Active Directory Federation Services (AD FS) to be able to authenticate using X.509 certificates against Azure AD. With Azure AD certificate-based authentication, customers can authenticate directly against Azure AD. AZure AD CBA eliminates the need for federated AD FS, which helps simplify customer environments and reduce costs.
+Before this feature brought cloud-managed support for CBA to Azure AD, customers had to implement federated certificate-based authentication. Federated CBA requires deploying Active Directory Federation Services (AD FS) to be able to authenticate using X.509 certificates against Azure AD. With Azure AD certificate-based authentication, customers can authenticate directly against Azure AD. Azure AD CBA eliminates the need for federated AD FS, which helps simplify customer environments and reduce costs.
 
 The following images show how Azure AD CBA simplifies the customer environment by eliminating federated AD FS. 
 
diff --git a/articles/active-directory/authentication/how-to-certificate-based-authentication.md b/articles/active-directory/authentication/how-to-certificate-based-authentication.md
@@ -54,7 +54,7 @@ Optionally, you can also configure authentication bindings to map certificates t
 
 ## Step 1: Configure the certificate authorities
 
-Only one Certificate Distribution Point (CDP) for a trusted CA is supported. The CDP can only be HTTP URLs. Online Certificate Status Protocol (OCSP) or Lightweight Directory Access Protocol (LDAP) URLs are not supported.
+Only one CRL Distribution Point (CDP) for a trusted CA is supported. The CDP can only be HTTP URLs. Online Certificate Status Protocol (OCSP) or Lightweight Directory Access Protocol (LDAP) URLs are not supported.
 
 [!INCLUDE [Configure certificate authorities](../../../includes/active-directory-authentication-configure-certificate-authorities.md)]
 
diff --git a/articles/applied-ai-services/metrics-advisor/how-tos/anomaly-feedback.md b/articles/applied-ai-services/metrics-advisor/how-tos/anomaly-feedback.md
@@ -63,9 +63,9 @@ As the figure below shows, you could select `ChangePoint` for the feedback Type,
 
 ## Seasonality
 
-For seasonal data, when we perform anomaly detection, one step is to estimate the period(seasonality) of the time series, and apply it to the anomaly detection phase. Sometimes, it's hard to identify a precise period, and the period may also change. An incorrectly defined period may have side effects on your anomaly detection results. You can find the current period from a tooltip, its name is `Min Period`.
+For seasonal data, when we perform anomaly detection, one step is to estimate the period(seasonality) of the time series, and apply it to the anomaly detection phase. Sometimes, it's hard to identify a precise period, and the period may also change. An incorrectly defined period may have side effects on your anomaly detection results. You can find the current period from a tooltip, its name is `Min Period`. `Window` is a recommended window size to detect the last point within the window. `Window` usually is \(`Min Period` &times; 4 \) + 1. 
 
-:::image type="content" source="../media/feedback/min-period.png" alt-text="Tooltip overlay with the words Period and the number seven highlighted in red.":::
+:::image type="content" source="../media/feedback/min-period.png" alt-text="Tooltip overlay with the words Min Period and the number seven highlighted in red.":::
 
 You can provide feedback for period to fix this kind of anomaly detection error. As the figure shows, you can set a period value. The unit `interval` means one granularity. Here zero intervals means the data is non-seasonal. You could also select `AutoDetect` if you want to cancel previous feedback and let the pipeline detect period automatically. 
  
@@ -107,4 +107,4 @@ Another way to view feedback history is from a series. You will see several butt
 ## Next steps
 - [Diagnose an incident](diagnose-an-incident.md).
 - [Configure metrics and fine tune detection configuration](configure-metrics.md)
-- [Configure alerts and get notifications using a hook](../how-tos/alerts.md)
+- [Configure alerts and get notifications using a hook](../how-tos/alerts.md)
diff --git a/articles/cognitive-services/language-service/question-answering/quickstart/sdk.md b/articles/cognitive-services/language-service/question-answering/quickstart/sdk.md
@@ -46,6 +46,7 @@ To learn about automating your question answering pipeline consult the REST API
 
 * [Authoring API reference](/rest/api/cognitiveservices/questionanswering/question-answering-projects)
 * [Authoring API cURL examples](../how-to/authoring.md)
+* [Runtime API reference](/rest/api/cognitiveservices/questionanswering/question-answering)
 
 ## Next steps
 
diff --git a/articles/frontdoor/concept-end-to-end-tls.md b/articles/frontdoor/concept-end-to-end-tls.md
@@ -38,7 +38,7 @@ Certificates from internal CAs or self-signed certificates aren't allowed.
 
 ## Online Certificate Status Protocol (OCSP) stapling
 
-OSCP stapling is supported by default in Azure Front Door and no configuration is required.
+OCSP stapling is supported by default in Azure Front Door and no configuration is required.
 
 ## Backend TLS connection (Azure Front Door to backend)
 
diff --git a/articles/postgresql/concepts-query-performance-insight.md b/articles/postgresql/concepts-query-performance-insight.md
@@ -20,7 +20,7 @@ For Query Performance Insight to function, data must exist in the [Query Store](
 ## Viewing performance insights
 The [Query Performance Insight](concepts-query-performance-insight.md) view in the Azure portal will surface visualizations on key information from Query Store. 
 
-In the portal page of your Azure Database for PostgreSQL server, select **Query performance Insight** under the **Intelligent Performance** section of the menu bar. Displaying the **Query Text is no longer supported**. However, the query text can still be viewed by connecting to azure_sys and querying 'query_store.query_texts_view'.
+In the portal page of your Azure Database for PostgreSQL server, select **Query performance Insight** under the **Intelligent Performance** section of the menu bar. **Query Text is no longer supported** is shown. However, the query text can still be viewed by connecting to azure_sys and querying 'query_store.query_texts_view'.
 
 :::image type="content" source="./media/concepts-query-performance-insight/query-performance-insight-landing-page.png" alt-text="Query Performance Insight long running queries":::
 
diff --git a/articles/postgresql/flexible-server/overview.md b/articles/postgresql/flexible-server/overview.md
@@ -14,8 +14,8 @@ ms.custom: "mvc, references_regions"
 [Azure Database for PostgreSQL](../overview.md) powered by the PostgreSQL community edition is available in three deployment modes:
 
 - [Single Server](../overview-single-server.md)
-- Flexible Server 
-- Hyperscale (Citus)
+- [Flexible Server](./overview.md) 
+- [Hyperscale (Citus)](../hyperscale/overview.md)
 
 In this article, we will provide an overview and introduction to core concepts of flexible server deployment model.
 
diff --git a/articles/service-fabric/service-fabric-cluster-resource-manager-advanced-placement-rules-placement-policies.md b/articles/service-fabric/service-fabric-cluster-resource-manager-advanced-placement-rules-placement-policies.md
@@ -125,6 +125,15 @@ The **AllowMultipleStatelessInstancesOnNode** placement policy allows placement
 
 If you've ever seen a health message such as "`The Load Balancer has detected a Constraint Violation for this Replica:fabric:/<some service name> Secondary Partition <some partition ID> is violating the Constraint: ReplicaExclusion`", then you've hit this condition or something like it. 
 
+To opt in to apply this placement policy on your service, enable the following configurations:
+
+```xml
+<Section Name="Common">
+  <Parameter Name="AllowCreateUpdateMultiInstancePerNodeServices" Value="True" />
+  <Parameter Name="HostReuseModeForExclusiveStateless" Value="1" />
+</Section>
+```
+
 By specifying the `AllowMultipleStatelessInstancesOnNode` policy on the service, InstanceCount can be set beyond the number of nodes in the cluster.
 
 Code:
@@ -140,10 +149,6 @@ PowerShell:
 New-ServiceFabricService -ApplicationName $applicationName -ServiceName $serviceName -ServiceTypeName $serviceTypeName -Stateless –PartitionSchemeSingleton –PlacementPolicy @(“AllowMultipleStatelessInstancesOnNode”) -InstanceCount 10 -ServicePackageActivationMode ExclusiveProcess 
 ```
 
-> [!NOTE]
-> The placement policy is currently in preview and behind the `EnableUnsupportedPreviewFeatures` cluster setting. Since this is a preview feature for now, setting the preview config prevents the cluster from getting upgraded to/from. In other words, you will need to create a new cluster to try out the feature.
->
-
 > [!NOTE]
 > Currently the policy is only supported for Stateless services with ExclusiveProcess [service package activation mode](/dotnet/api/system.fabric.description.servicepackageactivationmode).
 >
