Merge pull request #262710 from ahammer/docs-editor/collecting-user-feedback-1704747938

Create article collecting-user-feedback

Author: v-ccolin

articles/communication-services/concepts/troubleshooting-info.md

@@ -17,7 +17,7 @@ This document helps you troubleshoot issues that you may experience within your
 
 ## Getting help
 
-We encourage developers to submit questions, suggest features, and report problems as issues. To aid in doing this, we have a [dedicated support and help options page](../support.md) which lists your options for support. 
+We encourage developers to submit questions, suggest features, and report problems as issues. To aid in getting help, we have a [dedicated support and help options page](../support.md) that lists your options for support. 
 
 To help you troubleshoot certain types of issues, you may be asked for any of the following pieces of information:
 
@@ -83,7 +83,7 @@ When troubleshooting issues with the Call Automation SDK, like call management o
 - From the header of API response, locate the field `X-Ms-Skype-Chain-Id`.
 
     ![Screenshot of response header showing X-Ms-Skype-Chain-Id.](media/troubleshooting/response-header.png) 
-- From the callback events your application receives after executing an action e.g. `CallConnected` or `PlayFailed`, locate the correlationID.
+- From the callback events your application receives after executing an action. For example `CallConnected` or `PlayFailed`, locate the correlationID.
 
     ![Screenshot of call disconnected event showing correlation ID.](media/troubleshooting/correlation-id-in-callback-event.png)
 
@@ -166,16 +166,11 @@ Console.WriteLine($"Email operation id = {emailSendOperation.Id}");
 
 ## Accessing Support Files in the Calling SDK
 
-[!INCLUDE [Public Preview](../includes/public-preview-include.md)]
+Calling SDK provides convenience methods to get access to the Log Files. These files can serve valuable to Microsoft support specialists and engineers. Pro-actively collecting these logs when issues are detected is recommended.
 
-Calling SDK provides convenience methods to get access to the Log Files. To actively collect, it is encouraged to pair this functionality with your applications support tooling.
+## Enable and Access Call Logs
 
