Merge branch 'main' of https://www.github.com/MicrosoftDocs/azure-docs-pr into updateOverview

Author: rboucher

articles/aks/cluster-autoscaler.md

@@ -30,7 +30,7 @@ Both the horizontal pod autoscaler and cluster autoscaler can also decrease the
 The cluster autoscaler may be unable to scale down if pods can't move, such as in the following situations:
 
 * A pod is directly created and isn't backed by a controller object, such as a deployment or replica set.
-* A pod disruption budget (PDB) is too restrictive and doesn't allow the number of pods to be fall below a certain threshold.
+* A pod disruption budget (PDB) is too restrictive and doesn't allow the number of pods to fall below a certain threshold.
 * A pod uses node selectors or anti-affinity that can't be honored if scheduled on a different node.
 
 For more information about how the cluster autoscaler may be unable to scale down, see [What types of pods can prevent the cluster autoscaler from removing a node?][autoscaler-scaledown].

articles/app-service/manage-backup.md

@@ -27,7 +27,7 @@ There are two types of backups in App Service. Automatic backups made for your a
 
 |Feature|Automatic backups | Custom backups |
 |-|-|-|
-| Pricing tiers | **Basic**, **Standard**, **Premium**. | **Basic**, **Standard**, **Premium**, **Isolated**. |
+| Pricing tiers | **Basic**, **Standard**, **Premium**, **Isolated**. | **Basic**, **Standard**, **Premium**, **Isolated**. |
 | Configuration required | No. | Yes. |
 | Backup size | 30 GB. | 10 GB, 4 GB of which can be the linked database. |
 | Linked database | Not backed up. | The following linked databases can be backed up: [SQL Database](/azure/azure-sql/database/), [Azure Database for MySQL](../mysql/index.yml), [Azure Database for PostgreSQL](../postgresql/index.yml), [MySQL in-app](https://azure.microsoft.com/blog/mysql-in-app-preview-app-service/). |

articles/azure-monitor/logs/change-pricing-tier.md

@@ -14,7 +14,7 @@ Each Log Analytics workspace in Azure Monitor can have a different [pricing tier
 ## Permissions required
 To change the pricing tier for a workspace, you must be assigned to one of the following roles: 
 
-- Log Analytics Contributor role
+- Log Analytics Contributor role.
 - A custom role with `Microsoft.OperationalInsights/workspaces/*/write` permissions.
 
 ## Changing pricing tier
@@ -24,7 +24,7 @@ Use the following steps to change the pricing tier of your workspace using the A
 
 1. From the **Log Analytics workspaces** menu, select your workspace, and open **Usage and estimated costs**. This displays a list of each of the pricing tiers available for this workspace.
 
-2. Review the estimated costs for each pricing tier. This estimate assumes that the last 31 days of your usage is typical. In the example below, based on the data patterns from the previous 31 days, this workspace would cost less in the Pay-As-You-Go tier (#1) compared to the 100 GB/day commitment tier (#2).  
+2. Review the estimated costs for each pricing tier. This estimate assumes that the last 31 days of your usage is typical. Choose the tier with the lowest estimated cost.  
 
 :::image type="content" source="media/manage-cost-storage/pricing-tier-estimated-costs.png" alt-text="Pricing tiers":::
 

articles/azure-resource-manager/templates/test-toolkit.md

@@ -2,7 +2,7 @@
 title: ARM template test toolkit
 description: Describes how to run the Azure Resource Manager template (ARM template) test toolkit on your template. The toolkit lets you see if you have implemented recommended practices.
 ms.topic: conceptual
-ms.date: 11/16/2022
+ms.date: 03/21/2023
 ms.author: tomfitz
 author: tfitzmac
 ---
@@ -31,7 +31,7 @@ To learn more about the ARM template test toolkit, and for hands-on guidance, se
 
 1. If you don't already have PowerShell, [install PowerShell on Windows](/powershell/scripting/install/installing-powershell-core-on-windows).
 
-1. [Download the latest .zip file](https://aka.ms/arm-ttk-latest) for the test toolkit and extract it.
+1. [Download the latest .zip file](https://github.com/Azure/arm-ttk/releases) for the test toolkit and extract it.
 
 1. Start PowerShell.
 
@@ -59,7 +59,7 @@ To learn more about the ARM template test toolkit, and for hands-on guidance, se
 
 1. If you don't already have PowerShell, [install PowerShell on Linux](/powershell/scripting/install/installing-powershell-core-on-linux).
 
-1. [Download the latest .zip file](https://aka.ms/arm-ttk-latest) for the test toolkit and extract it.
+1. [Download the latest .zip file](https://github.com/Azure/arm-ttk/releases) for the test toolkit and extract it.
 
 1. Start PowerShell.
 
@@ -97,7 +97,7 @@ To learn more about the ARM template test toolkit, and for hands-on guidance, se
    brew install coreutils
    ```
 
-1. [Download the latest .zip file](https://aka.ms/arm-ttk-latest) for the test toolkit and extract it.
+1. [Download the latest .zip file](https://github.com/Azure/arm-ttk/releases) for the test toolkit and extract it.
 
 1. Start PowerShell.
 

articles/azure-signalr/signalr-resource-faq.yml

@@ -6,7 +6,7 @@ metadata:
   ms.service: signalr
   ms.topic: faq
   ms.custom: devx-track-dotnet
-  ms.date: 11/13/2019
+  ms.date: 03/21/2023
   ms.author: lianwei
 title: Azure SignalR Service FAQ
 summary: |
@@ -93,7 +93,7 @@ sections:
       - question: |
           Where does my data reside?
         answer: |
-          Azure SignalR service works as a data processor service and doesn't store any customer data. Azure SignalR service processes customer data within the region the customer deploys the service instance in. If you use Azure SignalR Service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.
+          Azure SignalR Service does not store any customer data. If you use Azure SignalR Service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.
 
       - question: |
           How do I choose between Azure SignalR service and Azure Web PubSub service?

articles/azure-web-pubsub/resource-faq.md

@@ -5,7 +5,7 @@ author: yjin81
 ms.author: yajin1
 ms.service: azure-web-pubsub
 ms.topic: overview 
-ms.date: 11/11/2021
+ms.date: 03/21/2023
 ---
 
 # Azure Web PubSub service FAQ
@@ -33,4 +33,4 @@ Azure Web PubSub service is more suitable for situations where:
 
 ##  Where does my data reside?
 
-Azure Web PubSub service works as a data processor service and doesn't store any customer data. Azure Web PubSub service processes customer data within the region the customer deploys the service instance in. If you use Azure Web PubSub service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.
+Azure Web PubSub does not store any customer data. If you use Azure Web PubSub service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.

articles/backup/backup-azure-enhanced-soft-delete-about.md

@@ -3,7 +3,7 @@ title: Overview of enhanced soft delete for Azure Backup (preview)
 description: This article gives an overview of enhanced soft delete for Azure Backup.
 ms.topic: conceptual
 ms.custom: references_regions
-ms.date: 03/06/2023
+ms.date: 03/21/2023
 ms.service: backup
 author: jyothisuri
 ms.author: jsuri
@@ -43,7 +43,7 @@ The key benefits of enhanced soft delete are:
 
 ## Supported regions
 
-Enhanced soft delete is currently available in the following regions: East US, West US, West US 2, West Central US, Japan East, Brazil South, Australia East, and North Europe.
+Enhanced soft delete is available in all Azure public regions.
 
 ## Supported scenarios
 

articles/communication-services/concepts/service-limits.md

@@ -129,6 +129,12 @@ Chat messages are stored for 90 days. Submit [a request to Azure Support](../../
 
 ## Voice and video calling
 
+### PSTN Call limitations
+
+| **Name**         | Limit  |
+|--|--|
+|Number of outbound concurrent calls | 2 
+
 ### Call maximum limitations
 
 | **Name**         | Limit  |

articles/cosmos-db/emulator-command-line-parameters.md

@@ -38,7 +38,7 @@ To view the list of parameters, type `Microsoft.Azure.Cosmos.Emulator.exe /?` at
 | `Shutdown` | Shuts down the emulator. | `Microsoft.Azure.Cosmos.Emulator.exe /Shutdown` |
 | `DataPath` | Specifies the path in which to store data files. The default value is `%LocalAppdata%\CosmosDBEmulator`. | `Microsoft.Azure.Cosmos.Emulator.exe /DataPath=E:\SomeDataFolder` |
 | `Port` | Specifies the port number to use for the emulator. The default value is `8081`. | `Microsoft.Azure.Cosmos.Emulator.exe /Port=65000` |
-| `ComputePort` | Specified the port number to use for the compute interop gateway service. The gateway's HTTP endpoint probe port is calculated as `ComputePort + 79`. Hence, `ComputePort` and `ComputePort + 79` must be open and available. The default value is `8900`. | `Microsoft.Azure.Cosmos.Emulator.exe /ComputePort=65100` |
+| `ComputePort` | Specifies the port number to use for the compute interop gateway service. The gateway's HTTP endpoint probe port is calculated as `ComputePort + 79`. Hence, `ComputePort` and `ComputePort + 79` must be open and available. The default value is `8900`. | `Microsoft.Azure.Cosmos.Emulator.exe /ComputePort=65100` |
 | `EnableMongoDbEndpoint=3.2` | Enables API for MongoDB version 3.2. | `Microsoft.Azure.Cosmos.Emulator.exe /EnableMongoDbEndpoint=3.2` |
 | `EnableMongoDbEndpoint=3.6` | Enables API for MongoDB version 3.6. | `Microsoft.Azure.Cosmos.Emulator.exe /EnableMongoDbEndpoint=3.6` |
 | `EnableMongoDbEndpoint=4.0` | Enables API for MongoDB version 4.0. | `Microsoft.Azure.Cosmos.Emulator.exe /EnableMongoDbEndpoint=4.0` |

articles/cosmos-db/mongodb/quickstart-java.md

@@ -26,7 +26,7 @@ In this quickstart, you create and manage an Azure Cosmos DB for API for MongoDB
 
 ## Prerequisites
 - An Azure account with an active subscription. [Create one for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio). Or [try Azure Cosmos DB for free](https://azure.microsoft.com/try/cosmosdb/) without an Azure subscription. You can also use the [Azure Cosmos DB Emulator](https://aka.ms/cosmosdb-emulator) with the connection string `.mongodb://localhost:C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==@localhost:10255/admin?ssl=true`.
-- [Java Development Kit (JDK) version 8](https://www.azul.com/downloads/azure-only/zulu/?&version=java-8-lts&architecture=x86-64-bit&package=jdk). 
+- [Java Development Kit (JDK) version 8](https://adoptium.net/temurin/releases/?version=8). 
 - [Maven](https://maven.apache.org/download.cgi). Or run `apt-get install maven` to install Maven.
 - [Git](https://git-scm.com/downloads). 
 
@@ -112,7 +112,7 @@ Now go back to the Azure portal to get your connection string information and co
 
 ## Run the console app
 
-1. Run `mvn package` in a terminal to install required npm modules
+1. Run `mvn package` in a terminal to install required packages
 
 2. Run `mvn exec:java -D exec.mainClass=GetStarted.Program` in a terminal to start your Java application.