Merge branch 'MicrosoftDocs:main' into heidist-toc-proto

Author: HeidiSteen

articles/ai-services/speech-service/batch-synthesis.md

@@ -48,7 +48,7 @@ To submit a batch synthesis request, construct the HTTP PUT request path and bod
 - Optionally you can set the `description`, `timeToLiveInHours`, and other properties. For more information, see [batch synthesis properties](batch-synthesis-properties.md).
 
 > [!NOTE]
-> The maximum JSON payload size that will be accepted is 2 megabytes. Each Speech resource can have up to 300 batch synthesis jobs that are running concurrently.
+> The maximum JSON payload size that will be accepted is 2 megabytes.
 
 Set the required `YourSynthesisId` in path. The `YourSynthesisId` have to be unique. It must be 3-64 long, contains only numbers, letters, hyphens, underscores and dots, starts and ends with a letter or number.
 

articles/ai-services/speech-service/bring-your-own-storage-speech-resource.md

@@ -48,12 +48,100 @@ Consider the following rules when planning BYOS-enabled Speech resource configur
 
 ## Create and configure BYOS-enabled Speech resource
 
-This section describes how to create a BYOS enabled Speech resource.
+This section describes how to create a BYOS enabled Speech resource. 
+
 
 ### Request access to BYOS for your Azure subscriptions
 
 You need to request access to BYOS functionality for each of the Azure subscriptions you plan to use. To request access, fill and submit [Cognitive Services & Applied AI Customer Managed Keys and Bring Your Own Storage access request form](https://aka.ms/cogsvc-cmk). Wait for the request to be approved.
 
+### (Optional) Check whether Azure subscription has access to BYOS
+
+You can quickly check whether your Azure subscription has access to BYOS. This check uses [preview features](/azure/azure-resource-manager/management/preview-features) functionality of Azure.
+
+# [Azure portal](#tab/portal)
+
+This functionality isn't available through Azure portal.
+
+> [!NOTE]
+> You may view the list of preview features for a given Azure subscription as explained in [this article](/azure/azure-resource-manager/management/preview-features), however note that not all preview features, including BYOS are visible this way.
+
+# [PowerShell](#tab/powershell)
+
+To check whether an Azure subscription has access to BYOS with PowerShell, we use [Get-AzProviderFeature](/powershell/module/az.resources/get-azproviderfeature) command.
+
+You can [install PowerShell locally](/powershell/azure/install-azure-powershell) or use [Azure Cloud Shell](../../cloud-shell/overview.md).
+
+If you use local installation of PowerShell, connect to your Azure account using `Connect-AzAccount` command before trying the following script.
+
+```azurepowershell
+# Target subscription parameters
+# REPLACE WITH YOUR CONFIGURATION VALUES
+$azureSubscriptionId = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
+
+# Select the right subscription
+Set-AzContext -SubscriptionId $azureSubscriptionId 
+
+# Check whether the Azure subscription has access to BYOS
+Get-AzProviderFeature -ListAvailable -ProviderNamespace "Microsoft.CognitiveServices" | where-object FeatureName -Match byox
+```
+
+If you get the response like this, your subscription has access to BYOS.
+```powershell
+FeatureName ProviderName                RegistrationState
+----------- ------------                -----------------
+byoxPreview Microsoft.CognitiveServices Registered
+```
+
+If you get empty response or `RegistrationState` value is `NotRegistered` then your Azure subscription doesn't have access to BYOS and you need to [request it](#request-access-to-byos-for-your-azure-subscriptions).
+
+# [Azure CLI](#tab/azure-cli)
+
+To check whether an Azure subscription has access to BYOS with Azure CLI, we use [az feature show](/cli/azure/feature) command.
+
+You can [install Azure CLI locally](/cli/azure/install-azure-cli) or use [Azure Cloud Shell](../../cloud-shell/overview.md).
+
+> [!NOTE]
+> The following script doesn't use variables because variable usage differs, depending on the platform where Azure CLI runs. See information on Azure CLI variable usage in [this article](/cli/azure/azure-cli-variables).
+
+If you use local installation of Azure CLI, connect to your Azure account using `az login` command before trying the following script.
+
+```azurecli
+az account set --subscription "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
+
+az feature show --name byoxPreview --namespace  Microsoft.CognitiveServices --output table
+```
+
+If you get the response like this, your subscription has access to BYOS.
+```dos
+Name                                     RegistrationState
+---------------------------------------  -------------------
+Microsoft.CognitiveServices/byoxPreview  Registered
+```
+If you get empty response or `RegistrationState` value is `NotRegistered` then your Azure subscription doesn't have access to BYOS and you need to [request it](#request-access-to-byos-for-your-azure-subscriptions).
+
+> [!Tip]
+> See additional commands related to listing Azure subscription preview features in [this article](/azure/azure-resource-manager/management/preview-features).
+
+# [REST](#tab/rest)
+
+To check through REST API whether an Azure subscription has access to BYOS use [Features - List](/rest/api/resources/features/list) request from Azure Resource Manager REST API.
+
+If your subscription has access to BYOS, the REST response will contain the following element:
+```json
+{
+  "properties": {
+    "state": "Registered"
+  },
+  "id": "/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/providers/Microsoft.Features/providers/Microsoft.CognitiveServices/features/byoxPreview",
+  "type": "Microsoft.Features/providers/features",
+  "name": "Microsoft.CognitiveServices/byoxPreview"
+}
+```
+If the REST response doesn't contain the reference to `byoxPreview` feature or its state is `NotRegistered` then your Azure subscription doesn't have access to BYOS and you need to [request it](#request-access-to-byos-for-your-azure-subscriptions).
+***
+
+
 ### Plan and prepare your Storage account
 
 If you use Azure portal to create a BYOS-enabled Speech resource, an associated Storage account can be created automatically. For all other provisioning methods (Azure CLI, PowerShell, REST API Request) you need to use existing Storage account.

articles/ai-services/speech-service/speech-services-quotas-and-limits.md

@@ -86,10 +86,10 @@ These limits aren't adjustable. For more information on batch synthesis latency,
 
 | Quota | Free (F0) | Standard (S0) |
 |-----|-----|-----|
-|REST API limit | Not available for F0 | 50 requests per 5 seconds |
-| Max JSON payload size to create a synthesis job  | N/A | 500 kilobytes |
-| Concurrent active synthesis jobs | N/A | 200 |
-| Max number of text inputs per synthesis job | N/A | 1000 |
+|REST API limit | Not available for F0 | 100 requests per 10 seconds |
+| Max JSON payload size to create a synthesis job  | N/A | 2 megabytes |
+| Concurrent active synthesis jobs | N/A | No limit |
+| Max number of text inputs per synthesis job | N/A | 10000 |
 |Max time to live for a synthesis job since it being in the final state  | N/A | Up to 31 days (specified using properties) |
 
 #### Custom neural voice - professional

articles/aks/quickstart-event-grid.md

@@ -21,7 +21,7 @@ In this quickstart, you create an AKS cluster and subscribe to AKS events.
 * [Azure CLI][azure-cli-install] or [Azure PowerShell][azure-powershell-install] installed.
 
 > [!NOTE]
-> In case there are issues specifically with EventGrid notifications, as can be seen here [Service Outages](https://azure.status.microsoft/status), please note that AKS operations wont be impacted and they are independent of Event Grid outages. 
+> In case there are issues specifically with EventGrid notifications, as can be seen here [Service Outages](https://azure.status.microsoft/status), please note that AKS operations won't be impacted and they are independent of Event Grid outages. 
 
 ## Create an AKS cluster
 

articles/app-service/environment/version-comparison.md

@@ -2,7 +2,7 @@
 title: 'App Service Environment version comparison'
 description: This article provides an overview of the App Service Environment versions and feature differences between them.
 author: seligj95
-ms.date: 7/24/2023
+ms.date: 4/22/2024
 ms.author: jordanselig
 ms.topic: article
 ---
@@ -65,6 +65,7 @@ App Service Environment v3 runs on the latest [Virtual Machine Scale Sets](../..
 |---------|---------|---------|---------|
 |IP-based Transport Layer Security (TLS) or Secure Sockets Layer (SSL) binding with your apps     |Yes         |Yes         |No         |
 |Custom domain suffix    |Yes (requires SNI based TLS connection)        |Yes (only supported with certain API versions)         |[Yes](how-to-custom-domain-suffix.md)         |
+|Default host name|If you have a custom domain suffix, the default host name includes your custom domain suffix and is in the form *APP-NAME.internal.contoso.com*. |If you have a custom domain suffix, the default host name includes your custom domain suffix and is in the form *APP-NAME.internal.contoso.com*. |The default host name always uses the App Service Environment default domain suffix and is in the form *APP-NAME.ASE-NAME.appserviceenvironment.net*. App Service Environment v3 keeps the default domain suffix when you add a custom domain suffix. If you add a custom domain suffix, the custom domain suffix configuration is under the `customDnsSuffixConfiguration` property. |
 |Support for App Service Managed Certificates   |No         |No         |No        |
 
 ### Backup and restore
@@ -185,4 +186,4 @@ Due to hardware changes between the versions, there are some regions where App S
 > [App Service Environment v3 Networking](networking.md)
 
 > [!div class="nextstepaction"]
-> [Using an App Service Environment v3](using.md)
+> [Using an App Service Environment v3](using.md)

articles/automation/automation-linux-hrw-install.md

@@ -4,7 +4,7 @@ description: This article tells how to install an agent-based  Hybrid Runbook Wo
 services: automation
 ms.subservice: process-automation
 ms.custom: linux-related-content
-ms.date: 09/17/2023
+ms.date: 04/21/2024
 ms.topic: conceptual
 ---
 
@@ -58,9 +58,14 @@ The Hybrid Runbook Worker feature supports the following distributions. All oper
   16.04 LTS | Xenial Xerus
   14.04 LTS | Trusty Tahr
 
+> [!NOTE]
+> Hybrid Worker would follow support timelines of the OS vendor.
+
 > [!IMPORTANT]
 > Before enabling the Update Management feature, which depends on the system Hybrid Runbook Worker role, confirm the distributions it supports [here](update-management/operating-system-requirements.md).
 
+
+
 ### Minimum requirements
 
 The minimum requirements for a Linux system and user Hybrid Runbook Worker are:

articles/automation/automation-windows-hrw-install.md

@@ -3,7 +3,7 @@ title: Deploy an agent-based Windows Hybrid Runbook Worker in Automation
 description: This article tells how to deploy an agent-based Hybrid Runbook Worker that you can use to run runbooks on Windows-based machines in your local datacenter or cloud environment.
 services: automation
 ms.subservice: process-automation
-ms.date: 09/17/2023
+ms.date: 04/21/2024
 ms.topic: conceptual 
 ---
 
@@ -50,6 +50,9 @@ The Hybrid Runbook Worker feature supports the following operating systems:
 * Windows 8 Enterprise and Pro
 * Windows 7 SP1
 
+> [!NOTE]
+> Hybrid Worker would follow support timelines of the OS vendor.
+
 ### Minimum requirements
 
 The minimum requirements for a Windows system and user Hybrid Runbook Worker are:

articles/azure-arc/index.yml

@@ -169,3 +169,7 @@ additionalContent:
         - title: Azure IoT Operations Preview – enabled by Azure Arc
           summary: Azure IoT Operations is a unified data plane for the edge that helps organizations deploy the industrial metaverse.
           url: /azure/iot-operations/
+        # Card
+        - title: Azure Arc site manager (preview)
+          summary: Use Arc sites to represent your on-premises environments and see centralized monitoring information across your edge infrastructure.
+          url: /azure/azure-arc/site-manager/

articles/azure-arc/site-manager/breadcrumb/toc.yml

@@ -0,0 +1,11 @@
+- name: Azure
+  tocHref: /azure
+  topicHref: /azure/index
+  items:
+  - name: Azure Arc
+    tocHref: /azure/azure-arc
+    topicHref: /azure/azure-arc
+    items:
+    - name: Site manager
+      tocHref: /azure/azure-arc/site-manager
+      topicHref: /azure/azure-arc/site-manager

articles/azure-arc/site-manager/faq.md

@@ -0,0 +1,34 @@
+---
+title: Frequently asked questions
+description: "Frequently asked questions to understand and troubleshoot Azure Arc sites and site manager"
+author: kgremban
+ms.author: kgremban
+ms.service: azure-arc
+#ms.subservice: site-manager
+ms.topic: faq #Don't change
+ms.date: 02/16/2024
+ms.custom: references_regions
+
+#customer intent: As a customer, I want answers to questions so that I can answer my own questions.
+
+---
+
+# Frequently asked questions: Azure Arc site manager (preview)
+
+The following are frequently asked questions and answers for Azure Arc site manager.
+
+**Question:** I have resources in the resource group, which aren't yet supported by site manager. Do I need to move them?
+
+**Answer:** Site manager provides status aggregation for only the supported resource types. Resources of other types won't be managed via site manager. They continue to function normally as they would without otherwise.
+
+**Question:** Does site manager have a subscription or fee for usage?
+
+**Answer:** Site manager is free. However, the Azure services that integrated with sites and site manager might have a fee. Additionally, alerts used with site manager via monitor might have fees as well.
+
+**Question:** What regions are currently supported via site manager? What regions of these supported regions aren't fully supported?
+
+**Answer:** Site manager supports resources that exist in [supported regions](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-arc&regions=all), with a few exceptions. For the following regions, connectivity and update status aren't supported for Arc-enabled machines or Arc-enabled Kubernetes clusters:
+
+* Brazil South
+* UAE North
+* South Africa North