Merge pull request #312539 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-03 18:00 UTC

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

articles/azure-maps/azure-maps-qps-rate-limits.md

@@ -35,6 +35,7 @@ The following list shows the QPS usage limits for each Azure Maps service by Pri
 | Search service - Batch | 10 | 10 | Not Available |
 | Search service - single request | 500 | 500 | 50 |
 | Search service - single request reverse | 250 | 250 | 50 |
+| Search service - single request geocode autocomplete | 100 | Not Applicable | Not Applicable |
 | Timezone service | 50 | 50 | 50 |
 | Traffic service | 50 | 50 | 50 |
 | Weather service | 50 | 50 | 50 |

articles/azure-maps/how-to-search-for-address.md

@@ -215,7 +215,7 @@ The example in this section uses [Get Geocoding] to convert an address into lati
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
     ```http
-    GET https://atlas.microsoft.com/geocode?api-version=2025-01-01&subscription-key={Your-Azure-Maps-Subscription-key}&query=400 Broad St, Seattle, WA 98109
+    GET https://atlas.microsoft.com/geocode?api-version=2026-01-01&subscription-key={Your-Azure-Maps-Subscription-key}&query=400 Broad St, Seattle, WA 98109
     ```
 
 1. Select the **Create** button.
@@ -248,7 +248,7 @@ This example demonstrates how to use the Get Geocode Autocomplete API to search
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
     ```http
-    https://atlas.microsoft.com/geocode:autocomplete?api-version=2025-06-01-preview&query=university of w&bbox=-168,-52,5,84&subscription-key={Your-Azure-Maps-Subscription-key}
+    https://atlas.microsoft.com/geocode:autocomplete?api-version=2026-01-01&query=university of w&bbox=-168,-52,5,84&subscription-key={Your-Azure-Maps-Subscription-key}
     ```
 
 1. Select the run button, then review the response body.
@@ -271,7 +271,7 @@ Next, narrow down the area included in your search to the United States, using t
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
     ```http
-    https://atlas.microsoft.com/geocode:autocomplete?api-version=2025-06-01-preview&query=university of w&bbox=-168,-52,5,84&countryRegion=us&subscription-key={Your-Azure-Maps-Subscription-key}
+    https://atlas.microsoft.com/geocode:autocomplete?api-version=2026-01-01&query=university of w&bbox=-168,-52,5,84&countryRegion=us&subscription-key={Your-Azure-Maps-Subscription-key}
     ```
 
 1. Select the run button, then review the response body.
@@ -294,7 +294,7 @@ Next, focus your search to include more results in a specific area within the de
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
     ```http
-    https://atlas.microsoft.com/geocode:autocomplete?api-version=2025-06-01-preview&query=university of w&bbox=-168,-52,5,84&countryRegion=us&coordinates=-122.136791,47.642232&subscription-key={Your-Azure-Maps-Subscription-key}
+    https://atlas.microsoft.com/geocode:autocomplete?api-version=2026-01-01&query=university of w&bbox=-168,-52,5,84&countryRegion=us&coordinates=-122.136791,47.642232&subscription-key={Your-Azure-Maps-Subscription-key}
     ```
 
 1. Select the run button, then review the response body.
@@ -322,7 +322,7 @@ The examples in this section demonstrate the difference between searching for a
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
     ```http
-    https://atlas.microsoft.com/geocode:autocomplete?api-version=2025-06-01-preview&query=dis&coordinates=-117.920219,33.809570&subscription-key={Your-Azure-Maps-Subscription-key}
+    https://atlas.microsoft.com/geocode:autocomplete?api-version=2026-01-01&query=dis&coordinates=-117.920219,33.809570&subscription-key={Your-Azure-Maps-Subscription-key}
     ```
 
 1. Select the run button, then review the response body.
@@ -341,7 +341,7 @@ The examples in this section demonstrate the difference between searching for a
 1. When no values are provided for the `resultTypeGroups` parameter, queries can return both place and address values. If your only interested in searching for addresses, include `resultTypeGroups=address` in your request:
 
     ```http
-    https://atlas.microsoft.com/geocode:autocomplete?api-version=2025-06-01-preview&query=dis&coordinates=-117.920219,33.809570&resultTypeGroups=address&subscription-key={Your-Azure-Maps-Subscription-key}
+    https://atlas.microsoft.com/geocode:autocomplete?api-version=2026-01-01&query=dis&coordinates=-117.920219,33.809570&resultTypeGroups=address&subscription-key={Your-Azure-Maps-Subscription-key}
     ```
 
     Notice that the response contains *address* values that include:
