---
title: "NDS for Azure - Supported Parameters and Limits"
slug: "nds-azure-supported-parameters-limits"
updated: 2025-12-11T17:29:47Z
published: 2025-12-11T17:29:47Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nasuni.com/llms.txt
> Use this file to discover all available pages before exploring further.

# NDS for Azure - Supported Parameters and Limits

This section outlines the key parameters and operational limits of Nasuni Data Service (NDS) for Azure. These values reflect current product behavior and are intended to help customers plan and optimize their use of NDS.

## Operational Boundaries

- **Read-only access** - Data cannot be added, modified, or deleted via NDS.
- **Volume-level authentication** - Access is granted at the container/volume scope.
- **ACLs as metadata only** - Tile permissions/ACLs are presented in metadata but not enforced by NDS.
- **Empty directories** - NDS does not present directories that contain no files.

## Large File Downloads

| Condition | Limit / Guidance |
| --- | --- |
| Single Get Blob request | ≤ 1.1 GB / 1,181,116,007 bytes |
| Files > 1.1 GB | Download in parts with HTTP Range headers ```http GET /{container}/{blob} Range: bytes=0-1181116006 ``` |

**Example (2 GB file):**

- First request: `Range: bytes=0-1073741823` (first 1 GB chunk)
- Second request: `Range: bytes=1073741824-2147483647` (remaining)

## Connectivity Requirements

- Outbound traffic over SSL/443 must be allowed to the UaaS/NDS deployment from the Nasuni Management Console (NMC) and the volume owner Edge Appliances for the target volumes.
- Traffic over SSL/443 must also be allowed between the UaaS/NDS deployment and the AWS S3 bucket/Azure Storage Account backing the target Nasuni volumes.
- Recommended: **Public network access** on Azure Storage Account(s) should be in the default **Enabled**state. This allows UaaS/NDS to be deployed in the same region as the storage account, avoiding Inter-Region egress charges that would otherwise be billed to the customer’s Azure subscription.
  - Optional: **Public network access** might be set to **Enabled**, but with **Public network access scope** set to **Enable from selected networks**, allowing traffic from the public IP address of the UaaS/NDS deployment. This configuration requires UaaS/NDS to be deployed in a different region from the storage account, generating Inter-Region egress charges billable to the customer’s Azure subscription.