Merge pull request #260942 from MicrosoftDocs/main

12/12 11:00 AM IST Publish

Author: Saisang

.openpublishing.redirection.json

@@ -3106,8 +3106,8 @@
             "redirect_document_id": false
         },
         {
-            "source_path": "active-directory/authentication/concept-mfa-plan.md",
-            "redirect_url": "active-directory/authentication/howto-mfa-getstarted",
+            "source_path": "articles/active-directory/authentication/concept-mfa-plan.md",
+            "redirect_url": "/entra/identity/authentication/howto-mfa-getstarted",
             "redirect_document_id": false
         },
         {

articles/ai-services/speech-service/pronunciation-assessment-tool.md

@@ -34,9 +34,6 @@ At the bottom of the Assessment result, two overall scores are displayed: Pronun
 
 **Content Score**: This score provides an aggregated assessment of the content of the speech and includes three sub-aspects. This score is only available in the speaking tab for an unscripted assessment.
 
-> [!NOTE]
-> Content score is currently available on the following regions in Speech Studio: `westcentralus`, `eastasia`, `eastus`, `northeurope`, `westeurope`, and `westus2`. All other regions will have Content score available starting from Nov 30, 2023.  
-
 - **Vocabulary score**: Evaluates the speaker's effective usage of words and their appropriateness within the given context to express ideas accurately, as well as the level of lexical complexity.
 - **Grammar score**: Evaluates the correctness of grammar usage and variety of sentence patterns. It considers lexical accuracy, grammatical accuracy, and diversity of sentence structures, providing a more comprehensive evaluation of language proficiency.
 - **Topic score**: Assesses the level of understanding and engagement with the topic discussed in the speech. It evaluates the speaker's ability to effectively express thoughts and ideas related to the given topic.

articles/ai-services/speech-service/regions.md

@@ -32,15 +32,15 @@ The following regions are supported for Speech service features such as speech t
 | ----- | ----- | ----- |
 | Africa | South Africa North | `southafricanorth` <sup>6</sup>|
 | Asia Pacific | East Asia | `eastasia` <sup>5</sup>|
-| Asia Pacific | Southeast Asia | `southeastasia` <sup>1,2,3,4,5,7</sup>|
+| Asia Pacific | Southeast Asia | `southeastasia` <sup>1,2,3,4,5,7,9</sup>|
 | Asia Pacific | Australia East | `australiaeast` <sup>1,2,3,4,7</sup>|
 | Asia Pacific | Central India | `centralindia` <sup>1,2,3,4,5</sup>|
 | Asia Pacific | Japan East | `japaneast` <sup>2,5</sup>|
 | Asia Pacific | Japan West | `japanwest` |
 | Asia Pacific | Korea Central | `koreacentral` <sup>2</sup>|
 | Canada | Canada Central | `canadacentral` <sup>1</sup>|
 | Europe | North Europe | `northeurope` <sup>1,2,4,5,7</sup>|
-| Europe | West Europe | `westeurope` <sup>1,2,3,4,5,7</sup>|
+| Europe | West Europe | `westeurope` <sup>1,2,3,4,5,7,9</sup>|
 | Europe | France Central | `francecentral` |
 | Europe | Germany West Central | `germanywestcentral` |
 | Europe | Norway East | `norwayeast` |
@@ -51,7 +51,7 @@ The following regions are supported for Speech service features such as speech t
 | Middle East | UAE North | `uaenorth` <sup>6</sup>|
 | South America | Brazil South | `brazilsouth` <sup>6</sup>|
 | US | Central US | `centralus` |
-| US | East US | `eastus` <sup>1,2,3,4,5,7</sup>|
+| US | East US | `eastus` <sup>1,2,3,4,5,7,9</sup>|
 | US | East US 2 | `eastus2` <sup>1,2,4,5</sup>|
 | US | North Central US | `northcentralus` <sup>4,6</sup>|
 | US | South Central US | `southcentralus` <sup>1,2,3,4,5,6,7</sup>|
@@ -76,6 +76,8 @@ The following regions are supported for Speech service features such as speech t
 
 <sup>8</sup> The region doesn't support Custom Neural Voice.
 
+<sup>9</sup> The region supports personal voice.
+
 ## Intent recognition
 
 Available regions for intent recognition via the Speech SDK are in the following table.

articles/app-service/troubleshoot-diagnostic-logs.md

@@ -197,17 +197,17 @@ With the new [Azure Monitor integration](https://aka.ms/appsvcblog-azmon), you c
 
 The following table shows the supported log types and descriptions: 
 
-| Log type | Windows | Windows Container | Linux | Linux Container | Description |
-|-|-|-|-|-|-|
-| AppServiceConsoleLogs | Java SE & Tomcat | Yes | Yes | Yes | Standard output and standard error |
-| AppServiceHTTPLogs | Yes | Yes | Yes | Yes | Web server logs |
-| AppServiceEnvironmentPlatformLogs | Yes | N/A | Yes | Yes | App Service Environment: scaling, configuration changes, and status logs|
-| AppServiceAuditLogs | Yes | Yes | Yes | Yes | Login activity via FTP and Kudu |
-| AppServiceFileAuditLogs | Yes | Yes | TBA | TBA | File changes made to the site content; **only available for Premium tier and above** |
-| AppServiceAppLogs | ASP.NET, .NET Core, & Tomcat <sup>1</sup> | ASP.NET & Tomcat <sup>1</sup> | .NET Core, Java, SE & Tomcat Blessed Images <sup>2</sup> | Java SE & Tomcat Blessed Images <sup>2</sup> | Application logs |
-| AppServiceIPSecAuditLogs  | Yes | Yes | Yes | Yes | Requests from IP Rules |
-| AppServicePlatformLogs  | TBA | Yes | Yes | Yes | Container operation logs |
-| AppServiceAntivirusScanAuditLogs <sup>3</sup> | Yes | Yes | Yes | Yes | [Anti-virus scan logs](https://azure.github.io/AppService/2020/12/09/AzMon-AppServiceAntivirusScanAuditLogs.html) using Microsoft Defender for Cloud; **only available for Premium tier** | 
+| Log Name| Log type | Windows | Windows Container | Linux | Linux Container | Description |
+|-|-|-|-|-|-|-|
+| App Service Console Logs | AppServiceConsoleLogs | Java SE & Tomcat | Yes | Yes | Yes | Standard output and standard error |
+| HTTP logs | AppServiceHTTPLogs | Yes | Yes | Yes | Yes | Web server logs |
+| App Service Environment Platform Logs | AppServiceEnvironmentPlatformLogs | Yes | N/A | Yes | Yes | App Service Environment: scaling, configuration changes, and status logs|
+| Access Audit Logs | AppServiceAuditLogs | Yes | Yes | Yes | Yes | Login activity via FTP and Kudu |
+| Site Content Change Audit Logs | AppServiceFileAuditLogs | Yes | Yes | TBA | TBA | File changes made to the site content; **only available for Premium tier and above** |
+| App Service Application Logs | AppServiceAppLogs | ASP.NET, .NET Core, & Tomcat <sup>1</sup> | ASP.NET & Tomcat <sup>1</sup> | .NET Core, Java, SE & Tomcat Blessed Images <sup>2</sup> | Java SE & Tomcat Blessed Images <sup>2</sup> | Application logs |
+| IPSecurity Audit logs | AppServiceIPSecAuditLogs  | Yes | Yes | Yes | Yes | Requests from IP Rules |
+| App Service Platform logs | AppServicePlatformLogs  | TBA | Yes | Yes | Yes | Container operation logs |
+| Report Antivirus Audit Logs | AppServiceAntivirusScanAuditLogs <sup>3</sup> | Yes | Yes | Yes | Yes | [Anti-virus scan logs](https://azure.github.io/AppService/2020/12/09/AzMon-AppServiceAntivirusScanAuditLogs.html) using Microsoft Defender for Cloud; **only available for Premium tier** | 
 
 <sup>1</sup> For Tomcat apps, add `TOMCAT_USE_STARTUP_BAT` to the app settings and set it to `false` or `0`. Need to be on the *latest* Tomcat version and use *java.util.logging*.
 

articles/azure-web-pubsub/howto-web-pubsub-tunnel-tool.md

@@ -0,0 +1,118 @@
+---
+title: Azure Web PubSub local tunnel tool (Preview)
+titleSuffix: Azure Web PubSub Service
+description: This article describes the awps-tunnel local tunnel tool to help improve local development experience.
+author: vicancy
+ms.author: lianwei
+ms.service: azure-web-pubsub
+ms.topic: how-to
+ms.date: 12/12/2023
+---
+
+#  Azure Web PubSub local tunnel tool
+
+Web PubSub local tunnel provides a local development environment for customers to enhance their local development experience. There's no need to use third-party tools to expose local ports anymore, use Web PubSub local tunnel as the tunnel between the Web PubSub service and your local server to keep your local development environment secure and safe.
+
+Web PubSub local tunnel provides:
+* A way to tunnel traffic from Web PubSub to your local server
+* A way to view the end-to-end data flow from your client to Web PubSub through the tunnel and to your local server
+* Provides an embedded upstream server for you to get started
+* Provides a simple client for you to get started with your server development
+
+Benefits:
+* Secured local: no need to expose your local server to public
+* Secured connection: use Microsoft Entra ID and Web PubSub access policy to connect
+* Simple configuration: URL template sets to `tunnel:///<your_server_path>` 
+* Data inspection: vivid view of the data and the workflow
+
+## Prerequisite
+* [Node.js](https://nodejs.org/) version 16 or higher 
+
+## Install
+
+```bash
+npm install -g @azure/web-pubsub-tunnel-tool
+```
+
+## Usage
+
+```
+Usage: awps-tunnel [options] [command]
+
+A local tool to help tunnel Azure Web PubSub traffic to local web app and provide a vivid view to the end to end workflow.
+
+Options:
+  -v, --version   Show the version number.
+  -h, --help      Show help details.
+
+Commands:
+  status          Show the current configuration status.
+  bind [options]  Bind configurations to the tool so that you don't need to specify them every time running the tool.
+  run [options]   Run the tool.
+  help [command]  Display help details for subcommand.
+
+You could also set WebPubSubConnectionString environment variable if you don't want to configure endpoint.
+
+```
+
+## Prepare the credential
+
+Both connection string and Microsoft Entra ID are supported.
+
+### Using connection string
+
+1. In your Web PubSub service portal, copy your connection string from your Web PubSub service portal. 
+
+1. Set the connection string to your local environment variable and start `awps-tunnel`.
+
+# [Linux or macOS](#tab/bash)
+```bash
+export WebPubSubConnectionString="<your connection string>"
+```
+# [Windows](#tab/cmd)
+```cmd
+SET WebPubSubConnectionString=<your connection string>
+```
+
+---
+
+### Using Azure Identity
+
+1. In your Web PubSub service portal, go to Access control tab, and add role `Web PubSub Service Owner` to your identity.
+
+1. In your local terminal, use [Azure CLI](/cli/azure/authenticate-azure-cli) `az login` to sign in to your identity.
+
+1. Alternatively, you could set account information via [defined environment variables](/javascript/api/overview/azure/identity-readme#environment-variables), or use [Managed identity authentication](/entra/identity/managed-identities-azure-resources/overview#which-operations-can-i-perform-on-managed-identities) directly for supported Azure services.
+
+## Run
+1. In your Web PubSub service portal, go to Settings tab, specify the event handler URL template to start with `tunnel:///` to allow tunnel connection.
+
+    :::image type="content" alt-text="Screenshot of setting the upstream URL in hub settings." source="media\howto-web-pubsub-tunnel-tool\hub-settings.png" :::
+
+1. Run the tool with the hub you set before, for example, connect to an endpoint `https://<awps-host-name>.webpubsub.azure.com` with hub `chat`:
+    ```bash
+    awps-tunnel run --hub chat --endpoint https://<awps-host-name>.webpubsub.azure.com
+    ```
+
+    You could also use `awps-tunnel bind --hub chat --endpoint https://<awps-host-name>.webpubsub.azure.com` to save the configuration and then `awps-tunnel run`.
+
+1. You see output like `Open webview at: http://127.0.0.1:4000`, open the link in your browser and you could see the tunnel status and the workflow.
+
+1. Now switch to **Server** tab, and check *Built-in Echo Server* to start a builtin upstream server with code similar to the sample code shown below it.
+
+   :::image type="content" alt-text="Screenshot of starting built-in echo server." source="media\howto-web-pubsub-tunnel-tool\overview-upstream.png" :::
+
+1. Alternatively, you can start your own upstream server at http://localhost:3000. You can also specify option`--upstream http://localhost:<custom-port>` when `awps-tunnel run` or `awps-tunnel bind` to configure your own upstream server at a custom port. For example, run the below code to start this sample [upstream server](https://github.com/Azure/azure-webpubsub/tree/main/tools/awps-tunnel/server/samples/upstream/), when it starts, the upstream serves requests to http://localhost:3000/eventhandler/.
+  
+      ```bash
+      git clone https://github.com/Azure/azure-webpubsub.git
+      cd tools/awps-tunnel/server/samples/upstream
+      npm install
+      npm start
+      ```
+
+1. Now switch to **Client** tab, select `Connect` to start a test WebSocket connection to the Azure Web PubSub service. You would see the traffic goes through Web PubSub to Local Tunnel and finally reaches the upstream server. The tunnel tab provides the details of the request and responses, providing you with a vivid view of what is requesting your upstream server and what is reponding from the upstream server.
+
+   :::image type="content" alt-text="Screenshot of starting the test WebSocket connection and send message." source="media\howto-web-pubsub-tunnel-tool\overview-client.png" :::
+
+   :::image type="content" alt-text="Screenshot of showing the traffic inspection." source="media\howto-web-pubsub-tunnel-tool\overview-tunnel.png" :::

articles/azure-web-pubsub/media/howto-web-pubsub-tunnel-tool/hub-settings.png

@@ -50,6 +50,8 @@
           href: howto-generate-client-access-url.md
         - name: Configure event handler
           href: howto-develop-eventhandler.md
+        - name: Develop with local tunnel tool
+          href: howto-web-pubsub-tunnel-tool.md
         - name: Send client events to Event Hubs
           href: howto-develop-event-listener.md
         - name: Use server SDK with Azure Identity