Azure Storage
Enterprise File and Object Services
New Brunswick Community College · Moncton, Canada
Project overview
Explore object storage and cloud file shares through Azure Portal and command-line administration, including tiering, transfer tools and access management.
Technical problem
Choose suitable storage access patterns while balancing file-sharing requirements, access control, transfer reliability and storage tiers.
Architecture and objectives
Conceptual illustration of the documented scope, not a recovered topology or proof of connectivity.
- Provision StorageV2 resources with Standard_LRS and examine regional placement.
- Create Blob containers, upload/download objects and work with Hot/Cool access tiers.
- Configure Azure Files and practice SMB share mapping on Windows.
- Use Azure PowerShell storage commands and troubleshoot AzCopy paths and destination-container addressing.
Environment and configuration
| Area | Documented scope |
|---|---|
| Account scope | StorageV2; Standard_LRS |
| Object storage | Containers, blobs, Hot / Cool tiers |
| File services | Azure Files / SMB mapped drives |
| Administration | Azure Portal, PowerShell and AzCopy |
| Access | Storage contexts, role permissions and SAS workflows |
Configuration reference
Design and diagnostic reference; not a verbatim successful execution log.
# Reference commands; credentials intentionally omitted
New-AzStorageAccount
New-AzStorageContainer
Set-AzStorageBlobContent
# Check the local path convention and target container
# before running an authenticated AzCopy transfer.Troubleshooting
Distinguish Windows paths from Linux/WSL paths. Target a specific container rather than the storage-account root. Compare authentication context and network-access rules when a transfer fails.
Security considerations
Keep account keys, connection strings and SAS URLs private. Prefer scoped access with a defined expiry and review least-privilege permissions.
Evidence and verified outcomes
A local Azure Storage submission contains 31 embedded images and written responses. Reviewed evidence confirms historical resource-group creation and an Azure notification reporting a Storage Blob Data Contributor role assignment. The original storage-networking screenshot also shows selected-network access restrictions; it is retained locally because a source address is visible. Blob upload, mapped-drive and AzCopy outcomes remain unverified.
Historical academic work. No current cloud service, production deployment, performance metric or certification is implied.
Skills demonstrated in the documented scope
Screenshot evidence
Original academic lab screenshots. Captions state the visible result and its limits.
Azure confirms the Storage Blob Data Contributor role assignment. This does not verify all effective access paths.
Open full size ↗Source and validation notes
Based on the owner-supplied NBCC technical portfolio history and the bounded local evidence described above. Raw submissions and configuration exports are withheld from public download pending review for credentials, personal information and publication suitability.
View additional technical labs →