Merge pull request #288209 from MicrosoftDocs/main

10/10/2024 PM Publish

Author: Taojunshen

articles/api-management/workspaces-overview.md

@@ -97,7 +97,8 @@ Workspace gateways are currently available in the following regions:
 * North Central US
 * East US 2
 * UK South
-* France Central 
+* France Central
+* Germany West Central
 * North Europe
 * East Asia
 * Southeast Asia

articles/app-service/environment/overview.md

@@ -50,7 +50,7 @@ An App Service Environment is a single-tenant deployment of Azure App Service th
 
 Applications are hosted in App Service plans, which are created in an App Service Environment. An App Service plan is essentially a provisioning profile for an application host. As you scale out your App Service plan, you create more application hosts with all the apps in that App Service plan on each host. A single App Service Environment v3 can have up to 200 total App Service plan instances across all the App Service plans combined. A single App Service Isolated v2 (Iv2) plan can have up to 100 instances by itself.
 
-When you're deploying onto dedicated hardware (hosts), you're limited in scaling across all App Service plans to the number of cores in this type of environment. An App Service Environment that's deployed on dedicated hosts has 132 vCores available. I1v2 uses two vCores, I2v2 uses four vCores, and I3v2 uses eight vCores per instance. Only I1v2, I2v2, and I3v2 SKU sizes are available on App Service Environment deployed on dedicated hosts.
+If you have a requirement that you must have physical isolation all the way down to the hardware level, you can deploy your App Service Environment v3 onto dedicated hardware (hosts). When you're deploying onto dedicated hosts, you're limited in scaling across all App Service plans to the number of cores in this type of environment. An App Service Environment that's deployed on dedicated hosts has 132 vCores available. I1v2 uses two vCores, I2v2 uses four vCores, and I3v2 uses eight vCores per instance. Only I1v2, I2v2, and I3v2 SKU sizes are available on App Service Environment deployed on dedicated hosts. There's extra charges associated with deployment on dedicated hosts. Isolation down to the hardware level is typically not a requirement for the majority of customers. The limitations with dedicated host deployments should be considered before using the feature. To ensure a dedicated host deployment is right for you, you should review your security and compliance requirements before deployment.
 
 ## Virtual network support
 

articles/azure-netapp-files/manage-cool-access.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 08/20/2024
+ms.date: 10/10/2024
 ms.author: anfdocs
 ---
 
