Need to store some files outside your lab VM. There are a few options available to you. Each solution has different requirements and abilities, so let’s go over each solution. The table below lists important points to consider for each solution. The links for each option show how to configure that solution in Azure Lab Services.
|
Option
|
Important to know
|
|
Azure Files share with public endpoint
|
- Everyone has read/write access.
- No vnet peering required.
- Accessible to all VMs, not just lab VMs.
- If using Linux, students will have access to the storage account key.
|
|
Azure Files share with private endpoint
|
- Everyone has read/write access.
- Vnet peering required.
- Accessible only to VMs on same network (or peered network) as storage account.
- If using Linux, students will have access to the Storage Account key.
|
|
Azure Files with identity-base authorization
|
- Either read or read/write access permissions can be set for folder or file.
- Vnet peering required.
- Storage account must be connected to Active Directory.
- Storage Account key not used for students to connect to the file share.
|
|
NetApp Files with NFS volumes
|
- Either read or read/write access can be set for volumes.
- Permissions are set using student VM’s IP address.
- Vnet peering required.
- May need to register to use NetApp Files service.
- Linux only.
|
|
One Drive
|
- Either read or read/write access permissions can be set for folder or file.
- File access is fast because file is on the local drive.
- OneDrive can sync specified folders to the local disk and the cloud.
- One Drive is a syncing technology, so files will take up space on the local drive. If large amounts of data are needed, this may cause storage issues on the VM or syncing issues. See OneDrive limitations for details.
- Windows only.
|
Cost of using external storage is not included in the cost of using Azure Lab Services. For further details regarding pricing see
Please add comments below if you’ve used another external file service with Azure Lab Services. We’d love to hear about it.
Thanks,
Lab Services Team
