Merge pull request #298765 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

articles/app-service/tutorial-java-tomcat-connect-managed-identity-postgresql-database.md

@@ -7,7 +7,7 @@ ms.date: 06/04/2024
 author: KarlErickson
 ms.author: karler
 ms.reviewer: edburns
-ms.custom: passwordless-java, service-connector, devx-track-azurecli, devx-track-extended-java, AppServiceConnectivity
+ms.custom: passwordless-java, service-connector, devx-track-azurecli, devx-track-java, AppServiceConnectivity
 ---
 
 # Tutorial: Connect to a PostgreSQL Database from Java Tomcat App Service without secrets using a managed identity

articles/azure-netapp-files/azacsnap-cmd-ref-configure.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: reference
-ms.date: 04/01/2025
+ms.date: 04/23/2025
 ms.author: phjensen
 ---
 
@@ -243,7 +243,7 @@ When you add an *SAP HANA database* to the configuration, the following values a
 
 - `HANA SID` (JSON key: `sid`): The SAP HANA system ID (SID).
 - `HANA Instance Number` (JSON key: `instanceNumber`): The SAP HANA instance number.
-- `HANA HDB User Store Key` (JSON key: `hdbUserStoreName`): The SAP HANA user configured with permissions to run database backups.
+- `HANA HDB User Store Key` (JSON key: `hdbUserStoreName`): The SAP HANA KEY as shown by the `hdbuserstore List` command which uses the KEY to link the USER with permissions to run database backups to the ENV (hostname and port).  The [Enable communication with database](azacsnap-configure-database.md?tabs=sap-hana#enable-communication-with-the-database) section provides further details and examples.
 - `HANA Server's Address` (JSON key: `serverAddress`): The SAP HANA server's host name or IP address.
 - `Do you need AzAcSnap to automatically disable/enable backint during snapshot`: Defaults to `n` (no). You can set it to `y` (yes) to allow AzAcSnap to disable or re-enable the Backint interface. The [Backint coexistence](#backint-coexistence) section in this article explains this option in more detail.
 

articles/azure-netapp-files/azacsnap-configure-database.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/01/2025
+ms.date: 04/23/2025
 ms.author: phjensen
 ---
 
@@ -89,9 +89,12 @@ The following example commands set up a user (`AZACSNAP`) in SYSTEMDB on an SAP
     KEY FILE : /home/azacsnap/.hdb/sapprdhdb80/SSFS_HDB.KEY
 
     KEY AZACSNAP
-    ENV : <IP_address_of_host>:
-    USER: AZACSNAP
+      ENV : <IP_address_of_host>:
+      USER: AZACSNAP
     ```
+    
+    > [!IMPORTANT]
+    > The value of the `KEY` field is used for the configuration question "What is the SAP HANA HDB User Store Key (e.g. `hdbuserstore List`)?".
 
 ### Using SSL for communication with SAP HANA
 

articles/cloud-services-extended-support/enable-key-vault-virtual-machine.md

@@ -6,7 +6,7 @@ ms.service: azure-cloud-services-extended-support
 author: msmbaldwin
 ms.author: mbaldwin
 ms.reviewer: gachandw
-ms.date: 07/24/2024
+ms.date: 04/23/2025
 # Customer intent: As an IT administrator, I want to configure the Key Vault VM extension for Azure Cloud Services, so that I can automate certificate management and ensure timely updates for secured operations.
 ---
 

articles/communication-services/resources/troubleshooting/voice-video-calling/general-troubleshooting-strategies/includes/server-code-subcode.md

@@ -24,7 +24,7 @@ ms.subservice: calling
 | 4097 | 0 | Call ended for all users by the meeting organizer. | Success | |
 | 4507 | 495 | Call ended as application didn't provide valid Azure Communication Services token. | UnexpectedClientError |- Ensure that your application implements token refresh mechanism correctly. |
 | 5000 | 0 | Call ended for this participant as it was removed from the conversation by another participant. | Success | |
-| 5003 | 0 | Call ended successfully, as all callee endpoints declined the call. | Success | |
+| 5003 | 0 | Call was ended by Azure Communication Service as the call has ended. | Success | |
 | 5300 | 0 | Call ended for this participant as it was removed from the conversation by another participant. | Success | |
 | 7000 | 0 | Call ended by Azure Communication Services platform. | Success | |
 | 10003 | 487 | Call was accepted elsewhere, by another endpoint of this user. | Success | |

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

@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting Calling End codes and subcodes
+title: Understanding calling codes and subcodes errors
 description: include file
 services: azure-communication-services
 author: sloanster
@@ -51,7 +51,7 @@ There are different explanations for why a call ended. Here are the meanings of
 | 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 | |
+| 5003 | 0 | Call was ended by Azure Communication Service as the call has ended. | 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 isn't authorized for the Rooms meeting since user isn't part of invitee list.	 | UnexpectedClientError | |
@@ -61,6 +61,7 @@ There are different explanations for why a call ended. Here are the meanings of
 | 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 | |
+| 71005 | 401 | Call failed due to a validation error in Azure Communication Services. Try again, if issue persists, contact Azure Communication Services support. | 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 | |

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

@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting Calling SDK and codes
+title: Understanding calling codes and subcodes errors
 description: include file
 services: azure-communication-services
 author: slpavkov
@@ -83,6 +83,7 @@ For client errors, if the resultCategories property is `ExpectedError`, the erro
 | 43209 | 405 | Failed to render video stream, VideoStreamRenderer was disposed during initialization process. | ExpectedError ||
 | 43210 | 400 | Failed to dispose VideoStreamRenderer because it's already disposed. | ExpectedError ||
 | 43220 | 400 | Failed to create view, maximum number of active `RemoteVideoStream` views already reached. You can dispose of a previous one in order to create new one. | ExpectedError | Learn more about [how to properly support the best number of incoming video streams](../../../../../concepts/troubleshooting-info.md?tabs=csharp%2Cjavascript%2Cdotnet#enable-and-access-call-logs) |
+| 71005 | 401 | Call failed due to a validation error in Azure Communication Services. Try again, if issue persists, contact Azure Communication Services support. | UnexpectedClientError ||
 | | 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. |
 | | 487 | Call canceled, locally declined, ended due to an endpoint mismatch issue, or failed to generate media offer. | | Expected behavior. |