NEW File Shares Resource Types

Key Concepts

• Azure File Share as a standalone resource
• Storage Account as a container for multiple services (blobs, queues, tables, file shares)
• Shared Data Quota (IOPS, throughput) at the storage account level
• Shared Management Quota at the storage account level
• Microsoft.fileshares resource provider
• NFS protocol
• Provisioned v2 model (separate IOPS and throughput settings)
• Public vs. Private Endpoints
• Management Limits (bucket model with refill rate)
• Data Plane Limits
• Cost Allocation
• Storage Account Access Keys

1. Introduction: The Evolution of Azure File Shares

• The video addresses the misconception that Azure file shares are new, clarifying that they have existed as a service within Azure Storage Accounts.
• The key distinction is the introduction of a standalone "fileshare" resource, independent of a storage account.
• Currently, file shares are created as part of a storage account, which also supports blobs, queues, and tables.
• The storage account has many options that apply to all the services it offers, even if you only want a file share.

2. The Problem with Storage Account-Based File Shares

• Complexity: Creating a storage account involves numerous configuration options (performance tier, redundancy, networking, data protection, encryption), many of which are irrelevant if the sole purpose is a file share.
• Shared Limits: Storage accounts have shared data quotas (IOPS, throughput) and management quotas, impacting all file shares within that account.
• Networking Configuration: Networking configurations (private endpoints) apply at the storage account level, shared by all file shares.
• Cost Allocation: Difficult to accurately attribute costs to specific departments using different file shares within the same storage account. Requires creating multiple storage accounts for proper chargeback.
• Security: Storage account-level access keys pose a security risk, granting broad access to all services within the account.

3. The Solution: Standalone Azure File Share Resource

• Microsoft has introduced a new "fileshare" resource with its own resource provider (Microsoft.fileshares).
• This allows creating a file share directly, abstracting away the underlying storage account complexities.
• The top-level resource created under a resource group is now a fileshare.

4. Creating a Standalone File Share: A Step-by-Step Guide

• The video demonstrates creating a new file share via the Azure portal.
• Steps:
  1. Search for "fileshares" in the Azure portal.
  2. Select a resource group.
  3. Provide a unique name for the file share within the resource group (e.g., "sav fileshare 01").
  4. Choose the file share type (currently only SSD and NFS protocol are supported).
  5. Provision capacity.
  6. Select redundancy (LRS or ZRS).
  7. Optionally, manually set IOPS and throughput (similar to provisioned v2 model).
  8. Configure networking:
     • Enable/disable public endpoints.
     • Add private endpoints.
     • Restrict public endpoint access to specific subnets (recommended for NFS).
  9. Create the file share.

5. Benefits of Standalone File Shares

• Simplified Settings: Fewer configuration options, streamlining the creation process.
• Dedicated Network Configuration: Private endpoints are specific to the file share.
• Enhanced Security: No storage account key is required, improving security.
• Precise Cost Tracking: Easier cost allocation as each file share is a separate resource.
• Independent Limits: File shares have their own management and data plane limits.

6. Limits and Pricing

• Management Limits:
  • Follow the Azure Resource Manager model (bucket with refill rate).
  • Maximum bucket size for management reads: 375 operations.
  • Refill rate: 37 operations per second.
  • Similar limits apply to write and delete operations.
• Data Plane Limits: Each file share has its own data plane limits.
• Pricing: The pricing is the same as the regular provisioned v2 pricing for SSD NFS.

7. Use Cases and Considerations

• The standalone file share resource is ideal when a simple file share is needed without the complexities of a full storage account.
• Current Limitations: The CSI driver for AKS is not currently available for the new file share resource (but is planned).
• If a feature is missing, continue using file shares within storage accounts.
• As the standalone file share resource matures and gains more features, it will become a more attractive option.

8. Notable Quotes

• "John, you're insane. We already have file shares in Azure." - Hypothetical YouTube comment, highlighting the existing confusion.
• "So what we now have is the ability to create a file share. So this becomes a new type of resource with a new resource provider in Azure." - Emphasizing the key change.
• "There is no storage account key that can go and get access to this. So this is really the most secure way of doing this." - Highlighting the security benefits.

9. Technical Terms and Concepts

• Azure Storage Account: A container for various storage services (blobs, queues, tables, file shares).
• Azure File Share: A network file share service offered by Azure.
• IOPS (Input/Output Operations Per Second): A measure of storage performance.
• Throughput: The rate at which data can be transferred.
• NFS (Network File System): A distributed file system protocol.
• SMB (Server Message Block): A network file sharing protocol.
• Private Endpoint: A network interface that connects you privately and securely to a service powered by Azure Private Link.
• Public Endpoint: A publicly accessible endpoint for a service.
• CSI Driver (Container Storage Interface Driver): A driver that allows container orchestration systems (like Kubernetes) to access storage resources.
• AKS (Azure Kubernetes Service): A managed Kubernetes service in Azure.
• LRS (Locally Redundant Storage): Replicates data three times within a single data center.
• ZRS (Zone-Redundant Storage): Replicates data across multiple availability zones within a region.
• GA (Generally Available): A product or feature that is fully released and supported for production use.

10. Synthesis/Conclusion

The introduction of the standalone Azure File Share resource represents a significant improvement in usability, security, and cost management. By decoupling file shares from the complexities of storage accounts, Microsoft has provided a more streamlined and efficient solution for organizations that primarily need file sharing capabilities. While some features are still under development, the new resource promises to become the preferred method for deploying and managing Azure file shares as it reaches general availability and gains broader feature support. The key takeaway is the shift from file shares being a service within a storage account to a first-class resource in Azure.