Merge pull request #271018 from MicrosoftDocs/main

4/3 11:00 AM IST Publish

Author: Saisang

articles/aks/howto-deploy-java-liberty-app.md

@@ -105,6 +105,7 @@ API Management offers a free, managed TLS certificate for your domain, if you do
 * Not supported in the following Azure regions: France South and South Africa West
 * Currently available only in the Azure cloud
 * Does not support root domain names (for example, `contoso.com`). Requires a fully qualified name such as `api.contoso.com`.
+* Supports only public domain names
 * Can only be configured when updating an existing API Management instance, not when creating an instance
 
 

articles/api-management/configure-custom-domain.md

@@ -59,66 +59,6 @@ To run the application locally:
     pip install -r requirements.txt
     ```
 
-1. Integrate a database:
-
-    ```Python
-    
-    from azure.cosmos.aio import CosmosClient
-    from azure.cosmos import exceptions
-    from azure.cosmos.partition_key import PartitionKey
-
-    from configs.credential import HOST, MASTER_KEY, DATABASE_ID
-
-
-    def get_database_client():
-         # Initialize the Cosmos client
-         client = CosmosClient(HOST, MASTER_KEY)
-
-         # Create or get a reference to a database
-         try:
-             database = client.create_database_if_not_exists(id=DATABASE_ID)
-             print(f'Database "{DATABASE_ID}" created or retrieved successfully.')
-
-         except exceptions.CosmosResourceExistsError:
-             database = client.get_database_client(DATABASE_ID)
-             print('Database with id \'{0}\' was found'.format(DATABASE_ID))
-
-         return database
-
-
-    def get_container_client(container_id):
-         database = get_database_client()
-         # Create or get a reference to a container
-         try:
-             container = database.create_container(id=container_id, partition_key=PartitionKey(path='/partitionKey'))
-             print('Container with id \'{0}\' created'.format(container_id))
-
-         except exceptions.CosmosResourceExistsError:
-             container = database.get_container_client(container_id)
-             print('Container with id \'{0}\' was found'.format(container_id))
-
-         return container
-
-    async def create_item(container_id, item):
-        async with CosmosClient(HOST, credential=MASTER_KEY) as client:
-            database = client.get_database_client(DATABASE_ID)
-            container = database.get_container_client(container_id)
-            await container.upsert_item(body=item)
-
-    async def get_items(container_id):
-        items = []
-        try:
-            async with CosmosClient(HOST, credential=MASTER_KEY) as client:
-                database = client.get_database_client(DATABASE_ID)
-                container = database.get_container_client(container_id)
-                async for item in container.read_all_items():
-                    items.append(item)
-        except Exception as e:
-            print(f"An error occurred: {e}")
-
-        return items
-    ```
-
 1. Run the app:
 
     ```Console

articles/app-service/quickstart-python.md

@@ -4,7 +4,7 @@ description: Create your first WordPress site on Azure App Service in minutes.
 keywords: app service, azure app service, wordpress, preview, app service on linux, plugins, mysql flexible server, wordpress on linux, php
 author: msangapu-msft
 ms.topic: quickstart
-ms.date: 05/15/2023
+ms.date: 03/28/2024
 # ms.devlang: wordpress
 ms.author: msangapu
 ms.custom: mvc, linux-related-content
@@ -17,14 +17,6 @@ In this quickstart, you'll learn how to create and deploy your first [WordPress]
 
 To complete this quickstart, you need an Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs).
 