@@ -371,15 +371,15 @@ This example demonstrates making reverse searches using a few of the optional pa
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
     ```http
-    https://atlas.microsoft.com/reverseGeocode?api-version=2025-01-01&subscription-key={Your-Azure-Maps-Subscription-key}&coordinates=-122.332700,47.591180
+    https://atlas.microsoft.com/reverseGeocode?api-version=2026-01-01&subscription-key={Your-Azure-Maps-Subscription-key}&coordinates=-122.332700,47.591180
     ```
 
 1. Select the run button, and review the response body. You should see one query result. The response includes key address information about T-Mobile Park.
   
 1. Next, add the following parameter to the request: `resultTypes=Postcode1`
 
     ```http
-    https://atlas.microsoft.com/reverseGeocode?api-version=2025-01-01&subscription-key={Your-Azure-Maps-Subscription-key}&coordinates=-122.332700,47.591180&resultTypes=Postcode1
+    https://atlas.microsoft.com/reverseGeocode?api-version=2026-01-01&subscription-key={Your-Azure-Maps-Subscription-key}&coordinates=-122.332700,47.591180&resultTypes=Postcode1
     ```
 
 1. Select the run button, and compare the results to the results returned previously. Because the requested result type is now `Postcode1`, the response doesn't include street address information, just the zip code.
@@ -395,7 +395,7 @@ This example demonstrates how to search for a cross street based on the coordina
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
   
     ```http
-    https://atlas.microsoft.com/reverseGeocode?api-version=2025-01-01&coordinates=-122.12429011774091,47.61697905124655&subscription-key={Your-Azure-Maps-Subscription-key}
+    https://atlas.microsoft.com/reverseGeocode?api-version=2026-01-01&coordinates=-122.12429011774091,47.61697905124655&subscription-key={Your-Azure-Maps-Subscription-key}
     ```
 
 1. Select the run button, and review the response body.

articles/azure-netapp-files/customer-managed-keys-cross-tenant.md

@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: how-to
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
-ms.date: 09/03/2025
+ms.date: 02/17/2026
 ms.author: anfdocs
 # Customer intent: As an IT administrator managing Azure resources across multiple tenants, I want to configure cross-tenant customer-managed keys for volume encryption in Azure NetApp Files, so that I can enhance security and control over encryption keys used for sensitive data.
 ---
@@ -91,10 +91,22 @@ The configuration process for cross-tenant customer-managed keys has portions th
 
 ### Configure the NetApp account to use your keys 
 
->[!NOTE]
->Using the `az rest` command is the only supported way to configure your NetApp account to use CMK in a different tenant.
+> [!IMPORTANT]
+> If the NetApp account is configured with same-tenant customer-managed keys, you must switch the account back to Microsoft-managed keys before configuring cross-tenant CMK. To switch, navigate to **Encryption** in the Azure portal and change the encryption key source to **Microsoft-managed key**.
 
-<!-- check API version preview -->
+#### [Portal](#tab/portal-configure)
+
+1. In the Azure portal, navigate to your NetApp account and select **Encryption**.
+1. Select **Customer-managed key** as the encryption key source.
+1. Under **Key URI**, select **Enter key URI** and provide the URI of the encryption key.
+1. Under **Identity type**, select **User-assigned**.
+1. Select **Select an identity**, then choose the user-assigned managed identity.
+1. Under **Federated client ID**, enter the application (client) ID of the multitenant application.
+1. Select **Save**.
+
+Verify that `federatedClientId` is present in the encryption properties.
+
+#### [Azure CLI](#tab/cli-configure)
 
 1. With the `az rest` command, configure the NetApp account to use CMK in a different tenant:  
 
