Merge pull request #271569 from MicrosoftDocs/main

4/9 11:00 AM IST Publish

Author: Saisang

articles/ai-services/speech-service/whisper-overview.md

@@ -61,7 +61,7 @@ Whisper Model via Azure AI Speech might be best for:
 
 Regional support is another consideration. 
 - The Whisper model via Azure OpenAI Service is available in the following regions: EastUS 2, India South, North Central, Norway East, Sweden Central, and West Europe. 
-- The Whisper model via Azure AI Speech is available in the following regions: Australia East, Central US, East US, North Central US, South Central US, Southeast Asia, and West Europe.
+- The Whisper model via Azure AI Speech is available in the following regions: Australia East, East US, North Central US, South Central US, Southeast Asia, UK South, and West Europe.
 
 ## Next steps
 

articles/ai-studio/tutorials/deploy-chat-web-app.md

@@ -7,7 +7,7 @@ ms.service: azure-ai-studio
 ms.custom:
   - ignite-2023
 ms.topic: tutorial
-ms.date: 2/8/2024
+ms.date: 4/8/2024
 ms.reviewer: eur
 ms.author: aahi
 author: aahill
@@ -219,14 +219,6 @@ To avoid incurring unnecessary Azure costs, you should delete the resources you
 
 ## Remarks
 
-### Remarks about adding your data
-
-Although it's beyond the scope of this tutorial, to understand more about how the model uses your data, you can export the playground setup to prompt flow. 
-
-:::image type="content" source="../media/tutorials/chat-web-app/prompt-flow-open.png" alt-text="Screenshot of the chat playground with the open in prompt flow button in view." lightbox="../media/tutorials/chat-web-app/prompt-flow-open.png":::
-
-Following through from there you can see the graphical representation of how the model uses your data to construct the response. For more information about prompt flow, see [prompt flow](../how-to/prompt-flow.md).
-
 ### Chat history
 
 With the chat history feature, your users will have access to their individual previous queries and responses.

articles/aks/upgrade-aks-cluster.md

@@ -25,6 +25,7 @@ When you perform an upgrade from an *unsupported version* that skips two or more
 * If you're using the Azure CLI, this article requires Azure CLI version 2.34.1 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][azure-cli-install].
 * If you're using Azure PowerShell, this article requires Azure PowerShell version 5.9.0 or later. Run `Get-InstalledModule -Name Az` to find the version. If you need to install or upgrade, see [Install Azure PowerShell][azure-powershell-install].
 * Performing upgrade operations requires the `Microsoft.ContainerService/managedClusters/agentPools/write` RBAC role. For more on Azure RBAC roles, see the [Azure resource provider operations][azure-rp-operations].
+* Starting with 1.30 kubernetes version and 1.27 LTS versions the beta apis will be disabled by default when you upgrade to them.
 
 > [!WARNING]
 > An AKS cluster upgrade triggers a cordon and drain of your nodes. If you have a low compute quota available, the upgrade might fail. For more information, see [increase quotas](../azure-portal/supportability/regional-quota-requests.md).

articles/azure-arc/servers/ssh-arc-powershell-remoting.md

