Merge pull request #195884 from MicrosoftDocs/main

4/22 AM Publish

Author: huypub

articles/active-directory/develop/publisher-verification-overview.md

@@ -48,6 +48,8 @@ There are a few pre-requisites for publisher verification, some of which will ha
 
 -  An MPN ID for a valid [Microsoft Partner Network](https://partner.microsoft.com/membership) account that has completed the [verification](/partner-center/verification-responses) process. This MPN account must be the [Partner global account (PGA)](/partner-center/account-structure#the-top-level-is-the-partner-global-account-pga) for your organization. 
 
+-  The Azure AD tenant where the app is registered must be associated with the Partner Global account. If it's not the primary tenant associated with the PGA, follow the steps to [set up the MPN partner global account as a multi-tenant account and associate the Azure AD tenant](/partner-center/multi-tenant-account#add-an-azure-ad-tenant-to-your-account). 
+
 -  An app registered in an Azure AD tenant, with a [Publisher Domain](howto-configure-publisher-domain.md) configured.
 
 -  The domain of the email address used during MPN account verification must either match the publisher domain configured on the app or a DNS-verified [custom domain](../fundamentals/add-custom-domain.md) added to the Azure AD tenant. 

articles/aks/http-application-routing.md

@@ -17,6 +17,11 @@ When the add-on is enabled, it creates a DNS Zone in your subscription. For more
 > [!CAUTION]
 > The HTTP application routing add-on is designed to let you quickly create an ingress controller and access your applications. This add-on is not currently designed for use in a production environment and is not recommended for production use. For production-ready ingress deployments that include multiple replicas and TLS support, see [Create an HTTPS ingress controller](./ingress-tls.md).
 
+
+## Limitations
+
+* HTTP application routing doesn't currently work with AKS versions 1.22.6+
+
 ## HTTP routing solution overview
 
 The add-on deploys two components: a [Kubernetes Ingress controller][ingress] and an [External-DNS][external-dns] controller.

articles/azure-cache-for-redis/cache-high-availability.md

@@ -12,7 +12,7 @@ ms.author: franlanglois
 
 As with any cloud systems, unplanned outages can occur that result in a virtual machines (VM) instance, an Availability Zone, or a complete Azure region going down. We recommend customers have a plan in place to handle zone or regional outages.
 
-This article presents the information for customers to create a _business continuity and disaster recovery plan_ for their Azure Cache for Redis, or Azure Cache for Redis Enterprise implementation.
+This article presents the information for customers to create a *business continuity and disaster recovery plan* for their Azure Cache for Redis, or Azure Cache for Redis Enterprise implementation.
 
 Various high availability options are available in the Standard, Premium, and Enterprise tiers:
 
@@ -72,8 +72,8 @@ A zone redundant cache provides automatic failover. When the current primary nod
 
 A cache in either Enterprise tier runs on a Redis Enterprise *cluster*. It always requires an odd number of server nodes to form a quorum. By default, it has three nodes, each hosted on a dedicated VM.
 
-- An Enterprise cache has two same-sized *data nodes* and one smaller *quorum node*. 
-- An Enterprise Flash cache has three same-sized data nodes. 
+- An Enterprise cache has two same-sized *data nodes* and one smaller *quorum node*.
+- An Enterprise Flash cache has three same-sized data nodes.
 
 The Enterprise cluster divides Azure Cache for Redis data into partitions internally. Each partition has a *primary* and at least one *replica*. Each data node holds one or more partitions. The Enterprise cluster ensures that the primary and replica(s) of any partition are never collocated on the same data node. Partitions replicate data asynchronously from primaries to their corresponding replicas.
 
@@ -103,7 +103,7 @@ Consider choosing a geo-redundant storage account to ensure high availability of
 
 Applicable tiers: **Premium**
 
-[Geo-replication](cache-how-to-geo-replication.md) is a mechanism for linking two or more Azure Cache for Redis instances, typically spanning two Azure regions. Geo-replication is designed mainly for disaster recovery. Two Premium tier cache instances are connected through geo-replication in away that provides reads and writes to your primary cache, and that data is replicated to the secondary cache.
+[Geo-replication](cache-how-to-geo-replication.md) is a mechanism for linking two or more Azure Cache for Redis instances, typically spanning two Azure regions. Geo-replication is designed mainly for disaster recovery. Two Premium tier cache instances are connected through geo-replication in a way that provides reads and writes to your primary cache, and that data is replicated to the secondary cache.
 For more information on how to set it up, see [Configure geo-replication for Premium Azure Cache for Redis instances](./cache-how-to-geo-replication.md).
 
 If the region hosting the primary cache goes down, you’ll need to start the failover by: first, unlinking the secondary cache, and then, updating your application to point to the secondary cache for reads and writes.
@@ -137,4 +137,4 @@ Learn more about how to configure Azure Cache for Redis high-availability option
 - [Azure Cache for Redis Premium service tiers](cache-overview.md#service-tiers)
 - [Add replicas to Azure Cache for Redis](cache-how-to-multi-replicas.md)
 - [Enable zone redundancy for Azure Cache for Redis](cache-how-to-zone-redundancy.md)
-- [Set up geo-replication for Azure Cache for Redis](cache-how-to-geo-replication.md)
+- [Set up geo-replication for Azure Cache for Redis](cache-how-to-geo-replication.md)

articles/azure-monitor/containers/container-insights-prometheus-integration.md

@@ -277,11 +277,11 @@ For the following Kubernetes environments:
 - Azure Stack or on-premises
 - Azure Red Hat OpenShift and Red Hat OpenShift version 4.x
 
-run the command `kubectl apply -f <configmap_yaml_file.yaml`. 
+run the command `kubectl apply -f <config3. map_yaml_file.yaml>`. 
 
-For an Azure Red Hat OpenShift v3.x cluster, run the command, `oc edit configmaps container-azm-ms-agentconfig -n openshift-azure-logging` to open the file in your default editor to modify and then save it.
+For an example, run the command, `Example: kubectl apply -f container-azm-ms-agentconfig.yaml` to open the file in your default editor to modify and then save it.  
 
-The configuration change can take a few minutes to finish before taking effect, and all omsagent pods in the cluster will restart. The restart is a rolling restart for all omsagent pods, not all restart at the same time. When the restarts are finished, a message is displayed that's similar to the following and includes the result: `configmap "container-azm-ms-agentconfig" updated`.
+The configuration change can take a few minutes to finish before taking effect, and all omsagent pods in the cluster will restart. The restart is a rolling restart for all omsagent pods, not all restart at the same time. When the restarts are finished, a popup message is displayed that's similar to the following and includes the result: 'configmap "container-azm-ms-agentconfig' created to indicate the configmap resource created.
 
 ## Verify configuration
 

articles/cognitive-services/Speech-Service/speech-services-quotas-and-limits.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: speech-service
 ms.topic: conceptual
-ms.date: 01/24/2022
+ms.date: 04/22/2022
 ms.author: alexeyo
 ---
 
@@ -68,9 +68,9 @@ In the following tables, the parameters without the **Adjustable** row aren't ad
 
 | Quota | Free (F0)<sup>3</sup> | Standard (S0) |
 |--|--|--|
-| **Max number of transactions per second (TPS) per Speech service resource** |  |  |
-| Real-time API. Prebuilt neural voices and custom neural voices. | 20 per 60 seconds | 200<sup>4</sup> |
-| Adjustable | No<sup>4</sup> | Yes<sup>4</sup> |
+| **Max number of transactions per certain time period per Speech service resource** |  |  |
+| Real-time API. Prebuilt neural voices and custom neural voices. | 20 transactions per 60 seconds | 200 transactions per second (TPS) |
+| Adjustable | No<sup>4</sup> | Yes<sup>5</sup> |
 | **HTTP-specific quotas** |  |  |
 | Max audio length produced per request | 10 min | 10 min |
 | Max total number of distinct `<voice>` and `<audio>` tags in SSML | 50 | 50 |

articles/cognitive-services/language-service/concepts/model-lifecycle.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: language-service
 ms.topic: conceptual
-ms.date: 03/15/2022
+ms.date: 04/21/2022
 ms.author: aahi
 ---
 
@@ -58,7 +58,7 @@ Use the table below to find which model versions are supported by each feature.
 | Custom NER                                          | `2021-11-01-preview`                                                |                                    | `2021-11-01-preview`   |
 | Personally Identifiable Information (PII) detection | `2019-10-01`, `2020-02-01`, `2020-04-01`,`2020-07-01`, `2021-01-15` | `2021-01-15`                       |                        |
 | Question answering                                  | `2021-10-01`                                                        | `2021-10-01`                                  |
-| Text Analytics for health                           | `2021-05-15`                                                        | `2021-05-15`                       |                        |
+| Text Analytics for health                           | `2021-05-15`, `2022-03-01`                                                        | `2022-03-01`                       |                        |
 | Key phrase extraction                               | `2019-10-01`, `2020-07-01`, `2021-06-01`                            | `2021-06-01`                       |                        |
 | Text summarization                                  | `2021-08-01`                                                        | `2021-08-01`                       |                        |
 

articles/cosmos-db/mongodb/mongodb-indexing.md

@@ -241,13 +241,11 @@ In the preceding example, omitting the ```"university":1``` clause returns an er
 
 `cannot create unique index over {student_id : 1.0} with shard key pattern { university : 1.0 }`
 
-#### Note
-
-Support for unique index on existing collections with data is available in preview. You can sign up for the feature “Azure Cosmos DB API for MongoDB New Unique Indexes in existing collection” through the [Preview Features blade in the portal](./../access-previews.md).
-
 #### Limitations
 
-On accounts that have continuous backup or synapse link enabled, unique indexes will need to be created while the collection is empty.
+Unique indexes need to be created while the collection is empty. 
+
+Support for unique index on existing collections with data is available in preview for accounts that do not use Synapse Link or Continuous backup. You can sign up for the feature “Azure Cosmos DB API for MongoDB New Unique Indexes in existing collection” through the [Preview Features blade in the portal](./../access-previews.md). 
 
 #### Unique partial indexes
 

articles/data-factory/connector-sharepoint-online-list.md

@@ -7,7 +7,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 04/18/2022
+ms.date: 04/22/2022
 ms.author: jianleishen
 ---
 # Copy data from SharePoint Online List by using Azure Data Factory or Azure Synapse Analytics
@@ -104,7 +104,7 @@ The following sections provide details about properties you can use to define en
 
 ## Linked service properties
 
-The following properties are supported for an SharePoint Online List linked service:
+The following properties are supported for a SharePoint Online List linked service:
 
 | **Property**        | **Description**                                              | **Required** |
 | ------------------- | ------------------------------------------------------------ | ------------ |

articles/frontdoor/front-door-faq.yml

@@ -218,9 +218,12 @@ sections:
       - question: | 
           How does Front Door handle ‘domain fronting’ behavior? 
         answer: |
-          As of April 29, 2022, Microsoft has made a change to the behavior of Azure Front Door Standard/Premium/(classic) and Azure CDN from Microsoft (classic) in alignment with its commitment to stop allowing domain fronting behavior on its platform.  After this date, new Front Door and Azure CDN Standard from Microsoft resources that are created will block any HTTP request that exhibit this behavior.
+          As of April 29, 2022, Microsoft has made a change to the behavior of Azure Front Door Standard/Premium/(classic) and Azure CDN from Microsoft (classic) in alignment with its commitment to stop allowing domain fronting behavior on its platform.  Once blocking domain fronting is enabled, AFD and CDN resources will block any HTTP request that exhibit this behavior.
           If this behavior is enabled for your resource, requests where Host header in HTTP/HTTPS requests doesn't match the original TLS SNI extension used during the TLS negotiation, will be blocked.
-
+          
+          If you wish to block domain fronting for any existing Azure Front Door Standard and Premium, Azure Front Door (classic) and Azure CDN Standard from Microsoft (classic) resources or for new Azure Front Door Standard and Premium, Azure Front Door (classic) and Azure CDN Standard from Microsoft (classic) resources, please create a support request and provide your subscription and 
+          resource information. Upon enabling of blocking domain fronting behavior, Azure Front Door and Azure CDN Standard from Microsoft (classic) resources will block any HTTP request that exhibit this behavior.
+         
           When Front Door blocks a request due to this mismatch: 
           The client will receive a HTTP “421 Misdirected Request” error code response 
           Front Door will log the block in its diagnostic logs under the “Error Info” property with the value “SSLMismatchedSNI” 

articles/purview/.openpublishing.redirection.purview.json

@@ -149,6 +149,11 @@
         "source_path_from_root": "/articles/purview/tutorial-data-owner-policies-resource-group.md",
         "redirect_url": "/azure/purview/how-to-data-owner-policies-resource-group",
         "redirect_document_id": true
+      },
+      {
+        "source_path_from_root": "/articles/purview/how-to-enable-data-use-governance.md",
+        "redirect_url": "/azure/purview/how-to-enable-data-use-management",
+        "redirect_document_id": true
       }
 ]
 }