@@ -120,17 +132,84 @@ The configuration process for cross-tenant customer-managed keys has portions th
     ```
     Once you have sent the `az rest` command, your NetApp Account has been successfully configured with cross-tenant CMK. 
 
+    Verify the configuration by running:
+
+    ```azurecli
+    az netappfiles account show --resource-group <resourceGroupName> --name <NetAppAccountName> --query "{encryption: properties.encryption}" -o json
+    ```
+
+    The output should include `federatedClientId` in the encryption identity properties.
+
+---
+
 ### Create a volume 
 
->[!NOTE]
->To create a volume using cross-tenant CMK, you must use the Azure CLI.
+#### [Portal](#tab/portal-volume)
+
+1. In the Azure portal, select **Volumes** and then select **Add volume**.
+1. Follow the instructions in [Configure network features for an Azure NetApp Files volume](configure-network-features.md):
+    * [Set the Network Features option in volume creation page](configure-network-features.md#set-the-network-features-option).
+    * The network security group for the volume's delegated subnet must allow incoming traffic from NetApp's storage VM.
+1. For a NetApp account configured with cross-tenant customer-managed keys, perform the following steps:
+    * Select **Customer-Managed Key** in the **Encryption Key Source** dropdown menu.
+    * Select **Standard** as the **Network features** option. 
+    * Select a **key vault private endpoint**. 
+1. Continue to complete the volume creation process. Refer to:
+    * [Create an NFS volume](azure-netapp-files-create-volumes.md)
+    * [Create an SMB volume](azure-netapp-files-create-volumes-smb.md)
+    * [Create a dual-protocol volume](create-volumes-dual-protocol.md)
+
+#### [Azure CLI](#tab/cli-volume)
 
-1. Create the volume using the CLI: 
+Create the volume using the CLI: 
 
 ```azurecli
 az netappfiles volume create -g <resource group name> --account-name <NetApp account name> --pool-name <pool name> --name <volume name> -l southcentralus --service-level premium --usage-threshold 100 --file-path "<file path>" --vnet <virtual network name> --subnet default --network-features Standard --encryption-key-source Microsoft.KeyVault --kv-private-endpoint-id <full resource ID to the private endpoint to the customer's vault> --debug 
 ```
 
+---
+
+## Troubleshoot cross-tenant customer-managed keys
+
+This section describes issues encountered when configuring cross-tenant CMK and the information to resolve them.
+
+### Verify cross-tenant CMK configuration
+
+To confirm whether a NetApp account is correctly configured for cross-tenant CMK, check for the presence of `federatedClientId` in the account's encryption properties.
+
+#### [Portal](#tab/portal-CMK)
+
+Navigate to your NetApp account, select **Overview**, then select **JSON View**.
+  
+If cross-tenant CMK is correctly configured, the encryption properties should include `federatedClientId`.
+
+#### [Azure CLI](#tab/cli-CMK)
+
+Run the following command:
+
+```azurecli
+az netappfiles account show \
+    --resource-group <resourceGroupName> \
+    --name <NetAppAccountName> \
+    --query "{keySource: encryption.keySource, federatedClientId: encryption.identity.federatedClientId, userAssignedIdentity: encryption.identity.userAssignedIdentity}" \
+    -o json
+```
+If `federatedClientId` is missing, the account is configured with the same-tenant CMK and not with cross-tenant CMK.
+
+---
+
+### Missing Key URI or Encryption Key Source option 
+
+**Symptom:** When creating a volume in the Azure portal, the **Encryption Key Source** dropdown menu doesn't show **Customer-Managed Key**, or fields for **Key URI**, **subscription**, or **identity type** aren't visible.
+
+**Resolution:**
+1. Verify if the NetApp account is correctly configured for cross-tenant CMK as described in [Verify cross-tenant CMK configuration](#verify-cross-tenant-cmk-configuration).
+1. If the account does not have `federatedClientId`, switch the account to Microsoft-managed keys:
+    1. In the Azure portal, navigate to the **Encryption** page.
+    1. Change the encryption key source to **Microsoft-managed key**.
+    1. Select **Save**.
+1. Reconfigure the account for cross-tenant CMK by following the steps in [Configure the NetApp account to use your keys](#configure-the-netapp-account-to-use-your-keys).
+
 ## Next steps
 * [Configure customer-managed keys](configure-customer-managed-keys.md)
-* [Understand data encryption in Azure NetApp Files](understand-data-encryption.md)
+* [Understand data encryption in Azure NetApp Files](understand-data-encryption.md)