Azure Solutions Architecture · AZ-305 · Architecture Case Studies · by Raushan Ranjan, MCT
Imagine a company where all the digital files are stuffed into physical file cabinets. Product photos, marketing brochures, and HR documents are all in one messy room. The website team has to physically "fetch" photos for the online store, slowing everything down. The marketing team can’t access files from home, and the legal department needs a locked vault for sensitive documents.
This is the digital equivalent of a clunky on-premises file system: slow, expensive, inflexible, and not built for modern business needs. The goal is to find a simple, single solution in the cloud that solves all these issues.
Part 1: The Best Solution - The All-in-One Approach
The solution uses a single, smart storage system to handle all the different file types in the most efficient and cost-effective way.
The Analogy: A Digital Self-Storage Facility 📦
Think of Azure as a massive, high-tech self-storage company. We're going to rent a single, large storage unit called an Azure Storage Account. Inside this unit, we'll have different types of storage containers, each with its own rules and features, so we can store different items in the right place.
- Azure Blob Storage: This is like a massive, empty warehouse where you can throw in any item—photos, videos, or documents—without needing a specific label or shelf number. We'll use this for media and corporate documents.
- Azure Files: This is like a dedicated, shared filing cabinet that everyone in your office can access from anywhere, just like a network drive. We'll use this for the marketing team's documents.
Part 2: Designing the Solution for Each File Type
For Media Files (Website Photos & Videos)
The Problem: The website is slow because files are stored locally, and access patterns are unpredictable.
The Solution: Put all media files in Azure Blob Storage. We'll use access tiers to save money. We'll keep the most popular, frequently accessed files (like a best-selling product) in the Hot Tier.
Cost Savings: We will create a lifecycle management policy. This is like a smart robot that automatically moves files to a cheaper storage unit if they haven't been touched in a while. After 30 days of no access, the robot moves a file to the Cool Tier, and after 180 days, it moves it to the Archive Tier.
For Marketing Literature (Employee Mapped Drive)
The Problem: Employees need to access files via a familiar mapped drive, but also from home.
The Solution: Use Azure Files. This service gives employees a cloud-based file share that they can connect to as if it were a local network drive, making the transition seamless.
Why it fits: Azure Files is built specifically for this hybrid use case, allowing both internal and external access to the same file share without a complicated setup.
For Corporate Documents (Internal Web App)
The Problem: Documents need to be stored cheaply for compliance, and some must be locked for a specific period of time due to legal requirements.
The Solution: Store these documents in Azure Blob Storage.
Cost & Compliance: Initially, they can be in the Cool Tier. A lifecycle policy will move them to the cheap Archive Tier after a year. We'll use Immutable Storage with a time-based retention policy to lock the files, preventing anyone from deleting or changing them for the required number of years. For legal investigations, a legal hold can be placed on a file to ensure it is not deleted until the hold is manually removed.
Part 3: Why This Solution is the Best Fit
Solution 1: The All-in-One Approach (Recommended)
This solution is simple, smart, and saves money without sacrificing performance or security. By using a single Azure Storage Account, we centralize control, simplify management, and reduce costs. A standard storage account with access tiers is more than enough for most use cases and is far more affordable.
Solution 2: The Specialized Solution (Not Recommended)
This approach would involve using a separate, high-performance Premium Block Blob Storage account just for the public website's media files and a second, standard account for everything else. This adds significant cost and complexity to management and security. This is like buying a Ferrari for grocery shopping when a perfectly good family car would do the job.
Part 4: Aligning with the Well-Architected Framework
Our solution is built on the best practices from the five pillars of the Azure Well-Architected Framework to ensure a high-quality, stable, and efficient cloud architecture.
- Cost Optimization: Using Blob Access Tiers and automated lifecycle management automates cost savings by moving data to the cheapest possible tier as it ages.
- Performance Efficiency: Placing frequently accessed files in the Hot Tier and using Azure Files for mapped drives ensures both customers and employees experience fast, low-latency access.
- Reliability: The solution is built on Azure Storage, which has built-in redundancy. We would configure it with Zone-Redundant Storage (ZRS) to protect against datacenter failures and ensure high availability.
- Operational Excellence: Using a single storage account simplifies maintenance and management. Lifecycle management policies automate data tiering and deletion, reducing the operational burden on the IT team.
- Security: Data is protected at every level. All data is automatically encrypted. Access for employees is managed with Microsoft Entra ID and RBAC, while public access is secured with temporary, time-limited Shared Access Signatures (SAS). For network isolation, we will use a private endpoint to ensure the storage account is not exposed to the public internet.