Merge pull request #306877 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-14 11:00 UTC

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

articles/azure-maps/release-notes-map-control.md

@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: Release notes for the Azure Maps Web SDK. 
 author: sinnypan
 ms.author: sipa
-ms.date: 04/09/2025
+ms.date: 10/15/2025
 ms.topic: reference
 ms.service: azure-maps
 ms.subservice: web-sdk
@@ -16,6 +16,12 @@ This document contains information about new features and other changes to the M
 
 ## v3 (latest)
 
+### [3.7.0] (CDN: October 15, 2025, npm: TBA)
+
+#### New features
+
+- Add support for zoom level 0, allowing users to view the entire globe within a small map canvas.
+
 ### [3.6.1] (CDN: April 7, 2025, npm: April 9, 2025)
 
 #### Bug fixes

articles/azure-netapp-files/TOC.yml

@@ -25,6 +25,8 @@
         href: network-attached-storage-protocols.md
       - name: Understand SMB support 
         href: sever-message-block-support.md
+      - name: Understand Object REST API 
+        href: object-rest-api-introduction.md
       - name: Understand NAS permissions 
         items:
         - name: Understand NAS share permissions 
@@ -331,6 +333,16 @@
       items:
       - name: Create a dual-protocol volume 
         href: create-volumes-dual-protocol.md
+    - name: Manage object REST API access
+      items:
+      - name: Configure object REST API access
+        href: object-rest-api-access-configure.md
+      - name: Connect to Azure Databricks 
+        href: object-rest-api-databricks.md
+      - name: Connect to OneLake
+        href: object-rest-api-onelake.md
+      - name: Access volumes with an S3-compatible client 
+        href: object-rest-api-browser.md
     - name: Migrate volumes to Azure NetApp Files
       href: migrate-volumes.md
     - name: Manage volume access and encryption 

articles/azure-netapp-files/azure-netapp-files-introduction.md

@@ -27,6 +27,9 @@ Azure NetApp Files supports SMB, NFS, and dual protocols volumes and can be used
 - Databases.
 - High-performance computing.
 
+>[!NOTE]
+>Azure NetApp Files also supports integrations with S3. For more information, see [Understand object REST API](object-rest-api-introduction.md).
+
 For more information about workload solutions using Azure NetApp Files, see [Solution architectures using Azure NetApp Files](azure-netapp-files-solution-architectures.md).
 
 ## Performance, cost optimization, and scale
@@ -36,7 +39,7 @@ Azure NetApp Files is designed to provide high-performance file storage for ente
 | Functionality | Description | Benefit |
 | - | - | - | 
 | In-Azure bare-metal flash performance | Fast and reliable all-flash performance with submillisecond latency. | Run performance-intensive workloads in the cloud with on-premises infrastructure-level performance.
-| Multi-protocol support | Supports multiple protocols, including NFSv3, NFSv4.1, SMB 3.0, SMB 3.1.1, and simultaneous dual-protocol. | Seamlessly integrate with existing infrastructure and workflows without compatibility issues or complex configurations. |
+| Multi-protocol support | Supports multiple protocols, including NFSv3, NFSv4.1, SMB 3.0, SMB 3.1.1, and simultaneous dual-protocol. Also supports integration with S3. | Seamlessly integrate with existing infrastructure and workflows without compatibility issues or complex configurations. Azure Netapp Files also integrates with S3 using the [object REST API](object-rest-api-introduction.md). |
 | Four adaptable performance tiers (Flexible, Standard, Premium, Ultra) | Four performance tiers with dynamic service-level change capability based on workload needs, including cool access for cold data. | Choose the right performance level for workloads and dynamically adjust performance without overspending on resources.
 | Small-to-large volumes | Easily resize file volumes from 100 GiB up to 100 TiB without downtime. | Scale storage as business needs grow without over-provisioning, avoiding upfront cost.
 | Small-to-large volumes | Easily resize file volumes from 50 GiB up to 100 TiB without downtime. | Scale storage as business needs grow without over-provisioning, avoiding upfront cost.

articles/azure-netapp-files/includes/large-volumes-notice.md

@@ -9,6 +9,7 @@ ms.custom: include file
 # azure-netapp-files-create-volumes-smb
 # create-volumes-dual-protocol
 # azure-netapp-files-create-volumes
+# object-rest-api-access-configure.md
 # Customer intent: As a cloud administrator, I want to understand the volume quota options for Azure NetApp Files, so that I can select the appropriate volume size and ensure compliance with regional capacity requirements.
 ---
 

articles/azure-netapp-files/media/object-rest-api-access-configure/certificate-management.png

