Merge pull request #206988 from Juliako/patch-18

Create face-limited-access.md

Author: v-dirichards

articles/azure-video-indexer/connect-to-azure.md

@@ -9,6 +9,8 @@ ms.custom: ignite-fall-2021
 
 # Create an Azure Video Indexer account
 
+[!INCLUDE [Gate notice](./includes/face-limited-access.md)]
+
 When creating an Azure Video Indexer account, you can choose a free trial account (where you get a certain number of free indexing minutes) or a paid option (where you're not limited by the quota). With a free trial, Azure Video Indexer provides up to 600 minutes of free indexing to users and up to 2400 minutes of free indexing to users that subscribe to the Azure Video Indexer API on the [developer portal](https://aka.ms/avam-dev-portal). With the paid options, Azure Video Indexer offers two types of accounts: classic accounts(General Availability), and ARM-based accounts(Public Preview). Main difference between the two is account management platform. While classic accounts are built on the API Management, ARM-based accounts management is built on Azure, which enables apply access control to all services with role-based access control (Azure RBAC) natively.
 
 > [!NOTE]

articles/azure-video-indexer/create-account-portal.md

@@ -8,6 +8,8 @@ ms.date: 06/10/2022
 
 # Get started with Azure Video Indexer in Azure portal
 
+[!INCLUDE [Gate notice](./includes/face-limited-access.md)]
+
 This Quickstart walks you through the steps to get started with Azure Video Indexer. You'll create an Azure Video Indexer account and its accompanying resources by using the Azure portal.
 
 To start using Azure Video Indexer, you'll need to create an Azure Video Indexer account. The account needs to be associated with a [Media Services][docs-ms] resource and a [managed identity][docs-uami]. The managed identity will need to have Contributor permissions role on the Media Services.

articles/azure-video-indexer/customize-content-models-overview.md

@@ -8,6 +8,8 @@ ms.author: kumud
 
 # Customizing content models in Azure Video Indexer
 
+[!INCLUDE [Gate notice](./includes/face-limited-access.md)]
+
 Azure Video Indexer allows you to customize some of its models to be adapted to your specific use case. These models include [brands](customize-brands-model-overview.md), [language](customize-language-model-overview.md), and [person](customize-person-model-overview.md). You can easily customize these models using the Azure Video Indexer website or API.
 
 This article gives links to articles that explain the benefits of each type of customization. The article also links to how-to guides that show how you can implement the customization of each model.

articles/azure-video-indexer/customize-person-model-overview.md

@@ -8,6 +8,8 @@ ms.author: kumud
 
 # Customize a Person model in Azure Video Indexer 
 
+[!INCLUDE [Gate notice](./includes/face-limited-access.md)]
+
 Azure Video Indexer supports celebrity recognition in your videos. The celebrity recognition feature covers approximately one million faces based on commonly requested data source such as IMDB, Wikipedia, and top LinkedIn influencers. Faces that are not recognized by Azure Video Indexer are still detected but are left unnamed. Customers can build custom Person models and enable Azure Video Indexer to recognize faces that are not recognized by default. Customers can build these Person models by pairing a person's name with image files of the person's face.  
 
 If your account caters to different use-cases, you can benefit from being able to create multiple Person models per account. For example, if the content in your account is meant to be sorted into different channels, you might want to create a separate Person model for each channel. 

articles/azure-video-indexer/customize-person-model-with-api.md

@@ -10,6 +10,8 @@ ms.author: kumud
 
 # Customize a Person model with the Azure Video Indexer API
 
+[!INCLUDE [Gate notice](./includes/face-limited-access.md)]
+
 Azure Video Indexer supports face detection and celebrity recognition for video content. The celebrity recognition feature covers about one million faces based on commonly requested data source such as IMDB, Wikipedia, and top LinkedIn influencers. Faces that aren't recognized by the celebrity recognition feature are detected but left unnamed. After you upload your video to Azure Video Indexer and get results back, you can go back and name the faces that weren't recognized. Once you label a face with a name, the face and name get added to your account's Person model. Azure Video Indexer will then recognize this face in your future videos and past videos.
 
 You can use the Azure Video Indexer API to edit faces that were detected in a video, as described in this topic. You can also use the Azure Video Indexer website, as described in [Customize Person model using the Azure Video Indexer website](customize-person-model-with-api.md).

articles/azure-video-indexer/customize-person-model-with-website.md

@@ -10,6 +10,8 @@ ms.author: juliako
 
 # Customize a Person model with the Azure Video Indexer website
 
+[!INCLUDE [Gate notice](./includes/face-limited-access.md)]
+
 Azure Video Indexer supports celebrity recognition for video content. The celebrity recognition feature covers approximately one million faces based on commonly requested data source such as IMDB, Wikipedia, and top LinkedIn influencers. For a detailed overview, see [Customize a Person model in Azure Video Indexer](customize-person-model-overview.md).
 
 You can use the Azure Video Indexer website to edit faces that were detected in a video, as described in this article. You can also use the API, as described in [Customize a Person model using APIs](customize-person-model-with-api.md).

articles/azure-video-indexer/deploy-with-arm-template.md

@@ -8,6 +8,8 @@ ms.author: juliako
 
 # Tutorial: Deploy Azure Video Indexer by using an ARM template
 
+[!INCLUDE [Gate notice](./includes/face-limited-access.md)]
+
 In this tutorial, you'll create an Azure Video Indexer account by using the Azure Resource Manager template (ARM template, which is in preview). The resource will be deployed to your subscription and will create the Azure Video Indexer resource based on parameters defined in the *avam.template* file.
 
 > [!NOTE]

articles/azure-video-indexer/includes/face-limited-access.md

@@ -0,0 +1,13 @@
+---
+title: Face gate notice
+titleSuffix: Azure Video Indexer
+services: azure-video-indexer
+manager: femila
+ms.service: azure-video-indexer
+ms.topic: include 
+ms.date: 06/14/2022
+ms.author: juliako
+---
+
+> [!IMPORTANT]
+> Face identification, customization and celebrity recognition features access is limited based on eligibility and usage criteria in order to support our Responsible AI principles. Face identification, customization and celebrity recognition features are only available to Microsoft managed customers and partners. Use the [Face Recognition intake form](https://customervoice.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7en2Ais5pxKtso_Pz4b1_xUQjA5SkYzNDM4TkcwQzNEOE1NVEdKUUlRRCQlQCN0PWcu) to apply for access.

articles/azure-video-indexer/matched-person.md

@@ -8,6 +8,8 @@ ms.author: juliako
 
 # Matched person (preview)
 
+[!INCLUDE [Gate notice](./includes/face-limited-access.md)]
+
 Azure Video Indexer matches observed people that were detected in the video with the corresponding faces ("People" insight). To produce the matching algorithm, the bounding boxes for both the faces and the observed people are assigned spatially along the video. The API returns the confidence level of each matching.
 
 The following are some scenarios that benefit from this feature:
@@ -93,10 +95,10 @@ The following JSON response illustrates what Azure Video Indexer returns when tr
 
 It's important to note the limitations of Mapped person, to avoid or mitigate the effects of miss matches between people or people who have no matches.
 
-**Precondition** for the matching is that the person that showing in the Observed person was detected and can be found in the People insight.  
+**Precondition** for the matching is that the person that showing in the observed faces was detected and can be found in the People insight.  
 **Pose**: The tracks are optimized to handle observed people who most often appear on the front.  
-**Obstructions**: There may be miss matching between persons and observed people where there are obstruction (people or faces overlapping each other).  
-**Spatial allocation per frame**: There may be miss matching where different people appear in the same spatial position relatively to the frame in a short time.
+**Obstructions**: There is no match between faces and observed people where there are obstruction (people or faces overlapping each other).  
+**Spatial allocation per frame**: There is no match where different people appear in the same spatial position relatively to the frame in a short time.
 
 See the limitations of Observed people: [Trace observed people in a video](observed-people-tracing.md)
 

articles/azure-video-indexer/video-indexer-get-started.md

@@ -9,6 +9,8 @@ ms.custom: mode-other
 
 # Quickstart: How to sign up and upload your first video
 
+[!INCLUDE [Gate notice](./includes/face-limited-access.md)]
+
 This getting started quickstart shows how to sign in to the Azure Video Indexer website and how to upload your first video.
 
 When creating an Azure Video Indexer account, you can choose a free trial account (where you get a certain number of free indexing minutes) or a paid option (where you aren't limited by the quota). With free trial, Azure Video Indexer provides up to 600 minutes of free indexing to website users and up to 2400 minutes of free indexing to API users. With paid option, you create an Azure Video Indexer account that is [connected to your Azure subscription and an Azure Media Services account](connect-to-azure.md). You pay for minutes indexed, for more information, see [Media Services pricing](https://azure.microsoft.com/pricing/details/media-services/).