Merge pull request #274216 from MicrosoftDocs/main

5/03/2024 AM Publish

Author: Albertyang0

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

@@ -48,7 +48,7 @@ For step-by-step guidance in setting up WebLogic Server on Azure Kubernetes Serv
 - Prepare a local machine with Unix-like operating system installed (for example, Ubuntu, Azure Linux, macOS, Windows Subsystem for Linux).
   - [Azure CLI](/cli/azure). Use `az --version` to test whether az works. This document was tested with version 2.55.1.
   - [Docker](https://docs.docker.com/get-docker). This document was tested with Docker version 20.10.7. Use `docker info` to test whether Docker Daemon is running.
-  - [kubectl](https://kubernetes-io-vnext-staging.netlify.com/docs/tasks/tools/install-kubectl/). Use `kubectl version` to test whether kubectl works. This document was tested with version v1.21.2.
+  - [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl). Use `kubectl version` to test whether kubectl works. This document was tested with version v1.21.2.
   - A Java JDK compatible with the version of WLS you intend to run. The article directs you to install a version of WLS that uses JDK 11. Azure recommends [Microsoft Build of OpenJDK](/java/openjdk/download). Ensure that your `JAVA_HOME` environment variable is set correctly in the shells in which you run the commands.
   - [Maven](https://maven.apache.org/download.cgi) 3.5.0 or higher.
   - Ensure that you have the zip/unzip utility installed. Use `zip/unzip -v` to test whether `zip/unzip` works.

articles/app-service/environment/how-to-custom-domain-suffix.md

@@ -4,7 +4,7 @@ description: Configure a custom domain suffix for the Azure App Service Environm
 author: seligj95
 ms.topic: tutorial
 ms.custom: devx-track-arm-template
-ms.date: 04/23/2024
+ms.date: 05/01/2024
 ms.author: jordanselig
 zone_pivot_groups: app-service-environment-portal-arm
 ---
@@ -33,6 +33,7 @@ The connection to the custom domain suffix endpoint needs to use Server Name Ind
 
 - ILB variation of App Service Environment v3.
 - Valid SSL/TLS certificate must be stored in an Azure Key Vault in .PFX format. For more information on using certificates with App Service, see [Add a TLS/SSL certificate in Azure App Service](../configure-ssl-certificate.md).
+- Certificate must be less than 20 kb.
 
 ### Managed identity
 
@@ -60,7 +61,7 @@ If you choose to use Azure role-based access control to manage access to your ke
 
 ### Certificate
 
-The certificate for custom domain suffix must be stored in an Azure Key Vault. The certificate must be uploaded in .PFX format. Certificates in .PEM format aren't supported at this time. App Service Environment uses the managed identity you selected to get the certificate. The key vault can be accessed publicly or through a [private endpoint](../../private-link/private-endpoint-overview.md) accessible from the subnet that the App Service Environment is deployed to. In the case of public access, you can secure your key vault to only accept traffic from the outbound IP addresses of the App Service Environment.
+The certificate for custom domain suffix must be stored in an Azure Key Vault. The certificate must be uploaded in .PFX format and be smaller than 20 kb. Certificates in .PEM format aren't supported at this time. App Service Environment uses the managed identity you selected to get the certificate. The key vault can be accessed publicly or through a [private endpoint](../../private-link/private-endpoint-overview.md) accessible from the subnet that the App Service Environment is deployed to. To learn how to configure a private endpoint, see [Integrate Key Vault with Azure Private Link](../../key-vault/general/private-link-service.md). In the case of public access, you can secure your key vault to only accept traffic from the outbound IP addresses of the App Service Environment.
 
 :::image type="content" source="./media/custom-domain-suffix/key-vault-networking.png" alt-text="Screenshot of a sample networking page for key vault to allow custom domain suffix feature.":::
 
@@ -74,9 +75,10 @@ If you rotate your certificate in Azure Key Vault, the App Service Environment p
 
 1. From the [Azure portal](https://portal.azure.com), navigate to the **Custom domain suffix** page for your App Service Environment.
 1. Enter your custom domain name.
-1. Select the managed identity you've defined for your App Service Environment. You can use either a system assigned or user assigned managed identity. You're able to configure your managed identity if you haven't done so already. You can configure the managed identity directly from the custom domain suffix page using the "Add identity" option in the managed identity selection box.
+1. Select the managed identity you define for your App Service Environment. You can use either a system assigned or user assigned managed identity. You're able to configure your managed identity if you haven't done so already. You can configure the managed identity directly from the custom domain suffix page using the "Add identity" option in the managed identity selection box.
 :::image type="content" source="./media/custom-domain-suffix/managed-identity-selection.png" alt-text="Screenshot of a configuration pane to select and update the managed identity for the App Service Environment.":::
 1. Select the certificate for the custom domain suffix.
+    1. If you use a private endpoint to access the key vault, you can't use the default key vault certificate URL the portal interface provides. You must manually enter and use the private link URL, which is in the format *https://KEY-VAULT-NAME.privatelink.vaultcore.azure.net/secrets/CERTIFICATE-NAME*.
 1. Select "Save" at the top of the page. To see the latest configuration updates, refresh the page.
 :::image type="content" source="./media/custom-domain-suffix/custom-domain-suffix-portal-experience.png" alt-text="Screenshot of an overview of the custom domain suffix portal experience.":::
 1. It takes a few minutes for the custom domain suffix configuration to be set. Check the status by selecting "Refresh" at the top of the page. The banner updates with the latest progress. Once complete, the banner will state that the custom domain suffix is configured.
@@ -88,7 +90,7 @@ If you rotate your certificate in Azure Key Vault, the App Service Environment p
 
 ## Use Azure Resource Manager to configure custom domain suffix
 
-To configure a custom domain suffix for your App Service Environment using an Azure Resource Manager template, you need to include the below properties. Ensure that you've met the [prerequisites](#prerequisites) and that your managed identity and certificate are accessible and have the appropriate permissions for the Azure Key Vault.
+To configure a custom domain suffix for your App Service Environment using an Azure Resource Manager template, you need to include the below properties. Ensure that you meet the [prerequisites](#prerequisites) and that your managed identity and certificate are accessible and have the appropriate permissions for the Azure Key Vault. If you use a private endpoint to access the key vault, you can't use the default key vault certificate URL. You must use the private link URL, which is in the format *https://KEY-VAULT-NAME.privatelink.vaultcore.azure.net/secrets/CERTIFICATE-NAME*.
 
 You need to configure the managed identity and ensure it exists before assigning it in your template. For more information on managed identities, see the [managed identity overview](../../active-directory/managed-identities-azure-resources/overview.md).
 
@@ -153,7 +155,7 @@ Alternatively, you can update your existing ILB App Service Environment using [A
 1. Scroll to the bottom of the right pane. The **customDnsSuffixConfiguration** attribute is at the bottom.
 1. Enter your values for **dnsSuffix**, **certificateUrl**, and **keyVaultReferenceIdentity**.
 1. Navigate to the **identity** attribute and enter the details associated with the managed identity you're using.
-1. Select the **PUT** button that's located at the top to commit the change to the App Service Environment.
+1. Select the **PUT** button at the top to commit the change to the App Service Environment.
 1. The **provisioningState** under **customDnsSuffixConfiguration** provides a status on the configuration update. 
 
 ::: zone-end
@@ -197,7 +199,7 @@ However, just like apps running on the public multitenant service, you can also
 
 ## Troubleshooting
 
-If your permissions or network settings for your managed identity, key vault, or App Service Environment aren't set appropriately, you aren't able to configure a custom domain suffix, and you receive an error similar to the example shown in the screenshot. Review the [prerequisites](#prerequisites) to ensure you configured the needed permissions. You also see a similar error message if the App Service platform detects that your certificate is degraded or expired.
+The App Service platform periodically checks if your App Service Environment can access your key vault and if your certificate is valid. If your permissions or network settings for your managed identity, key vault, or App Service Environment aren't set appropriately or recently changed, you aren't able to configure a custom domain suffix. You receive an error similar to the example shown in the screenshot. Review the [prerequisites](#prerequisites) to ensure you configured the needed permissions. You also see a similar error message if the App Service platform detects that your certificate is degraded or expired.
 
 :::image type="content" source="./media/custom-domain-suffix/custom-domain-suffix-error.png" alt-text="Screenshot of a sample custom domain suffix error message.":::
 

articles/azure-arc/servers/concept-log-analytics-extension-deployment.md

@@ -25,7 +25,7 @@ Review the different methods to install the VM extension using one method or a c
 
 ### Use Azure Arc-enabled servers
 
-This method supports managing the installation, management, and removal of VM extensions from the [Azure portal](manage-vm-extensions-portal.md), using [PowerShell](manage-vm-extensions-powershell.md), the [Azure CLI](manage-vm-extensions-cli.md), or with an [Azure Resource Manager (ARM) template](manage-vm-extensions-template.md).
+This method supports managing the installation, management, and removal of VM extensions (including the Azure Monitor agent) from the [Azure portal](manage-vm-extensions-portal.md), using [PowerShell](manage-vm-extensions-powershell.md), the [Azure CLI](manage-vm-extensions-cli.md), or with an [Azure Resource Manager (ARM) template](manage-vm-extensions-template.md).
 
 #### Advantages
 

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

@@ -18,7 +18,11 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 * [Azure NetApp Files backup](backup-introduction.md) is now generally available (GA).
 
-    You still must register the feature before using it for the first time. 
+    Azure NetApp Files online snapshots are enhanced with backup of snapshots. With this backup capability, you can offload (vault) your Azure NetApp Files snapshots to a Backup vault in a fast and cost-effective way, further protecting your data from accidental deletion. 
+     
+    Backup further extends Azure NetApp Files’ built-in snapshot technology; when snapshots are vaulted to a Backup vault only changed data blocks relative to previously vaulted snapshots are copied and stored, in an efficient format. Vaulted snapshots however are still represented in full and can be restored to a new volume individually and directly, eliminating the need for an iterative full-incremental recovery process.   
+
+    This feature is now generally available in all [supported regions](backup-introduction.md#supported-regions). 
 
 ## April 2024 
 

articles/communication-services/how-tos/ui-library-sdk/includes/localization/android.md

@@ -1,6 +1,6 @@
 ---
 description: Learn how to use the Calling composite on Android.
-author: jorgegarc
+author: garchiro7
 
 ms.author: jorgegarc
 ms.date: 04/03/2022
@@ -16,20 +16,38 @@ The following table lists `CallCompositeSupportedLocale` IDs for out-of-the-box
 
 |Language| CallCompositeSupportedLocale|
 |---------|---------|
-|German| `CallCompositeSupportedLocale.DE`|
-|Japanese| `CallCompositeSupportedLocale.JA`|
-|English| `CallCompositeSupportedLocale.EN_US`|
-|Chinese (Traditional)| `CallCompositeSupportedLocale.ZH_TW`|
-|Spanish |`CallCompositeSupportedLocale.ES`|
-|Chinese (Simplified) |`CallCompositeSupportedLocale.ZH_CN`|
-|Italian |`CallCompositeSupportedLocale.IT`|
-|English (United Kingdom) |`CallCompositeSupportedLocale.EN_UK`|
-|Korean |`CallCompositeSupportedLocale.KO`|
-|Turkish |`CallCompositeSupportedLocale.TR`|
-|Russian |`CallCompositeSupportedLocale.RU`|
-|French |`CallCompositeSupportedLocale.FR`|
-|Dutch |`CallCompositeSupportedLocale.NL`|
-|Portuguese |`CallCompositeSupportedLocale.PT_BR`|
+| Arabic (Saudi Arabia) | `CallCompositeSupportedLocale.AR_SA`     |
+| German (Germany)      | `CallCompositeSupportedLocale.DE_DE`     |
+| English (US)          | `CallCompositeSupportedLocale.EN_US`     |
+| English (UK)          | `CallCompositeSupportedLocale.EN_UK`     |
+| Spanish (Spain)       | `CallCompositeSupportedLocale.ES_ES`     |
+| Spanish               | `CallCompositeSupportedLocale.ES`        |
+| Finnish (Finland)     | `CallCompositeSupportedLocale.FI_FI`     |
+| French (France)       | `CallCompositeSupportedLocale.FR_FR`     |
+| French                | `CallCompositeSupportedLocale.FR`        |
+| Hebrew (Israel)       | `CallCompositeSupportedLocale.IW_IL`     |
+| Italian (Italy)       | `CallCompositeSupportedLocale.IT_IT`     |
+| Italian               | `CallCompositeSupportedLocale.IT`        |
+| Japanese (Japan)      | `CallCompositeSupportedLocale.JA_JP`     |
+| Japanese              | `CallCompositeSupportedLocale.JA`        |
+| Korean (Korea)        | `CallCompositeSupportedLocale.KO_KR`     |
+| Korean                | `CallCompositeSupportedLocale.KO`        |
+| Dutch (Netherlands)   | `CallCompositeSupportedLocale.NL_NL`     |
+| Dutch                 | `CallCompositeSupportedLocale.NL`        |
+| Norwegian (Bokmål)    | `CallCompositeSupportedLocale.NB_NO`     |
+| Polish (Poland)       | `CallCompositeSupportedLocale.PL_PL`     |
+| Polish                | `CallCompositeSupportedLocale.PL`        |
+| Portuguese (Brazil)   | `CallCompositeSupportedLocale.PT_BR`     |
+| Portuguese            | `CallCompositeSupportedLocale.PT`        |
+| Russian (Russia)      | `CallCompositeSupportedLocale.RU_RU`     |
+| Russian               | `CallCompositeSupportedLocale.RU`        |
+| Swedish (Sweden)      | `CallCompositeSupportedLocale.SV_SE`     |
+| Turkish (Turkey)      | `CallCompositeSupportedLocale.TR_TR`     |
+| Turkish               | `CallCompositeSupportedLocale.TR`        |
+| Chinese (Simplified)  | `CallCompositeSupportedLocale.ZH_CN`     |
+| Chinese (Traditional) | `CallCompositeSupportedLocale.ZH_TW`     |
+| Chinese               | `CallCompositeSupportedLocale.ZH`        |
+
 
 ### Localization provider
 

articles/cosmos-db/mongodb/TOC.yml

@@ -16,6 +16,10 @@
           href: ru/introduction.md
         - name: API versions
           items:
+            - name: API version 6.0
+              href: feature-support-60.md
+            - name: API version 5.0
+              href: feature-support-50.md
             - name: API version 4.2
               href: feature-support-42.md
             - name: API version 4.0

articles/cosmos-db/mongodb/change-log.md

@@ -16,7 +16,15 @@ The Change log for the API for MongoDB is meant to inform you about our feature
 
 ## Azure Cosmos DB for MongoDB updates
 
-### Azure Cosmos DB for MongoDB vCore (with 5.0 support) (Preview)
+
+### Azure Cosmos DB for MongoDB RU supports versions 5.0 & 6.0
+
+Azure Cosmos DB for MongoDB RU now supports MongoDB versions 5.0 and 6.0, offering expanded coverage for MongoDB.
+
+[Read more on Mongo 5.0](./feature-support-50.md)
+[Read more on Mongo 6.0](./feature-support-60.md)
+
+### Azure Cosmos DB for MongoDB vCore (with 5.0 support)
 
 Azure Cosmos DB for MongoDB vCore supports many new features such as distributed ACID transactions, higher limits for unsharded collections and for shards themselves, improved performance for aggregation pipelines and complex queries, and more.
 

articles/cosmos-db/mongodb/error-codes-solutions.md

@@ -23,6 +23,7 @@ The following article describes common errors and solutions for deployments usin
 |------------|----------------------|--------------|-----------|
 | 2 | BadValue | One common cause is that an index path corresponding to the specified order-by item is excluded or the order by query doesn't have a corresponding composite index that it can be served from. The query requests a sort on a field that isn't indexed. | Create a matching index (or composite index) for the sort query being attempted. |
 | 2 | Transaction isn't active | The multi-document transaction surpassed the fixed 5-second time limit. | Retry the multi-document transaction or limit the scope of operations within the multi-document transaction to make it complete within the 5-second time limit. |
+| 9 | FailedToParse | Indicates that the Cosmos DB server was unable to interpret or process a parameter because the provided input did not conform to the expected or supported format. | Ensure only valid and supported parameters are included in your queries. 
 | 13 | Unauthorized | The request lacks the permissions to complete. | Ensure you're using the correct keys.  |
 | 26 | NamespaceNotFound | The database or collection being referenced in the query can't be found. | Ensure your database/collection name precisely matches the name in your query.|
 | 50 | ExceededTimeLimit | The request has exceeded the timeout of 60 seconds of execution. |  There can be many causes for this error. One of the causes is when the currently allocated request units capacity isn't sufficient to complete the request. This can be solved by increasing the request units of that collection or database. In other cases, this error can be worked-around by splitting a large request into smaller ones. Retrying a write operation that has received this error may result in a duplicate write. <br><br>If you're trying to delete large amounts of data without impacting RUs: <br>- Consider using TTL (Based on Timestamp): [Expire data with Azure Cosmos DB's API for MongoDB](time-to-live.md) <br>- Use Cursor/Batch size to perform the delete. You can fetch a single document at a time and delete it through a loop. This will help you slowly delete data without impacting your production application.|