Merge pull request #222228 from MicrosoftDocs/main

Merge main to live, 4 AM

Author: v-ccolin

articles/app-service/environment/migrate.md

@@ -3,7 +3,7 @@ title: Migrate to App Service Environment v3 by using the migration feature
 description: Overview of the migration feature for migration to App Service Environment v3
 author: seligj95
 ms.topic: article
-ms.date: 12/12/2022
+ms.date: 12/21/2022
 ms.author: jordanselig
 ms.custom: references_regions
 ---
@@ -44,6 +44,7 @@ At this time, App Service Environment migrations to v3 using the migration featu
 - Norway West
 - South Central US
 - South India
+- Southeast Asia
 - Switzerland North
 - Switzerland West
 - UAE North

articles/application-gateway/media/tutorial-protect-application-gateway/create-ddos-plan.png

@@ -41,6 +41,8 @@
     href: tutorial-ingress-controller-add-on-new.md
   - name: Ingress Controller add-on for AKS (Brownfield)
     href: tutorial-ingress-controller-add-on-existing.md
+  - name: Deploy Application Gateway with DDoS protection
+    href: tutorial-protect-application-gateway.md
 - name: Samples
   items:
   - name: Azure PowerShell

articles/application-gateway/media/tutorial-protect-application-gateway/enable-ddos-vnet.png

@@ -91,12 +91,9 @@ For stateful alerts, the alert is considered resolved when:
 |Alert type  |The alert is resolved when |
 |---------|---------|
 |Metric alerts|The alert condition isn't met for three consecutive checks.|
-|Log alerts| In log alerts, the alert is resolved at different rates based on the frequency of the alert:<ul> <li>**1 minute**: The alert condition isn't met for 10 minutes.</li> <li>**5-15 minutes**: The alert condition isn't met for three frequency periods.</li> <li>**15 minutes - 11 hours**: The alert condition isn't met for two frequency periods.</li> <li>**11 to 12 hours**: The alert condition isn't met for one frequency period.</li></ul>|
+|Log alerts| A log alert is considered resolved when the condition is not met for a specific time range. The time range differs based on the frequency of the alert:<ul> <li>**1 minute**: The alert condition isn't met for 10 minutes.</li> <li>**5-15 minutes**: The alert condition isn't met for three frequency periods.</li> <li>**15 minutes - 11 hours**: The alert condition isn't met for two frequency periods.</li> <li>**11 to 12 hours**: The alert condition isn't met for one frequency period.</li></ul>|
 
-When the alert is considered resolved, the alert rule sends out a resolved notification using webhooks or email and the monitor state in the Azure portal is set to resolved.
-
-> [!NOTE]
-> Log search alert is resolved after time range that teh alert wasn't met. Threrefore the resolve evaluation window is based on last unhealthy window.  
+When an alert is considered resolved, the alert rule sends out a resolved notification using webhooks or email, and the monitor state in the Azure portal is set to resolved.
 
 ## Manage your alerts programmatically
 

articles/application-gateway/toc.yml

@@ -124,8 +124,8 @@ A log alert rule monitors a resource by using a Log Analytics query to evaluate
 
 The target of the log alert rule can be:
 - A single resource, such as a VM. 