@@ -0,0 +1,56 @@
+---
+title: SSH access to Azure Arc-enabled servers with PowerShell remoting
+description: Use PowerShell remoting over SSH to access and manage Azure Arc-enabled servers.
+ms.date: 04/08/2024
+ms.topic: conceptual
+ms.custom: references_regions
+---
+
+# PowerShell remoting to Azure Arc-enabled servers
+SSH for Arc-enabled servers enables SSH based connections to Arc-enabled servers without requiring a public IP address or additional open ports.
+[PowerShell remoting over SSH](/powershell/scripting/security/remoting/ssh-remoting-in-powershell) is available for Windows and Linux machines.
+
+## Prerequisites
+To leverage PowerShell remoting over SSH access to Azure Arc-enabled servers, ensure the following:
+ - Ensure the requirements for SSH access to Azure Arc-enabled servers are met.
+ - Ensure the requirements for PowerShell remoting over SSH are met.
+ - The Azure PowerShell module or the Azure CLI extension for connecting to Arc machines is present on the client machine.
+
+## How to connect via PowerShell remoting
+Follow the below steps to connect via PowerShell remoting to an Arc-enabled server.
+
+#### [Generate a SSH config file with Azure CLI:](#tab/azure-cli)
+```bash
+az ssh config --resource-group <myRG> --name <myMachine> --local-user <localUser> --resource-type Microsoft.HybridCompute --file <SSH config file>
+```
+ 
+#### [Generate a SSH config file with Azure PowerShell:](#tab/azure-powershell)
+ ```powershell
+Export-AzSshConfig -ResourceGroupName <myRG> -Name <myMachine> -LocalUser <localUser> -ResourceType Microsoft.HybridCompute/machines -ConfigFilePath <SSH config file>
+```
+ ---
+
+#### Find newly created entry in the SSH config file
+Open the created or modified SSH config file. The entry should have a similar format to the following.
+```powershell
+Host <myRG>-<myMachine>-<localUser>
+	HostName <myMachine>
+	User <localUser>
+	ProxyCommand "<path to proxy>\.clientsshproxy\sshProxy_windows_amd64_1_3_022941.exe" -r "<path to relay info>\az_ssh_config\<myRG>-<myMachine>\<myRG>-<myMachine>-relay_info"
+```
+#### Leveraging the -Options parameter
+Levering the [options](/powershell/module/microsoft.powershell.core/new-pssession#-options) parameter allows you to specify a hashtable of SSH options used when connecting to a remote SSH-based session.
+Create the hashtable by following the below format. Be mindful of the locations of quotation marks.
+```powershell
+$options = @{ProxyCommand = '"<path to proxy>\.clientsshproxy\sshProxy_windows_amd64_1_3_022941.exe -r <path to relay info>\az_ssh_config\<myRG>-<myMachine>\<myRG>-<myMachine>-relay_info"'}
+```
+Next leverage the options hashtable in a PowerShell remoting command.
+```powershell
+New-PSSession -HostName <myMachine> -UserName <localUser> -Options $options
+```
+
+## Next steps
+
+- Learn about [OpenSSH for Windows](/windows-server/administration/openssh/openssh_overview)
+- Learn about troubleshooting [SSH access to Azure Arc-enabled servers](ssh-arc-troubleshoot.md).
+- Learn about troubleshooting [agent connection issues](troubleshoot-agent-onboard.md).

articles/azure-arc/servers/toc.yml

@@ -131,6 +131,8 @@
     items:
     - name: SSH access to Azure Arc-enabled servers
       href: ssh-arc-overview.md
+    - name: PowerShell remoting to Azure Arc-enabled servers
+      href: ssh-arc-powershell-remoting.md
     - name: Troubleshoot SSH access to Azure Arc-enabled servers
       href: ssh-arc-troubleshoot.md
   - name: Extended Security Updates
@@ -217,4 +219,4 @@
   - name: Regional availability
     href: https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-arc&regions=all
   - name: Product feedback
-    href: https://feedback.azure.com/d365community/forum/5c778dec-0625-ec11-b6e6-000d3a4f0858
+    href: https://feedback.azure.com/d365community/forum/5c778dec-0625-ec11-b6e6-000d3a4f0858

articles/azure-functions/durable/quickstart-netherite.md

@@ -42,7 +42,7 @@ If this isn't the case, we suggest you start with one of the following articles,
 > [!NOTE]
 > If your app uses [Extension Bundles](../functions-bindings-register.md#extension-bundles), you should ignore this section as Extension Bundles removes the need for manual Extension management.
 
-You'll need to install the latest version of the Netherite Extension on NuGet. This usually means including a reference to it in your `.csproj` file and building the project.
+You need to install the latest version of the Netherite Extension on NuGet. This usually means including a reference to it in your `.csproj` file and building the project.
 
 The Extension package to install depends on the .NET worker you are using:
 - For the _in-process_ .NET worker, install [`Microsoft.Azure.DurableTask.Netherite.AzureFunctions`](https://www.nuget.org/packages/Microsoft.Azure.DurableTask.Netherite.AzureFunctions).
@@ -93,7 +93,7 @@ Edit the storage provider section of the `host.json` file so it sets the `type`
 }
 ```
 
-The snippet above is just a *minimal* configuration. Later, you may want to consider [additional parameters](https://microsoft.github.io/durabletask-netherite/#/settings?id=typical-configuration).
+The snippet above is just a *minimal* configuration. Later, you may want to consider [other parameters](https://microsoft.github.io/durabletask-netherite/#/settings?id=typical-configuration).
 
 
 ## Test locally
@@ -107,13 +107,16 @@ While the function app is running, Netherite will publish load information about
 > [!NOTE]
 > For more information on the contents of this table, see the [Partition Table](https://microsoft.github.io/durabletask-netherite/#/ptable) article.
 
+> [!NOTE]
+> If you are using local storage emulation on a Windows OS, please ensure you're using the [Azurite](../../storage/common/storage-use-azurite.md) storage emulator and not the legacy "Azure Storage Emulator" component. Local storage emulation with Netherite is only supported via Azurite.
+
 ## Run your app on Azure
 
 You need to create an Azure Functions app on Azure. To do this, follow the instructions in the **Create a function app** section of [these instructions](../functions-create-function-app-portal.md).
 
 ### Set up Event Hubs
 
-You will need to set up an Event Hubs namespace to run Netherite on Azure. You can also set it up if you prefer to use Event Hubs during local development.
+You need to set up an Event Hubs namespace to run Netherite on Azure. You can also set it up if you prefer to use Event Hubs during local development.
 
 > [!NOTE]
 > An Event Hubs namespace incurs an ongoing cost, whether or not it is being used by Durable Functions. Microsoft offers a [12-month free Azure subscription account](https://azure.microsoft.com/free/) if you’re exploring Azure for the first time.

articles/azure-monitor/app/app-insights-overview.md

@@ -215,6 +215,24 @@ Application Insights doesn't handle sensitive data by default, as long as you do
 
 For archived information on this topic, see [Data collection, retention, and storage in Application Insights](/previous-versions/azure/azure-monitor/app/data-retention-privacy).
 
+### What is the Application Insights pricing model?
+
+Application Insights is billed through the Log Analytics workspace into which its log data ingested. 
+The default Pay-as-you-go Log Analytics pricing tier includes 5 GB per month of free data allowance per billing account. 
+Learn more about [Azure Monitor logs pricing options](https://azure.microsoft.com/pricing/details/monitor/).
+          
+### Are there data transfer charges between an Azure web app and Application Insights?
+
+* If your Azure web app is hosted in a datacenter where there's an Application Insights collection endpoint, there's no charge.
+* If there's no collection endpoint in your host datacenter, your app's telemetry incurs [Azure outgoing charges](https://azure.microsoft.com/pricing/details/bandwidth/).
+          
+This answer depends on the distribution of our endpoints, *not* on where your Application Insights resource is hosted.
+
+### Do I incur network costs if my Application Insights resource is monitoring an Azure resource (that is, telemetry producer) in a different region?
+
+Yes, you may incur more network costs, which vary depending on the region the telemetry is coming from and where it's going. 
+Refer to [Azure bandwidth pricing](https://azure.microsoft.com/pricing/details/bandwidth/) for details.
+
 ## Help and support
 
 ### Azure technical support

articles/communication-services/resources/troubleshooting/voice-video-calling/general-troubleshooting-strategies/overview.md

@@ -0,0 +1,85 @@
+---
+title: General troubleshooting strategies - Overview
+titleSuffix: Azure Communication Services - Troubleshooting Guide
+description: Overview of general troubleshooting strategies
+author: enricohuang
+ms.author: enricohuang
+
+services: azure-communication-services
+ms.date: 02/23/2024
+ms.topic: troubleshooting
+ms.service: azure-communication-services
+ms.subservice: calling
+---
+
+# Overview of general troubleshooting strategies
+
+Ensuring a satisfying experience during a call requires many elements to work together:
+
+* stable network and hardware environment
+* good user interface design
+* timely feedback to the user on the current status and errors
+
+To troubleshoot issues reported by users, it's important to identify where the issue is coming from.
+The issue could lie within the application, the SDK, or the user's environment such as device, network, or browser.
+
+This article explores some debugging strategies that help you identify the root of the problem efficiently.
+
+## Clarifying the issues reported by the users
+
+First, you need to clarify the issues reported by the users.
+
+Sometimes when users report issues, they may not accurately describe the problem, so there may be some ambiguity.
+For example, when users report experiencing a delay during a call,
+they may refer to a delay after the call is connected but before any sound is heard.
+Alternatively, they might refer to the delay experienced between two parties while they communicate with each other.
+
+These two situations are different and require different approaches to identify and resolve the issue.
+It's important to gather more information from the user to understand the problem and address it accordingly.
+
+## Understanding how often users and how many users encounter the issue
+
+When the user reports an issue, we need to understand its reproducibility.
+Only happening once and always happening are different situations.
+
+For some issues, you can also use [Call Diagnostics](../../../../concepts/voice-video-calling/call-diagnostics.md) tool and [Azure Monitor Log](../../../../concepts/analytics/logs/voice-and-video-logs.md) to understand how many users could have similar problems.
+
+Understanding the issue reproducibility and how many users are affected can help you decide on the priority of the issue.
+
+## Referring to documentation
+
+The documentation for Azure Communication Services Calling SDK is rich and covers many subjects,
+including concept documents, quickstart guides, tutorials, known issues, and troubleshooting guides.
+
+Take time to check the known issues and the service limitation page.
+Sometimes, the issues reported by users are due to limitations of the service itself. A good example would be the number of videos that can be viewed during a large meeting.
+The behavior of the user's browser or of its device could be the cause of the issue.
+
+For example, when a mobile browser operates in the background or when the user phone is locked, it may exhibit various behaviors depending on the platform. The browser might cease sending video frames altogether or transmit solely black frames.
+
+The troubleshooting guide, in particular, addresses various issues that may arise when using the ACS Calling SDK.
+You can check the list of common issues in the troubleshooting guide to see if there's a similar issue reported by the user,
+and follow the instructions provided to further troubleshoot the problem.
+
+## Reporting an issue
+
+If the issue reported by the user isn't present in the troubleshooting guide, consider reporting the issue.
+
+In most cases, you need to provide the callId together with a clear description of the issue.
+If you're able to reproduce the issue, include details related to the issue. For instance,
+
+* steps to reproduce the issue, including preconditions (platform, network conditions, and other information that might be helpful)
+* what result do you expect to see
+* what result do you actually see
+* reproducibility rate of the issue
+
+For more information, see [Reporting an issue](./reporting-an-issue.md).
+
+## Next steps
+
+Besides the troubleshooting guide, here are some articles of interest to you.
+
+* Learn how to [Optimizing Call Quality](../../../../concepts/voice-video-calling/manage-call-quality.md).
+* Learn more about [Call Diagnostics](../../../../concepts/voice-video-calling/call-diagnostics.md).
+* Learn more about [Troubleshooting VoIP Call Quality](../../../../concepts/voice-video-calling/troubleshoot-web-voip-quality.md).
+* See [Known issues](../../../../concepts/voice-video-calling/known-issues-webjs.md?pivots=all-browsers).

articles/communication-services/resources/troubleshooting/voice-video-calling/general-troubleshooting-strategies/reporting-an-issue.md

@@ -0,0 +1,54 @@
+---
+title: General troubleshooting strategies - Reporting an issue
+titleSuffix: Azure Communication Services - Troubleshooting Guide
+description: Learn how to report an issue.
+author: enricohuang
+ms.author: enricohuang
+
+services: azure-communication-services
+ms.date: 02/24/2024
+ms.topic: troubleshooting
+ms.service: azure-communication-services
+ms.subservice: calling
+---
+
+# Reporting an issue
+
+If the issue reported by the user can't be found in the troubleshooting guide, consider reporting the issue.
+
+Sometimes the problem comes from the app itself.
+In this case, you can test the issue against the calling sample
+[https://github.com/Azure-Samples/communication-services-web-calling-tutorial](https://github.com/Azure-Samples/communication-services-web-calling-tutorial) 
+to see if the problem can also be reproduced in the calling sample.
+
+## Where to report the issue
+
+When you want to report issues, there are several places to report them.
+You can refer to [Azure Support](../../../../support.md).
+
+You can choose to create an Azure support ticket.
+Additionally, for the ACS Web Calling SDK, if you found an issue during development,
+you can also report it at [https://github.com/Azure/azure-sdk-for-js/issues](https://github.com/Azure/azure-sdk-for-js/issues).
+
+## What to include when you report the issue
+
+When reporting an issue, you need to provide a clear description of the issue, including:
+
+* context
+* steps to reproduce the problem
+* expected results
+* actual results
+
+In most cases, you also need to include details, such as
+
+* environment
+  * operation system and version
+  * browser name and version
+  * ACS SDK version
+* call info
+  * `Call Id` (when the issue happened during a call)
+  * `Participant Id` (if there were multiple participants in the call, but only some of them experienced the issue)
+
+If you can only reproduce the issue on a specific device platform (for example, iPhone X), also include the device model when you report the issue.
+
+Depending on the type of issue, we may ask you to provide logs when we investigate the issue.