-[Log File Access Conceptual Document](../concepts/voice-video-calling/retrieve-support-files.md)
-[Log File Access Tutorials](../tutorials/log-file-retrieval-tutorial.md)
-
-## Enable and access call logs
-
-# [JavaScript](#tab/javascript)
+### [JavaScript]
 
 The Azure Communication Services Calling SDK relies internally on [@azure/logger](https://www.npmjs.com/package/@azure/logger) library to control logging.
 Use the `setLogLevel` method from the `@azure/logger` package to configure the log output level. Create a logger and pass it into the CallClient constructor:
@@ -198,35 +193,25 @@ AzureLogger.log = (...args) => {
 };
 ```
 
-# [iOS](#tab/ios)
-
-In an iOS Application, logs are stored in `.blog` files. Note that you can't view the logs directly because they're encrypted.
+### Native SDK (Android/iOS)
 
-These can be accessed by opening Xcode. Go to Windows > Devices and Simulators > Devices. Select your device. Under Installed Apps, select your application and click on "Download container".
+For Android, iOS and Windows the Azure Communication Services Calling SDK offers access to log files.
 
-This process gives you a `xcappdata` file. Right-click on this file and select “Show package contents”. You'll then see the `.blog` files that you can then attach to your Azure support request.
+For Calling Native SDK's, refer to [the log file access tutorials](../tutorials/log-file-retrieval-tutorial.md)
 
-# [Android](#tab/android)
-
-In an Android application, logs are stored in `.blog` files. Note that you can't view the logs directly because they're encrypted.
+### UI Libraries (Android, iOS)
 
-On Android Studio, navigate to the Device File Explorer by selecting View > Tool Windows > Device File Explorer from both the simulator and the device. The `.blog` file is located within your application's directory, which should look something like `/data/data/[app_name_space:com.contoso.com.acsquickstartapp]/files/acs_sdk.blog`. You can attach this file to your support request.
+If you are using the Azure Communication Services UI Libraries for Android or iOS, user feedback can be solicited through the built-in support form.
 
----
+For more information on how to use the support functionality of the Calling UI Support form, see the [Support Form integration tutorial](../tutorials/collecting-user-feedback/collecting-user-feedback.md). This document guides you through adding the necessary event handler, and creating a basic client/server implementation for centralized storage of support information. This guide is designed to guide you on your path towards an integration with the support services your organization uses.
 
-## Enable and access call logs (Windows)
+## Building end to end Support Flows in your ACS Integrations
 
-In a Windows application, logs are stored in `.blog` files. Note that you can't view the logs directly because they're encrypted.
-
-These are accessed by looking at where your app is keeping its local data. There are many ways to figure out where a UWP app keeps its local data, the following steps are just one of these ways:
-1. Open a Windows Command Prompt (Windows Key + R)
-2. Type `cmd.exe`
-3. Type `where /r %USERPROFILE%\AppData acs*.blog`
-4. Please check if the app ID of your application matches with the one returned by the previous command.
-5. Open the folder with the logs by typing `start ` followed by the path returned by the step 3. For example: `start C:\Users\myuser\AppData\Local\Packages\e84000dd-df04-4bbc-bf22-64b8351a9cd9_k2q8b5fxpmbf6`
-6. Please attach all the `*.blog` and `*.etl` files to your Azure support request.
+Whether you are using Calling SDK or Calling UI SDK, providing support to end users is a key component of any robust integration. The following document highlights the key considerations at each point of the Support feedback loop, and provides jumping off points to learn more.
 
+[Providing User Support](../concepts/voice-video-calling/retrieve-support-files.md)
 
+---
 <a name='finding-azure-active-directory-information'></a>
 
 ## Finding Microsoft Entra information
@@ -236,7 +221,7 @@ These are accessed by looking at where your app is keeping its local data. There
 * **Getting User ID**
 
 ## Getting Directory ID 
-To find your Directory (tenant) ID, follow the steps listed below:
+To find your Directory (tenant) ID, follow these steps:
 
 1. Navigate to [Azure portal](https://portal.azure.com) and sign in to the Azure portal using the credentials.
 1. From the left-pane, select Microsoft Entra ID.
@@ -245,7 +230,7 @@ To find your Directory (tenant) ID, follow the steps listed below:
     ![Screenshot of how to copy Microsoft Entra tenant ID and store it.](./media/troubleshooting/copy-aad-directory-id.png)
 
 ## Getting Application ID 
-To find your Application ID, follow the steps listed below:
+To find your Application ID, follow these steps:
 
 1. Navigate to [Azure portal](https://portal.azure.com) and sign in to the Azure portal using the credentials.
 1. From the left-pane, select Microsoft Entra ID.
@@ -257,7 +242,7 @@ To find your Application ID, follow the steps listed below:
    The directory (tenant) ID can also be found in the application overview page.
 
 ## Getting User ID
-To find your User ID, follow the steps listed below:
+To find your User ID, follow these steps:
 
 1. Navigate to [Azure portal](https://portal.azure.com) and sign in to the Azure portal using the credentials.
 1. From the left-pane, select Microsoft Entra ID.
@@ -267,7 +252,7 @@ To find your User ID, follow the steps listed below:
    ![Screenshot of how to copy Microsoft Entra user ID and store it.](./media/troubleshooting/copy-aad-user-id.png)
 
 ## Getting immutable resource ID 
-Sometimes you also need to provide immutable resource ID of your Communication Service resource. To find it, follow the steps listed below:
+Sometimes you also need to provide immutable resource ID of your Communication Service resource. To find it, follow these steps:
 
 1. Navigate to [Azure portal](https://portal.azure.com) and sign in to the Azure portal using the credentials.
 1. Open your Communication Service resource.
@@ -284,14 +269,14 @@ There are two ways to verify your Teams License eligibility to use Azure Communi
 * **Checking your current Teams license via Microsoft Graph API**
 
 #### Verification via Teams web client 
-To verify your Teams License eligibility via Teams web client, follow the steps listed below:
+To verify your Teams License eligibility via Teams web client, follow these steps:
 
 1. Open your browser and navigate to [Teams web client](https://teams.microsoft.com/).
 1. Sign in with credentials that have a valid Teams license. 
 1. If the authentication is successful and you remain in the https://teams.microsoft.com/ domain, then your Teams License is eligible. If authentication fails or you're redirected to the https://teams.live.com/v2/ domain, then your Teams License isn't eligible to use Azure Communication Services support for Teams users. 
 
 #### Checking your current Teams license via Microsoft Graph API
-You can find your current Teams license using [licenseDetails](/graph/api/resources/licensedetails) Microsoft Graph API that returns the licenses assigned to a user. Follow the steps below to use the Graph Explorer tool to view licenses assigned to a user:
+You can find your current Teams license using [licenseDetails](/graph/api/resources/licensedetails) Microsoft Graph API that returns the licenses assigned to a user. Follow these steps to use the Graph Explorer tool to view licenses assigned to a user:
 
 1. Open your browser and navigate to [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer)
 1. Sign in to Graph Explorer using the credentials.

articles/communication-services/concepts/ui-library/includes/mobile-ui-use-cases.md

@@ -81,6 +81,10 @@ Use the UI Library for mobile native platforms to give local and remote particip
 
 UI Library provides the capability to join a call skipping the setup screen of the call join experience. By default, user goes through a setup screen to join a call. Here, user sets the call configuration such as camera turn on or off, microphone turn on or off and audio device selection before joining a call. This screen requires user interaction to join a call, which might be unnecessary for some users. So we provide the capability to join a call by skipping the setup screen and providing the call configuration APIs. For more information, see [How to use Skip Setup Screen Feature](../../../how-tos/ui-library-sdk/skip-setup-screen.md)
 
+### Audio Only Mode
+
+The Audio Only Mode in the UI Library allows participants to join calls using only their audio, without sharing or receiving video. This feature is used to conserve bandwidth and maximize privacy. When activated, the Audio Only Mode automatically disables the video functionalities for both sending and receiving streams, and adjusts the UI to reflect this change by removing video-related controls. This mode can be enabled through the CallComposite configuration, more information available through the [Audio Only Quick Start](../../../how-tos/ui-library-sdk/audio-only-mode.md)
+
 ### Orientation
 
 UI Library supports screen orientation setup for each of the screen separately prior to launch the library experience. This allows application developers to set up a fixed orientation for the calling experience which would align their application orientation. To learn more about the list of supported orientation for both Android and iOS platform and usage of the API, see [How to use Orientation Feature](../../../how-tos/ui-library-sdk/orientation.md)