-- Multiple resources of the same type in the same Azure region, such as a resource group. This is currently available for selected resource types.
-- Multiple resources using [cross-resource query](../logs/cross-workspace-query.md#querying-across-log-analytics-workspaces-and-from-application-insights). 
+- A single container of resources, like a resource group or subscription.
+- Multiple resources using [cross-resource query](../logs/cross-workspace-query.md). 
 
 Log alerts can measure two different things, which can be used for different monitoring scenarios:
 - Table rows: The number of rows returned can be used to work with events such as Windows event logs, syslog, application exceptions.

articles/application-gateway/tutorial-protect-application-gateway.md

@@ -2,58 +2,49 @@
 title:  Azure Video Indexer accounts  
 description: This article gives an overview of Azure Video Indexer accounts and provides links to other articles for more details.
 ms.topic: conceptual
-ms.date: 11/19/2022
+ms.date: 12/21/2022
 ms.author: juliako
 ---
 
 # Azure Video Indexer account types
 
 This article gives an overview of Azure Video Indexer accounts types and provides links to other articles for more details.
 
-## A trial account
+## Trial account
 
-The first time you visit the [Azure Video Indexer](https://www.videoindexer.ai/) website, a trial account is automatically created. The trial Azure Video Indexer account has limitation on number of indexing minutes, support, and SLA.
+When starting out with [Azure Video Indexer](https://www.videoindexer.ai/), click **start free** to kick off a quick and easy process of creating a trial account. No Azure subscription is required and this is a great way to explore Azure Video Indexer and try it out with your content. Keep in mind that the trial Azure Video Indexer account has a limitation on the number of indexing minutes, support, and SLA.
 
-With a trial, account Azure Video Indexer provides:
+With a trial account, Azure Video Indexer provides:
 
-* up to 600 minutes of free indexing to the [Azure Video Indexer](https://www.videoindexer.ai/) website 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).
-
-When using the trial account, you don't have to set up an Azure subscription.
+* up to 600 minutes of free indexing to the [Azure Video Indexer](https://www.videoindexer.ai/) website users and
+* up to 2400 minutes of free indexing to users that subscribe to the Azure Video Indexer API on the [developer portal](https://api-portal.videoindexer.ai/).
 
 The trial account option is not available on the Azure Government cloud. For other Azure Government limitations, see [Limitations of Azure Video Indexer on Azure Government](connect-to-azure.md#limitations-of-azure-video-indexer-on-azure-government).
 
-## A paid (unlimited) account
-
-You can later create a paid account where you're not limited by the quota. Two types of paid accounts are available to you: Azure Resource Manager (recommended) and classic. The main difference between the two is account management platform. 
+## Paid (unlimited) account
 
-* ARM-based accounts management is built on Azure, which enables using [Azure RBAC](../role-based-access-control/overview.md) (recommended).
-* Classic accounts are built on the API Management.
+When you have used up the free trial minutes or are ready to start using Video Indexer for production workloads, you can create a regular paid account which doesn't have minute, support, or SLA limitations. Account creation can be performed through the Azure portal (see [Create an account with the Azure portal](create-account-portal.md)) or API (see [Create accounts with API](/rest/api/videoindexer/stable/accounts)).
 
-With the paid option, you pay for indexed minutes, for more information, see [Azure Video Indexer pricing](https://azure.microsoft.com/pricing/details/video-indexer/).
+Azure Video Indexer unlimited accounts are Azure Resource Manager (ARM) based and unlike trial accounts, are created in your Azure subscription. Moving to an unlimited ARM based account unlocks many security and management capabilities, such as [RBAC user management](../role-based-access-control/overview.md), [Azure Monitor integration](../azure-monitor/overview.md), deployment through ARM templates, and much more.
 
-When creating a new paid account, you need to connect the Azure Video Indexer account to your Azure subscription and an Azure Media Services account. 
+Billing is per indexed minute, with the per minute cost determined by the selected preset.  For more information regarding pricing, see [Azure Video Indexer pricing](https://azure.microsoft.com/pricing/details/video-indexer/).
 
 ## Create accounts
 
-> [!NOTE]
-> It is recommended to use Azure Video Indexer ARM-based accounts. 
-    
-* [Create an ARM-based (paid) account in Azure portal](create-account-portal.md). To create an account with an API, see [Accounts](/rest/api/videoindexer/preview/accounts)
+* To create an ARM-based (paid) account with the Azure portal, see [Create accounts with the Azure portal](create-account-portal.md). 
+* To create an account with an API, see [Create accounts](/rest/api/videoindexer/stable/accounts)
 
     > [!TIP]
     > Make sure you are signed in with the correct domain to the [Azure Video Indexer website](https://www.videoindexer.ai/). For details, see [Switch tenants](switch-tenants-portal.md).  
 * [Upgrade a trial account to an ARM-based (paid) account and import your content for free](import-content-from-trial.md).  
-* If you have a classic (paid) account, [connect an existing classic Azure Video Indexer account to an ARM-based account](connect-classic-account-to-arm.md).
-
-   Unless your code or infrastructure prevents you from moving from existing classic accounts, you should start using ARM-based accounts.
+   
+ ## Classic accounts
+ 
+Before ARM based accounts were added to Azure Video Indexer, there was a "classic" account type (where the accounts management plane is built on API Management.) The classic account type is still used by some users.
 
-## To get access to your account
-
-|   | ARM-based |Classic| Trial|
-|---|---|---|---|
-|Get access token | [ARM REST API](https://aka.ms/avam-arm-api) |[Get access token](https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Get-Account-Access-Token)|Same as classic|
-|Share account| [Azure RBAC(role based access control)](../role-based-access-control/overview.md)| [Invite users](restricted-viewer-role.md#share-the-account) |Same as classic|
+* If you are using a classic (paid) account and interested in moving to an ARM-based account, see [connect an existing classic Azure Video Indexer account to an ARM-based account](connect-classic-account-to-arm.md).
+ 
+For more information on the difference between regular unlimited accounts and classic accounts, see [Azure Video Indexer as an Azure resource](https://techcommunity.microsoft.com/t5/ai-applied-ai-blog/azure-video-indexer-is-now-available-as-an-azure-resource/ba-p/2912422).
 
 ## Limited access features
 
@@ -64,5 +55,3 @@ For more information, see [Azure Video Indexer limited access features](limited-
 ## Next steps
 
 Make sure to review [Pricing](https://azure.microsoft.com/pricing/details/video-indexer/).
-
-

articles/azure-monitor/alerts/alerts-overview.md

@@ -2,7 +2,7 @@
 title: Guidance and best practices
 description: Discover the best practices and guidance for backing up cloud and on-premises workload to the cloud
 ms.topic: conceptual
-ms.date: 12/22/2021
+ms.date: 12/22/2022
 ms.reviewer: dapatil
 author: v-amallick
 ms.service: backup
@@ -291,9 +291,9 @@ Governance in Azure is primarily implemented with [Azure Policy](../governance/p
 
 - Whenever new infrastructure is provisioned and new VMs are created, as a backup admin,  you need to ensure their protection. You can easily configure backups for one or two VMs. But it becomes complex when you need to configure hundreds or even thousands of VMs at scale. To simplify the process of configuring backups, Azure Backup provides you a set of built-in Azure Policies to govern your backup estate.  
 
-- **Central Policy**: If your organization has a central backup team that manages backups across application teams, you can use this policy to configure backup to an existing central Recovery Services vault in the same subscription and location as that of the VMs. You can choose to include/exclude VMs that contain a certain tag from the policy scope. 
+- **Auto-enable backup on VMs using Policy (Central backup team model)**: If your organization has a central backup team that manages backups across application teams, you can use this policy to configure backup to an existing central Recovery Services vault in the same subscription and location as that of the VMs. You can choose to include/exclude VMs that contain a certain tag from the policy scope. [Learn more](backup-azure-auto-enable-backup.md#policy-1---configure-backup-on-vms-without-a-given-tag-to-an-existing-recovery-services-vault-in-the-same-location).
 
-- **App Policy**: If you organize applications in dedicated resource groups and want to have them backed-up by the same vault, use this policy to automatically manage this action. You can choose to include/exclude VMs that contain a certain tag from the policy scope. 
+- **Auto-enable backup on VMs using Policy (where backup owned by application teams)**: If you organize applications in dedicated resource groups and want to have them backed-up by the same vault, use this policy to automatically manage this action. You can choose to include/exclude VMs that contain a certain tag from the policy scope. [Learn more](backup-azure-auto-enable-backup.md#policy-3---configure-backup-on-vms-without-a-given-tag-to-a-new-recovery-services-vault-with-a-default-policy).
 
 - **Monitoring Policy**: To generate the Backup Reports for your resources,  enable the diagnostic settings when you create a new vault. Often, adding a diagnostic setting manually per vault can be a cumbersome task. So, you can utilize an Azure built-in policy that configures the diagnostics settings at scale to all vaults in each subscription or resource group, with Log Analytics as the destination. 
 

articles/azure-monitor/alerts/alerts-types.md

@@ -27,7 +27,7 @@ Text-to-speech includes the following features:
 | Feature | Summary | Demo |
 | --- | --- | --- |
 | Prebuilt neural voice (called *Neural* on the [pricing page](https://azure.microsoft.com/pricing/details/cognitive-services/speech-services/)) | Highly natural out-of-the-box voices. Create an Azure account and Speech service subscription, and then use the [Speech SDK](./get-started-text-to-speech.md) or visit the [Speech Studio portal](https://speech.microsoft.com/portal) and select prebuilt neural voices to get started. Check the [pricing details](https://azure.microsoft.com/pricing/details/cognitive-services/speech-services/). | Check the [voice samples](https://azure.microsoft.com/services/cognitive-services/text-to-speech/#overview) and determine the right voice for your business needs. |
-| Custom neural voice (called *Custom Neural* on the [pricing page](https://azure.microsoft.com/pricing/details/cognitive-services/speech-services/)) | Easy-to-use self-service for creating a natural brand voice, with limited access for responsible use. Create an Azure account and Speech service subscription (with the S0 tier), and [apply](https://aka.ms/customneural) to use the custom neural feature. After you've been granted access, visit the [Speech Studio portal](https://speech.microsoft.com/portal) and select **Custom Voice** to get started. Check the [pricing details](https://azure.microsoft.com/pricing/details/cognitive-services/speech-services/). | Check the [voice samples](https://aka.ms/customvoice). |
+| Custom Neural Voice (called *Custom Neural* on the [pricing page](https://azure.microsoft.com/pricing/details/cognitive-services/speech-services/)) | Easy-to-use self-service for creating a natural brand voice, with limited access for responsible use. Create an Azure account and Speech service subscription (with the S0 tier), and [apply](https://aka.ms/customneural) to use the custom neural feature. After you've been granted access, visit the [Speech Studio portal](https://speech.microsoft.com/portal) and select **Custom Voice** to get started. Check the [pricing details](https://azure.microsoft.com/pricing/details/cognitive-services/speech-services/). | Check the [voice samples](https://aka.ms/customvoice). |
 
 ### More about neural text-to-speech features
 
@@ -76,12 +76,13 @@ Sample code for text-to-speech is available on GitHub. These samples cover text-
 * [Text-to-speech samples (SDK)](https://github.com/Azure-Samples/cognitive-services-speech-sdk)
 * [Text-to-speech samples (REST)](https://github.com/Azure-Samples/Cognitive-Speech-TTS)
 
-## Custom neural voice
+## Custom Neural Voice
 
-In addition to prebuilt neural voices, you can create and fine-tune custom neural voices that are unique to your product or brand. All it takes to get started is a handful of audio files and the associated transcriptions. For more information, see [Get started with custom neural voice](how-to-custom-voice.md).
+In addition to prebuilt neural voices, you can create and fine-tune custom neural voices that are unique to your product or brand. All it takes to get started is a handful of audio files and the associated transcriptions. For more information, see [Get started with Custom Neural Voice](how-to-custom-voice.md).
 
 ## Pricing note
 
+### Billable characters
 When you use the text-to-speech feature, you're billed for each character that's converted to speech, including punctuation. Although the SSML document itself is not billable, optional elements that are used to adjust how the text is converted to speech, like phonemes and pitch, are counted as billable characters. Here's a list of what's billable:
 
 * Text passed to the text-to-speech feature in the SSML body of the request
@@ -94,6 +95,15 @@ For detailed information, see [Speech service pricing](https://azure.microsoft.c
 > [!IMPORTANT]
 > Each Chinese character is counted as two characters for billing, including kanji used in Japanese, hanja used in Korean, or hanzi used in other languages.  
 
+### Model training and hosting time for Custom Neural Voice
+
+Custom Neural Voice training and hosting are both calculated by hour and billed per second. For the billing unit price, see [Speech service pricing](https://azure.microsoft.com/pricing/details/cognitive-services/speech-services/).
+
+Custom Neural Voice (CNV) training time is measured by ‘compute hour’ (a unit to measure machine running time). Typically, when training a voice model, two computing tasks are running in parallel. So, the calculated compute hours will be longer than the actual training time. On average, it takes less than one compute hour to train a CNV Lite voice; while for CNV Pro, it usually takes 20 to 40 compute hours to train a single-style voice, and around 90 compute hours to train a multi-style voice. The CNV training time is billed with a cap of 96 compute hours. So in the case that a voice model is trained in 98 compute hours, you will only be charged with 96 compute hours. 
+
+Custom Neural Voice (CNV) endpoint hosting is measured by the actual time (hour). The hosting time (hours) for each endpoint is calculated at 00:00 UTC every day for the previous 24 hours. For example, if the endpoint has been active for 24 hours on day one, it will be billed for 24 hours at 00:00 UTC the second day. If the endpoint is newly created or has been suspended during the day, it will be billed for its acumulated running time until 00:00 UTC the second day. If the endpoint is not currently hosted, it will not be billed. In addition to the daily calculation at 00:00 UTC each day, the billing is also triggered immediately when an endpoint is deleted or suspended. For example, for an endpoint created at 08:00 UTC on December 1, the hosting hour will be calculated to 16 hours at 00:00 UTC on December 2 and 24 hours at 00:00 UTC on December 3. If the user suspends hosting the endpoint at 16:00 UTC on December 3, the duration (16 hours) from 00:00 to 16:00 UTC on December 3 will be calculated for billing.
+
+
 ## Reference docs
 
 * [Speech SDK](speech-sdk.md)