@@ -0,0 +1,144 @@
+---
+title: Configure object REST API access in Azure NetApp Files 
+description: Learn how to configure object REST API access to manage S3 objects in Azure NetApp Files. 
+services: azure-netapp-files
+author: b-ahibbard
+ms.service: azure-netapp-files
+ms.topic: how-to
+ms.date: 10/13/2025
+ms.author: anfdocs
+---
+
+# Configure object REST API access in Azure NetApp Files (preview)
+
+Azure NetApp Files supports access to S3 objects with the [object REST API](object-rest-api-introduction.md) feature. With the object REST API feature, you can connect to services including Azure AI Search, Azure AI Foundry, Azure Databricks, OneLake, and others.
+
+## Considerations
+
+* Editing a bucket isn't currently supported. If you need to edit a bucket, you should instead create a new bucket with the same name as the one you want to edit then adjust the properties. 
+
+## Register the feature 
+
+The object REST API access feature in Azure NetApp Files is currently in preview. You need to register the feature before using it for the first time. Feature registration can take up to 60 minutes to complete.
+
+You must submit a [waitlist request](https://forms.office.com/r/pTpTESUSZb) to use the object REST API feature. 
+
+You can check the status of the feature registration with the command:
+
+```azurepowershell-interactive
+Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFEnableObjectRESTAPI
+```
+
+## Create the self-signed certificate
+
+You must generate a PEM-formatted SSL certificate. You can create the SSL certificate in the Azure portal or with a script.  
+
+<!-- DNS? -->
+
+### [Portal](#tab/portal)
+
+See the [Azure Key Vault documentation for creating a certificate](/azure/key-vault/certificates/tutorial-import-certificate). 
+
+When creating the certificate, ensure the **Content Type** is set to PEM. In the **Subject** field, set the Common Name (CN) to the IP address or fully qualified domain name (FQDN) of your Azure NetApp Files object REST API-enabled endpoint.
+
+### [Script](#tab/script)
+
+This script creates a certificate locally. Set the computer name `CN=` to the IP address or fully qualified domain name (FQDN) of your object REST API-enabled endpoint. This script creates a folder that includes the necessary PEM file and private keys. 
+
+Create and run the following script:
+
+```bash
+#!/bin/sh
+# Define certificate details 
+CERT_DAYS=365 
+RSA_STR_LEN=2048 
+CERT_DIR="./certs" 
+KEY_DIR="./certs/private" 
+CN="mylocalsite.local" 
+
+# Create directories if they don't exist 
+mkdir -p $CERT_DIR 
+mkdir -p $KEY_DIR 
+
+# Generate private key 
+openssl genrsa -out $KEY_DIR/server-key.pem $RSA_STR_LEN 
+
+# Generate Certificate Signing Request (CSR) 
+openssl req -new -key $KEY_DIR/server-key.pem -out $CERT_DIR/server-req.pem -subj "/C=US/ST=State/L=City/O=Organization/OU=Unit/CN=$CN" 
+
+# Generate self-signed certificate 
+openssl x509 -req -days $CERT_DAYS -in $CERT_DIR/server-req.pem -signkey $KEY_DIR/server-key.pem -out $CERT_DIR/server-cert.pem 
+
+echo "Self-signed certificate created at $CERT_DIR/server-cert.pem"
+```
+--- 
+
+## Enable object REST API access
+
+To enable object REST API, you must create a bucket. 
+
+1. From your NetApp volume, select **Buckets**. 
+1. To create a bucket, select **+Create**. 
+1. Provide the following information for the bucket:
+    * **Name**
+
+        Specify the name for your bucket. Refer to [Naming rules and restrictions for Azure resources](../azure-resource-manager/management/resource-name-rules.md#microsoftnetapp) for naming conventions.
+    * **Path**
+
+        The subdirectory path for object REST API access. For full volume access, leave this field blank or use `/` for the root directory.
+    * **User ID (UID)**
+
+        The UID used to read the bucket.
+
+    * **Group ID (GID)**
+
+        The GID used to read the bucket.
+
+    * **Permissions**
+
+        Select Read or Read-Write. 
+
+    :::image type="content" source="./media/object-rest-api-access-configure/create-bucket.png" alt-text="Screenshot of create a bucket menu." lightbox="./media/object-rest-api-access-configure/create-bucket.png":::
+
+1. If you haven't provided a certificate, upload your PEM file. 
+
+    To upload a certificate, provide the following information:
+
+    * **Fully qualified domain name**
+
+        Enter the fully qualified domain name. 
+
+    * **Certificate source**
+
+        Upload the appropriate certificate. Only PEM files are supported. 
+
+    Select **Save**. 
+
+1. Select **Create**. 
+
+<!-- 
+## Edit a bucket
+
+After you create a bucket, you have the option to modify the user identifier (UID or GID) of the bucket.
+
+1. In your NetApp account, navigate to **Buckets**. 
+1. Select the three dots `...` at the end of the line next to the name of the bucket you want to modify then select **Edit**. 
+1. Enter the new User ID or Group ID for the bucket. 
+1. Select **Save**. 
+-->
+
+## Delete a bucket
+
+Deleting a bucket is a permanent operation. You can't recover the bucket once it's deleted. 
+
+1. In your NetApp account, navigate to **Buckets**. 
+1. Select the checkbox next to the bucket you want to delete. 
+1. Select **Delete**. 
+1. In the modal, select **Delete** to confirm you want to delete the bucket. 
+
+## Next steps 
+
+* [Understand object REST API](object-rest-api-introduction.md)
+* [Connect to Azure Databricks](object-rest-api-databricks.md)
+* [Connect to an S3 browser](object-rest-api-browser.md)
+* [Connect to OneLake](object-rest-api-onelake.md)

articles/azure-netapp-files/media/object-rest-api-access-configure/create-bucket.png

@@ -0,0 +1,81 @@
+---
+title: Access an Azure NetApp Files object REST API-enabled volume with S3-compatible clients
+description: Learn how to access Azure NetApp Files object REST API-enabled volumes from S3-compatible clients
+services: azure-netapp-files
+author: b-ahibbard
+ms.service: azure-netapp-files
+ms.topic: how-to
+ms.date: 10/13/2025
+ms.author: anfdocs
+---
+# Access an Azure NetApp Files object REST API-enabled volume with S3-compatible clients
+
+You can use Azure NetApp Files' object REST API with an S3-compatible client, taking advantage of secure SSL communication and seamless data management.
+
+You must install a certificate on your machine before accessing the bucket with S3-compatible clients. This document covers accessing the bucket with the S3 Browser and AWS CLI. 
+
+## Install the certificate in the Trusted Root Certification Authorities
+
+Before accessing your object REST API-enabled volume with an S3-compatible client, you must install the certificate. 
+
+1. Open the Edge browser on your client system and navigate to your bucket's URL: `https://<your-bucket-endpoint-IP-or-FQDN>`.
+1. Select the lock icon in the address bar then select **Certificate (Valid)**.
+1. In the certificate dialog, select the **Details** tab then **Copy to file (or Export)**. Follow the steps in the export wizard, ensuring you choose the DER encoded binary X.509 (.CER) format. Save the .CER file to your local machine. 
+1. To install the certificate, select the .CER file on your local machine. 
+1. In the Certificate window, select **Install Certificate**. In the installation wizard, choose **Local machine** as your installation destination. Note that this requires administrator privileges.
+    In the Certificate Store screen, select **Place all certificates in the following store** then **Browse** and choose **Trusted Root Certification Authorities**.
+1. When you complete the steps in the installation wizard, a dialog confirms the certificate was installed successfully. 
+
+## Access files with S3 Browser
+
+1. Download and install [S3 Browser](https://s3browser.com/download.aspx).
+2. Add a [new account for S3-compatible storage](https://s3browser.com/s3-compatible-storage.aspx).
+    When adding the new account, follow these guidelines:
+
+    * **REST Endpoint**: Enter the endpoint URL for your volume: `https://<your-bucket-endpoint-IP-or-FQDN>`.
+    * **Access Key ID**: Use the access key created when you generated the bucket on the NFS volume.
+    * **Secret access key**: Use corresponding secret key from when you generated the bucket.
+    * Select **Encrypt Access Keys with a Password** and **Use secure transfer (SSL/TLS)**.
+
+1. After adding the account, verify the connection. In the S3 Browser, select your newly added account in the **Accounts** menu. If the connection was successful, you see your buckets and can manage the objects. 
+
+## Access files with the AWS CLI
+
+1. Download the AWS CLI:
+    * For Windows, [download the Microsoft Software Installer and run it]( https://aws.amazon.com/cli/).
+    *  For Linux, install the AWS CLI with CURL:
+    ```curl 
+    curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
+    unzip awscliv2.zip
+    sudo ./aws/install
+    ```
+1. Verify the installation succeeded with the command `aws --version`. The expected output is:
+    ```
+    aws-cli/2.x.x Python/3.x.x Linux/…
+    ```
+1. Configure the AWS CLI with the command `aws configure`.
+    When prompted, provide:
+    * **AWS access key ID** - Use the access key created when you generated the bucket on the NFS volume.
+    * **AWS secret access key** - The corresponding secret key from when you generated the bucket.
+    * **Default region name**: us-east-1 
+    * **Output**: JSON
+    >[!NOTE]
+    >When using AWS CLI with Azure NetApp Files buckets, always use us-east-1 as the default region name.
+1. List the buckets:
+    ```
+    aws s3 ls --endpoint-url https://<your-bucket-endpoint-IP-or-FQDN> --no-verify-ssl
+    ```
+1. List the objects in a bucket:
+    ```
+    aws s3 ls --endpoint-url https://<your-bucket-endpoint-IP-or-FQDN>(https://<your-bucket-endpoint-IP-or-FQDN>) s3://<bucket-name>/ --no-verify-ssl
+    ```
+1. Copy an object from a bucket to your local workstation:
+    ```
+    aws s3 cp --endpoint-url https://<your-bucket-endpoint-IP-or-FQDN> s3://<bucket-name>/<object-name> ./<local-object-name> --no-verify-ssl
+    ```
+
+## More information
+
+* [Configure object REST API](object-rest-api-access-configure.md)
+* [Understand object REST API](object-rest-api-introduction.md)
+* [AWS CLI command reference](https://docs.aws.amazon.com/cli/latest/reference/s3/ls.html)