-> [!IMPORTANT]
-> After November 28, 2022, [PHP will only be supported on App Service on Linux.](https://github.com/Azure/app-service-linux-docs/blob/master/Runtime_Support/php_support.md#end-of-life-for-php-74).
->
-> For migrating WordPress to App Service, visit [Migrating to App Service](migrate-wordpress.md). Additional documentation can be found at [WordPress - App Service on Linux](https://github.com/Azure/wordpress-linux-appservice).
->
-> To submit feedback on improving the WordPress experience on App Service, visit [Web Apps Community](https://feedback.azure.com/d365community/forum/b09330d1-c625-ec11-b6e6-000d3a4f0f1c).
->
-
 ## Create WordPress site using Azure portal
 
 1. To start creating the WordPress site, browse to [https://portal.azure.com/#create/WordPress.WordPress](https://portal.azure.com/#create/WordPress.WordPress).

articles/app-service/quickstart-wordpress.md

@@ -50,7 +50,7 @@ See [Class based model](../azure-signalr/signalr-concept-serverless-development-
 public class HubName1 : ServerlessHub
 {
     [FunctionName("SignalRTest")]
-    public async Task SendMessage([SignalRTrigger]InvocationContext invocationContext, string message, ILogger logger)
+    public Task SendMessage([SignalRTrigger]InvocationContext invocationContext, string message, ILogger logger)
     {
         logger.LogInformation($"Receive {message} from {invocationContext.ConnectionId}.");
     }
@@ -63,7 +63,7 @@ Traditional model obeys the convention of Azure Function developed by C#. If you
 
 ```cs
 [FunctionName("SignalRTest")]
-public static async Task Run([SignalRTrigger("SignalRTest", "messages", "SendMessage", parameterNames: new string[] {"message"})]InvocationContext invocationContext, string message, ILogger logger)
+public static Task Run([SignalRTrigger("SignalRTest", "messages", "SendMessage", parameterNames: new string[] {"message"})]InvocationContext invocationContext, string message, ILogger logger)
 {
     logger.LogInformation($"Receive {message} from {invocationContext.ConnectionId}.");
 }
@@ -73,7 +73,7 @@ Because it can be hard to use `ParameterNames` in the trigger, the following exa
 
 ```cs
 [FunctionName("SignalRTest")]
-public static async Task Run([SignalRTrigger("SignalRTest", "messages", "SendMessage")]InvocationContext invocationContext, [SignalRParameter]string message, ILogger logger)
+public static Task Run([SignalRTrigger("SignalRTest", "messages", "SendMessage")]InvocationContext invocationContext, [SignalRParameter]string message, ILogger logger)
 {
     logger.LogInformation($"Receive {message} from {invocationContext.ConnectionId}.");
 }
@@ -113,7 +113,7 @@ app.generic("function1",
 Here's the JavaScript code:
 
 ```javascript
-module.exports = async function (context, invocation) {
+module.exports = function (context, invocation) {
     context.log(`Receive ${context.bindingData.message} from ${invocation.ConnectionId}.`)
 };
 ```

articles/azure-functions/functions-bindings-signalr-service-trigger.md

@@ -14,12 +14,12 @@ ms.author: anfdocs
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
 
+## March 2024
+
 * [Large volumes (Preview) improvement:](large-volumes-requirements-considerations.md) new minimum size of 50 TiB
 
     Large volumes support a minimum size of 50 TiB. Large volumes still support a maximum quota of 500 TiB. 
 
-## March 2024
-
 * [Availability zone volume placement](manage-availability-zone-volume-placement.md) is now generally available (GA).
 
     You can deploy new volumes in the logical availability zone of your choice to create cross-zone volumes to improve resiliency in case of zonal failures. This feature is available in all availability zone-enabled regions with Azure NetApp Files presence.

articles/azure-netapp-files/whats-new.md

@@ -76,17 +76,17 @@ The class-based model is dedicated for C#.
 The class-based model provides better programming experience, which can replace SignalR input and output bindings, with the following features:
 - More flexible negotiation, sending messages and managing groups experience.
 - More managing functionalities are supported, including closing connections, checking whether a connection, user, or group exists.
-- Strongly Typed hub
-- Unified connection string setting in one place.
+- Strongly typed hub
+- Unified hub name and connection string setting in one place.
 
 The following code demonstrates how to write SignalR bindings in class-based model:
 
-In the *Functions.cs* file, define your hub, which extends a base class `ServerlessHub`:
+Firstly, define your hub derived from a class `ServerlessHub`:
 ```cs
 [SignalRConnection("AzureSignalRConnectionString")]
 public class Functions : ServerlessHub
 {
-    private const string HubName = nameof(Functions);
+    private const string HubName = nameof(Functions); // Used by SignalR trigger only
 
     public Functions(IServiceProvider serviceProvider) : base(serviceProvider)
     {
@@ -126,7 +126,7 @@ var host = new HostBuilder()
 
 ### Negotiation experience in class-based model
 
-Instead of using SignalR input binding `[SignalRConnectionInfoInput]`, negotiation in class-based model can be more flexible. Base class `ServerlessHub` has a method `NegotiateAsync`, which allows user to customize negotiation options such as `userId`, `claims`, etc.
+Instead of using SignalR input binding `[SignalRConnectionInfoInput]`, negotiation in class-based model can be more flexible. Base class `ServerlessHub` has a method `NegotiateAsync`, which allows users to customize negotiation options such as `userId`, `claims`, etc.
 
 ```cs
 Task<BinaryData> NegotiateAsync(NegotiationOptions? options = null)
@@ -141,7 +141,7 @@ You could send messages, manage groups, or manage clients by accessing the membe
 - `ServerlessHub.UserGroups` for managing users with groups, such as adding users to groups, removing users from groups.
 - `ServerlessHub.ClientManager` for checking connections existence, closing connections, etc.
 
-### Strongly Typed Hub
+### Strongly typed Hub
 
 [Strongly typed hub](/aspnet/core/signalr/hubs?#strongly-typed-hubs) allows you to use strongly typed methods when you send messages to clients. To use strongly typed hub in class based model, extract client methods into an interface `T`, and make your hub class derived from `ServerlessHub<T>`.
 
@@ -158,7 +158,7 @@ Then you can use the strongly typed methods as follows:
 [SignalRConnection("AzureSignalRConnectionString")]
 public class Functions : ServerlessHub<IChatClient>
 {
-    private const string HubName = nameof(Functions);
+    private const string HubName = nameof(Functions);  // Used by SignalR trigger only
 
     public Functions(IServiceProvider serviceProvider) : base(serviceProvider)
     {
@@ -176,18 +176,18 @@ public class Functions : ServerlessHub<IChatClient>
 > [!NOTE]
 > You can get a complete project sample from [GitHub](https://github.com/aspnet/AzureSignalR-samples/tree/main/samples/DotnetIsolated-ClassBased/).
 
-### Unified connection string setting in one place
+### Unified hub name and connection string setting in one place
 
-You might have noticed the `SignalRConnection` attribute used on serverless hub classes. It looks like this:
-```cs
-[SignalRConnection("AzureSignalRConnectionString")]
-public class Functions : ServerlessHub<IChatClient>
-```
-
-It allows you to customize where the SignalR Service bindings look for connection string. If it's absent, the default value `AzureSignalRConnectionString` is used.
+* The class name of the serverless hub is automatically used as `HubName`.
+* You might have noticed the `SignalRConnection` attribute used on serverless hub classes as follows:
+    ```cs
+    [SignalRConnection("AzureSignalRConnectionString")]
+    public class Functions : ServerlessHub<IChatClient>
+    ```
+    It allows you to customize where the connection string for serverless hub is. If it's absent, the default value `AzureSignalRConnectionString` is used.
 
 > [!IMPORTANT]
-> `SignalRConnection` attribute doesn't change the connection string setting of SignalR triggers, even though you use SignalR triggers inside the serverless hub. You should specify the connection string setting for each SignalR trigger if you want to customize it.
+> SignalR triggers and serverless hubs are independent. Therefore, the class name of serverless hub and `SignalRConnection` attribute doesn't change the settings of SignalR triggers, even though you use SignalR triggers inside the serverless hub.
 
 # [In-process model](#tab/in-process)
 
@@ -229,7 +229,7 @@ public class HubName1 : ServerlessHub
 }
 ```
 
-All functions that want to use the class-based model need to be a method of the class that inherits from **ServerlessHub**. The class name `SignalRTestHub` in the sample is the hub name.
+All functions that want to use the class-based model need to be a method of the class that inherits from **ServerlessHub**. The class name `HubName1` in the sample is the hub name.
 
 ### Define hub method
 
@@ -250,13 +250,13 @@ In class based model, `[SignalRParameter]` is unnecessary because all the argume
 
 ### Negotiation experience in class-based model
 
-Instead of using SignalR input binding `[SignalR]`, negotiation in class-based model can be more flexible. Base class `ServerlessHub` has a method.
+Instead of using SignalR input binding `[SignalR]`, negotiation in class-based model can be more flexible. Base class `ServerlessHub` has a method:
 
 ```cs
 SignalRConnectionInfo Negotiate(string userId = null, IList<Claim> claims = null, TimeSpan? lifeTime = null)
 ```
 
-This features user customizes `userId` or `claims` during the function execution.
+This feature allows user to customize `userId` or `claims` during the function execution.
 
 ## Use `SignalRFilterAttribute`
 

articles/azure-signalr/signalr-concept-serverless-development-config.md

@@ -47,7 +47,7 @@ Microsoft Entra authorizes access rights to secured resources through [Azure rol
 
 Before assigning an Azure RBAC role to a security principal, it's important to identify the appropriate level of access that the principal should have. It's recommended to grant the role with the narrowest possible scope. Resources located underneath inherit Azure RBAC roles with broader scopes.
 
-You can scope access to Azure SignalR resources at the following levels, beginning with the narrowest scope:
+You can scope access to Azure Web PubSub resources at the following levels, beginning with the narrowest scope:
 
 - **An individual resource.**
 

articles/azure-web-pubsub/concept-azure-ad-authorization.md

@@ -0,0 +1,32 @@
+---
+title: Device and permission issues - askDevicePermission API takes too long
+titleSuffix: Azure Communication Services - Troubleshooting Guide
+description: Learn how to troubleshoot when askDevicePermission API takes too long.
+author: enricohuang
+ms.author: enricohuang
+
+services: azure-communication-services
+ms.date: 03/29/2024
+ms.topic: troubleshooting
+ms.service: azure-communication-services
+ms.subservice: calling
+---
+
+# The askDevicePermission API takes too long
+The [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API prompts the end user via the browser asking if they allow permission to use camera or microphone.
+If the end user approves camera or microphone usage, then those devices are available to be used in a call. The devices availability is reflected in available device list.
+
+User taking a long time to approve the permission can cause delay in the API response.
+
+Occasionally, the device list update step can take a long time.
+A delay in the driver layer is usually the cause of the issue. The issue can happen with some virtual audio devices in particular. [Chromium Issue 1402866](https://bugs.chromium.org/p/chromium/issues/detail?id=1402866&no_tracker_redirect=1)
+
+## How to detect using the SDK
+To detect this issue, you can measure the time difference between when you call the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API and when the promise resolves or rejects.
+
+## How to mitigate or resolve
+If the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API fails due to the user not responding to the UI permission prompt,
+the application can retry the API again and the user should see the UI permission prompt.
+
+As for other reasons, such as the device list updating taking too long to complete, the user should check their devices and see if there's any device that could potentially be causing this issue.
+They may need to update or remove the problematic device to resolve the issue.

articles/communication-services/resources/troubleshooting/voice-video-calling/device-issues/ask-device-permission-api-takes-too-long.md

@@ -0,0 +1,36 @@
+---
+title: Device and permission issues - getMicrophones API doesn't return detailed microphone list
+titleSuffix: Azure Communication Services - Troubleshooting Guide
+description: Learn how to troubleshoot when getMicrophones API doesn't return detailed microphone list.
+author: enricohuang
+ms.author: enricohuang
+
+services: azure-communication-services
+ms.date: 03/29/2024
+ms.topic: troubleshooting
+ms.service: azure-communication-services
+ms.subservice: calling
+---
+
+# The getMicrophones API doesn't return detailed microphone list
+If a user reports they can't see the detailed microphone list,
+it's likely because the user didn't grant permission to access the microphone.
+When the permission state is `prompt` or `denied`, the browser doesn't provide detailed information about the microphone devices.
+In this scenario, the [`DeviceManager.getMicrophones`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-devicemanager-getmicrophones) API returns an array with one object, where the `id` is set to `microphone:` and the name is set to an empty string.
+
+It's important to note that this scenario differs from the scenario where a user doesn't have any microphone on their device. If a device doesn't have any microphones the [`DeviceManager.getMicrophones`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-devicemanager-getmicrophones) API returns an empty array, indicating that there's no available microphone devices on the user's system.
+
+## How to detect using the SDK
+[`DeviceManager.getMicrophones`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-devicemanager-getmicrophones) API returns an empty array or an array with an object, where the `id` is set to `microphone:` and the name is set to an empty string.
+
+Additionally, to detect the scenario where the user removes the microphone during the call and there are no available microphones in the system,
+the application can listen to the [`noMicrophoneDevicesEnumerated`](/javascript/api/azure-communication-services/@azure/communication-calling/latestmediadiagnostics?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-latestmediadiagnostics-nomicrophonedevicesenumerated) event being raised to true in the [User Facing Diagnostics Feature](../../../../concepts/voice-video-calling/user-facing-diagnostics.md).
+This event can help the application understand the current situation, so it can show a warning message on its UI accordingly.
+
+## How to mitigate or resolve
+Your application should always call the [`DeviceManager.askDevicePermission`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-devicemanager-askdevicepermission) API to ensure that the required permissions are granted.
+If the user doesn't grant the microphone permission, your application should display a warning message on its user interface.
+
+Additionally, your application should listen to the [`noMicrophoneDevicesEnumerated`](/javascript/api/azure-communication-services/@azure/communication-calling/latestmediadiagnostics?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-latestmediadiagnostics-nomicrophonedevicesenumerated) event and show a message when there are no available microphone devices.
+If the application provides a device selection page before the call,
+it can also check whether the microphone list is empty and shows a warning accordingly indicating no mic devices available.