@@ -26,6 +26,7 @@ The storage with cool access feature provides options for the “coolness period
 * A cool-access capacity pool can contain both volumes with cool access enabled and volumes with cool access disabled.
 * To prevent data retrieval from the cool tier to the hot tier during sequential read operations (for example, antivirus or other file scanning operations), set the cool access retrieval policy to **Default** or **Never**. For more information, see [Enable cool access on a new volume](#enable-cool-access-on-a-new-volume).
 * After the capacity pool is configured with the option to support cool access volumes, the setting can't be disabled at the _capacity pool_ level. You can turn on or turn off the cool access setting at the _volume_ level anytime. Turning off the cool access setting at the volume level stops further tiering of data.  
+* Files moved to the cool tier remains there after you disable cool access on a volume. You must perform an I/O operation on _each_ file to return it to the warm tier. 
 * You can't use [large volumes](large-volumes-requirements-considerations.md) with cool access.
 * For the maximum number of volumes supported for cool access per subscription per region, see [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md#resource-limits).
 * Considerations for using cool access with [cross-region replication](cross-region-replication-requirements-considerations.md) and [cross-zone replication](cross-zone-replication-introduction.md):

articles/bastion/bastion-connect-vm-ssh-linux.md

@@ -61,16 +61,15 @@ In order to connect to the Linux VM via SSH, you must have the following ports o
 
 1. Use the following sections in this article to configure authentication settings and connect to your VM.
 
-   * [Microsoft Entra ID Authentication](#microsoft-entra-id-authentication-preview)
+   * [Microsoft Entra ID Authentication](#microsoft-entra-id-authentication)
    * [Username and password](#password-authentication)
    * [Password - Azure Key Vault](#password-authentication---azure-key-vault)
    * [SSH private key from local file](#ssh-private-key-authentication---local-file)
    * [SSH private key - Azure Key Vault](#ssh-private-key-authentication---azure-key-vault)
 
-## Microsoft Entra ID authentication (Preview)
-
+## Microsoft Entra ID authentication
 > [!NOTE]
-> Microsoft Entra ID Authentication support for SSH connections within the portal is in Preview and is currently being rolled out.
+> Microsoft Entra ID Authentication support for SSH connections within the portal is only supported for Linux VMs.
 
 If  the following prerequisites are met, Microsoft Entra ID becomes the default option to connect to your VM. If not, Microsoft Entra ID won't appear as an option.
 

articles/communication-services/quickstarts/voice-video-calling/includes/video-effects/video-effects-javascript.md

@@ -19,11 +19,12 @@ You can use the Video effects feature to add effects to your video in video call
 
 ## Using video effects
 ### Install the package
-> [!NOTE]
+> [!IMPORTANT]
 > Background blur and background replacement for **Web Desktop browsers** is in GA availability. This quickstart uses the Azure Communication Services Calling SDK version of `1.13.1` (or greater) and the Azure Communication Services Calling Effects SDK version greater than or equil to `1.0.1`. Currently desktop browser support for creating video background effects is only supported on Chrome and Edge Desktop Browser (Windows and Mac) and Mac Safari Desktop.
 
-> [!IMPORTANT]
-> Background blur and replacement for **Android Chrome mobile browser** is available in public preview starting in build [1.29.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1291-beta1-2024-08-26) and later beta WebJS SDK versions. This preview version is provided without a service-level agreement, and we don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
+> [!NOTE]
+> Background blur and background replacement for **Android Chrome and Android Edge mobile browser** is available in public preview starting in build [1.29.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1291-beta1-2024-08-26) and later beta WebJS SDK versions.
 
 Use the `npm install` command to install the Azure Communication Services Effects SDK for JavaScript.
 

articles/communication-services/resources/troubleshooting/voice-video-calling/includes/codes/call-end.md

@@ -2,15 +2,14 @@
 title: Troubleshooting Calling End codes and subcodes
 description: include file
 services: azure-communication-services
-author: slpavkov
-manager: aakanmu
+author: sloanster
 
 ms.service: azure-communication-services
 ms.subservice: azure-communication-services
-ms.date: 7/22/2024
+ms.date: 10/10/2024
 ms.topic: include
 ms.custom: include file
-ms.author: slpavkov
+ms.author: micahvivion
 ---
 
 ## Understanding calling codes and subcodes errors
@@ -40,35 +39,46 @@ There are different explanations for why a call ended. Here are the meanings of
 |--- |--- |--- |--- |--- |
 | 0 | 0 | Call ended successfully by local participant. | Success | |
 | 0 | 487 | Call ended successfully as caller canceled the call. | Success | |
-| 0 | 603 | Call ended successfully as it was declined from callee. | Success | |
-| 3100 | 410 | Call setup failed due to unexpected network problem on the client, please check client's network and retry. | UnxpectedClientError | - Ensure that you're using the latest SDK in a supported environment.<br> |
-| 3101 | 410 | Call dropped due to unexpected network problem on the client, please check client's network and retry. | UnxpectedClientError | |
-| 3112 | 410 |  Call setup failed due to network configuration problem on the client side, please check client's network configuration, and retry. | ExpectedError | |
+| 0 | 603 | Call ended successfully as it was declined from callee. | Success | Call ended because it was declined from the target user via either the client SDK, Call Automation, Graph, PSTN, or Teams reject function. |
+| 7 | 496 | Call ended as client lost network connection abruptly, and despite retrying multiple times it wasn't able to connect | ExpectedError | Browser is offline or has network issues. Check your browser's network connection and retry. |
+| 3100 | 410 | Call setup failed due to unexpected network problem on the client, check the client's network and retry. | UnxpectedClientError | Check network configuration, make sure it follows Azure Communication Calling network [requirements](../../../../../concepts/voice-video-calling/network-requirements.md). |
+| 3101 | 410 | Call dropped due to unexpected network problem on the client, check the client's network and retry. | UnxpectedClientError | Check network configuration, make sure it follows Azure Communication Calling network [requirements](../../../../../concepts/voice-video-calling/network-requirements.md).  |
+| 3111 | 410 | Call setup failed, unable to process media offer while connecting the call. | UnxpectedClientError | Try again. If issue persists, gather [call info](../../references/how-to-collect-call-info.md), [client logs](../../references/how-to-collect-client-logs.md), [browser console logs](../../references/how-to-collect-browser-verbose-log.md) and contact Azure Communication Services support. |
+| 3112 | 410 |  Call setup failed due to network configuration problem on the client side, check the client's network configuration, and retry. | ExpectedError | |
 | 4097 | 0 | Call ended for all users by the meeting organizer. | Success | |
+| 4502 | 490 | Call failed due to network connectivity problems, browser failed to complete the network HTTP request. | UnexpectedClientError | Client failed to complete HTTP request and response. Try again. If issue persists, gather [call info](../../references/how-to-collect-call-info.md), [client logs](../../references/how-to-collect-client-logs.md), [browser console logs](../../references/how-to-collect-browser-verbose-log.md) and contact Azure Communication Services support. |
+| 4506 | 408 | Call timed out. Check if the callee received and accepted the call. | UnexpectedClientError | Try again. If issue persists, gather [call info](../../references/how-to-collect-call-info.md), [client logs](../../references/how-to-collect-client-logs.md), [browser console logs](../../references/how-to-collect-browser-verbose-log.md) and contact Azure Communication Services support. |
 | 4507 | 495 | Call ended as application didn't provide valid Azure Communication Services token. | UnexpectedClientError | Ensure that your application implements token refresh mechanism correctly. |
 | 4521 | 0 | Call ended because user disconnected from the call abruptly. This might be caused by a user closing the application that hosted the call, such as a user terminated the application by closing the browser tab without proper hang-up. | ExpectedError | |
 | 5000 | 0 | Call ended for this participant. Participant removed from the conversation by another participant. | Success | |
 | 5003 | 0 | Call ended successfully, as all callee endpoints declined the call. | Success | |
-| 5300 | 0 | Call ended for this participant. Participant removed from the conversation by another participant. | Success | |
+| 5300 | 0 | Call ended for this participant as it was removed from the conversation by another participant. | Success | Call ended for this participant as another participant removed it, it could be another client, Call Automation API, Graph API. |
 | 5317 | 0 | Target participant is removed due to participant role update. | ExpectedError | |
-| 5828 | 403 | The join is not authorized for the Rooms meeting since user is not part of invitee list.	 | UnexpectedClientError | |
-| 5829 | 403 | The join is not allowed for the Rooms meeting beyond end time or prior to start time of the meeting. | UnexpectedClientError | |
+| 5828 | 403 | The join isn't authorized for the Rooms meeting since user isn't part of invitee list.	 | UnexpectedClientError | |
+| 5829 | 403 | The join isn't allowed for the Rooms meeting beyond end time or prior to start time of the meeting. | UnexpectedClientError | |
 | 5830 | 403 | Only Communication Services user is allowed to join the Rooms meeting. | ExpectedError | |
-| 7000 | 0 | Call ended by Azure Communication Services platform. | Success | |
-| 10003 | 487 | Call was accepted elsewhere, by another endpoint of this user. | Success | |
-| 10004 | 487 | Call was canceled on timeout, no callee endpoint accepted on time. Ensure that user saw the notification and try to initiate that call again. | ExpectedError | |
-| 10024 | 487 | Call ended successfully. Call declined by all callee endpoints. | Success | - Try to place the call again. |
+| 7000 | 0 | Call was ended by Azure Communication Service Call Automation API or a server bot. | Success | Call was ended by ACS Call Automation API or Graph bot. |
+| 10003 | 487 | Call was canceled for this user endpoint as it was accepted elsewhere, by another endpoint. | Success | A call was initiated to target user (start call, add participant, transfer), target user had multiple active endpoints at the same time, on one of the endpoints user accepted the call. This is normal behavior, only one endpoint can accept and connect to a call. All other endpoints receive subcode 10003 to indicate that call was already accepted. |
+| 10004 | 487 | Call was canceled on timeout, as target user didn't accept or reject it on time. Ensure that user saw the notification and/or application can handle it automatically and try to initiate that call again. | ExpectedError | Call was canceled after predefined amount of time (usually 2 minutes) as target user didn't accept or reject. |
+| 10009 | 401 | Unauthenticated identity. Ensure that your Azure Communication Services token is valid and not expired. | UnexpectedClientError | |
+| 10024 | 487 | Call ended successfully. Call declined by all callee endpoints. | Success | Try to place the call again. |
+| 10037 | 480 | Target user didn't have any endpoints registered with ACS. Ensure that target user has at least one active endpoint and  it's online. | ExpectedError | If the target user is using the Azure Communication Services Calling SDK, ensure that the SDK is initialized successfully in their client application. If the target user is a Teams user, make sure that their client is online. Make sure that the target user's identifier (CommunicationUserIdentifier, MicrosoftTeamsUserIdentifier, or MicrosoftTeamsBotIdentifier) is correct. If the Graph API `user` has property `department` set to `Microsoft Communication Application Instance` the `MicrosoftTeamsBotIdentifier` should be specified. |
 | 10057 | 408 | Call failed, callee failed to finalize call setup, most likely callee lost network or terminated the application abruptly. Ensure clients are connected and available. | ExpectedError | |
+| 10076 | 480 | Target user was registered but it wasn't online at the time of the call. Ensure that target user has at least one active endpoint and  it's online. | ExpectedError | If the target user is using the Azure Communication Services Calling SDK, ensure that the SDK is initialized successfully in their client application and their endpoint is online. If the target user is a Teams user, make sure that their client is online. |
+| 10077 | 480 | Target user was registered with ACS and/or for push notifications, but it wasn't online at the time of the call. Ensure that target user has at least one active endpoint and  it's online. | ExpectedError | If the target user is using the Azure Communication Services Calling SDK, ensure that the SDK is initialized successfully in their client application and their endpoint is online. If application leverages Push Notifications make sure they're configured correctly. If the target user is a Teams user, make sure that their client is online. |
+| 10078 | 480 | Remote client endpoint not registered or not reachable. Ensure the remote client endpoint is successfully sending network requests to Azure Communication Services. | ExpectedError | - If the target user is using the Azure Communication Services Calling SDK, ensure that the SDK is initialized successfully in their client application and their endpoint is online. If application leverages Push Notifications make sure they're configured correctly. <br> - If the target user is a Teams user, make sure that their client is online. |
+| 301004 | 410 | Participant was removed from the call by the Azure Communication Services infrastructure due to inability to establish media connectivity with Azure Communication Services infrastructure during call setup. Check user's network configuration, including local network, firewalls, VPNs configuration and try again. | UnexpectedClientError | Ensure that user's network is configured correctly, follow 'Network Recommendations' public documentation. |
 | 301005 | 410 | Participant removed from the call by the Azure Communication Services infrastructure due to loss of media connectivity with the same infrastructure. This usually happens if participant leaves the call abruptly or loses network connectivity. If the participant wants to continue the call, they can reconnect. | UnexpectedClientError | Ensure that you're using the latest SDK in a supported environment. |
+| 540000 | 0 | Call ended successfully by local PSTN caller. | Success | |
 | 510403 | 403 | Call ended, previously marked as a spam and now blocked. | ExpectedError | - Ensure that your Communication Services token is valid and not expired. <br />  - Ensure to pass in `AlternateId` in the call options. |
 | 540487 | 487 | Call ended successfully as caller canceled the call. | Success | |
 | 560000 | 0 | Call ended successfully by remote PSTN participant. | Success |Possible causes: <br /> - User ended the call. <br /> - Call ended by media agent. |
-| 560486 | 486 | Call ended because remote PSTN participant was busy. The number called was already in a call or having technical issues. |
+| 560486 | 486 | Call ended because remote PSTN participant was busy. The number called was already in a call or having technical issues. | Success | - For Direct Routing calls, check your Session Border Control logs and settings and timeouts configuration. Possible causes: The number called was already in a call or having technical issues. |
 | | 404 | Call not found. | | Ensure that the number you're calling (or call you're joining) exists. |
 | | 408 | Call controller timed out. | | Call Controller timed out waiting for protocol messages from user endpoints. Ensure clients are connected and available. |
 | | 410 | Local media stack or media infrastructure error. | | Ensure that you're using the latest SDK in a supported environment. |
 | | 430 | Unable to deliver message to client application. | | Ensure that the client application is running and available. |
 | | 480 | Remote client endpoint not registered. | | Ensure that the remote endpoint is available. |
 | | 481 | Failed to handle incoming call. | | File a support request through the Azure portal. |
-| | 490, 491, 496, 497, 498 | Local endpoint network issues. | | Check your network. |
+| | 490, 491, 496, 497, 498 | Local endpoint network issues. | | Check network configuration, make sure it follows Azure Communication Calling network [requirements](../../../../../concepts/voice-video-calling/network-requirements.md). |
 | | 500, 503, 504 | Communication Services infrastructure error. | | File a support request through the Azure portal. |